Cookie Policy
Last updated 6 August 2026
We set no cookies of our own — none for analytics, none for advertising, none at all. One page carries somebody else's: the booking page embeds the Cal.com calendar, and Cal.com sets cookies when it loads. That page is the only one, and this policy is mostly about being specific on that point.
The booking page
Opening /book loads a calendar served by Cal.com. It is their code and it sets their cookies — typically to hold the state of the booking you are making and their own session. We do not read those cookies, we cannot see them, and nothing they store is passed to us. What reaches us is the booking itself: a name, an email address, and a time.
They load with the page rather than on a click, so opening that page is what sets them. If you would rather that did not happen, do not open it — email us and we will arrange a time by hand, which reaches the same calendar.
Every other page
No cookies. Not essential ones, not analytics ones, not advertising ones. The homepage, the case studies, the FAQ, the writing, and these legal pages set nothing on your device and load nothing from another domain.
That includes the session request form in the education section. It sets no cookies and loads nothing from anyone else — it sends a single message to the service that forwards it to us, and only when you press send. The Privacy page describes what that message contains.
Why there is no cookie banner
For most of this site the answer is that there is nothing to consent to. Nothing is placed on your device, so a banner would be asking permission for something that is not happening.
The booking page is the honest exception, and we would rather write that down than leave it unsaid: the Cal.com calendar sets its cookies as that page loads, which means they are set before you have agreed to anything. That is a real gap, we know it is one, and the fix is either a prompt on that page or making the calendar load only once you ask for it. If this matters to you before we have made the change, email us and we will book the time without the calendar involved.
The one thing stored locally
If you switch between light and dark, your choice is saved in your browser's local storage. Local storage is not a cookie: it is not attached to network requests, it is never sent to our servers, and it cannot be read by any other site.
It holds a single value — the word 'light' or 'dark'. Nothing else, and nothing that identifies you.
Third parties
One: the Cal.com calendar on the booking page. Beyond it there is no embedded video, no font service, no chat widget, no social buttons, and no CDN-hosted scripts. Typefaces are served from this domain. Links to other sites — including tools we have built — are ordinary links, and those sites have their own policies.
Which page a third party runs on is the whole of the difference here, so it is worth being exact. The calendar is embedded on /book, so on that page their code executes and their cookies are set. It is on no other page, so everywhere else nothing of theirs runs and nothing is stored. If you only ever read the work and the writing, no third party has been involved in your visit at all.