Privacy policy

Effective November 2, 2026 · Last updated November 2, 2026

This policy explains what personal information BookkeepLedger collects, why, who we share it with, and the choices you have. "BookkeepLedger", "we" and "us" means Bookkeep Accounting Software Inc., a Delaware corporation. It applies to the BookkeepLedger web and mobile apps and to this website.

1. Who this covers

• Account holders and team members who sign in to BookkeepLedger. We decide how your account information is used.
• People in our customers' books, such as a business's customers, vendors, contractors and employees. We process their information for the business that uses BookkeepLedger and only on its instructions. If you're one of those people, contact the business you deal with, and we'll help it answer your request.
• People who pay an invoice through a BookkeepLedger payment link. The business that sent the invoice is responsible for your information, and Stripe processes the payment.

2. What we collect

3. Bank data and Plaid

BookkeepLedger uses Plaid Inc. to connect to your bank and credit card accounts. When you choose Add bank, Plaid's window opens and you sign in to your bank there. Your bank username and password are given to Plaid and your bank. BookkeepLedger never sees or stores them.

With your permission, Plaid sends us:

• your bank's name, and each account's name, type (such as checking, savings or credit card) and last four digits;
• account balances;
• transactions: date, amount, description, merchant name and Plaid's category; and
• where your bank supports it and you ask us to, a report of past transactions so we can import your history.

We use bank data only to provide BookkeepLedger to you: to fill your bank feed, suggest categories, match transactions to invoices, bills and receipts, reconcile your accounts and produce your reports. We don't sell bank data, use it for advertising, or share it with anyone except the service providers in section 6 that help us run BookkeepLedger.

Plaid gives us an access token for each connection. We encrypt it with AES-256-GCM before storing it, and use it only to fetch updates for your connected accounts.

You can disconnect a bank at any time from Banking → Bank accounts in the app. When you do, we stop fetching data and remove the connection at Plaid. Transactions already in your books stay there, because they're part of your accounting records; you can ask us to delete them as described in section 9. You can also manage the apps connected through Plaid at my.plaid.com.

Plaid handles your information under its own End User Privacy Policy, which you agree to when you connect an account.

4. How we use it

Beta requests on this website

When you ask for beta access, we store what you enter in the form with Cloudflare, which hosts this website. We use it to email you a confirmation, to tell our team about your request, and to contact you about the beta. We don't add you to a mailing list. The form uses Cloudflare Turnstile to check that it isn't being filled in by a bot. We keep beta requests until the beta ends or you ask us to delete yours, then delete them within 30 days.

We don't sell personal information and we don't share it for cross-context behavioral advertising. The BookkeepLedger app has no advertising or analytics trackers. We don't use your books or your conversations with the desk to train AI models.

5. How the AI features work

• AI in BookkeepLedger runs on Claude models from Anthropic, accessed through Amazon Bedrock in our own AWS account, with processing in AWS regions in the United States. When you use the desk, or when we read a receipt or statement, the parts of your books or the file needed for that task are sent to Bedrock, and the result comes back to us.
• Under AWS's Bedrock data protection terms, model providers such as Anthropic don't get access to our prompts and outputs, and Bedrock doesn't use them to train models.
• The desk works with the permissions of the person asking. It can't change your books by itself: every change it wants to make becomes a proposal that a person in your company must approve. Approved changes are recorded in the audit log.
• We keep your desk conversations, the desk's steps and proposals, and the notes it keeps about your business, so you can see what happened and so later conversations have context. You can see and delete those notes under What the desk remembers.
• AI output can be wrong. Check it before you rely on it.

6. Who we share it with

We share personal information only as this policy describes:

• Service providers that host and run BookkeepLedger for us, under contracts that limit how they use it. They're listed below and on our subprocessors page.
• People in your company. Team members you invite see the company data their role allows.
• Recipients you choose, such as the customers you send invoices or reminders to.
• Plaid and Stripe, as part of the bank connection and payment features you choose to use. They also process data under their own privacy policies.
• For legal and safety reasons, when the law requires it or to protect the rights, property or safety of our users, the public or us. Where the law allows, we'll tell you about a request for your data before we respond to it.
• A buyer or successor, if we're involved in a merger, acquisition or sale of assets. Your information would stay subject to this policy.

7. How long we keep it

• Account and company data, including your books and bank data: while your account or company is open. When it closes, you have 30 days to export your data. We then delete it within 30 days, except where the law requires us to keep it.
• Backups are kept for 7 days, so deleted data leaves our backups within 7 days of being deleted from the live system.
• Server logs are kept for 30 days. They include IP addresses but not passwords, tokens or the contents of your books.
• Data export files we generate for you are deleted after 1 day.
• Beta requests: until the beta ends or you ask us to delete yours, then deleted within 30 days.
• Recovery codes: only a keyed hash, until you make a new set.
• Invitations expire after 7 days.
• Background job records, such as a receipt being read: up to 24 hours after they finish, or 7 days if they fail.
• Billing records we must keep by law, for as long as the law requires.

8. How we protect it

• Two-step sign-in is required for every account. Recovery codes are stored only as keyed hashes. Resetting an authenticator signs out every existing session.
• Each company's data is kept separate. Every request is checked against the signed-in user's company and role, and the database enforces row-level security so one company's data can't be read or written in another company's context.
• Role-based permissions for owners, admins, accountants and viewers.
• Encryption. Data is encrypted in transit with HTTPS. The database, cache, backups and file storage are encrypted at rest. Plaid access tokens are also encrypted with AES-256-GCM before they're stored.
• An audit log of changes made in each company, including changes approved from the desk.
• Rate limits on account recovery, AI features and public endpoints, and verified signatures on Plaid and Stripe webhooks.
• Automated scanning of dependencies and container images before code is deployed.

No system is perfectly secure. If we learn of a breach that affects your personal information, we'll tell you and the authorities as the law requires.

9. Your choices and rights

• Access and correction. You can see and edit your account and company information in the app.
• Export. On the Pro plan, owners, admins and accountants can export the books from Export to QuickBooks (QuickBooks IIF files and a transactions CSV). On any plan, email us and we'll send you a copy of your data.
• Deletion. Email us to delete your account, a company, or bank data. We'll confirm your identity first and respond within 30 days.
• Bank connections. Disconnect a bank from Banking → Bank accounts, as described in section 3.
• Notifications. Turn push notifications off in Settings or on your device.
• Other rights. Depending on where you live, you may have more rights, such as to know what we hold about you, to have it deleted or corrected, or to appeal a decision we make about your request. Email us to use them. We won't discriminate against you for using your privacy rights.

10. Where your data is stored

BookkeepLedger is offered to businesses in the United States. Your data is stored and processed in the United States, in Amazon Web Services' US East (N. Virginia) region, and AI requests are processed in AWS regions in the United States.

11. Cookies and local storage

BookkeepLedger doesn't use advertising or analytics cookies, in the app or on this website. The web app keeps your sign-in session in your browser's local storage so you stay signed in. The beta form on this website uses Cloudflare Turnstile, which checks your browser for signs of automation and doesn't track you across sites. Plaid's window and Stripe Checkout run under their own terms and may set their own cookies when you use them.

12. Children

BookkeepLedger is for businesses and isn't meant for anyone under 18. We don't knowingly collect information from children.

13. Changes to this policy

We'll post changes here and update the date at the top. For significant changes, we'll tell account owners by email or in the app before they take effect.

14. Contact us

Bookkeep Accounting Software Inc. Privacy questions and requests: info@bookkeepsoftware.com.