Skip to content

Cookies

Draft, to be finalised before launch.

What runs in your browser

Four things from outside this site’s own code run in your browser:

  • PostHog, our analytics.
  • Sentry, which reports errors on the site to us.
  • Vercel Speed Insights, which measures how fast pages load.
  • Cloudflare Turnstile, which checks the contact and waitlist forms for automated spam.

There is no advertising script on this site. Our privacy page says nothing is sold or shared with advertisers.

PostHog: what it sends

PostHog only starts on a copy of the site built with a PostHog key. Our set-up gives that key to the live site only, so a preview or a developer’s copy of the site does not load PostHog at all. It also does not start in a browser with “Do Not Track” or Global Privacy Control switched on, as described below.

Where it runs, PostHog sends:

  • that a page was viewed, and that you left it;
  • your clicks, changes to form fields and form submissions, with the text of what you clicked on, which PostHog collects automatically;
  • the address of the first page you landed on and of the page that sent you here, and any campaign tags in that address;
  • with every event, details of your browser and device: which browser and version, the operating system, the type of device, your time zone and language, and the size of your screen and browser window.

PostHog’s own settings also decide some of what it collects, and we control those settings. As read on 29 September 2026, they have automatic click capture, heatmaps (where on a page people click, move the pointer and scroll) and error capture switched on. Session recording is off, and so are surveys, product tours and feature flags. Network timing is switched on, but it only applies to session recordings, so with recording off it collects nothing.

All of this is sent to /ingest, an address on this site, which passes it on to PostHog. PostHog may also use that address to load more of its own code.

Our privacy page says IP addresses are anonymised before any event is stored.

PostHog: what it stores, and for how long

PostHog gives your browser a random identifier. It is not your name, your email address or an account. It is what lets us tell one visit from two, and a returning browser from a new one.

It keeps what it saves in three places:

  • A cookie, named ph_ followed by the site’s PostHog project key and _posthog. It holds the identifier, the current visit, and the first page you landed on and the page that sent you here. It expires 365 days after PostHog last wrote it, and PostHog writes it again as you use the site.
  • Local storage, under the same name. It holds the same things and more of PostHog’s own settings. Local storage has no expiry date: it stays until you clear it.
  • Session storage, which keeps things for the current visit only. It holds a copy of where you came from (the referring site, and the search engine if you arrived from one) and any campaign tags in the link you followed, plus PostHog’s own bookkeeping, such as telling one open tab from another. Your browser removes session storage when you close the tab.

Sentry: what it sends

Sentry only starts on a finished build of the site that has been given a Sentry address to report to.

When something on a page goes wrong, Sentry sends us an error report. The report includes what the page was doing just before: recent clicks, the requests the page made and any messages the page logged. Sentry also sends a short record that a visit happened, so we can see whether a new version of the site has more errors than the last one.

It is set not to send personal details. It does not record your screen and does not measure performance.

Sentry stores nothing in your browser: no cookie, and nothing in local or session storage.

Vercel Speed Insights: what it sends

Speed Insights loads a small script from this site’s own address, provided by Vercel, which hosts the site. It reports how quickly each page loaded and responded, and which page it was, to Vercel. It sends no reports from a copy of the site a developer is working on.

That script is Vercel’s, not part of this site’s code, so Vercel’s own documentation describes exactly what it collects.

Cloudflare Turnstile, on the contact and waitlist forms

Turnstile is not loaded until you click into, or start typing in, the contact form or the waitlist form. It is then loaded from Cloudflare, at challenges.cloudflare.com, and runs a check in your browser to tell a person from an automated program. It shows you something only if it needs you to respond.

Cloudflare’s own privacy policy covers the information that check uses. Only the contact and waitlist pages have these forms, and no other page loads Turnstile.

What “Do Not Track” and Global Privacy Control change

If your browser has “Do Not Track” or the newer Global Privacy Control setting switched on, this site does not start PostHog at all. PostHog then stores nothing in your browser: no cookie, and nothing in local or session storage. It sends nothing about your visit either.

The site checks for these settings each time a page loads, so switching one on takes full effect from the next page you open. Anything PostHog stored on an earlier visit, before you switched the setting on, stays until you clear it.

This site’s code does not tell Sentry, Speed Insights or Turnstile to act on Do Not Track or Global Privacy Control.

You can clear cookies and site data for this site in your browser’s settings at any time. That removes PostHog’s identifier, and a later visit will be counted as a new browser.

Cookie banner

There is no cookie banner on this site today. That will be reviewed before launch.

Questions

See our privacy page for what we collect and why, or get in touch.