Cookie policy
Last updated ·
What this website stores in your browser, what it does not, and how to change it. This describes what the site actually does today rather than the cookie estate a site of this kind usually has.
What this covers
This policy covers this website. It sits alongside the privacy policy, which explains what we do with personal information once we hold it. Data inside a client’s own systems is covered by the data processing terms and not by this policy.
Storage we do use
One item, and it is deliberately not a cookie. If you arrive from a campaign link, the site records the campaign parameters in your browser’s session storage under the key cfx-attribution, so that an enquiry you choose to send can carry the campaign that produced it. Session storage is first-party, is never attached to a request the way a cookie is, is readable only by this site, and is discarded the moment you close the tab. A cookie would have made attribution non-essential storage and dragged an entire consent flow behind it. If your browser blocks storage the capture quietly does nothing and your enquiry is unaffected.
Analytics
This site uses null to count page views. It is loaded only after you accept the analytics category, it is removed again if you withdraw that acceptance, and it does not run on the page views that precede your decision.
How we record your choice
Each consent decision is also written to a record on our server: the time, the categories, the version of the policy you were shown, the language, and the answer. A refusal is recorded exactly as an acceptance is — it is the same audit fact. That record lives on our server rather than in your browser, and it is what we would produce if a regulator asked what you were shown and what you said.
Third-party content
There are no embedded videos, no social media widgets, no advertising tags, no chat widgets and no third-party font host — the web fonts are served from this domain, so loading a page contacts nobody but us. The consent banner is built from a library bundled into the site rather than fetched from another origin, so even it makes no third-party request.
Controlling what is stored
Every browser can block or clear cookies and site data, usually per site. Doing that for this site removes the attribution record described above and nothing else — nothing here depends on storage, and the site works the same without it. Where there is a choice to make, a “Cookie preferences” control appears in the footer and reopens it; while there is nothing to consent to, that control stays hidden rather than sitting on the page as a button that does nothing.
Changes to this policy
The current version of this policy is 2026-08-12.1, and that version string is stored with every consent record, so any record can be traced back to the exact wording it was given under. A substantive change bumps the version and asks anyone who has already decided to decide again. The effective date is at the top of this page.