NOBIDLegal
Effective 6 September 2026
Cookies and local storage
This site sets one cookie and writes one entry to local storage, and both hold the same thing: the answer you gave the banner. Below are the three categories that banner offers, the two keys by name, and what removing them does.
The three categories
| Category | What it covers | Status |
|---|---|---|
| Strictly necessary | One entry recording the answer you give here, plus the theme and layout choices you make on the desk page. No identifier, no profile, nothing sent anywhere. | In use · cannot be disabled |
| Analytics | Aggregate page counts, with no cross-site identifier. The site runs none today; this switch decides the answer if that ever changes, and the changelog will say so on the day it does. | Not currently used |
| Preferences | Remembers the reference price, size and tier you last quoted on the desk, so the page comes back the way you left it. Stored in your browser and never transmitted. | In use when enabled |
The middle row is the unusual one. Analytics is offered as a switch for something that does not exist: there is no analytics package on this site, no tag manager and no third-party script of any kind, so today the switch governs nothing. It is wired anyway, because a desk will be asked about it in diligence and because a reader who declines something ought to have their answer recorded whether or not it currently bites.
What is stored, by name
| Key | Kind | Contents | Lifetime |
|---|---|---|---|
nobid.consent.v1 | Local storage | JSON with four fields: necessary (always true), analytics, preferences, and at — the ISO instant the answer was given. | Until site data is cleared |
nobid_consent | Cookie | Two characters: a or - for analytics, p or - for preferences. Accepting everything stores ap; rejecting everything stores --. | Max-Age 15,724,800 seconds — 60 × 60 × 24 × 182, so 182 days. Path /, SameSite Lax, and Secure whenever the page is served over HTTPS. |
nobid.desk.v1 | Local storage | The inputs you last quoted on the desk — quote asset, reference price, size, tier, curve progress and the ether rate. Written only while the Preferences category is on, and deleted the moment it is switched off. Never transmitted; the desk page does its arithmetic in your browser. | Until site data is cleared, or Preferences is withdrawn |
Why the answer is written twice
The cookie exists because the answer to a cookie question that is not itself a cookie is a category error, and because a page rendered on the server will eventually need to read the answer before it paints. Local storage exists because a cookie is capped at a few kilobytes shared across the whole origin, and this is the record that has to survive.
Of the two, only the cookie travels: local storage never leaves the machine, while a cookie is attached to every request the browser makes to this site. Two characters, four possible values across every reader — enough to decide whether to paint a banner, not enough to tell anyone apart. Nothing on the server reads it today.
Nobody else sets anything
There are no third-party cookies here, because there is no third party. No advertising or affiliate partner, no embedded video or social widget, no session recorder. Typefaces are fetched at build time and served from this origin, so a page load makes no request to a font host. If any of that ever changes it will be dated in the changelog, and the Analytics switch will be doing something before it is described as doing it.
Nothing is stored until you answer
Both optional categories default to off, and a storage read that fails — private browsing, site data blocked, an extension in the way — is treated as no answer rather than as agreement. Consent is never inferred from continued reading, from scrolling, or from dismissing anything.
One asymmetry is worth stating rather than denying: in the banner, “Reject all” and “Accept all” sit side by side in the same row and are one click each, but the accept is filled and the reject is outlined. That is a difference in emphasis. It is also the whole of it — there is no extra step, no pre-ticked box, and nothing is loaded before either is pressed.
Withdrawing consent
“Cookie settings” in the footer of every page reopens the panel, which is where the control lives rather than on this page: an answer has to be withdrawable from wherever you happen to be reading, not only from the page that documents it. Choosing “Reject all” there rewrites the record with both optional categories off and stamps it with the moment of the change.
That changes the answer rather than deleting it. To remove both entries outright, clear site data for this origin in your browser; the privacy page describes exactly where that control sits and what it leaves behind, which is nothing.