Trust
Security at Ledger Bridge
Last updated October 29, 2026
Ledger Bridge helps accountants, bookkeepers, and crypto accounting firms turn Koinly, Summ, and generic CSV crypto transaction data into balanced, traceable journals for Xero and QuickBooks. This page describes how we handle your client data. A few operational details are still being finalised and are marked below — we won't claim anything we haven't actually done.
What we process
- Transaction exports you upload (Koinly CSV, Summ ZIP, or generic CSV), and optional capital-gains or mapping files.
- Account details you provide at sign-up — name, email, and phone if you choose to give one.
- Workspace settings such as entity name and export preferences.
- Payment details when you buy a plan — handled directly by Stripe; we never see or store your card number.
Where data lives
- Hosting
- A dedicated VPS running our application and a Postgres 16 database as isolated containers, behind a reverse proxy that terminates TLS with a Let's Encrypt certificate. It is not shared serverless infrastructure. [PLACEHOLDER: provider name and region, pending confirmation this is OK to publish]
- Backups
- [PLACEHOLDER: backup frequency, retention, and storage location — not yet finalised].
- Encryption
- All traffic to the app is encrypted in transit (TLS/HTTPS). At rest, connected Xero/QuickBooks OAuth tokens, two-factor secrets, uploaded source files, and manual-payment screenshots are individually encrypted (AES-256-GCM) before being stored — not just relying on whole-disk encryption. Passwords are hashed, never stored in plain text.
Who can access data
Your workspace is private to the account owner and anyone they explicitly invite as an editor or viewer. Support staff cannot see your real data without your permission: when you ask for help, we clone an isolated copy of the relevant workspace for support to work from — your real books are never touched directly, and nothing from a proposed fix applies until you review and approve it. Support access grants expire automatically and every action is logged to an activity trail you can see. [PLACEHOLDER: named roles with production access, and whether MFA is mandatory for them]. We do not sell client transaction data.
Sub-processors
We use a small number of processors to run the product:
- Stripe, to process payments. We never see or store your card number.
- A transactional email provider, to send password resets and sign-in codes you request.
- Xero, QuickBooks Online, or Google — only if and when you explicitly connect one.
- Our hosting provider, to run the application and database.
[PLACEHOLDER: we'll post an update here before adding a sub-processor that touches customer content.]
Retention and deletion
- Active workspace
- Imported files and journals stay until you replace or delete them, or close the account.
- After a deletion request
- [PLACEHOLDER: days until purge from primary storage and from backups — not yet finalised].
- How to delete
- Today, email team@ledgerbridge.si from your account email to request deletion. An in-app self-serve delete is on the roadmap — we'll link it here once it ships.
Compliance and certifications
None yet. We haven't pursued SOC 2 or ISO 27001, and we won't claim a certification we haven't actually completed. [PLACEHOLDER: roadmap date, if one is set].
Report a vulnerability
Email team@ledgerbridge.si. Please don't include real client data in the report. [PLACEHOLDER: target acknowledgement time].
More
See the Privacy Policy, the Terms of Service, and About.
