Security

Your ledger stays in QuickBooks

The connector reads QuickBooks when your assistant asks and passes the answer along; Caribooks keeps no synchronized copy of your books. Its database and files are hosted in Canada, in the AWS region ca-central-1. Some services process information outside Canada, among them vendor portal sessions and the AI model hosts. The privacy policy, linked at the bottom of this page, lists everything Caribooks keeps, where, for how long and how to have it deleted.

A token, never your password

Connecting a company goes through the standard Intuit authorization (OAuth). Intuit hands us a token that only opens your books; we never see your QuickBooks password. You can revoke that token at any time, from the Caribooks portal or directly with Intuit, and access dies immediately.

You approve every change

A connected company starts with full access: the assistant can read your books and change them. In Claude and ChatGPT, it asks you before each change, and a delete or a void needs your explicit confirmation of that specific record. Before an email goes to a customer, the assistant shows you what would be sent and to which address, and waits for your yes. The account owner can switch any company to read-only at any time, under Settings → Companies. On a team, each person also has their own level for each company: Read or Write.

A routine starts by asking

A new routine proposes and waits: nothing moves in your books without your approval. You then decide, routine by routine, whether it asks first or just does it, and Just do it only frees the safe changes, such as attaching a receipt. Deleting, voiding and sending a document always require your confirmation, whatever the setting. Every applied change can be undone, and you can switch any routine off.

Passwordless sign-in

Your Caribooks account opens with a link or a code sent to your email, or with your Google or Microsoft account. It has no Caribooks password, so there's no password to steal. Anyone can add a second step, a code from an authenticator app, under Settings, Security. Bank access requires it: each person on an account with a connected bank sets it up, and connecting a first bank asks for it.

Encryption and isolation

Every connection uses TLS 1.2 or higher. The database, files and backups are encrypted at rest (AES-256), and the access tokens for QuickBooks, banks, Stripe and mailboxes are encrypted again in the application (AES-256-GCM), with the key kept outside the code. Each account's data is walled off by row-level security, and the database is closed to the browser: only our server code reaches it.

Who can reach your data

Two people: the CEO and one developer. Every account they use to reach production systems or customer data is protected by multi-factor authentication.

If something goes wrong

If a breach affects your information, the account owner hears from us by email within 72 hours of our becoming aware of it: what happened, what it touched and what we are doing about it. The Data Processing Addendum sets this out, along with every subprocessor, what it does and where, and 15 days' notice before we add one.

AI models: no retention, no training

Claude, ChatGPT or Microsoft Copilot receives your questions and the QuickBooks data that answers them, and handles them under its own policy and your settings with it. On a personal Claude or ChatGPT plan, the provider can train on your conversations, which quote your books, unless you turn that off; the help center shows how. The work Caribooks itself gives a model (reading each document, sorting documents between your companies, routines, naming the merchants on your bank transactions) runs on GLM 5.3 Flash, an open model, reached through OpenRouter on Together AI, DigitalOcean, Modal or Parasail and no other host, with no data retention and no training. Caribooks does not sell your data or train any model with it.

What Caribooks cannot do

Intuit's API does not open everything, and we won't pretend otherwise. A routine cannot see the bank feed's For review queue, cannot reconcile an account, cannot move money and cannot read payroll. What it touches is the entries and the documents inside QuickBooks.

What we don't have

No SOC 2 audit yet: we're a small team and we won't claim certifications we don't hold. The day we earn one, it will be listed here. To report a vulnerability or ask anything: support@caribooks.com, and we answer fast.

→ Full privacy policy

→ Data Processing Addendum