Privacy
Last updated: November 5, 2026
The connector
Your ledger stays in QuickBooks. What Caribooks stores depends on the features you use. The connector reads QuickBooks when you ask Claude, ChatGPT or Microsoft Copilot a question and passes the results to your assistant. Caribooks does not keep a synchronized copy of your ledger. We keep the account and connection details needed to provide the service, usage records, and any bookkeeping rules or task instructions you save. Your assistant handles the responses under its own privacy policy and your settings.
What we keep
Your account email, QuickBooks access tokens (AES-256 encrypted), connected company details, billing information and usage records. We also retain bookkeeping rules and task instructions you save through the connector. When you use document sorting across several companies, we cache company names, addresses and tax identifiers from QuickBooks to help identify the recipient. If you sign in with Google or Microsoft, that provider sends us your name, your email address and, if you have one, your profile photo.
Autopilot and in-app conversations
Autopilot stores your task instructions, in-app conversations, run history and proposals so you can review its work. This history can include QuickBooks data. For supported changes, we also keep the records needed to undo them. The models processing this information are described below. In-app conversations and run history remain available for review; archiving a conversation hides it from the list without deleting its messages. Contact support@caribooks.com to request deletion.
The optional document box
If you upload documents or email them to Caribooks, we store the files, extracted text and document details to sort them, find them and attach them to QuickBooks. The document box can be used with the connector or Autopilot. Receipt files are removed from our storage once attached to QuickBooks. A copy of a document QuickBooks already has is removed after 30 days. Every other file stays until you delete it. We clear the document box’s extracted text when a receipt is filed or a document is deleted. Details read from a document, such as its total and its lines, stay until you delete it. Document history remains. Text already included in conversations or Autopilot history can remain.
Expense claims
When a client company reimburses your expenses through Caribooks, we keep your name, your email and the receipts you send, for that company only.
Receipts asked of a client
When the person who keeps your books asks you for missing receipts through Caribooks, we keep your email, the language of your emails, the date and receipt count of the last email and, if you stop these reminders, the day you did, for that company only. The email lists the date, vendor and amount of each expense missing a receipt; Resend sends it. What you drop goes to the company’s document box. This is deleted with the company’s data, 29 days after the company is disconnected.
Where your data is hosted
The database and files are hosted on Supabase in the AWS Montréal region (ca-central-1); the application runs on Vercel in Montréal (yul1). Vercel Workflow, which runs Autopilot from Virginia (iad1), receives only identifiers and counts. The conversation with the model, with the QuickBooks data it reads, stays in the Supabase database, where it is kept after the run for debugging and deleted with the company’s data, 29 days after the company is disconnected. Runs from before this update keep theirs at Vercel until it expires, at most 96 days after the run. Vendor portal sessions are hosted in the United States by Browserbase. AI requests and the other services described on this page may also process information outside Canada.
The live demo
Questions typed in the live demo (caribooks.com/en/try) are sent to Anthropic’s Claude Haiku, through OpenRouter, to answer them from a fictional QuickBooks company. Do not type personal information in it. Caribooks keeps neither the questions nor the answers. It keeps the demo’s monthly cost and, to limit questions per hour, a fingerprint of your IP address (a hash with a secret key, never the address itself), deleted after 24 hours. What the demo creates or changes in the fictional company is undone every hour.
Your AI assistant and the models
When you query your books through Claude, ChatGPT or Microsoft Copilot, that provider processes your questions and the data that answers them under its policy and your settings. Routines and vendor-portal setup use GLM 5.3 Flash, an open model, through OpenRouter. OpenRouter runs it for us on Together AI, DigitalOcean, Modal or Parasail and nowhere else, with requests sent under a no-retention, no-training setting. The model receives the transactions and documents being examined, your rules and your instructions. Training and retention terms depend on the provider and service settings; they can differ from the document sorting described below. Caribooks does not sell your data or use it to train its own models.
Document sorting
AI sorting is used when rules and recipient details cannot settle which company a document belongs to. With one connected company, documents are assigned to it without a model call. With several companies, documents with an uncertain recipient wait for your choice on the Documents page. When needed, AI sorting sends the filename, sender, email subject, up to 12,000 characters of text, and the candidate companies' names, addresses and tax numbers. This text can contain personal or banking information; it is not automatically anonymized. Competing models are tested with fictional documents. The sorter uses GLM 5.3 Flash through OpenRouter, hosted by Together AI, DigitalOcean, Modal or Parasail. Every sorting request requires a zero-data-retention endpoint, disallows data collection and prohibits any host other than these four. These requirements apply to the four hosts; OpenRouter applies its own policy and account settings. They do not guarantee processing in Canada.
Document reading
Each document in the document box is read once by an AI model so you and your assistant can find it: the vendor, date, number, total, taxes, due date, last four digits of the card, recipient, a short summary and the lines bought. The model receives the filename and up to 40,000 characters of the document's text, or a picture of a photo or of a scanned PDF's first page. For a short PDF, such as a one-page invoice, it also receives a picture of its first page, to read a vendor's name that only appears in a logo. For every document, it also receives the names of your connected companies, so it never takes one of them for the vendor. This text can contain personal or banking information; it is not automatically anonymized. Reading uses GLM 5.3 Flash through OpenRouter, hosted by Together AI, DigitalOcean, Modal or Parasail, with the same requirements as sorting: a zero-data-retention endpoint, no data collection and no host other than these four. They do not guarantee processing in Canada.
Optional vendor portals
If you connect a vendor portal to collect invoices, Browserbase hosts the browser in the United States and retains its sign-in session so it can be reused. Browser session recording and logging are disabled. To find and collect the invoices, the buttons and links of the vendor's pages, screenshots of those pages and the invoice text are sent to a model through OpenRouter. A screenshot shows what the page shows, which can include your name, address, account number and amounts; Caribooks does not keep it. For the last attempt, Caribooks keeps the labels of the buttons and links offered and clicked, and how each step ended, so a failure can be explained; it keeps no address, page text or screenshot, and the next attempt replaces this record. Removing that vendor connection deletes its saved browser context; invoices already collected remain in your document box.
Your mailbox, if you connect it
If you, or someone on your team, connect a Gmail or Outlook mailbox on the Vendors page, Caribooks reads it with read-only access, and only for the vendors paid in the last year by the Autopilot companies that mailbox serves. For each of them, Caribooks first learns how its invoices arrive: it looks for the vendor's name, or a close variant, in the sender and subject of messages, and GLM 5.3 Flash, through OpenRouter on Together AI, DigitalOcean, Modal or Parasail with no retention and no training, reads the sender, subject, a short preview, the invoice and the links of a few of those messages to compare the amount and date with the vendor's expenses in QuickBooks, or to spot the portal where the vendor posts its invoices. Once it knows the sender (or the one you name), it reads only that sender's messages: the past year's invoices that match an expense still missing its document, then each new one. A kept invoice is filed in the document box (its attachment, or the email itself as a PDF) and read like any other document; the other messages it looks at are not kept. Caribooks never sends mail from your account. The access token is stored AES-256 encrypted. You can disconnect the mailbox on the Vendors page at any time: Caribooks then deletes the token and, for Gmail, gives Google its consent back. This data is not used for advertising, not sold, and not used to train AI models. Caribooks' use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Your bank accounts, if you connect them
If you connect a bank on the Banks page, you sign in to it in Plaid’s window: Caribooks never sees your bank username or password. Plaid, a US company, gives Caribooks an access token, stored AES-256 encrypted, and each account’s name, type, currency and last four digits. Caribooks also keeps each account’s balance with the time it was read: Plaid’s last reading, taken when your bank feed is updated, or the bank’s own answer when you choose Refresh balances on Manage banks. Caribooks reads the account’s transactions from Plaid to find the ones QuickBooks does not have yet, starting 30 days before you connected or at the start date you choose. It keeps those as your bank feed: the date, description, merchant, amount and category of each, the entry Caribooks suggests and what you decided. Suggestions come from Caribooks’ own code. To name a merchant it has not seen before, Caribooks sends an AI model only the words the bank printed for it on a purchase (for example “PREMIERE MOISSO”). It never sends the amount, the date, the account or a transfer to a person. The model is GLM 5.3 Flash, reached through OpenRouter and hosted by Together AI, DigitalOcean, Modal or Parasail, with no data retention and no training. Caribooks keeps the name for your account; a name you type when adding a transaction replaces it. The names are deleted when you disconnect your last bank. When you ask your AI assistant about your bank accounts, the transactions it needs to answer go to that assistant, as QuickBooks data does. A transaction that turns up in QuickBooks leaves the feed; the others stay while the bank is connected. To tell when the feed needs updating without reading your whole books each time, Caribooks keeps the company’s vendor names, accounts, tax codes and closing date as QuickBooks last gave them, and deletes them with the company’s data, 29 days after you disconnect it. When you disconnect a bank on the Banks page, Caribooks deletes its access token, its accounts and its whole feed, and asks Plaid to remove the connection. Deleting your Caribooks account disconnects every bank the same way. If no company in your account is on Autopilot for 30 days, Caribooks disconnects your banks the same way, after an email 7 days before. A transaction you added to QuickBooks stays there. Plaid handles your bank sign-in under its own privacy policy.
Your Stripe account, if you connect it
If you connect Stripe on the Payouts page, you approve Caribooks’ app on Stripe’s own page: Caribooks never sees your Stripe password. Stripe gives Caribooks read-only access, as tokens stored AES-256 encrypted. Caribooks reads your Stripe balance and activity from the first day you choose: each sale with its customer’s name and email, the invoice’s products and taxes, Stripe’s fees, refunds, disputes and payouts. It keeps each of those with what it booked in QuickBooks, so nothing is booked twice. Caribooks’ own code does the booking; no AI model reads your Stripe data. When you set it up with your AI assistant, what Caribooks prepared (your products, tax rates, sales volume and your customers’ names) goes to that assistant, as QuickBooks data does. When you disconnect Stripe on the Payouts page, Caribooks first removes its app from your Stripe account, unless another Caribooks connection still uses that Stripe account, then deletes its tokens and every Stripe record it kept; if Stripe refuses to remove the app, Stripe stays connected and the page gives you a reference to send to support. What Caribooks booked stays in QuickBooks. You can also remove the app from your Stripe dashboard. Deleting your Caribooks account disconnects Stripe the same way.
Cookies and visit analytics
The only tracking cookies the site sets are those that measure our ChatGPT ads, described below. On the public pages, and never in the portal, PostHog records how visitors move through the site: clicks, scrolling and a recording of the visit with form fields hidden. PostHog keeps a visit identifier in your browser tab. It is gone when you close the tab, so one visit cannot be linked to the next. This data is hosted in the United States and recordings are kept for up to 30 days. PostHog does not keep your IP address, and we have opted out of PostHog using this data to train its models. When you create an account, we attach to it the first page of your visit, the site that sent you there, the link’s campaign tags (UTM) and that visit identifier; until then, these stay in your browser tab. That identifier also lets us see, alongside your account, which pages you viewed during the visit you signed up from. PostHog then receives, under that identifier, the account’s first steps: first sign-in, first company connected, first assistant connected, first request and first subscription. It receives no name, email address, company name or QuickBooks data. Fathom counts visits without cookies. If you open any page of the site with ?analytics=off at the end of its address, neither PostHog nor Fathom counts your visits any more, and your browser remembers that choice until you open a page with ?analytics=on. We advertise in ChatGPT. On the public pages, except the sign-in page, OpenAI’s measurement pixel tells OpenAI when it loads and keeps two first-party cookies: the identifier of the ChatGPT ad you clicked, for 30 days, and a random browser reference, for up to a year. If you create an account after clicking one of our ads, we attach both to the account and tell OpenAI, under that identifier, when the account is created, when its first company is connected and when it first subscribes. OpenAI receives no name, email address, company name or QuickBooks data, and learns nothing about accounts that did not come from an ad. ?analytics=off turns this pixel off too. Anything else your browser keeps is there to sign you in to the portal.
Booking a demo
If you book a demo, we keep your name, your email, your note, your time zone and the time you chose, so your link can move or cancel it. A free onboarding session is booked the same way from your account: we also link it to that account, with the page or email you booked it from, and it is deleted with the account. The demo or session is an event on Xavier Peich's Google calendar: Google receives your name and email and sends you the invitation. Cloudflare Turnstile checks that a person filled in the form. If our outreach partner contacted you on LinkedIn on our behalf, the messages go through Conneqter, and the call you book is handled in HighLevel, which sends its confirmation and reminders and puts it on the same Google calendar. Both services receive your name and what you share with us in the conversation or the booking form, such as your email and company. To delete a booking, write to support@caribooks.com.
Access and deletion
You can disconnect a QuickBooks company from the portal: Caribooks then revokes its QuickBooks access and deletes its tokens at once. If you revoke Caribooks’ access from your Intuit account instead, Caribooks notices within a day. Either way, nothing reaches the company any more, and what Caribooks keeps for it stays 29 days, so that reconnecting the same company to your account brings it back. On day 29 Caribooks deletes it all: its routines and their run history, its changes in Approvals, its rules, its vendor settings and vendor portals with their saved sign-ins, its expense claims, its client’s email and the expenses not to ask them for, its bank feed with the vendors, accounts and tax codes kept for it and the link from your bank accounts to its books, its documents with their files, and its own receiving address and drop link. Before that, Caribooks removes its app from any Stripe account connected to the company, unless another Caribooks connection still uses that Stripe account. The account owner is emailed when the company is disconnected and seven days before the deletion. The account owner can also ask, in the portal, for it all to be deleted at once instead of on day 29. Nothing changes in QuickBooks. When your access to Caribooks ends (a cancelled plan, or a trial that ends without one), everything stays 90 days; the account owner is emailed 30 days and 7 days before, and on day 90 Caribooks disconnects every company, bank and mailbox and deletes what it keeps. To request access to, correction of or deletion of your personal information, or deletion of your Caribooks account, contact support@caribooks.com. We will explain the scope of the deletion and any records that must be retained.
Provider privacy policies
Which providers receive your information depends on the features you use. Resend processes emails and their attachments; Sentry receives diagnostics and service usage logs. The policies below explain each provider’s practices.
- SupabaseDatabase, files and authentication
- VercelApplication hosting and workflow state
- StripeBilling, and your Stripe activity when you connect Stripe on the Payouts page
- ResendAccount emails, emails to your clients and incoming documents
- SentryError diagnostics and service logs
- OpenRouterModel requests
- Together AIOpen model host: routines, document sorting and reading, vendor portals, merchant names on bank transactions
- DigitalOceanOpen model host: routines, document sorting and reading, vendor portals, merchant names on bank transactions
- ModalOpen model host: routines, document sorting and reading, vendor portals, merchant names on bank transactions
- ParasailOpen model host: routines, document sorting and reading, vendor portals, merchant names on bank transactions
- PlaidBank connections, when you connect a bank
- BrowserbaseOptional vendor portal sessions
- OpenAIChatGPT and OpenAI models, and measurement of our ChatGPT ads
- AnthropicClaude and Anthropic models
- MicrosoftSign-in with Microsoft, and Microsoft Copilot and Outlook when you connect them
- GoogleSign-in with Google, Gmail when you connect it, and the calendar invitation for a demo or onboarding session you book
- CloudflareBot check on the sign-in, demo and onboarding booking, and live demo pages (Turnstile)
- FathomCookieless audience analytics
- PostHogVisit recordings and heatmaps of the public site, and the sign-up funnel
- HighLevelBooking, confirmations and reminders for calls our outreach partner arranges
- ConneqterLinkedIn messages our outreach partner sends from Xavier Peich’s profile
The ones that process customer data on Caribooks’ behalf are listed in the Data Processing Addendum.
Caribooks · Peich Technologies Inc., Montréal