Your privacy, in plain words

What we collect

• The pages you open. For each page, we note its address without the language part, the language you read it in, your device and browser type, the country and region your connection appears to come from, and the site that sent you, if any.
• A few things you do in lessons. We note when you play a video, check an answer in Practice (which question, and whether it was right), tick a Checkpoint, change language, or send feedback (only that you sent it, and what kind of note it was). We never record what you type.
• Languages your browser lists that Relish doesn’t offer. If your browser prefers a language we don’t have yet, we note which one, once per visit, to learn which language to add next.
• Masked replays, only if you accept. A recording of how a page looks and moves while you use it, so we can see where a lesson confuses people. Everything you type is hidden before it leaves your browser, and the feedback form is left out of replays entirely.
• The notes you send us. If you use “Suggest a correction”, your note, your email address if you add one, the page you were on and its language go to a private repository on GitHub that only the Relish team can read. They don’t go to our analytics.
• A check that you’re a person. Sending a note also runs Cloudflare Turnstile, which looks at your browser to tell people from bots.
• Your account, if you sign in. Your email address, kept so we can send you a sign-in link and recognise you next time; when and from which browser you signed in; the Checkpoints you tick and the answers you give in each lesson, kept so they are there when you come back; and a cookie that keeps you signed in. Asking for links is counted per network address for a minute, to stop abuse.

Why we collect it

To see which lessons people use and where they get stuck, so we know what to fix or write next, and to choose which language to add. We don’t sell this information, and we don’t use it to follow you to other sites.

Where it goes

• PostHog stores our analytics and replays, in the United States. PostHog’s privacy policy (opens in a new tab)
• Cloudflare serves this site, passes analytics on to PostHog and sends your sign-in links by email. Like any host, it handles your IP address and the basics of each request, and it runs the spam check. Cloudflare’s privacy policy (opens in a new tab)
• GitHub holds the notes you send, in the United States. GitHub’s privacy statement (opens in a new tab)
• Videos load from YouTube only after you press play, through its privacy-enhanced player, and then YouTube’s own rules apply. Google’s privacy policy (opens in a new tab)

How long we keep it

We use PostHog’s default retention and haven’t changed it. On the plan Relish uses today, that means analytics events are kept for a year and session replays for 30 days. Notes sent through the feedback form stay in the private GitHub repository until the Relish team deletes them. Your account and your progress stay until you delete your account, and a sign-in session lasts 30 days.

Your choices

• The first time you visit, a notice asks whether Relish may remember your browser and record masked sessions. Accept turns both on. Decline keeps both off, and Relish remembers your answer.
• Either way, Relish counts page views and the actions above without cookies and without storing anything on your device, so those counts can’t follow you from one visit to the next.
• What Relish keeps on your device: your language (a cookie called NEXT_LOCALE), your theme and your answer to the notice (in local storage). If you sign in, a cookie called better-auth.session_token keeps you signed in for up to 30 days. If you accept, PostHog also keeps a random ID and your session in a cookie and in local storage, for up to a year.
• If you have an account, its page lets you sign out, download everything Relish stores about you as a JSON file, or delete the account, which removes your account, your sign-ins and your progress at once.
• Change your mind at any time with “Privacy choices” in the footer of every page.
• To stop even the cookie-free counting, turn on your browser’s tracking protection or use a content blocker. Relish works the same without it.

Questions or requests

Use “Suggest a correction” at the bottom of any page, choose “An idea”, and tell us what you’d like to know or have deleted. We read every note.