Cookies there are none

This site sets no cookies. There is no banner to dismiss and nothing for you to agree to. Since every other site asks, here is why this one does not.

What a cookie is

A cookie is a small piece of text a website asks your browser to store and then hand back on the next request. Cookies are how a site remembers that you are signed in, what is in a basket, or which language you picked. Used that way they are useful and uncontroversial.

The same mechanism also lets a site, or a company whose code that site loads, recognise the same browser again later and across other sites. That is how a record of where a browser has been gets built, and it is the part people object to.

Why most sites need a banner

Most sites load things from other companies: analytics, embedded video, hosted fonts, maps, chat widgets, advertising. Those arrive with cookies and identifiers that are not needed to show you the page, and in much of the world the law requires a site to ask before setting them. The banner is that request for permission. It exists because something is happening that you might reasonably refuse.

Why this site does not

There is nothing here to ask you about.

• It sets no cookies of its own. No preference cookie, no session cookie, no counter.
• It runs no analytics, no tag manager and no tracking pixels.
• It embeds nothing: no video, no map, no chat, no social widget, no advertising.
• Its typefaces are served from relom.games itself, so no font service sees your IP address.
• It has no forms, accounts or logins, so there is no session to remember.

A banner here would be theatre: a consent box asking your permission for something that never happens, and one more thing to click before you can read the page. We would rather just show you the page.

Your browser will still do its own housekeeping, such as caching the stylesheet and images so the site loads faster next time, and whatever extensions you have installed will do whatever they do. None of that is ours, we did not ask for it, and none of it reaches us.

If this ever changes

This is the part of the page that matters. If we add analytics, an embedded video, a hosted font, a chat widget, accounts or anything else that sets a cookie or calls another company's server, then this page is rewritten and a consent banner is built first — before the thing that needs consent is switched on.

Not in the same release. Not afterwards, once someone notices. The order is: say what it does, ask permission, then collect. A site that collects first and documents later has already broken the promise, and no amount of tidy wording afterwards puts that back.