We don't run advertising pixels, session-replay tools, or third‑party trackers. If it isn't listed below, this site doesn't do it.
(a) The contact form
What: name, organisation, work email, what you're exploring, and your message — whatever you type into the contact form.
Purpose: replying to your enquiry.
Legal basis: our legitimate interest in responding to enquiries about our own product — you've contacted us expecting a reply, and we don't use the details for anything else.
Retention: for as long as the enquiry needs, and for up to 24 months afterwards (so we can pick a thread back up if you get back in touch) — then deleted.
Processor: when the form's backend is active, the message is sent via Resend (a transactional email delivery service) to our inbox. Until then, the form falls back to opening your own email client, so the message goes directly to us with no processor in between.
(b) Booking a walkthrough
What: name, email, and the slot you pick — only when the online scheduler on /book/ is switched on.
Purpose: arranging a call.
Legal basis: our legitimate interest in scheduling a meeting you've asked for.
Processor: when enabled, the scheduler is provided by Cal.com, a third‑party booking service — your booking details are processed under Cal.com's own privacy policy. Until the scheduler is switched on, /book/ only offers the email path in (a), with no third party involved.
(c) Analytics
What: aggregate page-view counts and performance metrics.
How: when switched on, this site uses Cloudflare Web Analytics — a cookieless measurement service. It sets no cookies, collects no personal data, and does no cross‑site tracking. It cannot identify you or link your visit to any other site you use.
Why no cookie banner: because nothing here stores information on your device or accesses information already stored there, it falls outside the UK PECR consent requirement — there is nothing to consent to.
(d) Server logs
What: standard web-server logs (IP address, requested page, timestamp, user agent) — generated automatically by Cloudflare Pages, our hosting provider, for every site on the internet that serves pages over HTTP.
Purpose: keeping the site running securely — abuse prevention, fault diagnosis.
Retention: governed by Cloudflare's own log-retention policy, not something we configure per visitor.