Private preview / draft — subject to review before external launch

Privacy Policy

Effective October 23, 2026

1. Scope of this draft

Atlas Life is an owner-operated, private personal prototype for one owner, not a service open to public registration. This notice describes the current app, not a legal compliance certification. It must be reviewed and updated before any general public release.

2. Information used by the app

  • Email and authentication information needed to create the owner account and sign in.
  • Chat messages, workspaces, tasks, projects, checklists, notes, memories and meetings entered or saved in the app.
  • Manually entered account balances, transactions, recurring subscription schedules, review acknowledgements, debts and dated payment or balance-correction histories.
  • Finance preferences the owner sets, such as a chosen category for a merchant or a dismissed recurring-charge suggestion.
  • App preferences, such as timezone and demo mode. Demo records are labeled fictional and are not real financial activity.
  • Basic technical information and logs handled by hosting and service infrastructure, such as request information and errors.

Optional bank and investment imports happen only after the owner explicitly links an account through Plaid, the only active external financial integration (see section 6). Earlier integrations (Stripe Financial Connections, Teller and SimpleFIN) are retired: they can no longer link, refresh or receive events. Any records they previously imported may remain until the owner asks for deletion, and any old credentials stay encrypted server-side and are never used.

3. Why information is used

The app uses information to save and sync workspace items, generate daily briefs, provide AI assistance, calculate estimated cash forecasts, authenticate access, support security and diagnose errors. Forecasts and AI output can be incomplete or inaccurate and are not a verified statement of bank activity.

4. Service providers and AI processing

Atlas Life uses Lovable for app hosting and the Lovable AI Gateway, and Lovable Cloud's Supabase-based authentication and database services. AI requests are processed through the gateway by external language-model providers as necessary.

Model requests can include relevant chat, task, note, memory and account or other financial context. Private information does not necessarily stay within the app or a single platform. Providers' own policies and service settings govern their processing, logging and retention; this notice does not promise a universal training opt-out.

Plaid is the only external financial-data provider. It processes data under its own terms and end-user privacy policy (plaid.com/legal). Bank sign-in happens in Plaid's own window; Atlas Life never sees bank passwords. Stripe payments and payment onboarding are not used.

Do not put passwords, bank credentials, access tokens or client certificates into AI chat. Information sent in chat may be shared for external AI processing.

5. Banking and financial records

Owner-tracked financial records are created and changed through Talk to Atlas, not manual finance forms. Financial commands save private records only; they cannot move money, place trades or cancel merchant subscriptions. Maintained balances and projections depend on the entries provided. Net worth uses tracked USD cash, actual reported holdings and liabilities, with incomplete coverage and dated snapshots labeled; unknown brokerage cash is not invented. Personal, business, unassigned and workspace display associations are stored privately. Mapped retirement holdings and unassigned liabilities are excluded from personal net worth; a workspace association does not verify legal ownership. Bank posting and provider refresh delays occur, so imports are never instant or real-time.

Subscription schedules describe expected charges, not confirmed payments. Matching against available records may flag possible duplicate charges but cannot prove a double charge or complete history. Marking canceled in Atlas does not cancel with the merchant. Manual debt payments update private balances and preserve history; they do not move money, create bank transactions or automatically add forecast bills.

Linked bank balances reported by Plaid are treated as authoritative and are not reduced again by manual entries. Possible duplicate copies of the same account (for example a retired legacy import and a Plaid copy) count only once. This notice does not itself authorize any bank connection.

Atlas Life analyzes recorded transactions on its own servers with fixed, rule-based logic: it assigns spending categories from merchant names, recognizes charges that repeat on a regular cycle, and projects cash from known recurring items. These results are estimates that can be wrong, and the owner can override a merchant's category or dismiss a suggestion. Financial questions asked in chat are answered from these records; when the AI writes the wording of an answer, it receives only summary figures (totals, category amounts, counts and projections), not a raw list of transactions.

Plaid bank and investment connections

Plaid is an optional read-only Production Trial integration. No account is linked until the owner explicitly authorizes it in Plaid Link. Bank mode requests Transactions and permitted balances; investment mode requests Investments only. Atlas does not request Auth, Identity, Transfer, routing numbers or trading permissions, and never collects bank passwords. Institution and holdings availability depend on Plaid and the institution.

Atlas stores an encrypted access token in server-only storage, masked account details, balance snapshots, transaction history and, when returned, brokerage accounts, securities and holdings with shares, prices, value and cost basis. Holdings are kept separate from cash. Non-USD bank activity is excluded from USD analytics; likely duplicate sources are held out of totals until the owner chooses a preferred copy. No records are merged by guessing.

Updates run only when the owner presses Refresh, with rate limits; there is no Plaid background notification or webhook processing. Data is not real-time. Disconnecting asks Plaid to revoke access and removes the stored access token, but keeps imported records as dated snapshots. Plaid and institutions may retain copies under their own policies (plaid.com/legal/#end-user-privacy-policy). Trial has 10 lifetime production Items; removing an Item does not restore a slot. Investment transaction history is not requested; adding that endpoint later may enable a fee subscription on a paid tier.

6. Sessions, logs and advertising

Authentication uses session storage and may use cookies or browser storage to keep the owner signed in. Third-party infrastructure may maintain its own technical and security logs. Atlas Life is not designed for targeted advertising, and its operator does not intentionally sell personal data. These statements do not describe or override providers' independent policies.

7. Access and security

Personal records are protected by authenticated access and per-user row-level access rules. Integration secrets are limited to server-side use. The public privacy page contains static text, not personal records. These measures reduce risk but do not guarantee absolute security or establish any certification or regulatory compliance.

8. Retention and control

Saved records generally remain until deleted or the private instance is retired. Some copies, logs and backups follow service providers' retention schedules and may take time to expire; no automatic deletion deadline is promised.

The owner can review, correct or delete individual records wherever the app provides those controls. Complete account deletion and data export are not yet guaranteed self-service tools. For this owner-operated instance, the operator controls the underlying storage.

Before a public launch, a documented request method, appropriate self-service controls and a dedicated operator contact must be supplied. This draft does not offer a button or contact address that pretends to provide full deletion or export.

9. Children

This private personal app is not intended for children under 13 and is not open to public registration. It does not claim to perform age verification.

10. Changes and contact

The operator may update this notice as the private project changes, with a revised effective date. A dedicated contact method and reviewed policy are required before any general public release. No public operator email or address has been supplied for this draft.