Cookies
Cookies
Five cookies, all of them doing a job you asked for. No analytics, no advertising, and nothing that follows you anywhere. The payment form sets its own, and only while you are paying.
updated 2026-09-13
Why there is no consent banner
Consent is required for cookies that are not strictly necessary — analytics, advertising, anything that builds a profile or follows you between sites. The rule that requires it, in the ePrivacy Directive, exempts storage that is strictly necessary for a service the user explicitly requested.
Every cookie below is in that exempt class: they exist to keep you signed in, to finish a sign-in you started, and to remember a switch you pressed. There is no analytics script on this site, no advertising, and no social embed.
One third party does set cookies, and only in one place. The payment form is the merchant of record's own, shown inside the payment page, and it stores what it needs to process the card and to resist fraud. That is storage strictly necessary for a payment you asked for, so it is exempt on the same ground as the rest — but it is a third party, it is not ours, and saying otherwise would be untrue. It is set nowhere else on this site: browsing the register sets nothing.
If that ever changes — if an analytics tool is added — a banner appears first, it defaults to off, and nothing non-essential loads until you say so. That is a promise about the order of events, not an intention.
The cookies
All five are set by this site only, sent over HTTPS, and marked so that other sites cannot read them. Four of the five are httpOnly, which means the page itself cannot read them either — so a script injected into the page cannot steal your sign-in.
| Name | What it does | How long |
|---|---|---|
oam_at | Keeps you signed in between page loads. | 15 minutes |
oam_rt | Renews the one above, so a visit does not end every quarter of an hour. Signing out ends it immediately. | 30 days, or until you sign out |
oam_pending | Holds a half-finished sign-in between the password and the emailed code, so reloading the page does not lose your place. | 10 minutes |
oam_exp | When the sign-in above expires, as a number. The only one the page itself can read, and it holds no identity — just a clock reading, so the page knows when to renew. | 30 days |
oam_oauth | Set only if you choose Continue with Google, and only for the length of that round trip. It is what proves the sign-in that comes back from Google is the one you started. | 10 minutes |
Not one of them is set before you sign in. Browsing the register, reading a minute, or buying one as a guest sets no cookie at all.
Two things kept in the browser
These are not cookies — they stay in your browser and are never sent to us, so they are listed for completeness rather than because they travel anywhere.
| Name | What it does |
|---|---|
oam_clock | Whether you chose the 12-hour or 24-hour clock. Set only when you press the switch. |
oam_refresh_at | A timestamp that stops several open tabs renewing the same sign-in at the same moment. Never leaves the browser. |
Turning them off
Your browser can refuse or delete any of them, and signing out removes the sign-in ones from both your browser and our records. Refusing them does not stop you reading the register or buying a minute — it only means you cannot stay signed in, because staying signed in is precisely what they do.
Payment
Paying takes you to the merchant of record's own checkout, on their domain, under their cookie policy. We do not embed their script here, and no payment page is loaded inside this one. See the terms for who the merchant of record is.