Privacy Policy

Last updated: October 9, 2026

LedgerBeaver LLC, a Texas limited liability company ("LedgerBeaver," "we," "us," or "our), provides a platform that helps small and medium-sized businesses automate financial operations. This Privacy Policy explains what information we collect, how we use it, who we share it with, and your rights regarding your data.

This policy applies to all users of the LedgerBeaver Service, including visitors to our marketing website (ledgerbeaver.com) and customers using the web application at app.ledgerbeaver.com.

1. What We Collect

We collect information you provide directly, information generated through your use of the Service, and limited information from third-party integrations. Here's what that breaks down into:

Scroll the table to see all details.

2. How We Collect Information

• Directly from you: When you sign up, configure your account, upload documents, connect integrations, or contact support.
• Automatically: Through server logs, API call tracking, and minimal analytics as you use the Service. We use Sentry for error monitoring and application performance data.
• From third-party integrations: When you connect an available service such as Plaid, Stripe, or a supported accounting-data import, we receive data as authorized by you.
• From your AI agents: When your MCP-connected agents make tool calls to our API, we log those calls and their results.

3. How We Use Your Data

We use your data for the following purposes, and only these purposes:

Scroll the table to see all details.

What we DO NOT do with your data:

• We do not sell your data — to anyone, ever
• We do not use your financial data to train AI models
• We do not use your data for targeted advertising
• We do not access your data for any reason other than providing and improving the Service, investigating support issues with your permission, or complying with legal obligations

4. Data Sharing and Third-Party Processors

We share data only with the service providers necessary to operate the platform, and only to the extent required. Here are our key sub-processors:

Scroll the table to see all provider details.

We also share data at your direction when you:

• Connect an available integration (for example, Plaid) — data flows through our Service to that provider as you configure
• Grant AI agents access via MCP tokens — your agents can read and write data as scoped by the permissions you set
• Use the vendor portal — vendors you invite can see invoices and payment status related to their relationship with you

Current hosted-AI status: owners and administrators of eligible Pro and Max workspaces can separately enable five TypeSafe Jev advisory purposes: on-demand AP invoice-exception suggestions, employee-expense account suggestions, PO evidence guidance, possible vendor-name comparisons, and selected CRM note follow-up guidance. Each suggestion requires an explicit request from an authorized person or, for AP exceptions, an authorized connected agent. CRM requests additionally require confirmation of the exact proposed excerpt. An expense suggestion never changes the account: a person must apply it, and a separate approval remains bound to the displayed coding revision. PO, vendor, and CRM guidance does not create receipts, merge records, send messages, approve spending, or move money. TypeSafe states that Jev customer requests and responses are not used to train its models; processing and retention still follow LedgerBeaver's agreement and TypeSafe's applicable terms, and we do not claim zero retention. Other TypeSafe assessment tasks, general product-help model requests, and cloud document transcription remain disabled. Verified book summaries and documentation help do not send content to a model provider.

AI agents and model providers you choose

When you connect an AI agent, LedgerBeaver makes information available within the connection's permissions and your account's access controls. Your agent may send prompts, files, tool results, financial records, and related personal data to its model provider or other services it uses. Those services may retain or use that information, including for model training where their applicable terms and your settings allow. Practices differ by product, account, contract, and settings; some business and API services exclude training by default. Review both the agent's and the model provider's terms, retention, data location, and settings before connecting business records. A training opt-out does not necessarily mean zero retention, no security processing, or no human review.

LedgerBeaver does not use Customer Data to train AI or machine-learning models. This commitment is separate from using automated processing or model inference to deliver an enabled feature. Providers LedgerBeaver engages to process Customer Data on our behalf remain subject to our applicable processor and sub-processor obligations; they are not independently selected customer services merely because their technology powers a LedgerBeaver feature.

Running your connected agent's model locally can reduce disclosure of that agent's model inputs to cloud AI providers, but the agent, extensions, telemetry, backups, or cloud fallback may still transmit content. It does not disable separate LedgerBeaver features that use service providers, such as the in-app assistant. LedgerBeaver remains a hosted service. Local inference does not change your existing rights in Customer Data or other individuals' privacy rights. See AI & Data Privacy for details.

Revoking a connection blocks new access to LedgerBeaver through that connection after revocation. It does not retrieve information already received by the agent or its providers; their retention and deletion terms apply to those copies.

We may also disclose data if required by law, court order, or valid legal process, or to protect our rights, property, or safety, and that of our users. We will notify you before such disclosure unless prohibited by law.

5. Data Retention and Deletion

5.1 Active Accounts

We retain Customer Data while your account is active and then apply our governed retention schedule when your account is closed. You may export eligible data before closure or contact [email protected] for assistance.

5.2 After Account Deletion

Account closure removes access and deletes eligible identity, integration-token, and operational data according to the applicable schedule. Posted accounting entries, invoices, bank transactions used in the books, source documents, consent evidence, security evidence, and other records may be retained in a restricted archive when required for accounting integrity, tax or legal duties, disputes, fraud prevention, or a legal hold. LedgerBeaver's engineering baseline retains core accounting records for seven years and consent evidence for ten years, subject to applicable law and contractual requirements. Retained records remain protected and are not used for ordinary product access.

5.3 Backups

Deleted data ages out of provider-managed backups under the applicable backup-rotation schedule. Backup copies are isolated from ordinary product access and used only for security, resilience, and disaster recovery.

6. Security

We protect your data with industry-standard technical and organizational measures:

• Encryption at rest: Customer Data and managed backups use provider-managed encryption at rest. Plaid access tokens receive an additional application-layer encryption control with key material held separately.
• Encryption in transit: Communication between your browser, our services, and third-party APIs uses TLS 1.2 or later.
• Access controls: Database row-level security, role-based application permissions, least-privilege production access, MFA requirements, scoped MCP tokens, and periodic access-review procedures protect Customer Data.
• Infrastructure: Hosted on Cloudflare (CDN, TLS, and DDoS protection), Railway (isolated containerized compute), and Supabase (managed PostgreSQL, authentication, storage, and row-level security).
• 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.
• Subscription billing: We do not handle raw card numbers. Stripe processes LedgerBeaver subscription billing; any business payment-provider connection has separate activation and customer controls. We retain only billing reference information needed for account administration.

If you believe you've discovered a security vulnerability, please email [email protected]. We participate in coordinated disclosure and will respond promptly.

7. Your Rights

Depending on your jurisdiction, you may have the following rights regarding your personal data:

To exercise any of these rights, email [email protected]. You can also start account deletion in the app. We will verify your identity before processing your request and respond within 30 days (or 45 days for complex requests, with notice).

CCPA Notice (California Residents): Under the California Consumer Privacy Act, as amended by the CPRA, California residents have the rights listed above. The categories of personal information we collect are described in Section 1. We do not sell personal information as defined by the CCPA. To exercise your CCPA rights, contact [email protected].

GDPR Notice (EEA and UK Residents): If you are located in the European Economic Area or the United Kingdom, the legal bases for our processing are set out in Section 3. The LedgerBeaver operator identified above is the data controller for personal data collected directly to operate the Service; customers generally act as controller for personal data they place in their workspace. For GDPR inquiries, contact [email protected]. You also have the right to lodge a complaint with your local data protection authority.

Data Processing Agreement (DPA): Our published DPA is a working draft pending qualified-counsel review and is not an executed agreement. Customers who require an executed DPA or EEA/UK transfer terms must contact [email protected] before onboarding restricted data.

8. Cookies and Tracking

LedgerBeaver's web application uses minimal browser storage:

• Authentication session storage: Supabase Auth stores the session in browser storage so the Service can keep you signed in.
• Preference storage: Theme and similar preferences may be stored in browser storage.

We do not use third-party tracking cookies, advertising cookies, or analytics cookies. We do not use Google Analytics, Facebook Pixel, or similar tracking services on the application. Our marketing website may use Cloudflare Web Analytics (privacy-first, no cookies) for aggregated page-view counts.

9. International Data Transfers

LedgerBeaver is based in the United States and hosts the core workspace on US-based infrastructure. Service providers may process data in other countries, as described in Section 4; use of a local connected model does not impose a US-only processing restriction on those services. If you are located outside the US, your data will be transferred to and processed in the United States and applicable provider locations. We take appropriate safeguards to ensure your data remains protected, including:

• Standard Contractual Clauses (SCCs) where applicable
• Provider contractual and data-processing terms where applicable
• Encryption at rest and in transit for all data regardless of location

10. Children's Privacy

The Service is not intended for individuals under the age of 18. We do not knowingly collect personal information from children. If we learn that a child under 18 has provided us with personal data, we will delete it promptly. If you believe a child has provided us with data, please contact [email protected].

11. Changes to This Policy

We may update this Privacy Policy from time to time to reflect changes in our practices, technology, or legal requirements. For material changes, we will notify you via email and/or in-app notice at least 30 days in advance and identify the effective date in that notice. The "Last updated" date records the latest revision, including clarifications. Continued use of the Service after changes take effect constitutes acceptance of the updated policy.

12. Contact Us

We're here to help. For privacy-related questions, requests, or concerns:

• Email: [email protected]
• Security: [email protected]
• Support: [email protected]

If you have a privacy complaint that we haven't resolved to your satisfaction, you may contact your local data protection authority.

Policy effective September 19, 2026; optional Ask Beaver processing disclosed October 9, 2026. These disclosures preserve the no-training commitment and do not authorize a new processing purpose. Each optional advisory purpose requires the separate opt-in described above.