First month free — no card needed. Use code at checkout. Limited to the first 25 companies.
First month free — code . Only 25 spots.
See plans →What we collect, what we do with it, who else touches it, and how to get rid of it. Written to be read, not to be survived.
Effective August 12, 2026 · Last updated August 18, 2026
In one paragraph. The financial files you load into Anchor BI are opened and processed inside your own browser and are never uploaded to us. What we store is the resulting set of figures, in a row only your login can read. We collect your name, email and company so we can run your account and contact you. We use Anthropic's Claude to write commentary on figures we already computed, never on your files. We do not sell your data, and we do not use it to train anything. You can delete your data, and ask us to erase your contact record, at any time.
This policy describes how Anchor Partners LLC, of Charlotte, North Carolina, trading as Anchor BI ("Anchor BI", "we", "us"), handles information in connection with the anchorbi.com website, the Anchor BI Online dashboard application, and our Power BI consulting engagements (together, the "Service").
It applies to you whether you are a visitor, a registered user, or a client. If you are using Anchor BI on behalf of a company, "you" means both you and that company.
When you load a trial balance, general ledger export, aging report, payroll register or T&E card statement into Anchor BI Online, the file is read and parsed by code running in your browser, on your device. There is no upload. We operate no file storage of any kind, no buckets, no attachment tables, no upload endpoint.
Because of this, the sensitive contents of your source files, transaction-level detail, individual invoices, customer and vendor names, are never transmitted to us and never held by us. Our Security page explains the architecture in more detail.
| What | When | Why |
|---|---|---|
| Name, email address, company name | When you create an account or submit the contact form | To create and run your account, and to reply to you |
| Password | At sign-up | To authenticate you. It is hashed by our authentication provider; we never see or store the password itself |
| Company logo, brand colors, plan selection | When you configure your account | To brand your dashboards and exports |
| Notes you type about your business | When you save context on your own numbers | To display alongside your figures, and to inform the AI commentary |
After your browser parses a file, the derived dataset is saved so your dashboard persists between sessions. That dataset consists of:
We do not retain full transaction detail. It is not needed to produce the statements.
If you choose to connect an accounting system such as QuickBooks Online, you authorize that connection through the provider's own consent screen. We then receive report-level data from their API, which we convert into the same derived form described above. We also store the access and refresh tokens for that connection, in a table configured so that no browser-held key can read it.
Our hosting and authentication providers record ordinary operational data: IP address, browser type, timestamps, and authentication events such as sign-ins and password resets. We use it to keep the Service running and secure.
We do not use third-party analytics, advertising or session-recording trackers. There is no Google Analytics, no advertising pixel and no behavioral tracking script anywhere on this site or in the dashboard.
If you subscribe to a paid plan, checkout is handled by Stripe on a page Stripe hosts. You give your card and billing address to Stripe, not to us. Stripe collects a billing address because sales tax depends on where you are.
What comes back to us, and all we store, is the identifier Stripe assigns your customer and subscription, the plan and modules on it, its status, the renewal date, and the number of logins it covers. That record is what unlocks features; it holds no card number, no expiry, and no billing address. Stripe's own handling of your payment details is governed by Stripe's privacy policy.
We do not sell, rent or trade your information. We do not use your data for advertising. We do not use your financial figures, your files or your account information to train artificial intelligence models, and we do not permit our providers to do so.
Anchor BI uses Claude, provided by Anthropic, for two purposes: writing plain-English commentary on your monthly figures, and helping categorize account names our deterministic rules cannot place.
What is sent to Anthropic: for commentary, figures Anchor has already computed, monthly revenue, gross profit and margin, net income, cash, receivables, payables, total assets, the largest month-over-month account movements, and any notes you saved. For account categorization, account names, account numbers and the account types you already confirmed, with no amounts at all.
What is never sent: your source files, transaction-level detail, invoice or customer lists, your credentials, or any connected system's tokens.
The request is made by a server-side function that requires a valid Anchor session, so our API key is never exposed in the browser. Anthropic does not use data submitted through its commercial API to train its models without express permission, and we have given no such permission. Anthropic automatically deletes API inputs and outputs within 30 days of receipt or generation. Limited exceptions apply under Anthropic's own policy, principally content flagged as violating their usage policy, which they may retain longer, and are described in Anthropic's data retention policy. We do not currently hold a zero-data-retention agreement with Anthropic.
The AI explains figures our software computed; it is instructed never to produce new arithmetic. Its commentary is informational and is not professional advice, see our Terms of Service.
We share information only with the service providers we need to operate, and only for that purpose. They are bound by their own agreements with us.
| Provider | Purpose | Information involved |
|---|---|---|
| Supabase | Database, authentication, server-side functions | Account details, derived financial dataset |
| Amazon Web Services | Infrastructure underlying Supabase | The above, stored at rest |
| Cloudflare | Website and application hosting | Request metadata; no financial data |
| Anthropic | AI commentary and account categorization | Computed figures and account names, per section 6 |
| Stripe | Subscription payments, invoices and the billing portal | Your email, card and billing address, held by Stripe; no financial dataset |
| Intuit | QuickBooks Online connection, if you enable it | Report data you authorize |
We may also disclose information if required by law, to enforce our terms, or to protect the rights and safety of our users. If Anchor BI is ever acquired or merged, information may transfer as part of that transaction; we will give notice before your information becomes subject to a different privacy policy.
Your data is stored in the United States, on Supabase infrastructure running on Amazon Web Services in the US West (Oregon) region, us-west-2. Information is encrypted in transit and at rest. If you access the Service from outside the United States, you are sending your information to the United States, where privacy laws differ from those in your country.
We keep your derived dataset and profile for as long as your account is open. Two controls are available, and they do different things:
To be clear about what survives both: the contact record created when you signed up or used the contact form, your name, email and company, is retained as part of our business records. We do not take automatic database backups on our current hosting plan, so once a row is deleted it is not held in any backup we could restore it from.
If you want your contact record erased as well, email [email protected] and we will delete it, ordinarily within 30 days.
Whatever your location, you may ask us to:
Email [email protected] to make a request. We will verify who you are before acting, and respond within 30 days.
Residents of California, and of other states with comprehensive privacy laws, have these rights by statute, including the right not to be discriminated against for exercising them. We do not sell personal information or share it for cross-context behavioral advertising, as those terms are defined under California law.
Our technical measures are described in full on the Security page. In summary: files are parsed client-side and never uploaded; stored rows are isolated per user by database-level row security; the privileged database key exists only server-side; and data is encrypted in transit and at rest.
No system is perfectly secure. If we become aware of a breach affecting your information, we will notify you and any regulator as required by law, without undue delay.
Anchor BI is a business tool and is not directed to anyone under 18. We do not knowingly collect information from children. If you believe a child has given us information, email us and we will delete it.
We will update this policy as the Service changes. The effective date at the top will change with it, and for material changes affecting how we handle your data we will notify registered users by email before the change takes effect.
Questions, requests, or anything that reads wrong to you:
[email protected]
Anchor Partners LLC
Charlotte, North Carolina, USA