Data & Compliance

Last updated: October 9, 2026

LedgerBeaver handles your financial records — invoices, bank details, ledgers, and the transactions that run your business. This page is a plain-English summary of how we treat that data and how we honor the privacy laws that apply to you. It complements our Privacy Policy and Terms of Service; where the full policy governs, we link to it.

• Principles
• Your rights
• US state privacy laws
• Making a request
• Security & residency
• Financial-data safeguards
• Sub-processors
• Breach notification
• Contact

1. Our data principles

Three commitments sit underneath everything below. They are also written into our Privacy Policy and Terms so they are contractually binding, not just marketing:

• We never sell your data. Not to advertisers, data brokers, or anyone else — under any definition of "sale," including the broad definitions in California and other state laws.
• We never train AI models on your financial data. Your books are used to run your books. When you connect your own AI agent, it operates under tokens you control and scopes you set.
• You retain your rights in Customer Data. As between you and LedgerBeaver, you retain the rights you have; we claim no ownership. Other individuals' privacy rights and third parties' rights remain intact. You can export eligible data and delete your account, subject to the retention rules described below.

Your connected AI and our commitments. Our no-training commitment covers LedgerBeaver's use of Customer Data. Agents and model services you independently select may receive information through an authorized connection and handle it under their applicable terms and settings, including model training where those terms and settings allow. Some business and API services exclude training by default; cloud processing does not automatically mean training.

Local inference can avoid sending your connected agent's model inputs to a cloud provider only when the agent and related components do not transmit content there. It does not control separate in-app provider features. LedgerBeaver still hosts your workspace. Eligible Pro and Max workspaces can separately enable TypeSafe Jev suggestions for AP invoice exceptions, employee-expense accounts, PO evidence, possible vendor-name matches, and selected CRM note follow-up. Each purpose has separate consent. PO requests use bounded status and line descriptions; vendor requests use bounded names and available country codes. CRM requests use a limited, filtered excerpt and allowed follow-up categories after explicit confirmation of the exact preview. Review the excerpt: filtering cannot guarantee removal of every confidential or personal detail. These three guidance features do not create receipts, merge records, send messages, approve spending, or move money. Each suggestion requires an explicit request from an authorized person or, for AP exceptions, an authorized connected agent. Expense requests use minimized expense and allowed-account facts; a person must apply the account, and approval remains a separate revision-bound decision. TypeSafe states that Jev customer requests and responses are not used to train its models, while processing and retention still follow the applicable agreement and terms. Other TypeSafe assessment tasks, general product-help model requests, and cloud document transcription remain disabled; verified summaries and documentation help do not send content to a model provider. Cloud or local inference does not change your existing rights in Customer Data or other individuals' privacy rights. Providers engaged by LedgerBeaver remain covered by our applicable data-protection obligations. See AI & Data Privacy and the Privacy Policy for details.

2. Your privacy rights

Regardless of where you live, LedgerBeaver extends the following core rights to every account holder. In some states these are legal obligations; we choose to offer them everywhere.

3. US state privacy laws

US state privacy laws continue to change and differ in applicability thresholds, definitions, response periods, appeals, and exemptions. LedgerBeaver applies the core rights above nationwide as an operational baseline and then applies any additional right or deadline required by the law governing a verified request. This summary is general information, not legal advice or a claim that every state law applies to every LedgerBeaver customer.

California (CCPA/CPRA) specifics

The categories of personal information we collect are detailed in Section 1 of our Privacy Policy. We do not sell or share personal information as those terms are defined by the CCPA, and we have not done so in the preceding 12 months. California residents may exercise their rights, or designate an authorized agent to do so, by contacting [email protected].

GDPR & UK (EEA / United Kingdom)

LedgerBeaver is a US-operated service serving primarily US small and medium businesses. If you are in the EEA or UK, review the legal bases in our Privacy Policy. Our published Data Processing Agreement is a working draft pending qualified-counsel review. Customers who require an executed DPA or international-transfer terms must contact us before onboarding restricted data.

4. How to make a privacy request

Email [email protected] with the right you want to exercise. For deletion, correction, and access requests we will:

• Verify your identity — typically by confirming control of the account email — before acting, so no one can request your data by impersonating you.
• Respond within 45 days, extendable once by another 45 days for complex requests, with notice to you.
• Honor authorized agents acting on your behalf where state law requires, with reasonable proof of authorization.
• Provide an appeal path where your state law grants one; appeal instructions are included in our response.

Account holders can also export most of their own data directly from the app at any time, and delete their account from account settings.

5. Security & data residency

The core workspace is hosted on US-based infrastructure. Service providers may process data in other countries; the Privacy Policy describes provider locations and transfers. A local connected model does not change those hosted processing locations. Our safeguards are described in full in Section 6 of that policy; in short:

• Provider-managed encryption at rest and encryption in transit (TLS 1.2+).
• Tenant isolation enforced at the database layer with row-level security, so one company's data is never reachable by another.
• Scoped agent access — AI agents you connect act under per-capability tokens you issue and can revoke.
• Least-privilege operations — production access is limited by documented role and MFA requirements and reviewed through an evidence-based access-review process.
• SOC 2 readiness — LedgerBeaver is working toward SOC 2 readiness through documented security controls and evidence collection. An independent SOC 2 examination has not yet been completed, and no SOC 2 report is currently available.

6. Financial-data safeguards

Plaid production access is approved. Customers can connect supported bank accounts to import transactions for reconciliation. Bank connectivity does not authorize payments; payment-provider connections require separate activation and customer controls.

Because we handle bookkeeping data, a few points beyond general privacy law are worth stating plainly:

• We never store full payment-card numbers. Card processing is handled by Stripe, a PCI DSS Level 1 provider; we retain only the last four digits for reference.
• Bank connectivity, where used, is brokered by Plaid; we store account metadata and tokens, not your online-banking credentials.
• LedgerBeaver is a software tool, not an accounting firm, tax preparer, or financial advisor. You remain responsible for reviewing and approving payments, journal entries, and statements, as set out in our Terms.
• To the extent we act as a financial-data service provider, we handle nonpublic personal information consistent with applicable financial-privacy expectations, including under the Gramm-Leach-Bliley Act (GLBA) where it applies.

7. Sub-processors

We rely on a small set of vetted infrastructure providers to run the platform. The current list — including what each one processes and where — is maintained in Section 4 of our Privacy Policy. When we add or replace a sub-processor that handles Customer Data, we update that list; material changes are communicated to customers in advance.

8. Breach notification

If a security incident affects your personal information, we will notify affected customers without undue delay and within the timeframes required by applicable law, describe what happened and what data was involved, and tell you the steps we are taking and what you can do. Suspected vulnerabilities can be reported to [email protected]; we practice coordinated disclosure.

9. Contact

• Privacy requests & questions: [email protected]
• Security & vulnerability reports: [email protected]
• General support: [email protected]

If we cannot resolve a privacy concern to your satisfaction, you may contact your state attorney general's office or, if applicable, your local data protection authority.

This summary is provided for convenience and does not replace our Privacy Policy and Terms of Service, which govern in the event of any conflict.

See how these controls apply to connected AI for accounting and the supported prepare, review and approval workflow.