Your clients' data is our entire job.
Ledgersync handles bank-level data for thousands of firms. Here is exactly how we protect it — no marketing fluff.
Security-first controls
Layered safeguards protect bank data, documents, user access, and sync activity across the platform.
AES-256 at rest, TLS 1.3 in transit
Every byte of client data encrypted in storage and on the wire. Keys rotated quarterly.
U.S.-based hosting
Data resides in AWS regions in the United States. No offshore processing.
Bank credentials never stored
Connections use Mastercard Open Banking tokenized credentials — Ledgersync never sees a username or password.
Role-based access + audit log
Every read, write, sync, and admin action is logged with user, IP, and timestamp. Exportable for your own audits.
Bring your own access policy
SSO via Google Workspace and Microsoft 365. SAML/SCIM for firms on Enterprise.
Specifics, not slogans.
If you're filling out a vendor security questionnaire, copy from here.
- Data residency
- United States (AWS us-east-1 / us-west-2)
- Encryption at rest
- AES-256 (AWS KMS)
- Encryption in transit
- TLS 1.3
- Penetration testing
- Annual, by accredited third party
- Vulnerability disclosure
- security@ledgersync.com
- Breach notification
- Within 72 hours of confirmed incident
- Data retention
- Active during subscription + 90 days post-cancel, then permanently deleted
- Sub-processors
- AWS, Mastercard Open Banking, Stripe (billing)
For a full security packet or DPA — email security@ledgersync.com.
50+ help articles. A real human. Or ask our AI.
Search the knowledge base, message support, or try the new Ledgersync AI assistant (beta) — it answers from our docs and the public site in seconds.
Ready to automate the data work?
Start your 30-day free trial. Credit card required at sign-up — you won't be charged until the trial ends, and you can cancel anytime.
30 days free · credit card required · cancel anytime