Security & Data Handling

Sign-in is Google only — there are no passwords for the app itself. Access is invite-only: an email address must be on the owner's approved list before any app data is available, and that check runs on the server, not in the browser.

Every record is scoped to the account that created it and enforced by database-level access rules, so one user's queries cannot return another user's transactions.

Statement files are parsed in your browser. Password protected PDFs are unlocked locally, and the file itself is not uploaded to a server for parsing. Only the resulting transaction rows are saved to your account.

Ledger has no bank connection and never asks for banking credentials, card numbers, OTPs or net-banking logins. If a page ever asks you for those, it is not Ledger.

If you configure an AI provider, your API key is stored encrypted and used only for categorisation requests you trigger. Keys are never shown back to you in full and are not exposed to the browser.

All traffic to the app is served over HTTPS.

If you believe you have found a security problem, email sayantan.royy@gmail.com with the details and steps to reproduce. Please do not publish the issue before it has been addressed, and do not access or modify data that is not yours while testing. Reports are read by the owner directly and acknowledged as quickly as possible.