Privacy

What is stored, in full

Two things, and both of them live in your own browser rather than on a server:

• The consent record. The answer you gave the cookie banner — whether analytics and preferences are permitted — the instant you gave it, and the theme and layout choices you make on the desk page.
• The desk inputs, if you allow them. With the Preferences category switched on, the reference price, size and tier you last quoted on the desk page are kept so the page comes back the way you left it. With it switched off, nothing is written.

There is no account, no sign-in, no email capture and no form that submits anywhere. The desk page’s arithmetic runs in the browser: the numbers you type into it are never transmitted, which is also why the desk cannot know what anyone has quoted. The exact storage keys, their contents and their lifetimes are listed on the cookies page.

The one thing that travels

The consent record is written twice: to local storage, which never leaves the machine, and to a small cookie, which by definition is attached to every request your browser makes to this site. That cookie holds two characters — one for analytics, one for preferences. It carries no identifier and nothing that distinguishes one reader from another beyond which of two switches they set, which is four possible values across every reader of the site. Nothing on the server reads it today; it exists so that a future server-rendered page can know the answer before it paints.

What is not here

No analytics of any kind. No tag manager, no pixel, no session recorder, no A/B framework, no advertising or affiliate partner, no embedded video or social widget, and no third-party script at all. The typefaces are Google’s designs but are fetched at build time and served from this origin, so opening a page here makes no request to a font host. Nobody else sets a cookie on this site, because there is nobody else on it.

The Analytics switch in the banner therefore governs nothing today. It is wired anyway, so the answer is on record before it ever governs something, and the day that changes will be dated in the changelog before it is true.

The layer this site does not control

Any site reachable over the internet is served by a host, and a request to a host carries an IP address, a user agent, a URL and a timestamp. Hosts keep such records to deliver pages, to cache them and to defend against abuse, here as everywhere. Nobid runs no analysis over those logs, joins them to nothing, and keeps no separate copy of them — but saying “we collect nothing” without saying this would be exactly the omission that makes most privacy pages worthless. Retention at that layer is the host’s and not this site’s, and this page will not quote a number it cannot verify.

Rights, and the strongest way to exercise them

Where data protection law applies, a reader has rights of access, rectification, erasure, restriction, objection and portability. Those rights bite on records held about identifiable people. Nobid holds none: there is no store to search, no export to produce and no profile to correct, so a request would be answered with a copy of this page and nothing else.

The effective exercise is therefore mechanical rather than administrative. Clearing this site’s data removes everything that exists about your reading of it, and there is no server-side copy to survive it:

1. To withdraw consent. “Cookie settings” in the footer of any page reopens the panel. Choosing “Reject all” rewrites the record with both optional categories off and stamps it with the moment of the change. Note that this changes the answer rather than deleting it — the record of having answered remains.
2. To delete it. Every current browser offers “clear site data” or “remove cookies and site data” for a single site, reached from the icon at the left of the address bar. In developer tools, the Application or Storage panel lists both entries for this origin and removes them individually.
3. What that leaves. Nothing. The next visit shows the banner again, because a missing record is treated as no answer and never as consent.

Consent is never inferred

The default for both optional categories is off, and a storage read that fails — private browsing, blocked site data, an extension in the way — is treated as no answer rather than as agreement. There is no automated decision-making about people here: the quote waterfall is arithmetic on numbers a reader typed, it reads nothing about who typed them, and it returns the same output for the same inputs on any machine.

Changes to this page

This page carries an effective date, and a change to it is dated in the changelog like any other. If the answer to “what is collected” ever stops being “the consent record, in your browser”, that will be written here before it is true, not after.