Cookies & browser storage
Last updated: October 21, 2026 · Version 2026-08-03
Placeholder — pending legal review
This page is a plain-language description, not legal advice, and has not yet been reviewed by counsel. It is an accurate account of what the product does today; the wording may change.
The short version
Relme sets no advertising cookies and no cross-site tracking cookies. Nothing here is sold or shared with data brokers. What we do store falls into three groups: what is needed to keep you signed in, what remembers a setting you chose, and analytics — and analytics is off until you allow it.
One thing is separate from all three: opening someone's public profile, or one of their public project pages, tells us the page was read, and opening the code on their Relme Card tells us the card was scanned, so its owner can see how many people visited. That stores nothing on your device, and the analytics choice below does not switch it off.
Analytics in your browser
Checking this device…
The choice is stored in one first-party cookie on this device, so it does not follow you to another browser. Changing it takes effect immediately — no reload, no sign-in required.
Everything we store, in full
This list is generated from the same registry the code uses, so it is the complete set — not a representative sample.
Strictly necessary
Relme cannot work without these. They keep you signed in and remember the analytics choice you made. There is no way to switch them off and still have an account.
sb-<project>-auth-token
Cookie · Set by Relme · Until you sign out; refreshed while you keep using Relme.
Keeps you signed in. Set by our authentication provider (Supabase) when you log in, and read on every request to know it is you. Large sessions are split across numbered cookies of the same name.
sb-<project>-auth-token-code-verifier
Cookie · Set by Relme · Minutes — deleted as soon as sign-in completes.
A one-time value that completes a sign-in or email-confirmation link securely. Written when the link is requested and consumed the moment you land back on Relme.
relme_cookie_consent
Cookie · Set by Relme · 6 months, or until you change the choice.
Remembers the analytics choice you made on this device, so you are not asked again. Holds only that choice and the version of this page it was made against — no identifier.
relme_cookie_asked
Session storage · Set by Relme · One browser tab — it dies when the tab closes.
Only written if your browser refuses the cookie above. It records that the analytics question was already put to you, so the bar stops reappearing on every page. It records no answer — a choice that could not be stored still counts as 'no'.
Sentry (error reports)
No browser storage · Third party · Nothing is stored on your device.
When a page breaks, a scrubbed error report is sent to Sentry so we can fix it. It stores nothing in your browser, records no session replay, and everything you wrote is stripped before the report leaves your device — only ids and the technical failure survive. Runs only where the service is configured.
Your preferences
Small settings you chose yourself, kept on this device. They contain no identifier and are never sent to us or to anyone else — clearing your browser storage removes them.
relme-theme
Local storage · Set by Relme · Until you clear your browser storage.
A copy of your account's light/dark/system choice, so signed-in pages open in it with no flash. Pages you see signed out never read it.
relme-public-theme
Local storage · Set by Relme · Until you clear your browser storage.
Your light/dark choice on public profile pages (the sun/moon toggle). Only written when you click the toggle; until then those pages follow the profile owner's default.
relme-getting-started-collapsed
Local storage · Set by Relme · Until you clear your browser storage.
Whether you collapsed the Getting started checklist.
relme-studio-hint
Local storage · Set by Relme · Until you clear your browser storage.
Whether you dismissed the Profile Studio hint.
relme-interview-voice-replies
Local storage · Set by Relme · Until you clear your browser storage.
Whether Relme reads its replies aloud.
relme-interview-voice-rate
Local storage · Set by Relme · Until you clear your browser storage.
Your spoken-reply speed.
relme-interview-voice-id
Local storage · Set by Relme · Until you clear your browser storage.
Which of your device's voices reads replies aloud.
relme-interview-auto-advance
Local storage · Set by Relme · Until you clear your browser storage.
Whether Build with Relme moves on to the next question on its own.
library:qw
Local storage · Set by Relme · Until you clear your browser storage.
The width you dragged the question column to in the Question desk.
library:ew
Local storage · Set by Relme · Until you clear your browser storage.
The width you dragged the evidence column to in the Question desk.
relme-contact-draft
Local storage · Set by Relme · Until you send that request, empty the message, or clear your browser storage.
An unsent contact request you are writing — its reason and message, and whose page it is for — so it survives a reload. One draft at a time, never sent anywhere until you choose Send.
relme-vouch-draft
Session storage · Set by Relme · One browser tab — deleted once the vouch is picked up again, or when the tab closes.
A vouch you wrote before signing in — which project it is for, how you know the person, and your words — held only while you sign in with Google or enter a two-step code, then sent and deleted. Nothing is sent until you chose Send.
relme-pulse-offered
Session storage · Set by Relme · One browser tab — it dies when the tab closes.
Remembers that the occasional “How's Relme?” card was already offered today in this tab, so it never reappears while you navigate. Holds only the date — no identifier, never sent anywhere.
Analytics
Measurement, so we can see which parts of Relme people actually finish. Off until you allow it, and stopped the moment you decline.
relme_a_sid
Session storage · Set by Relme · One browser tab — it dies when the tab closes.
A random id that ties the page views in one browser tab together, so we can see where a flow gets abandoned. It is created fresh per tab, is never linked across tabs or visits, and is deleted the moment you decline.
Vercel Web Analytics
No browser storage · Third party · Nothing is stored on your device.
Aggregate page-view counts from our host, Vercel. It stores nothing in your browser and sets no cookie, but the page view is sent to Vercel. Without your permission the script is never loaded; if you allow it and then turn it off, page views stop at once and the script itself is gone on your next page load.
Visit counts on public profiles
Only on public profile and project pages, and when a Relme Card's code is opened. Opening them tells Relme the page was read, or the card was scanned, so the person whose profile it is can see how many people visited. This is separate from analytics: it stores nothing on your device, and the analytics choice above does not switch it off.
Profile visit count
No browser storage · Set by Relme · Nothing is stored on your device. The visit record on our side is kept until we delete it — see the Privacy Policy.
When you open someone's public profile or one of their public project pages, your browser sends Relme one short message saying the page was read: the profile's handle (and which project, on a project page), a share-link code if the link you followed had one, the source the link was tagged with (its utm_source, sent only if it names a site on our fixed list), and the address of the page that sent you there — of which we keep only the site name (for example google.com), never the full address. Our server adds whether the request looks like it came from a person's browser, and a visitor code made from your IP address, your browser's User-Agent string, the profile, a random value replaced every week and a secret kept only on our servers — so repeat visits to that profile in the same week count as one visitor, and the code is different on every other profile. Your IP address itself is not stored with the visit. The profile's owner sees totals, never a list of visits. Nothing is written to your browser, and turning analytics off does not stop this message.
What the choice does not cover
Turning analytics off stops analytics in your browser: the third-party script is not loaded, our own analytics beacon is not sent, and the per-tab id is deleted. If you allow it and later turn it off, measurement stops immediately and the script is gone on your next page load.
It does not stop the visit count on public profile pages. Whatever you chose, opening someone's public profile still sends one message from your browser saying the page was read, so its owner can see how many people visited. That message writes nothing to your device; what we keep from it is described under “Visit counts on public profiles” above and in the Privacy Policy. Asking a public profile's chat a question is counted for its owner in the same way, by our server rather than your browser, and so is scanning a member's Relme Card: the scan is recorded when the card's link is opened, before you reach the profile.
It does not stop our own servers recording an action you took. When you are signed in, that means things you did in your account — a draft published, a suggestion approved, or an app you connected (such as your own Claude or ChatGPT) calling one of Relme's tools, recorded by name (which tool, and whether it worked). The Relme team can see these actions, account by account, to improve the product and to ask you for feedback — never what you wrote: no story or question text, and nothing a connected app said. They are never shown to other people. They are not part of your account data export, and when you delete your account they are kept but no longer linked to you, so the totals they add up to stay accurate.
A small number of these are also recorded when you are not signed in — today, opening our home page, our sign-up page or our membership page, and pressing the join button there, so we can see how many people arrive and how many wanted to join before we were ready. A record like that is stored with no account attached, which also means it is not part of anyone's export and is not removed by deleting an account, because there is nothing linking it to a person. We are telling you rather than letting you find the gap between this sentence and the truth.
Our servers also keep short-lived operational logs (for example an IP address used for rate limiting and abuse protection). That is not something a browser setting can switch off, and it is covered in the Privacy Policy.
Turning things off yourself
Your browser can block or delete all of the above. Blocking the strictly-necessary cookies will sign you out and prevent you from signing back in; clearing local storage resets the preferences listed above and nothing else. Relme keeps working either way, minus those conveniences.
For completeness: our codebase contains an unused interface component that would set sidebar_state, but it is not part of the running app and that cookie is never created. We list it here rather than let you discover a discrepancy.
Changes and contact
If what we store changes materially, the version above changes with it and everyone is asked again — a previous answer stops counting until it is re-made. A correction that changes neither what we store nor what the choice controls moves the date but not the version, so an answer you already gave still stands. Questions: hello@relme.io.
See also our Privacy Policy and Terms of Service.