Privacy Policy

Effective 3 August 2026 · the short version: we store almost nothing, and sell none of it

What we store, and why

DataWhyWhere
Email address + password hashYour sign-inFirebase Authentication (Google)
Your tier and its expiryDeciding what to unlockFirestore
Timezone, chosen symbol, watchlistSo your settings follow you across devicesFirestore + your browser
A few flags about this browser: whether it has signed in here before, your last known tier, which tips you dismissedSo a page opens the right way before the network answers (the sign-in tab, the locks)Your browser only — never sent to us

That is the whole list. Passwords are handled entirely by Firebase Authentication — we never see them.

What we don't do

Payments

Card and payment details are collected and processed by our merchant partners (for example Whop) on their own pages, under their own privacy policies. We never receive your card number. What we receive is the email used at checkout, so we can activate the matching account.

The embedded widgets

If you meet our widget on someone else's site: it sets no cookies and runs no analytics. It fetches public statistical data from our servers, which involves your IP address in the ordinary way any web request does; we don't log it beyond standard hosting logs.

Infrastructure

The service runs on Google Firebase (hosting, authentication, database). Google processes data on our behalf under its own terms: firebase.google.com/support/privacy.

Your choices

Both of these are buttons on your account page — neither needs to go through us, and neither waits on somebody reading email.

Two limits we would rather state than let you discover: our nightly backups still hold a copy until they rotate out, which takes at most 30 days; and if you bought a plan, the payment processor keeps its own record for accounting, which we cannot delete on your behalf. Deleting an account does not refund Pro time already paid for.

Changes

Material changes will be dated at the top of this page.