Privacy Policy
Last updated: November 10, 2026
Jump to a topic 10 sections
Flatbooks helps bookkeepers and accounting firms consolidate a client’s multiple QuickBooks Online companies — finding the exact intercompany break and, with your approval, posting the correcting entry back to QuickBooks.
This policy explains what we collect, how we use it, and the choices you have.
Information we collect
- Account information your name and email, handled through our authentication provider when you sign up.
- Workspace data the clients (consolidation groups), connected companies, and the account, customer and vendor mappings you create.
- Billing information handled by our payment processor. We never see or store your full card number.
- Diagnostics error reports and basic product analytics, used to keep the service working and improve it.
Your QuickBooks data
When you connect a QuickBooks Online company, you authorize Flatbooks — through Intuit’s API — to access that company’s accounting data: its trial balance, balance sheet, profit & loss, and chart of accounts; its company details (its legal name and accounting settings, such as when its fiscal year starts); the names of its customers and vendors, to find the other connected companies among them, and, for a customer or vendor that is one, its open balance and its sales or purchases by account; its journal entries, to find and check the corrections Flatbooks posts and undoes; and, when you compare two companies’ ledgers, the general ledger entries in their intercompany accounts (for a connected company kept as a customer or vendor, its entries in receivables or payables), including each entry’s name and memo. We use this only to build the consolidation, detect intercompany breaks, and produce the export. Our product analytics hears only how those checks came out (whether a consolidation tied out, and how many breaks it found), never an amount, an account, or a company’s name.
The one-click fix writes a single correcting journal entry back to a company — and only after you have reviewed and approved the exact entry. You can undo a posted fix. We request the minimum scope needed (accounting only). We store the OAuth tokens Intuit issues — encrypted at rest never your QuickBooks username or password.
How we use it
To provide the service (consolidate, detect, fix, export), process billing, provide support, and keep the service secure and reliable. We do not sell your data or your clients’ data, and we do not use it for advertising.
Storage & security
QuickBooks tokens are encrypted at rest (AES-256-GCM). Data is transmitted over HTTPS. Connection and financial data is accessible only by our server, never exposed to the browser.
Cookies
We use first-party cookies for sign-in, connecting QuickBooks, preferences and, only after your permission, optional website analytics. We use no advertising or cross-site tracking cookies and no device fingerprinting.
- Signing you in a session cookie set by our authentication provider so you stay signed in. Strictly necessary.
- Connecting QuickBooks four short-lived cookies (about ten minutes) that carry a one-time security token, remember which client you were connecting, and — when you use Reconnect — which company that button meant, so the connection can’t be forged, misrouted, or quietly swapped for a different company. They also remember the report month to return you to after connecting. They’re removed as soon as the connection finishes.
- Remembering your reporting month the month you last selected, kept for 45 days, so returning mid-close doesn’t reset your practice to the current calendar month. A preference, nothing more.
- Your analytics choice a signed first-party preference cookie remembers Accept or Reject for up to six months. Browser storage also remembers a rejection and any pending withdrawal retry, so a network failure cannot silently turn analytics back on. This preference contains no visitor identifier.
- Optional browser reference after Accept, a separate signed first-party cookie connects this browser’s visits for up to 30 days. A reference is pseudonymous, not a guarantee of anonymity. It is not used across websites or to recognize you on other devices. A change of signed-in account starts a new reference.
Optional analytics are off until you accept. Rejecting does not prevent signup or use of Flatbooks. Open the Privacy settings control on any page to accept, reject or withdraw. We also keep optional analytics off when your browser sends Global Privacy Control or Do Not Track. With permission, we count public-page visits with Vercel Web Analytics, which sets no cookies. Each Vercel page view isn’t tied to you or your IP address; the provider does not receive our optional browser reference. These aggregate counts include the page, referring site, approximate location, and device and browser type. Its visitor-count hash is discarded after 24 hours. For these page counts, links are recorded without their personal parts: only campaign tags and referral codes are kept.
When you create a workspace, we keep the campaign tag of the link you first followed to Flatbooks (for example, utm_source=linkedin), or the name of the website that sent you, so we know which channels bring bookkeepers to us. The campaign tag travels in the links themselves rather than an attribution cookie. It’s kept with your account and workspace, included in your record export, and deleted with your account.
With analytics permission, we record which signup steps complete, how long requests take, and technical error codes in Flatbooks. A random reference connects those steps within this browser tab for up to 30 minutes and is removed when workspace setup opens. A signup reference from our authentication provider may connect the diagnostic to its records. These diagnostics exclude the names, email addresses, verification codes, and invitation tokens entered in the form. We do not duplicate these optional step-by-step histories in our error-monitoring provider. Basic technical fault reports remain separate operational diagnostics, without an optional visitor or signup-attempt history. Reporting availability does not affect signup.
With analytics permission, the private operator activity view records page visits, navigation and button actions, scroll positions, walkthrough playback and video positions, sample interactions, download requests and signup milestones. It records named actions, not page text, typed form values, passwords, verification codes, financial amounts, accounting contents, raw URLs or invitation/OAuth tokens. No screen recordings are made. When you sign in, this browser’s consented history can be connected to your account and workspace; the view displays the existing account profile. Withdrawing removes the optional history linked to this browser from Flatbooks and stops new optional collection. A failed removal is reported so you can retry.
Server records of product requests, such as workspace setup, QuickBooks connections, corrections and workbook preparation, remain operational account records used to provide support and explain request outcomes. They do not depend on optional browser analytics. Activity and consent records linked to your workspace are included in its record export and removed with account deletion. A daily cleanup removes activity and browser-reference records older than 30 days. Missing observations do not establish what happened next; a video position does not prove it was watched, and a download request does not prove a file was opened.
Service providers
We rely on a small set of providers, each processing data only to perform their function:
- Intuit (QuickBooks Online) the source of the accounting data you connect.
- Authentication, payments, database, hosting, and error monitoring providers to sign you in, bill you, store your workspace data, run the app, count visits to our public pages, and detect faults.
- Email delivery (Resend) to send the waitlist confirmation, and to tell our team when someone joins the waitlist or creates a workspace. It receives the email address and, with those notices, the number of multi-entity clients and the note given on the waitlist form, or the campaign tag or referring site a new workspace came from.
- Product analytics (PostHog) to count, from our server, how the app is used. It receives an event each time a client’s books are consolidated afresh, keyed to your workspace and client ids, that says how the checks came out and never an amount, an account, or a company’s name; and a count of waitlist submissions that identifies no one.
Your choices
- Disconnect any time disconnecting a company removes the connection and revokes Flatbooks’ access at Intuit. QuickBooks gives Flatbooks one grant per company, so if another Flatbooks workspace still has that company connected, we delete your copy and the grant stays with that workspace until it disconnects too.
- Delete your account delete it yourself any time from Account settings; this disconnects your companies as above and permanently removes your data, except the billing records our payment processor, Stripe, keeps as the law requires. We also retain the deletion-prevention reference described below. You can also email us.
- Access & correction email us to access or correct your information.
- On the waitlist but not a customer you have no account to delete; email founder@flatbooks.io and we’ll take your address off the list. The confirmation email carries the same link.
Data retention
We retain your workspace and connection data while your account is active. When you disconnect a company we remove the connection and its token, and revoke the token at Intuit unless another Flatbooks workspace still has that company connected; when you delete your account we delete your data. Your billing and payment records (your email address, invoices and payments) are kept by our payment processor, Stripe, as the law requires.
After account deletion, Flatbooks keeps a one-way hash of the account reference indefinitely, solely to prevent delayed requests from recreating deleted activity. This deletion-prevention record contains no name, email, original account reference, workspace details or activity history, and is not used for analytics.
Changes
We may update this policy; we’ll revise the date above when we do.
Contact
Questions about privacy: founder@flatbooks.io. See also our Terms of Service.