Cookie Policy

Most cookie policies are written before anyone checks what the site actually does. This one was written afterwards, by loading every page in a browser and reading what was left behind. Here is the result.

The short version

This is deliberate. Two data protection regimes apply to this practice, the Nigeria Data Protection Regulation where I work from and the GDPR where most client systems sit, and the simplest way to hold to both is to collect nothing in the first place. A site with no cookies has nothing to ask consent for and nothing to lose. Everything below was checked by loading the site rather than assumed.

No page on this site sets a cookie of its own. Not one. There is no analytics, no advertising tag, no remarketing pixel and no session cookie, because there are no visitor accounts and nothing here needs to remember you between pages.

There is no consent banner either, and that is a consequence rather than an oversight. One page loads a booking calendar from another company, and that is set out in full below.

The one thing this site stores in your browser

  • What it is called: bf-theme-v2
  • What it is: a local storage entry, which is not a cookie. A cookie is sent to the server with every request. This is not, and never leaves your browser.
  • When it appears: only when you click the light and dark mode toggle. Read the site without touching it and nothing is stored at all.
  • What it holds: the word light or the word dark. Nothing else, and nothing that identifies you.
  • What it is for: so the site opens in the mode you chose instead of flashing the wrong one at you.
  • How long it lasts: until you clear this site’s data. Clearing it makes the site follow your device’s own light or dark setting again.

The booking calendar on the contact page

The contact page embeds a booking calendar so you can pick a time without leaving the site. It comes from Cal.com’s European service at app.cal.eu, and there are three things worth being exact about.

  • It loads when the page opens, not when you click it. Opening the contact page makes a request to that company whether or not you book anything, which means it receives your IP address and your browser’s identification string.
  • It can set its own cookies and storage, under its own domain. I cannot read those from this site, so I cannot list them for you accurately, and I am not going to guess at a list. What it sets is governed by that company’s own privacy and cookie policy, not by this one.
  • You can avoid it entirely. Blocking third party content for this site in your browser stops the calendar loading, and the rest of the contact page carries on working, including the contact form and every answer on it. The page also carries a direct link to the same booking page if you would rather visit it deliberately.

That is the only third party connection anywhere on this site. No other page requests anything from anyone else.

What is deliberately not here

  • No analytics of any kind. No visitor counts, no heatmaps, no session recording, no funnel tracking.
  • No advertising or remarketing tags, and no social media pixels.
  • No fonts loaded from a font service. The two typefaces are served from this site’s own server, which is why no font company learns that you visited.
  • No scripts loaded from a content delivery network. The animation library is served from here too.
  • No embedded video, no map, no chat widget, no social buttons.
  • No visitor accounts, so no login or session cookie. No comments, so no comment cookie.

If any of that ever changes, this page changes before the thing goes live, not after.

Server logs, which are not cookies

The web server keeps an access log, as every web server does: the IP address, the page requested, the time, and the browser identification string. That is not a cookie and you cannot turn it off in your browser, so it is covered in the privacy policy instead of here.

Managing what your browser keeps

Every browser has a setting for site data, usually under privacy or site permissions. Clearing this site’s data removes the light and dark preference and nothing else, because there is nothing else. Blocking third party content stops the booking calendar loading and leaves the rest of the site intact.

Contact

If something on this page does not match what you see in your own browser, tell me and I will fix the page. Write to [email protected] or use the contact page.

Last updated 20 August 2026. Verified against the live site on the same date.