Your financial records deserve straightforward privacy information.
This policy explains the standard Personal Ledger installation. The site operator should update it whenever hosting, analytics, payment processing, integrations or data practices change.

Last updated: August 29, 2026
1. Information stored by Personal Ledger
The application may store your name, email address, password hash, account names and balances, transactions, categories, payees, tags, budgets, recurring items, reconciliation records, uploaded receipts or statements, preferences, subscription status and payment-reference submissions.
2. Trial and payment information
Creating the one month free trial does not require a credit card. The standard release does not collect card numbers during signup. If the operator enables manual bank-transfer payments, customers may submit a payment date, payment reference and optional notes for administrator review. The operator's receiving-bank instructions are stored as site settings and shown to signed-in customers when appropriate.
3. Where information is stored
Application records are stored in the MySQL database configured for this installation. Uploaded documents are stored on the hosting account and are intended to be delivered through authenticated application routes rather than direct public URLs.
4. Analytics and advertising
The standard package does not include third-party advertising trackers or analytics scripts. If the operator adds analytics, advertising, bank connections, payment processors or other integrations later, this policy should be updated.
5. Support requests
Public support requests can include the visitor's name, reply email, topic, priority, subject and message. Signed-in requests may also include limited diagnostics such as application version, database-connectivity status, upload-folder status, currency and timezone. Support diagnostics are designed not to include passwords, database credentials, account balances or transaction details.
6. Cookies and sessions
Personal Ledger uses a session cookie for authenticated sessions and security controls such as CSRF protection. The standard package does not use advertising cookies.
7. Data sharing
The standard application does not automatically sell personal financial information to advertisers. Information may still be processed by the hosting and email providers chosen by the site operator as necessary to operate the service.
8. Data retention and deletion
The operator controls the live database and backups. Deleting records from the live application may not remove copies already present in hosting or offline backups.
9. Security
Personal Ledger includes password hashing, prepared database statements, CSRF protection, session controls and protected document access. No web application can guarantee absolute security; HTTPS, hosting security, database credentials, updates and backups must be managed carefully.
10. Questions
Use the Contact page or Support Center for privacy questions.