Cookies
Last updated 8 October 2026
One cookie is needed to keep this site standing up, and it is not ours. There is no analytics, no advertising and nothing that follows you, so there is nothing to consent to and no banner in your way.
The short version
We set no cookies of our own, and we measure nothing. No analytics, no advertising pixel, no social tag, no fingerprinting. Nothing on this site reports your visit to anybody.
The law here is the Privacy and Electronic Communications Regulations, which require your consent before anything is stored on, or read from, your device — unless it is strictly necessary for the thing you asked for. What is below is strictly necessary, which is why you are not asked.
A banner asking permission for something exempt, or for something that never happens, would be worse than none: it teaches people to click past the ones that matter.
What is actually stored
__cf_bm— Cloudflare — about 30 minutes- Tells a person apart from an automated request, so the site stays available when it is under load or under attack. It holds a random identifier and is used for that and nothing else. Cloudflare delivers this site; it does not advertise to you.
- Nothing else
- No second cookie, and nothing in your browser’s own storage. If you look and find something we have not named here, tell us — that would be a fault.
If we ever do measure
We may one day want to know which of these pages are read. If we do, you will be asked before anything runs, in a way that makes refusing exactly as easy as agreeing, and you will be able to change your mind afterwards from the foot of any page.
Nothing will be set first and explained later, and carrying on reading will not be treated as an answer. This page will say what it is, cookie by cookie, before it is switched on rather than after.
What leaves your browser regardless
Being straightforward about this is more useful than a clean claim.
Our web server keeps the ordinary record of every request: the address it came from, the page asked for, the time, and what the browser reported itself to be. That is how a web server works and how we find out when something is broken. It is not tied to you as a person, and it is not used to build a picture of you.
The typefaces are served from this website, not from Google. They used to come from Google Fonts, which meant Google was told your address before a word of the page had been read and before you had been asked anything. The files now sit beside the pages, so nothing at all leaves your browser for a third party.
If you send us an enquiry, what you typed is kept so that we can answer it. The privacy policy says how, and for how long.
If this changes
If we ever add something new that stores anything on your device, we will ask before it runs, in the same way, with refusing no harder than agreeing. We will not set something first and tell you afterwards, and we will not treat carrying on reading as though it were an answer.
If what we ask about changes, the question is put to you again rather than quietly covered by an answer you gave to something else. The date at the top of this page tells you when it was last true.
Questions
byappointment@cleave.com, marked for the attention of Sanay Shah, who is our Data Protection Contact.




