Privacy Policy

1. What personal data we collect

• Authentication identity — your Clerk user ID, email address, first and last name.
• Financial transactions you enter manually — amount, currency, date, merchant or description, and category.
• Financial accounts — name, institution, balance snapshots.
• Budgets, savings goals, assets, and liabilities you create — labels, target amounts, notes.
• Error and performance traces when the application misbehaves — stack traces, request paths, your user ID, browser, and operating system. Sent to Sentry.
• Aggregate usage events — page views, referrer, approximate country. Sent to Plausible. No cookies, no IP retention.

Atlas does not collect bank login credentials, payment-card numbers or CVVs, or identifiers of anyone other than the account holder.

2. Sub-processors

Each of the following services may process your personal data on the operator's behalf:

3. Encryption

Every external network edge uses TLS 1.2 or higher. Postgres volumes are encrypted at rest by Railway, and database backups are encrypted at rest by Cloudflare R2 in a private bucket with no public access.

4. Retention

• Active account data is kept for as long as the account is active.
• Soft-deleted records are retained indefinitely so historical financial data remains auditable. They can be promoted to hard deletes on request.
• Sentry error traces: 30 days.
• Database backups: daily copies are kept for 30 days and weekly copies for six months, then deleted automatically. A hard deletion request removes your records from the live database immediately; copies already written to backup storage age out on that schedule.
• Plausible analytics: aggregate event counts indefinitely, no user-level identifiers retained.

5. Right to deletion

1. Export your data from the in-app Data Export tab.
2. Delete your Clerk user from the Clerk dashboard.
3. Request hard deletion of your records from the operator using the contact below.

6. Access controls

Application access is gated by a Clerk user allowlist enforced server-side; non-listed Clerk users receive HTTP 403. Infrastructure access (Railway, Sentry, Plausible, registrar) is protected by personal accounts with two-factor authentication enabled. The deploy workflow is the only automated path to production.

7. Contact

The data controller for this deployment is the operator. Reach them at woo.sung@vendingmachine.design.