Security

Our primary database is hosted by Supabase in a Canadian region. Application hosting is on Vercel's global edge network. Static and cached content may be served from edge locations outside Canada, but customer books and personal information are stored in Canada.

All network traffic between your browser, our application, and our database is served exclusively over HTTPS with modern TLS (1.2 or higher). HTTP requests are redirected to HTTPS. We use HSTS to reduce downgrade risk.

Primary database storage is encrypted at rest using industry-standard algorithms (AES-256). Backups inherit the same encryption. Passwords are stored as salted hashes, never in plaintext.

Access to production systems is restricted to a minimum set of personnel using strong authentication and hardware-backed credentials. Privileged actions are logged. We do not read customer books for any purpose other than providing the Service, responding to a support request you initiated, investigating a security incident, or complying with valid legal process.

We support sign-in with email and password, and sign-in with Google. Passwords are subject to minimum-length requirements and stored only as salted hashes. We recommend using a password manager and a unique password for Ledg. Suspicious sign-in activity triggers email alerts.

Customer data is isolated at the database layer using PostgreSQL row-level security. Every query is scoped to the authenticated user's corporation; no query path bypasses this layer. Administrative operations that override row-level security are limited to a short, auditable list of tasks.

Our database provider takes automated daily backups of the primary database with point-in-time recovery for a rolling window. Backups are encrypted and retained for the period required to meet our business-continuity and regulatory obligations.

We monitor availability, error rates, and unusual sign-in patterns. Alerts are routed to an on-call process. We keep audit logs for sensitive actions and retain them long enough to investigate an incident.

If we become aware of a breach of security safeguards that creates a real risk of significant harm to you, we will notify you and the Office of the Privacy Commissioner of Canada as required by PIPEDA, and we will keep a record of the breach in our breach log for at least twenty-four (24) months. See our Privacy Policy for details on breach notification.

Security is shared. We commit to the practices on this page. You commit to using a strong, unique password, keeping your credentials confidential, signing out on shared devices, and notifying us promptly at legal@ledg.ca if you suspect unauthorized access.

If you believe you have found a vulnerability, please email legal@ledg.ca with enough detail for us to reproduce it. Do not access data that is not your own and do not degrade the Service for other users. We will acknowledge your report promptly and work with you on a coordinated timeline for disclosure.