Skip to content
Ledgerbelt

Security

How Ledgerbelt protects client data

A leak of client books would end this product, so every change is held to the rules below. This page describes how Ledgerbelt is designed.

An archive corridor lined with bound ledgers and a lit reading desk

What we store, and what we do not

Tools read the ledger live from QuickBooks Online, Xero or Sage and work in memory. Accounting data is not written to our database, logs, analytics or error reports.

We store the account of each person who signs in, the firm they belong to, the list of connected client companies, the encrypted access tokens for those connections, and the audit log. If a tool ever needs to keep something, we document what, why and for how long before it ships.

Access tokens

Access tokens from the providers are encrypted at rest with AES-256-GCM. Each token gets a fresh random value for every encryption, and it is bound to the firm and connection it belongs to, so a stored value cannot be copied to a different record and still work.

Encryption keys are kept in the server environment, not in the database, and the key set supports rotation without downtime. Plaintext tokens stay inside the server process and are never written to logs.

Connecting a client company

Connections use the provider's OAuth flow. Each attempt carries a single-use, expiring state value tied to your firm and your user, and it is checked before anything is exchanged. Redirect addresses are matched exactly.

We ask for the least access a connection needs, and read-only access where the provider offers it. Approval happens at the provider, not in Ledgerbelt.

Isolation between firms

Every firm is a separate tenant. Each database query is scoped to the signed-in firm, and the database enforces the same rule with row-level security. The application role does not own the tables and cannot bypass the policy.

The firm and user are always taken from your session, never from anything in the request.

Sign-in and sessions

Ledgerbelt has no passwords. You sign in with a single-use link sent to your email, and it expires quickly. Sessions are stored on the server so they can be revoked. They end after a short idle period and after an absolute limit.

Session cookies are marked HttpOnly and Secure, are restricted to our own host, and are not sent on cross-site requests that could be abused.

Disconnecting and deleting

A firm owner can disconnect any client company with one click. Ledgerbelt revokes access at the provider first, then deletes the stored tokens. A firm owner can also delete the whole firm, which removes its tokens at once.

Both actions are written to the audit log.

Audit log

Ledgerbelt records sign-ins, connections, disconnections, tool runs and exports: who did it, for which firm and connection, and when. The log is append-only. It never contains accounting data or tokens.

Protection in the browser

The site is served over HTTPS with strict transport security. A strict content security policy limits which scripts can run, pages cannot be embedded in other sites, and the browser is told not to guess content types or share more than it needs when following links. No third-party scripts run in the signed-in product.

Every action is checked

Each action that changes data re-checks who is calling, confirms their role, validates the input and verifies where the request came from. Sign-in, connect and tool runs are rate limited. Errors and logs are sanitised so provider messages cannot leak tokens or secrets.

How we build

We keep the dependency list short, pin exact versions, and scan for known vulnerabilities, leaked secrets and code issues on every change.

Ready to connect your first client company?

Get early access