Privacy Policy

SuperBooks is an AI-assisted accounting and bookkeeping product operated by 14930398 Canada Inc., a Canadian corporation ("SuperBooks", "we", "us", "our"). We help individuals and businesses connect their financial accounts, organize transactions and documents, and produce clean books, reports, and invoices.

This policy applies to the SuperBooks website (superbooks.io), the web application (app.superbooks.io), the SuperBooks browser extension, and related services (together, the Services). It doesn't cover third-party products we link to or that you choose to connect, which have their own privacy practices.

• —Account information — your name, email address, and a hashed password if you set one. For business accounts we also collect your company name and role. If you sign in with Google or Apple, we receive basic profile details (such as your name and email) from that provider.
• —Financial-account data — when you connect a bank or card account through Plaid, we receive read-only transaction history, balances, account and institution names, and similar details. We do not receive or store your online-banking username or password.
• —Documents you add — receipts, invoices, bills, and statements you upload or forward to your workspace (including through Magic Inbox or a mailbox you connect), and the data we extract from them.
• —Books and content — the categories, rules, notes, reconciliations, invoices, and reports you create in SuperBooks.
• —Billing information — your plan and subscription status. Subscription payments are handled by our billing providers (RevenueCat and Stripe); we receive limited details such as your card brand and its last four digits, never your full card number.
• —Usage and device data — log data, app interactions, approximate location derived from your IP address, device and browser type, and similar diagnostics.
• —Communications — messages you send to support and the preferences you set.

SuperBooks connects to your financial institutions through Plaid, a specialized financial-data provider. The connection is read-only: SuperBooks can see transactions and balances to build your books, but it cannot move money, initiate payments, or make changes to your accounts.

You enter your banking credentials with Plaid, not with SuperBooks, and they are never shared with us. Plaid's handling of the information you provide during a connection is described in Plaid's end-user privacy policy. You can disconnect an account at any time from your settings, which stops further data from being retrieved.

If you connect a third-party source — for example a Google (Gmail) mailbox so we can import receipts and invoices — we access only what's needed to provide that feature, and you can disconnect it at any time from your settings.

SuperBooks offers an optional browser extension. Its only purpose is to send a receipt, invoice, or other document you choose into your SuperBooks inbox. You install it yourself, and nothing reaches your SuperBooks inbox until you connect it to your account.

What it looks at, and when:

• —Only when you act. The extension captures something only when you start it: dragging a region after choosing "Clip this page", using one of its right-click "Send to SuperBooks" items, picking or dropping files in its popup, or pressing "Import this PDF". It does not capture pages on its own.
• —Screenshots are cropped on your device. A region clip takes a picture of the visible tab, crops it to the rectangle you drew, and uploads only that crop. The rest of the screenshot never leaves your browser.
• —Spotting an embedded PDF. When you open the popup, the extension checks the tab you're on for an embedded PDF so it can offer you an import button. It reads only that page's own markup to answer the question and sends nothing anywhere. It does not run on pages where you haven't opened the popup.
• —The address of the tab you're on. While the popup is open, the extension checks whether that tab is itself a PDF so it can offer to import it. It does not build, store, or send a record of the pages you visit.
• —Files you point it at. When you right-click an image or a link, the extension fetches that file from the site it's on and forwards it. If you choose "Clip this page" on a page it can't draw on, such as the browser's built-in PDF viewer, it fetches the file at that tab's address instead. Either way it forwards only images, PDFs, and files whose type the site doesn't declare — a page's HTML, for example, is never uploaded.
• —Sites that need you signed in. If that first request fails, for example because the site only gives the file to signed-in visitors, the extension tries once more with your browser's existing cookies for that site, as your browser would if you opened the file yourself. Those cookies go only to that site. They are never read by the extension or sent to SuperBooks.

What SuperBooks receives and keeps: the file itself (which may contain personal and financial details such as names, addresses, and amounts), its name (the name of the file you picked, or the last part of the web address it came from), its type, and its size. It becomes an item in your team's SuperBooks inbox, where the members of that team can see it, and the file is stored with our storage provider, Backblaze B2. To show you who you're connected as and what you sent recently, the popup also reads your account details, your team, and your ten most recent inbox items from SuperBooks. It holds them in memory only while the popup is open and never writes them to your device. The extension stores two things on your device: its access token and a random install identifier (see the welcome-page paragraph below).

Keeping and deleting what you send: a file sent from the extension stays in your team's inbox until you or a teammate delete it. Deleting an inbox item removes its file from our storage; a record of its name, type, and size may remain until the team is deleted. Closing your account deletes the stored files of any team you are the only member of; files in a team that still has other members stay with that team. To have a file, or everything you have sent through the extension, deleted without doing it yourself, email support@superbooks.io from the address on your account and we will delete it within 30 days. Copies held in backups may remain for a limited time after that.

Where your data goes: two destinations, both declared in the extension's manifest so your browser can show them to you before you install. It calls the SuperBooks app at app.superbooks.io to read your inbox and register a new item, and it uploads the file's bytes directly to our file-storage provider, Backblaze B2. Fetching a file you right-clicked is simply a request to the site already hosting it, and carries nothing about you beyond what your browser would send anyway. The extension itself contains no analytics or tracking service — diagnostic errors are written to your browser's own developer console and are not sent anywhere. The one request that happens before you connect is the welcome page described next, which your browser (not the extension) makes once on first install.

The welcome page on first install. On first install the extension opens a SuperBooks welcome page in a new tab. That page request carries a random install identifier the extension generated, its version number, and the name of the store it was installed from, and nothing from your account or your browsing. The identifier is created once, kept in the extension's local storage on that device, and is used for nothing else. When the page loads we record the install together with that identifier, the version and, if present, the campaign information from our first-touch cookie (the sb_ft cookie, which holds how you first reached SuperBooks, such as a campaign source or referring site); without that cookie, or when that cookie was first set by this welcome page itself, the install is recorded as coming from the extension's store listing. The record is made on our own servers and in our self-hosted PostHog, and if your browser already has a PostHog identifier for SuperBooks and it is ready when the page loads, or you are signed in, the record is attached to that identifier so it joins the rest of your activity there. It does not run again when the extension updates. We do not set up an uninstall page, so nothing is recorded if you remove the extension.

Connecting creates a separate access token for the extension, distinct from your web sign-in. It is issued only from a SuperBooks tab where you are already signed in and have approved the connection, and it cannot be used to issue further tokens. It is stored in your browser's local extension storage on that device only, and is never synced to your other devices. The token acts as you, in the team that was active when you connected, with the same access you have in the web app; the extension itself uses it only to read the details above and to add files to your inbox. It stops working when you disconnect, when it is revoked, or after about a week in which the extension isn't used.

Choosing Disconnect in the popup asks SuperBooks to revoke that token and removes the local copy from your browser. If that request doesn't reach us, the local copy is removed anyway, so the extension stops using it. Either way, disconnecting never signs you out of the web app. If the token stops working, the extension deletes it and asks you to reconnect.

SuperBooks' use and transfer of information received from the browser extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

• —Provide, operate, and maintain the Services — importing transactions, organizing documents, and generating books, reports, and invoices.
• —Categorize and reconcile transactions, including with automated and AI-assisted methods, to save you time.
• —Authenticate you, secure your account, and prevent fraud and abuse.
• —Process subscription payments and manage your plan.
• —Where you enable invoice payments, help you collect payment from your customers through Stripe.
• —Communicate with you about your account, security, and changes, and — where permitted — about product updates.
• —Understand and improve how the Services perform, and develop new features.
• —Comply with legal obligations and enforce our terms.

Some features use AI models to read your transactions and documents — for example to suggest a category, extract fields and text from a receipt or PDF (including optical character recognition), or answer a question about your books. This processing happens to deliver the feature you've asked for.

For the financial assistant, transaction and customer enrichment, and document classification we use Anthropic's Claude models, which we reach through OpenRouter. When you import transactions from a CSV file, we send its column names and first three rows through OpenRouter, asking one of Google's Gemini models to suggest which column is which. If we switch on text extraction from documents, that step uses Google's Gemini models through the Google AI API, or the same OpenRouter route. Where we rely on external AI providers, they act as our service providers under contractual confidentiality and may only process your data to perform the task we request.

We don't sell your personal information, and we don't share it for cross-context behavioural advertising. We share it only in these limited circumstances:

• —Service providers / subprocessors — companies that aggregate financial data, process payments, host our infrastructure, and provide AI processing, acting on our instructions.
• —At your direction — when you ask us to share data, export it, or connect a third-party integration.
• —Legal and safety — when required by law, regulation, or legal process, or to protect the rights, property, or safety of you, us, or others.
• —Business transfers — in connection with a merger, acquisition, financing, or sale of assets, subject to this policy.

We use a small, vetted set of providers to run SuperBooks. We require each to protect your data and to use it only to provide services to us:

• —Plaid — read-only connections to your bank and card accounts.
• —Stripe and RevenueCat — subscription billing, and, where you enable it, collecting payment on the invoices you send (processed through Stripe).
• —Google — Gemini AI for document processing; Google sign-in, and Gmail import if you connect it.
• —OpenRouter and Anthropic — AI models for the financial assistant and for categorizing and enriching your transactions (Anthropic's Claude models, reached through OpenRouter, which may route requests through its own infrastructure providers). OpenRouter also carries the CSV-import column suggestion described above.
• —logo.dev — bank and merchant logos (see the section below).
• —Backblaze — storage for the files you upload, including documents sent from the browser extension.
• —Cloudflare — delivers our websites and the app and protects them from attacks, and measures how quickly pages load (see Cookies and analytics below).

Our product analytics (PostHog) and error monitoring (Sentry) run on our own self-hosted infrastructure, and we send transactional email (such as sign-in links and receipts) from our own email infrastructure — so that data stays on systems we operate rather than a third-party SaaS. We also rely on cloud hosting providers to run our application and database. A current list of subprocessors is available on request at support@superbooks.io.

To show bank and merchant logos, our servers fetch images from logo.dev using only the institution's or merchant's public web domain (for example, chase.com). No information that identifies you is sent, and the request is made by our servers rather than your browser.

We use cookies and similar technologies to keep you signed in, remember your preferences, and secure the Services. For product analytics we use PostHog, which we self-host on our own infrastructure. Our public marketing site may additionally use Google Analytics where it is enabled.

Our websites and the app are delivered through Cloudflare, which also runs Cloudflare Web Analytics on every page: a small script reports the page you visited, the referring page, your browser type and how long the page took to load. It sets no cookies and does not build a profile of you, and we use it only to keep the sites fast and reliable.

Our first-touch cookie. On your first visit we set a first-party cookie named sb_ft, and keep a copy of the same value in your browser's local storage under the same name. It records how you first reached SuperBooks: the date and time of that first visit, the path of the first page you loaded (never its query string), the name of the website that referred you (the site's name only, not the page address), any campaign or ad-click parameters on the link you followed (such as utm_source or gclid), and any referral code or referral-link click identifier (ref or dub_id). When you arrive through an AI assistant's connect or sign-in request, it also records one name from a fixed list identifying which assistant it was (claude, chatgpt, cursor, vscode, windsurf, microsoft_copilot, local_client, or other), never the address the assistant sent you from. Your browser sends this cookie only to superbooks.io addresses, which are delivered through Cloudflare as described in this section, and to no other domain. One of those addresses, status.superbooks.io, is our status page; it is served by Uptimely, a product of our own, so your browser's requests to that page include this cookie too. Our own servers read it when you sign up and store it with your account, and when the welcome page of the browser extension loads (see the browser extension section). We record what it holds in our self-hosted PostHog, including again on your later subscription events (started, renewed and cancelled). When you connect an AI assistant to your account, we also record which assistant it is, from the same fixed list.

You can control cookies through your browser settings, and disabling some may affect functionality. We don't sell your personal information or use it for cross-context behavioural advertising.

To understand how people move through the product and to reproduce bugs, we record replays of a sample of sessions on our website (superbooks.io) and in the app — about one in ten — using our self-hosted PostHog. A replay is a reconstruction of the pages you saw and the actions you took, rebuilt from the structure of the page — it is not a video, and it does not use your screen, camera, or microphone.

Replays are masked in your browser, before anything is sent to us. Visible text content is replaced with placeholder characters, so balances, transaction amounts, customer names, invoice line items, and document titles are never recorded. Everything you type into a form field is masked as well. Some surfaces are excluded from the recording entirely rather than masked: password fields, the Plaid window where you enter banking credentials, the payment window where you enter card details, previews of the documents you upload, the two-factor QR codes shown when you set up an authenticator app or connect a messaging account, and the link to your referral payout portal.

Masking applies to the text a page displays, not to every value behind it. Link and image addresses and other element attributes — for example the address of a page you visited or the label a screen reader would read — are recorded as they are. A replay also contains the layout of the page, the elements you clicked, where you scrolled, and diagnostic messages the app logs to your browser console. Replays are linked to your account so we can investigate a problem you report. We keep them for up to five years and then delete them. Our self-hosted error-monitoring tool (Sentry) also records replays, with the same masking rules: about one in ten sessions, plus any session in which the website or the app hits an error, so we can see what led up to it.

We keep your information for as long as your account is active and as needed to provide the Services. After you close your account we delete or de-identify your data within a reasonable period, except where we must retain certain records to comply with legal, tax, accounting, or audit obligations, resolve disputes, or enforce our agreements. Documents you upload, including those sent from the browser extension, are kept until they are deleted from the team's inbox or the team itself is deleted, and deleted files are removed from our storage. Our operational logs and error reports run on infrastructure we operate; they can include file names and team identifiers, and we keep them only as long as needed to debug and secure the service.

We protect your data with encryption in transit and at rest, access controls, network isolation, and continuous monitoring. Connections to your financial institutions are read-only, and our analytics and error monitoring run on infrastructure we operate. No system is perfectly secure, but we work hard to safeguard your information and to notify you and the authorities of incidents where the law requires.

To report a security concern, email security@superbooks.io.

Depending on where you live, you may have rights over your personal information, including to:

• —Access, correct, or download a copy of your data.
• —Delete your data or close your account.
• —Withdraw consent, or object to or restrict certain processing.
• —Ask us not to share your information, and complain to a privacy regulator.

You can exercise many of these directly in the app — you can export your books and close your account from your settings, as explained on our account deletion page — or by emailing support@superbooks.io. We'll respond as required by applicable law.

As a Canadian company, we handle personal information in line with Canada's Personal Information Protection and Electronic Documents Act (PIPEDA). If you're in Quebec, additional rights under Quebec's Law 25 may apply. You can raise a concern with us first, and you may also complain to the Office of the Privacy Commissioner of Canada or, in Quebec, the Commission d'accès à l'information.

If you're in the United Kingdom or the European Economic Area, we act as the controller of your personal information and rely on legitimate interests, performance of a contract, consent, or legal obligation as the basis for processing, and you may have additional rights under the UK or EU GDPR.

We operate from Canada and may process and store your information in Canada, the United States, and other countries where we or our service providers — such as Plaid, Stripe, and Google — operate. Where we transfer personal data across borders, we use appropriate safeguards as required by applicable law.

The Services are intended for people aged 16 and older and are not directed to children. We don't knowingly collect personal information from anyone under 16; if you believe a child has provided us data, contact us and we'll delete it.

We may update this policy from time to time. When changes are material we'll take reasonable steps to let you know, such as posting a notice or emailing you. The "last updated" date above always reflects the current version.

Questions about this policy or your data? Email us at support@superbooks.io. For security matters, contact security@superbooks.io.