Cookie policy

The short version

This site sets no cookies of its own. It loads no analytics, no advertising, no tag manager, no social widget, no embedded video and no chat box, and it runs no third-party JavaScript at all. There is consequently no consent banner, because there is nothing to consent to.

That is the whole answer for most visitors. The rest of this page exists because "we use cookies to improve your experience" is the standard formula and is usually untrue in one direction or the other, so it is worth setting out exactly what does and does not happen.

What a cookie is, and what else counts

A cookie is a small file a website asks your browser to store and send back on later visits — how a site recognises that two requests came from the same browser. Cookies set by the site you are visiting are first-party; cookies set by another domain whose code the page loads are third-party.

The rules also cover technologies doing the same job by other means: local storage, session storage, IndexedDB and tracking pixels. This policy covers all of them, because a site avoiding cookies while storing an identifier in local storage would be following the letter of the rules and not the point.

Cookies this site sets

None. No first-party cookie, no local storage entry, no session storage entry and no IndexedDB database is created by this website.

There is also no preference to remember: no theme toggle, no language switch, no dismissible banner, no basket and no login. Nothing a cookie would be for, even a harmless one.

Third-party cookies

None, and that follows from how the site is built rather than from a policy that could quietly change. The pages load no external script, no external stylesheet, no external image, no iframe and no font from a third-party service — the typefaces are served from this site's own files.

So no other company learns you visited this site by way of its code running on these pages. That is a description of what the current build does, and this page is updated if it stops being true.

The hosting network

This site is served by Cloudflare. A network of this kind may set a strictly necessary cookie of its own to route traffic or to distinguish an automated request from a person, independently of anything in this site's code. Where that happens it is exempt from the consent requirement, because it exists to deliver the service you asked for rather than to track you.

Nothing in the site's own configuration enables an interstitial challenge or a bot-protection page, so in normal operation no such cookie is expected. The enquiry form's protection against automated submission is a hidden form field, which stores nothing in your browser.

Why there is no consent banner

Consent is required for cookies that are not strictly necessary. This site sets none, so there is nothing for a banner to ask about, and showing one would be theatre: a dialogue collecting a decision about something that does not exist, plus a click for every visitor.

If a future version introduces anything requiring consent — analytics, an embedded video, a chat widget — a banner will be added before that feature ships, and this page will list what it covers. The order matters: a banner appearing at the same time as the tracker is the only honest sequence.

How to control cookies anyway

You do not need this site's cooperation, and the controls are worth knowing regardless of what any individual site claims. Every current browser can block cookies, block third-party cookies specifically, delete what is stored, and show you exactly what a site has set.

• Chrome: Settings → Privacy and security → Third-party cookies; per-site under Site settings
• Firefox: Settings → Privacy & Security → Cookies and Site Data, with Enhanced Tracking Protection above it
• Safari: Settings → Privacy, including Prevent cross-site tracking
• Edge: Settings → Cookies and site permissions
• Any of them: open developer tools and read the storage panel to see what a site actually stored

Server logs are not cookies

Serving you a page reveals your IP address to the hosting provider, which keeps short-lived request logs. That is separate from cookies: it happens in the provider's infrastructure rather than in your browser, and blocking cookies does not affect it. What those logs hold is covered in the privacy policy, where it belongs.

Changes to this policy

This page is updated before any feature that sets a cookie is added to the site, and whenever the hosting arrangement changes in a way that alters what its network stores in your browser.

What the site stores in your browser, beyond cookies

For completeness, because "we set no cookies" is sometimes technically true of a site that nevertheless leaves a great deal behind.

This site writes no entry to local storage, no entry to session storage, and no IndexedDB database. It registers no service worker, so nothing continues running after you close the tab and nothing caches pages outside the browser's ordinary HTTP cache. It requests no permission — no notifications, no location, no camera, no microphone — and it asks your browser to remember no preference of any kind.

The ordinary HTTP cache still applies: your browser may keep a copy of a page, a stylesheet or a font so a second visit is faster. That is your browser's own behaviour rather than storage this site requests, it holds no identifier, and clearing your browsing data removes it.

How to verify any of this yourself

Every claim on this page is checkable in about thirty seconds, and checking it is more reliable than believing a policy page.

Open your browser's developer tools before loading the site, then look at the storage panel: it lists cookies, local storage, session storage and IndexedDB for the current origin, and all four should be empty. The network panel lists every request the page made, and the only hosts should be this site's own domain. The console should show no requests being blocked, because there is no third-party code attempting any.

If you find something on this site that contradicts this page, that is a defect worth reporting through the enquiry form, and it would be fixed here as well as in the build.