Cookie Policy

This page is about what gets stored on your own device when you use this site. What happens to information you send us, such as your name and email address in the contact form, is covered by our Privacy Policy.

Two things, and both are strictly necessary, so we do not ask your permission for either.

Your answer to the cookie banner. It is kept in your browser so that we do not ask you the same question on every visit. It holds nothing about you, it is never sent to us, and clearing your browser data removes it.

A security cookie from Cloudflare. Cloudflare, which hosts this site, sets a cookie called cf_clearance to tell visitors apart from automated traffic and to protect the site against malicious traffic. It does not track you and stores no personal data. If you block it, parts of the site may not open when the Cloudflare security checks are triggered.

We also count visits with Cloudflare Web Analytics, which stores nothing on your device. Our Privacy Policy covers what it does.

This is not in use today. Your answer decides whether we may turn it on later.

Marketing would let us measure whether an advert brought you here.

Both forms on this site are protected by Cloudflare Turnstile, a service that works out whether a submission came from a person. It receives your IP address, some technical details about your browser and the name of the page you are on. It does not read what you type into the form.

It starts when you begin using a form, not when you open the page, and for almost everyone it stays invisible: you only see it if it decides it needs you to confirm something. We do not ask your permission first, because a check that anyone can switch off is not a check, and because it stores nothing on your device.

Without it, anyone could use our forms to send email at our expense. Cloudflare publishes its own notice covering what it does with what it receives.

Booking a call uses Calendly, a scheduling service we do not own. When you choose a time, Calendly needs to know who is asking, so it stores its own information in your browser and receives your IP address. Its own notice covers what it does with that.

Opening the calendar also fills in what you already told this page, so that you do not type it twice: the situations you ticked, your self-check level, and your name and email address if you entered them in the contact form or asked us to send you your result. All of it is visible in Calendly's own form, and you can change or delete any of it before you book. What happens to it afterwards is a privacy matter rather than a storage one, so it is not covered here.

None of this happens until you ask for the calendar. The booking button loads nothing on its own, so if you never open the calendar, Calendly never learns that you visited.

Select Cookie settings at the bottom of any page. Your current answer is shown, and you can change any part of it. Closing it without choosing leaves your answer as it was, so looking is free.

Turning something off stops it from that point on. We cannot take back information a third party has already received, and we will not tell you otherwise.