Trust
Security at LedgerWire
LedgerWire moves accounting data between your app and your customers’ QuickBooks Desktop files. This page describes how that data is protected today. It is an honest description of the current system, not a certification.
Transport
- Every API call, setup page and Web Connector exchange uses HTTPS (TLS). The Web Connector itself refuses non-HTTPS endpoints.
- The Web Connector runs on your customer’s PC and connects outbound to LedgerWire. No inbound ports are opened on their network.
Credentials
- Production API keys (
lw_live_) are stored only as SHA-256 hashes and shown once. Sandbox keys stay visible because they only reach simulated data. - Web Connector passwords are stored hashed for authentication and encrypted with AES-256-GCM so the hosted setup page can show them to your customer. You can regenerate them at any time.
- Keys can be rolled or revoked instantly from the dashboard.
Data handling
- LedgerWire does not copy your customers’ company files. It stores the requests and responses of calls you make, for request logs, for the retention period of your plan (7, 30, 90 or 365 days).
- The hosted sandbox contains only generated sample data.
- Webhooks are signed with HMAC-SHA256 and a per-endpoint secret.
Access in QuickBooks
Your customer grants access inside QuickBooks (Integrated Applications) and can remove it there at any time. A connection can also be set up read-only.
Reporting a vulnerability
Email the address on the privacy page. We acknowledge reports within two business days.
Not yet
LedgerWire does not hold a SOC 2 report yet. If your buyer requires one, tell us what they need and we will answer the questionnaire directly.