Daily Ledger Privacy

Development privacy notice · October 5, 2026

Information stored

Google sign-in supplies your stable provider identifier, name, and email. Daily Ledger stores the transactions, plans, tasks, habits, workouts, meals, goals, preferences, and notification state you enter. Email registration stores your name, normalized email, and a salted password hash; plaintext passwords are never stored. Password reset records contain expiry and token hashes. Essential reset emails use Resend when configured. It does not request Gmail access.

How your information is used

Your records power your private workspace and reports. Essential session cookies maintain sign-in and protect requests; authentication tokens are not kept in browser local storage. Optional reminder and product emails are controlled in Settings and sent through Resend when configured.

Hosting and demo data

The configured production architecture uses Vercel for the frontend and Railway/PostgreSQL for the API and records. Google provides identity verification. Demo mode saves example data and your demo edits only in this browser, separate from signed-in records.

Access and retention

You can export your workspace in Settings. Plan downgrades do not delete your records. For account deletion or privacy requests, contact the operator who provided your deployment. Production operators must publish their identity, privacy contact, retention policy, and applicable processing terms before collecting real user data.