Cookie Policy
The short version, because there isn't much to say: Yamma doesn't use tracking or advertising cookies.
In short
- Our main cookie is the session cookie that keeps you signed in. It's strictly necessary and can't be turned off without logging you out. If you pick a plan on the pricing page, a second short-lived cookie carries that choice into sign-up and is deleted once used.
- Everything else that persists on your device is localStorage. Mostly UI preferences like theme and dismissed alerts. It stays on your device and is never read by our servers.
- Our analytics (Vercel Analytics) is cookieless and doesn't identify you.
- Because we set no non-essential cookies, we don't show a cookie consent banner. There's nothing optional to consent to.
- Subscribing to a plan or managing billing takes you to Stripe's own hosted pages. Their cookies there are covered by Stripe's policy, not this one.
1. What we actually use
One essential cookie, a handful of localStorage entries for UI preferences, and a cookieless analytics tool.
| Name | Type | Purpose |
|---|---|---|
| Supabase auth session | Cookie | Keeps you signed in. |
| yamma-theme / yamma-theme-mode | localStorage | Remembers your light/dark mode and colour theme before your account preferences load. |
| yamma-action-centre-intro-seen | localStorage | Remembers you've seen the first-run tooltip so it doesn't show again. |
| yamma_plan_intent | Cookie | Remembers which plan you picked on the pricing page so it's still selected after you sign up. Cleared as soon as it's been used. |
| yamma-home-activity-view | localStorage | Remembers whether you last viewed your spending as a timeline or a calendar. |
| Dismissed nav alerts | localStorage | Remembers which alerts you've dismissed so they don't reappear. |
| Draft form inputs (e.g. the budgets grid) | localStorage | Protects unsaved input if you accidentally navigate away or lose connection. |
| Vercel Analytics | Cookieless | Aggregate, anonymised page-view counts. Doesn't set a cookie or identify you individually. |
2. Why no consent banner
Under UK PECR, consent is only required for storage on your device that isn't needed for a service you've asked for. Everything we store is, so there's nothing to ask permission for.
The Supabase session cookie is "strictly necessary". Required for you to be logged in at all, which UK cookie law (PECR) exempts from consent requirements. The plan-choice cookie is only set when you pick a plan, to carry that choice into sign-up, and is deleted as soon as it's used.
PECR covers more than cookies: it applies to anything stored on your device, localStorage included. Each localStorage item above exists only to make a feature you're using work the way you set it (your theme, a draft you haven't saved yet, alerts you've dismissed) stays on your device, and is never sent to or read by our servers. That's storage needed to provide a service you've asked for, which PECR exempts from consent.
If that ever changes. For example, if we add a genuinely optional analytics or marketing cookie in future. We'll add a proper consent banner before we do, not after.
3. Controlling this yourself
Clearing cookies or site data in your browser will log you out and reset your local preferences. Nothing more.
Because we set so little, there's not much to manage. Clearing your browser's cookies for Yamma will simply sign you out; clearing site data will also reset your local theme preference and dismissed-alerts list until you sign back in.
4. When you subscribe to a plan
Subscribing or managing your subscription takes you to Stripe's own checkout and billing pages, which are subject to Stripe's cookie policy, not ours.
Yamma doesn't embed any payment form or Stripe script directly on its own pages. Subscribing to a plan or managing an existing subscription takes you to a page hosted directly by Stripe (Checkout, and the Customer Portal). While you're on those pages you're on Stripe's domain, not Yamma's, and any cookies set there (Stripe uses some for fraud prevention and to process your payment) are governed by Stripe's own cookie policy, not this one. Once you're redirected back to Yamma, this policy applies again as normal.
Questions about any of this, or want to exercise one of your data rights? Contact help@yamma.money.