Security

How we handle your finance data

A plain account of the controls in place today and what is still planned. If something you need is not here, ask us before you connect anything.

In place

Controls built into the platform

Data isolated per organization

Every row of finance data carries your organization’s ID, and Postgres row-level security policies restrict each query to the organization it belongs to.

Append-only audit log

Suggestions, edits, approvals and exception decisions are written to an audit log that the database itself refuses to update or delete.

Encrypted connector credentials

API keys and tokens for Stripe, your ledger and other connectors are encrypted at rest with AES-256-GCM before they are stored, and decrypted only when a sync runs.

People approve ledger changes

Agents can draft journals and propose matches. Anything that writes to your ledger requires a person to approve it under the policy you set.

Role-based access

Team members see and do what their role allows. Approval policies set who can approve what.

Compliance status

SOC 2 Type I is planned for 2027

We do not have a SOC 2 report today. We are building toward a SOC 2 Type I audit, planned for 2027, and we will say so here when the report is in hand.

Until then, we are happy to walk through how the controls above work and answer a security questionnaire as accurately as we can.

What we do not claim
  • No SOC 2, ISO 27001 or other certification yet.
  • No third-party penetration test report to share yet.
  • Direct writes to QuickBooks and Xero are not available yet; they arrive with those connectors, behind approval.
Questions

Security questions or a concern to report

Email madhuri@billverge.com. If you think you have found a vulnerability, please include steps to reproduce and do not access other customers’ data.

Walk through the controls with us

Book a demo and bring your security questions. We will show how isolation, approvals and the audit log work on example data.