1. Who operates Ledger Workbench
Ledger Workbench is developed and operated by Elvin Stauffer, an individual developer. This policy covers the software, this informational website, the public QuickBooks authorization callback service and support communications. For privacy questions, contact elvin.northstar@gmail.com.
The business operating a local Ledger Host manages its own users, business records, devices and backups. This website is not that business’s accounting server.
2. Information used by the software
Depending on enabled workflows, Ledger Workbench may process company information, vendors, accounts, items, bills, expenses, transaction details, identifiers, supporting evidence and related accounting information. Evidence may include documents, receipts and messages acquired through configured sources.
It also processes user and permission information, connection metadata, interpretations, mappings, workflow decisions and audit/history information needed to operate those workflows.
If you contact support, Elvin Stauffer receives your email address and the information you choose to include. Please provide only information needed for the request, and remove unnecessary personal or financial details from attachments.
3. Local operation and protection
Normal application, database and evidence operations are designed to run on the business’s local Ledger Host. QuickBooks access and refresh tokens are protected on that host using Windows-backed protection. They are not provided to the desktop client or intended to be retained by the public callback service.
This protection is specific to connection credentials. It is not a claim that all financial records, documents or backups are encrypted at rest. The business remains responsible for host access, device security and backup handling. No software or security measure can guarantee protection against every risk.
4. QuickBooks and other enabled integrations
QuickBooks Online access begins only after authorization through Intuit. Ledger Workbench does not request or store your QuickBooks password. After authorization, Intuit provides OAuth authorization credentials/tokens and company identifiers needed for the connection.
Information is transmitted to Intuit when necessary to perform authorized QuickBooks operations. Other enabled integrations communicate with their respective service providers as needed for the workflows you configure. Data therefore does not always remain on the local machine. Intuit handles information under its privacy statement.
5. Public website and OAuth callback
Cloudflare hosts the public website and a narrowly scoped HTTPS OAuth callback bridge. The bridge may temporarily process limited callback and handoff information needed to securely return QuickBooks authorization to the local Ledger Host. This can include an authorization code, company identifier and transaction correlation information.
The bridge is not Ledger’s hosted accounting database. Normal Ledger accounting records and evidence are not uploaded to it as part of ordinary operation, and it is not intended to retain long-lived QuickBooks access or refresh tokens.
Cloudflare may process technical request, network and security information, such as IP addresses and request metadata, to deliver and protect the service. Temporary application cleanup does not guarantee immediate destruction of every provider log, backup or recovery copy. See Cloudflare’s privacy policy.
This site includes no advertising, analytics trackers, remote fonts or third-party JavaScript. The authorization flow uses a short-lived browser cookie for connection status; visiting the informational pages does not require a Ledger account.
6. Purposes and sharing
Information is used to operate configured workflows, connect authorized services, preserve evidence and accounting history, support review and audit, respond to support requests, troubleshoot issues and protect the software and public service.
Information may be processed by providers needed for those purposes, including Intuit, Cloudflare and the email service used for support communications. Disclosures may also be necessary to meet applicable legal obligations or protect against misuse. Do not send credentials to support.
7. Retention, disconnect and deletion
Information may be retained as reasonably necessary for application operation, accounting and audit history, troubleshooting, security, legal obligations, backups or other legitimate purposes. No fixed retention period is promised by this policy. Local retention and backup handling depend in part on the business operating the Ledger Host.
Disconnecting or revoking QuickBooks authorization is separate from deleting retained business data. It does not automatically delete local accounting records, evidence, mappings, audit history or backups.
For privacy or deletion requests, email Privacy Request or Data Deletion Request to elvin.northstar@gmail.com. Describe the request without sending secrets. Identity and authority may need to be verified before action is taken. Requests involving records on a business’s local host may require that business’s administrator. Deletion may be subject to accounting, audit, legal or backup constraints.
8. Policy changes and contact
Changes to this policy will be published on this page with an updated effective date. Contact Elvin Stauffer at elvin.northstar@gmail.com with questions about this policy.