Privacy notice

What we store

The app stores the spending records, categories, budgets, import-batch metadata, and review decisions that you create. Each record is tied to the Google account used to sign in and is separated from other users' records.

Google sign-in

Google is used only to authenticate you. The app keeps the authentication data required to maintain your session; it does not use Google to read your financial accounts.

Transaction-file extraction

When you choose files for import, the files are processed in server memory and sent directly to OpenAI's API to extract suggested transactions. The app does not save upload bytes to its disk, database, object storage, or the OpenAI Files API. Suggested transactions always require your review before they can be added to the ledger.

The raw extraction response is encrypted at rest for up to 30 days for limited troubleshooting, then its ciphertext is purged automatically. Normal application logs do not include uploaded content or names, transaction descriptions, notes, email addresses, raw model output, OAuth tokens, cookies, or secrets.

Security and retention

The service uses HTTPS in production. Its PostgreSQL database is self-hosted with network access limited to the application host. Ledger records remain until you delete them; archived categories remain attached to historical transactions so past reports stay accurate.

Questions or requests

Contact the application owner through the deployment contact published with this service for questions, access requests, or deletion requests.