Skip to content

Privacy Policy

Stoke helps you maintain a financial independence plan. This draft describes the website, public tools and signed-in application. Joseph handles privacy questions at joseph@stokemoney.com.

Information you provide and connect

  • Identity and workspace. Your login email, authentication identity, profile details such as name and avatar, workspace membership and account preferences.
  • Financial records. Accounts, institutions, balances, holdings, transactions and connection metadata received through Plaid or SnapTrade. We also store manual accounts, balances, assets and liabilities you enter, corrections, categories, merchant rules, and which accounts and holdings you include in your plan.
  • Planning inputs. Your age, spending, contributions, goal and return or withdrawal assumptions, saved scenarios, projections and recorded plan snapshots.
  • Billing and support. Subscription and payment status, Stripe customer references, limited card details such as brand, last four digits and expiry, and messages you send to Joseph. Payment details are entered with Stripe; Stoke does not receive your full card number or security code through checkout.
  • Exports and operation. Requested transaction CSV files and export job records, sync/job status, errors, security and request logs. Export files are stored on the application server; a transaction CSV is not a full account archive.

Why we process it

We use this information to authenticate you, separate workspace data, connect and refresh authorized sources, reconcile and classify transactions, calculate and explain your plan, save your changes, process subscriptions, respond to requests, and diagnose and protect the service. Data shared in a workspace can remain available to its other authorized members.

Services that process information

  • Hosting and storage. Supabase provides authentication, database and uploaded-file storage. The web and application hosting infrastructure processes requests and operational logs.
  • Financial connections. Plaid and SnapTrade process the authorization and financial information needed for the connections you choose. Connection availability, history and freshness depend on the institution and provider.
  • Payments and email. Stripe processes checkout, subscriptions and its billing portal. Resend delivers Stoke email, including a saved FIRE Check result and its assumptions when you request one. Authentication email is delivered through the configured Supabase authentication email service.
  • Analytics. PostHog processes page and interaction events and session replay when configured. See the masking and public-tool distinctions below.

Transaction classification

When classification is enabled, TypeSafe’s Jev, or the configured OpenAI-compatible classifier, receives transaction text and attributes to suggest categories. These include merchant names and guesses, normalized description, counterparty, provider category, amount in cents, direction, currency, account and transaction type, date and metric classification, together with workspace category names. The OpenAI-compatible path also uses internal transaction and category identifiers to match results. These requests do not include connection credentials or account balances.

When configured, TypeSafe also processes posted transactions without a manual metric classification to distinguish spending, income and transfers. Those requests use the transaction fields above without the metric classification or account/transaction identifiers. TypeSafe request content must be treated as retained. We have not confirmed an account-specific retention duration or zero-retention arrangement; this draft makes no blanket claim about AI training or processor deletion.

Website, tools and browser storage

The current waitlist asks for your email address. Page events and ordinary network metadata can include browser/device information, page URLs and approximate location. PostHog is configured to mask inputs, text and element attributes in replay, omit request bodies and headers, and block marked sensitive regions. Masking is a safeguard; it does not mean every financial screen is excluded from recording. Login sessions, preferences and navigation state also use browser storage.

FIRE Reality Check. Your entered numbers stay in your browser unless you choose to save the result. Your device keeps your last check; its Forget control removes that local copy. Saving sends your email, inputs, result, changed assumptions and optional research answers to Stoke for result delivery, future plan setup and learning which scenarios to model. Check analytics record ranges and choices rather than entered amounts or exact ages. A saved server copy requires a deletion request.

Personal Finance Quiz. The quiz uses sample numbers. It does not save your answers or score in browser storage or send them to Stoke’s servers. Explicit analytics events record progress, quiz version and question identity/position, without answers, correctness or score. Its question, answer, feedback and results areas are excluded from autocapture; session replay is disabled on the quiz route.

Retention and deletion

Active app records support your saved plan and its history. Account deletion removes or relinquishes data according to workspace ownership: shared workspace records can remain for other members. Cleanup spans local records, uploaded files, exports, connections, billing and the authentication identity; a failed step can require retry or founder assistance. A minimal subject/status/timestamp marker remains to prevent deleted identities from regaining access with stale tokens.

Deletion from active app storage is distinct from copies already downloaded or emailed, retained backups and logs, and records held independently by financial, payment or other processors. Exact backup, log, export and processor retention schedules are not confirmed for publication. Do not assume disconnecting an institution or deleting an account erases every copy across these systems. Ask Joseph to confirm the scope and outcome of a request.

Your choices, requests and security

You can review connection permissions in Connections and correct supported records and assumptions in the app. To request access, correction, deletion, or removal from the waitlist, email Joseph from your login or signup address. We confirm identity, workspace authority, available scope and a suitable delivery method before fulfillment. No complete archive or automatic delivery is promised. See data request help.

Workspace access controls and protected credential storage reduce unauthorized access. No internet service can guarantee absolute security. Do not email bank passwords, access tokens or full card details. Questions and concerns go to joseph@stokemoney.com.

Approved changes to this notice need an effective date and a communication approach before publication. This draft does not establish a notification commitment.