Your recent, watchlist and portfolio tickers are listed when the field is empty. Press Enter to build the selected strategy type on the chosen ticker. Press Option or Command with Enter to change the strategy type.
Get started

Legal

Privacy Policy

Terms of service

This page states what optiontracker.app collects, why it is collected, where it lives, and how to get all of it out — or delete all of it — whenever you choose.

What is collected, and why

Account

An email address and a password. The password is stored as a hash by Supabase, the authentication provider — we never see it. A display name is optional and appears only to you and to us — the site has no public profiles.

What you put in

Saved trades, wheel cycles, stock lots, realized trades, watchlists, alerts, notes and imported trade history. These records exist so the trackers can do their arithmetic; they are stored against your account and only you can read them.

Copilot conversations

Messages you send the copilot are processed by Anthropic, the AI provider, to produce the reply, and screenshots submitted to the brokerage-screenshot importer are read the same way. Signed-in conversations are kept as chat history in your account and deleted with it. Anonymous copilot turns are held in a short-lived server-side session and are never written to the database.

Feedback

What you type into the feedback box, plus an optional reply address. Each submission also gets an AI-written summary, produced by Anthropic, for triage, and is emailed to us through Resend, the email provider — the email carries your words and, if you gave one, your reply address. Feedback deliberately outlives its author: deleting your account keeps the reports you sent but strips your account id, device id and reply address from them.

Usage events

Funnel moments — a page view, a save, a signup — are logged so we can see which parts of the product get used. Events from a signed-in session are keyed to your account id and are deleted with the account. Events from an anonymous visit are keyed to a salted hash of a random cookie (described below); the cookie’s value itself is never stored, and the hash cannot be traced back to a device.

Product analytics and session replay

The same funnel moments, plus page views, are also sent to PostHog, a product-analytics provider, and PostHog records a masked replay of how the pages are used — where you click, scroll and move between screens. Every piece of text on the page except the navigation labels, and everything you type, is replaced with asterisks before it leaves your browser; images and charts are blanked; addresses in links lose their query strings and a saved trade’s ticker. A recording therefore contains no dollar figures, position sizes, strikes, tickers of saved trades, account details, email address or name; no network traffic and no console output are captured. Events and recordings from a signed-in session are keyed to your account id — never your email or name — and an anonymous visit is keyed to a random id PostHog keeps in your browser’s local storage. Nothing is sent when your browser sends Do Not Track or Global Privacy Control, and nothing is sent from our own operator and test accounts.

Pro launch list

An email address and the page that captured it, collected before Pro went on sale (“tell me when this ships”). No name, no card. A signup made while signed in is linked to your account, and deleting the account deletes it. A signup made while signed out stores the salted device hash described under usage events, which connects the signup to the same visitor’s anonymous events; that signup belongs to no account and is kept until the launch announcement is sent, or until you ask for it to be removed.

Technical

Requests carry an IP address, used for rate limiting under a hashed key, and Vercel, the hosting provider, keeps standard server logs. When you sign in, Supabase also records the session’s IP address; the Security section of your account page shows it beside each signed-in device, and the address is deleted with the session. There are no advertising scripts. Three analytics scripts run on the site: PostHog, described above, and Google Analytics and Ahrefs Analytics, which measure site traffic — pages, sources and sessions.

Market data

Quotes, chains and news come from Massive, a market-data vendor, 15 minutes delayed. Your browser never talks to the vendor: every request goes through our servers, which forward the ticker being looked up and nothing about you. The vendor’s API key stays on the server.

Cookies and browser storage

  • Session cookies — set by Supabase when you sign in, so you stay signed in.
  • ot_auth — a yes/no hint that a session exists, so public pages can show the right buttons. It identifies nobody.
  • ot_aid — a random value, kept for a year, so an anonymous visitor counts as one visitor rather than several page views. Only a salted hash of it ever reaches the database.
  • Browser storage — anonymous saved trades live in your browser’s local storage and never leave the device until you create an account; your theme choice is kept the same way.
  • Analytics storage — PostHog keeps a random device id and session id in local storage (it sets no cookie here); Google Analytics sets its _ga cookies.

There are no advertising cookies and no cross-site tracking cookies.

Where your data lives

In a Postgres database managed by Supabase. Every table that holds your records carries row-level security enforced by the database — for your trading data it is keyed to your user id on every operation, and a handful of operational tables (feedback, usage events, the launch list, billing records) are instead readable only by the site operator. A script signs in as a second user and confirms the core account tables show it nothing. The site itself is served by Vercel.

Who processes your data

  • Supabase — database and authentication.
  • Vercel — hosting and server logs.
  • Anthropic — copilot messages, imported screenshots and feedback summaries, to produce the AI output described above.
  • Resend — email delivery: the signup and sign-in emails the authentication system sends you, and the email that forwards each feedback submission to us — your words and, if you gave one, your reply address.
  • Stripe — payments for Pro: subscribing creates a Stripe customer under your email, and the checkout form — card details, billing address — is Stripe’s own page. Card details never reach our servers.
  • Massive — receives the tickers you look up, and nothing about you.
  • PostHog — product-analytics events keyed to your account id or a random device id, and the masked session recordings described above.
  • Google (Google Analytics) and Ahrefs — site-traffic analytics.

That list is complete. Your data is never sold, no advertiser has access to it, and nothing is shared beyond these processors unless the law requires it.

Export and deletion

Your account page exports everything to JSON in one click — trades, cycles, lots, realized trades, watchlists, alerts and chat history, with the row counts listed before you download. The same page deletes the account: it states the exact number of rows that will be removed, asks you to type DELETE, and then removes them permanently, valuation snapshots included. The exceptions are feedback, which is kept with your identity stripped, as described above, and billing records if you subscribed, described under Retention. Anonymous saves exist only in your browser — clearing the browser’s site data removes them.

Retention

Account data is kept for as long as the account exists and destroyed when you delete it — launch-list signups made while signed in included. A launch-list signup made while signed out belongs to no account and is kept until the launch announcement is sent or you ask for its removal. Billing records outlive the account: if you subscribed, the record of what was bought, when, for how much and under which email is kept for accounting after deletion removes everything else. Anonymous copilot sessions live in server memory and expire on their own. Anonymous usage events carry no recoverable identity from the moment they are written.

Children

The service is not directed at children, and no account should be created for anyone under 18.

Changes

When this policy changes, the effective date at the top changes with it, and a material change will be announced on the site.

Contact

The feedback box in the footer below reaches us directly — with or without an account — and takes a reply address if you want an answer. Questions about your data, an export or a deletion all belong there.