This is a plain-language description of what this site stores in your browser, written to be read rather than survived. It is not legal advice.
01
The short version
This website sets no cookies of its own, and stores nothing in your browser's local storage. There is no analytics product, no advertising tag, no pixel, no session replay and no cross-site tracking of any kind on these pages.
That is also why there is no consent banner sitting on top of the page: there is nothing to consent to, and asking you to click through a dialogue that does nothing would be theatre.
02
What a cookie actually is
A cookie is a small piece of data a website asks your browser to keep and send back on later requests. localStorage and sessionStorage are close relatives — they hold data in the browser but are not sent back automatically. This page covers all three, because from your side they amount to the same question: what is this site keeping about me?
03
What this site sets
Nothing. The site's own script handles the mobile index sheet, scroll reveals and the enquiry builder entirely in memory. It reads your reduced motion preference from the browser rather than storing a choice, and it writes no cookie, no localStorage key and no sessionStorage key.
If we ever need a functional cookie — to remember a preference you set, for example — it will be listed here by name and purpose before it ships.
04
The layer in front of the site
Cloudflare sits in front of this site as its content-delivery and security layer. Checked against the live site, it currently sets none — requests to this domain come back with no cookie at all, browser user-agent included. Cloudflare's bot-protection can set a short-lived security cookie if that setting is turned on, so this may change without the site itself changing.
That is a security cookie, not an advertising one: it exists to tell automated abuse apart from people, it is not used to build a profile of you, and it is not shared for marketing. It is Cloudflare's, set under Cloudflare's own terms.
05
Third-party requests
Loading a page here makes one request to a domain we do not control:
- Google Fonts — the typefaces this site is set in are served from fonts.googleapis.com and fonts.gstatic.com. Font delivery does not set a cookie, but the request itself reaches Google's servers, which means Google can see the IP address it came from and log it under its own privacy policy.
That is the entire list. Every other asset on these pages — images, stylesheets, scripts, the logo — is served from this domain. If you ever see a request to some other host while loading this site, please tell us at [email protected]; it would mean either a mistake on our side or something between you and us that should not be there.
06
What this site never does
- No analytics cookies or scripts of any kind.
- No advertising tags, conversion pixels or remarketing lists. The site carries no advertising.
- No session replay, heatmaps or scroll recording.
- No fingerprinting — we do not use canvas, font or audio tricks to identify a browser.
- No cross-site or cross-device tracking, and no data broker enrichment.
07
Controlling it yourself
Your browser, not this site, is where cookies are ultimately controlled. All of these work here, and none of them will break the page:
- Block cookies outright in your browser's privacy settings. This site does not need them.
- Clear what is stored — in most browsers, under Settings, then Privacy, then Clear browsing data.
- Use a private or incognito window, which discards storage when you close it.
- Run a blocker — uBlock Origin, Privacy Badger or similar. There is nothing here for them to block, and the site is built to work without JavaScript at all.
If you would rather your browser never contacted Google for the fonts, a content blocker will stop that request too. The page then falls back to a system typeface and remains completely readable.
08
If this changes
If we ever add anything that stores data in your browser beyond what is strictly needed to serve the page, we will list it here, update the date at the top, and put a real consent mechanism in place before switching it on rather than after.