Cookie Policy

A display preference

The interface records your colour-scheme preference so the site renders the same way on your next visit. It holds a single display value, contains no identifier, and cannot be used to recognise you.

That is the only thing the site's own code stores. Cookies set from the tag manager container are a separate matter, and they are in the next section.

Google Tag Manager

Every page loads a container from Google Tag Manager. Nothing on the site needs it to work, so blocking it costs you nothing: it exists to measure which pages get read and how visitors arrive.

A container is a shell. What it loads is configured by us inside it, and the usual occupant is Google Analytics, which sets cookies carrying a random identifier so one visit can be told apart from the next. That identifier is not your name, and we cannot look you up with it.

• Analytics cookies come from the container, not from this site's own code.
• They measure pages, referrers and approximate location rather than the person reading.
• No embedded social or video player sets anything, because there are no embeds.

Following a link to the application, or to a service such as WhatsApp, takes you to a site governed by that provider's own policy, not this one.

Your browser already does this

Blocking cookies will not break this site, because nothing here depends on them; the container simply never reports anything. Your browser's own privacy settings are the right place to change this, and they apply to every site you visit rather than only this one.

An extension that blocks Google Tag Manager, or a browser that clears third-party storage on close, achieves the same result more thoroughly than a per-site setting.

If you would like to know what we hold about you more generally, see our Privacy Policy, or write to us directly.