Cookies

Essential cookies only

CryptoBuddy uses only the essential cookies listed below. We do not use optional, analytics, tracking or advertising cookies, so there is no cookie banner and nothing to accept or reject.

When you arrive from one of our links, the link or campaign that brought you (for example a utm_ tag, a referral or tracked link, or an ad click id) travels in the page address into sign-up and is recorded against your new account on our servers. No cookie is used for this.

Strictly necessary cookies

`sb-<project>-auth-token` (sometimes split into numbered parts such as `.0` and `.1`) — the Supabase sign-in session that keeps you logged in. Essential. Up to 400 days, renewed while you use the product and removed when you log out.

`sb-<project>-auth-token-code-verifier` — a one-time security code used while you sign in with Google or reset your password. Essential. Deleted as soon as that sign-in or reset completes.

`cb_tz` and `cb_tzid` — your timezone offset and timezone name, so the app can work out your local day for “today’s scan” and send the weekly email at 09:00 your time. Essential. 1 year.

`cb_signup_picks` — set only when you sign up with Google: carries whether you ticked the sign-up email box through Google’s sign-in so we can honour that choice. Essential. Up to 1 hour, deleted as soon as sign-up completes.

`cb_view_as` — staff accounts only: lets the founder preview the product as another member type (trial, plan or billing state). Essential for that tool. 12 hours.

Payment and sign-in providers

Stripe sets `__stripe_mid` (1 year) and `__stripe_sid` (30 minutes) when its payment form loads on the checkout step. They are used to prevent fraud and are strictly necessary to take a payment; Stripe’s own cookie policy applies.

Google sign-in runs on Google’s own pages and may set Google cookies under Google’s policies. External links you follow are covered by the destination site’s policies.

Product measurement

We measure how the product is used on our own servers (which features are used, tied to your account identifier). This needs no extra cookie beyond your sign-in session. We do not use a browser analytics script, advertising cookies or session recording. The Privacy Policy explains how this information is handled.

Storage in your browser

Some settings and feature state are kept in your browser’s own storage (local storage, or session storage that is cleared when you close the tab). They stay on your device, are not sent to us as cookies, are not used for tracking or advertising, and remain until you clear them or the feature removes them:

Display: `cb-simplify-theme-v2` and `cryptobuddy-theme` (light or dark theme), `cb-palette` (colour palette), `cb-simple-nav` (full or compact navigation) and `cb:sound` (sound on or off).

Guides and onboarding: `cb:guides:v1:…` (which guides you have seen, or that you turned them off), `cb:trial:…` and `cb:trial-goal` (your trial checklist progress, the goal you picked and the dismissed tour card) and `cb:getting-started:v1:…` (the dismissed getting-started card).

Charts: `cb:charts:last` (the last chart you opened), `cb:charts:prefs` (your chart settings) and `cb:charts:candles:…` with `cb:charts:candles-index` (a short copy of recently viewed price history so a chart opens instantly).

Work in progress: `cb:support-draft:v1` (an unsent support message), `cb:active-generation:…` (lets an analysis that is still running resume if you reload) and, in session storage, `cb:reveal-batch` (new results to reveal when a generation finishes) and `cb:usage-nudge` (a usage notice you have already seen this session).