Security

Per-client isolation

Every client's books live in a separate organization with its own access control — there is no shared pool of transactions that a filter carves up. Each business you manage is its own org, with its own double-entry ledger, its own documents, and its own membership list.

Access is granted per business. Someone with access to one client's books sees nothing of another client's unless they are explicitly added to that organization too. If you run books for multiple clients, each stays in its own walled-off set.

Your data stays yours

Your documents are used to keep your books — that is the whole job. The bills, receipts, and invoices you upload are read by OCR and an LLM to extract vendor, totals, tax, dates, and line items, and every extracted field links back to its highlighted location on your original document so you can verify where each value came from.

Because each business is isolated in its own organization, your documents and transactions are processed in the context of your books, not mixed into anyone else's.

We are an early-stage product, and we will not pad this page with claims we have not earned. We do not currently hold certifications like SOC 2, and we will not list badges we do not have. What we can describe honestly is the architecture: isolated organizations, a real double-entry ledger, and an audit trail that cannot be edited after the fact.

Every change is recorded

Every action on your books lands in an append-only audit trail — entries are added, never edited or deleted. When a transaction or extracted document falls below the AI's confidence threshold, it routes to a human review queue, and each approve or reject decision is recorded with a memo explaining why.

That means you can always answer the question 'who changed this, when, and why' — for AI categorizations and human decisions alike. High-confidence items that never needed a human touch are traceable too: every transaction carries its confidence score, and every extracted field links to the exact spot on the source document it came from.

Access control

Sign-in is via email/password or Google, handled through Clerk. Access to books is governed by role-based organization membership: what you can see and do depends on your role within each specific business.

There are no all-access accounts spanning every client by default. Membership is per organization, so adding a bookkeeper, an owner, or a reviewer to one business grants access to that business only.

Questions welcome

If you have a security question this page does not answer, email hello@aibookkeeper.com and we will give you a straight answer — including 'we don't have that yet' when that is the truth.

We are early-stage: pricing will be published at launch, no sales calls required, and QuickBooks Online sync is in development. As the product matures, this page will grow with it — and it will only ever describe what actually exists.