Cookie Policy

We measure visits, so we know which pages are worth writing. That runs for everyone and sets two cookies. It tells us a page was read, roughly when, and which city the request came from. It does not tell us who you are.

Separately, we would like to record how pages are used, so we can see where a layout is confusing rather than guess at it. That is the more intrusive of the two and it is the one we ask about. It does not run unless you agree, and enquiry forms are excluded from it entirely.

No advertising cookies, now or later. No tracking pixels. Nothing is sold, and nothing is used to follow you to other websites.

A cookie is a small file a website asks your browser to keep and hand back on your next visit. Some are genuinely necessary, such as remembering that you are signed in. Most of the ones people object to are the other kind: they exist so you can be counted, profiled or advertised to later.

Ours are the counting kind and the recording kind. There is nothing to sign in to on this site, and we are not in the business of following people around.

Visit counting. Google Analytics, always on

_ga

Distinguishes one browser from another so a returning visitor is not counted twice. Expires after two years.

_ga_ED4WNVJVMC

Keeps the state of the current visit, so three pages read in one sitting count as one visit rather than three. Expires after two years.

Session recording. Microsoft Clarity, only if you agree

_clck

Ties this browser to its recorded sessions, so repeat visits are not counted as new people. Expires after one year.

_clsk

Joins the pages of a single visit into one recording rather than several. Expires after one day.

That is the complete list. If it ever grows, this page changes before the cookie does.

Counting visits is the ordinary measurement any published site does. It records no more about you than a server log already does, and presenting it as a question would be a question in name only.

Recording a session is different in kind rather than in degree. It captures where the pointer moved, what was clicked and how far the page was scrolled, and replays it. That is worth asking about, so it is the one thing the banner asks, and it is a real question with a real no.

Your answer is kept in your browser local storage rather than in a cookie. It would be lawful as a cookie, but writing one to record that you did not want recording is the kind of thing that makes these pages distrusted. The value stays on your device and is never sent to us.

Both tools can do considerably more than we ask of them. These are off permanently, in every state, including for anyone who agrees to recording.

• Advertising storage, advertising user data and ad personalisation. We run no campaigns, so there is nothing for them to do, and a permission you do not use is a permission worth not having.
• Google Signals, which would link browsing across devices for signed-in Google users.
• Any sharing of this data for advertising purposes.

Your address is truncated by Google before storage, so the location we see is a city rather than a household.

On the recording side, the enquiry forms carry a masking attribute in the page itself, not merely a setting in a dashboard. Your name, your email, your phone number and your description of what is not working are excluded at source. We ask for those so a person can call you back, not so they can be replayed.

The form posts to our own server

When you send an enquiry it goes straight to us. No third party sits in the middle of it, and it works whether or not you allowed recording.

Server logs

Our hosting provider records the requests it serves, including the address they came from. That is how a site is kept running and defended, it is not a cookie, and your choice here does not affect it. The privacy policy covers it.

Fonts are served by us

The typefaces load from this site rather than from a font network, so opening a page does not announce your visit to a third party.

Use the control below to allow or refuse session recording. It takes effect immediately and needs no reload. Turning it off stops the recorder and deletes both of its cookies.

Visit counting is not covered by that control. If you would rather not be counted at all, your browser is the reliable route: block cookies for this site, or install the opt-out add-on Google publishes, which works across every site that uses Analytics rather than this one alone.

Deleting the four cookies by hand works too, and simply means your next visit is counted as a new one.

Three things, and each would be a deliberate decision rather than something that creeps in.

• Live chat, which has to remember a conversation across pages to work at all.
• An embedded video or map, which brings the cookies of whoever hosts it.
• Advertising measurement, if we ever run campaigns that report back.

If any of them is added, this page is updated to name it before it goes live, and anything that is not strictly necessary is asked about first.