COOKIES AND STORAGE
What we keep in your browser.
One cookie, one offline cache, and nothing else. No advertising, no analytics, no tracking, no third-party storage — and therefore no banner, because a banner for a choice that does not exist is theatre.
How to read this
Drafted by the engineering team so that every factual statement traces to running code. Not reviewed by a qualified data-protection lawyer. Last checked September 13, 2026. Where we cannot yet make a commitment, the document says so, dates it, and names what would close it. We would rather you found the gap here than found it yourself.
What would change that: A review is commissioned when the first controller who is not us signs the processing agreement, or at the first paid business customer — whichever comes first. It is deferred rather than skipped: today there is no customer to make these statements to.
What changed in this version: New document. There was no published storage inventory before, and a product that stores anything in a browser owes one whether or not it needs consent for it.
A printed copy carries this version and its date, and leaves the navigation behind.
Everything we store in your browser
| Name | Kind | What it is for | How long | Who gets it | Needed? |
|---|---|---|---|---|---|
hr_session | Cookie | Remembers that you are signed in. Without it every page would ask again. httpOnly, so no script on the page can read it, and it never leaves this site. | Up to 7 days, or until you sign out | Host.Rodeo only | Necessary |
hr_clint_thread | Cookie | Which conversation with Clint you are in, so it survives moving between pages. It holds an identifier, never any of what was said. | 7 days | Host.Rodeo only | Necessary |
hr_clint_visit | Cookie | Only if you talk to Clint before making an account: the handle that finds your thread, so signing up does not throw the conversation away. httpOnly. We hold only a one-way digest of it, so the handle in your browser is the whole of the authority over that thread. | 24 hours | Host.Rodeo only | Necessary |
hr_oidc | Cookie | Only during a sign-in through your organisation: keeps that one attempt honest. | 10 minutes | Host.Rodeo only | Necessary |
host-rodeo-e0-static-… | Cache Storage | A copy of this build's own files and the offline page, so a page still opens when your connection drops. Public files only. Nothing about your account, no answers and no API replies are ever put in it. | Until a new version replaces it, or you clear site data | Stays in your browser | Necessary |
How to stop any of it: Sign out, or clear this site’s data in your browser. The service stops working the way it does with it, which is what “necessary” means.
Every one of these is needed for the service to work, so there is nothing here to consent to and no banner asking you. A banner with nothing behind it trains people to click through the ones that matter.
Why there is no cookie banner
Consent is required for storage that is not strictly necessary for a service you asked for. Everything in the table above is strictly necessary: one of them is how the site knows you are signed in, and the other is how a page still opens when your connection drops. There is nothing optional to consent to, so asking you would be a decision-shaped thing with no decision inside it.
If that ever changes — if we ever want to store something optional — you will get a real choice, refusing will be exactly as easy as accepting, refusing will keep the service working, and nothing optional will be stored before you have chosen. Until then, this page is the notice and there is nothing to switch off.
Clearing it yourself
Signing out clears the session cookie and the copy of your own data the page was holding. Clearing site data in your browser removes everything in the table, including the offline cache; the site will simply fetch a fresh copy next time. Nothing in your browser is needed to recover your account.
None of it is readable by anyone else's site, none of it is sent anywhere but back to us, and none of it identifies you to a third party — there are no third-party scripts on any page here, which is enforced by the security policy the browser applies rather than by our good intentions.
Earlier versions
Every version this document has had. The one above is what you are reading now.
- Version 1.0 took effect September 12, 2026— current
We do not publish the superseded text, because a stack of old contracts on a public page is a way to be read out of context. The version you accepted stays retrievable: ask us naming the version and we will send you that exact text.
The rest of the shelf
Questions about any of this reach a real person at the contact page, with or without an account — [email protected] for anything about your own data, [email protected] for a security report. We answer within 10 working days.