Security
Last updated November 8, 2026
Ledgerpair touches your books, so we built it to keep as little as possible and to check every request.
What we hold
- Ids, amounts, dates, statuses and one-way hashes about your customers and documents. No customer names, emails, phones, addresses or memos.
- Access tokens for your CRM, QuickBooks Online and Xero, and Stripe restricted keys, encrypted with AES-256-GCM. Stripe keys must be restricted and read-only; full secret keys are refused.
How requests are checked
- Every webhook from your CRM, QuickBooks Online and Xero is signature-checked over its raw body before anything is read, and handled once.
- CRM events signed for any other app are ignored.
- Connecting your books uses a signed, short-lived, one-time link, and must finish in the browser that started it, by the account owner.
- Every page and action checks who is signed in and which account they belong to. One business can never see another's data.
- Owners, bookkeepers and staff each see and change only what their role allows.
- Sign-in pages and public forms are rate-limited.
How writes are kept safe
- Nothing writes until the owner approves a dry run. Pause stops every write at once.
- Every create is reserved first and sent with a unique key, so a retry never makes a second copy.
- Ledgerpair never deletes anything in your CRM or your books, and never writes into a closed period.
- Every write is logged with what caused it.
Where it runs
The app runs on Netlify and stores its records in a Neon Postgres database, both over encrypted connections. When you remove Ledgerpair, your data is deleted 30 days later (see the Privacy Policy).
Reporting a problem
Email hello@goldstandardweb.com with "Security" in the subject. We'll reply within 24 hours and keep you posted until it's fixed. Please don't test against accounts that aren't yours.