What we store on your device, and what we will not store until you ask.

Your choice

A first visit shows a bar: essential only, manage, or accept analytics. Reject is a real button, not a buried link. You can change this at any time.

Essential (always)

These live in local storage on this browser, not as tracking cookies. They make the product remember a room and a preference. They are not sent to PostHog.

• rm.cookie_consent — whether you allowed analytics.
• rm.theme — light, dark, or follow the phone.
• rm.kitchen — pans and kit you said you have, so scale and cookability can answer.
• rm.demo — demo mode, so a walkthrough is a kitchen rather than an empty first-run.
• Mise-en-place ticks and similar on-device cooking state for this browser.

Analytics (only if you accept)

We store a random rm.analytics_id so two events can belong to the same browser without using your name. Events go to PostHog in the EU through our server. Paths, not query strings. Never a recipe, a transcript, an email or a message. Withdraw consent from Cookie settings; we then stop sending. Hosting logs on Vercel (when deployed) are separate and ordinary for any website.

Counting visits (no cookie, everyone)

Separately from analytics, we add 1 to a counter for today’s date, the page you opened and a single source word such as youtube or instagram, taken from the link you followed. It sets nothing on your device and stores no identifier, no IP address, no query string and no referring page, so it cannot be tied to you or joined up between visits. It tells us how many people came and which link brought them, which analytics cannot, because analytics only runs for people who accept.

Third parties in the product

YouTube playback uses the privacy-enhanced youtube-nocookie.com host so watching a source does not hand YouTube a profile from our player. Signing in uses Supabase. Those are part of the feature you asked for, not a marketing pixel.