Privacy Policy

LedgerBug is self-hostable accounting software. This page describes the application's default data flows, but it is not a privacy policy for every deployment. The operator of each deployment controls the data it collects and must publish terms that match its configuration, jurisdiction, integrations, and retention practices.

Information we process

• Account information — your name, email, and firm, used to authenticate you and scope access to your firm's data.
• Client accounting data — chart of accounts, trial balances, general-ledger transactions, journal entries, and financial statements you import or create.
• QuickBooks Online data — when you connect a QuickBooks company through Intuit's authorization, we retrieve accounting data (accounts, trial balance, general ledger) to bring the client's books into your engagement. We access only the data needed to provide the service.

How we use it

The application uses this data to provide the service — importing books, preparing and adjusting financial statements, reconciliations, reviews, and reports for the engagements you manage. We do not contain advertising or data-sale functionality. A deployment operator is responsible for its own practices and disclosures.

How we protect it

• Encrypted in transit (TLS) and at rest.
• Third-party access tokens (including QuickBooks/Intuit OAuth tokens) are encrypted at rest with AES-256-GCM and never exposed to the browser.
• All data is scoped to your firm; queries are isolated so one firm's data is never accessible to another.
• Access is restricted to authenticated firm users.

Subprocessors

Subprocessors depend on how LedgerBug is deployed and which optional integrations are enabled. A hosted deployment may use infrastructure, banking, accounting-data, storage, email, and AI providers. Operators must identify their actual providers and complete any required review before processing financial data.

QuickBooks connections

Connecting QuickBooks is optional and authorized by you through Intuit. You can disconnect at any time — from within QuickBooks, from LedgerBug, or through the deployment operator. On disconnection the application stops using the connection and removes its stored tokens through the supported disconnect flow.

Retention & your choices

Retention, export, and deletion policies are set by the deployment operator. Operators should document their retention schedule and provide a contact channel for privacy requests before onboarding users or financial data.

Contact

Contact the operator of your LedgerBug deployment for privacy or data requests. Security researchers should follow the project's vulnerability-reporting instructions in SECURITY.md.