What we store on your device.
We don’t use analytics or advertising cookies. The few things listed below are strictly necessary — for the bot-check on the Discovery, for the on-site chat to work, and for the studio login. That’s the lot.
What's on the site
Under the Privacy and Electronic Communications Regulations (PECR) we’re required to tell you about each cookie or cookie-equivalent stored on your device, even when it’s strictly necessary. Here’s the full list.
Cloudflare Turnstile (Discovery start only)
When you visit /discoveryand press “Start your brief”, Cloudflare Turnstile runs a silent bot-check before we let you into the form. It stores a short-lived token in your browser to confirm the check passed.
Why it’s here:to keep scripts and abusive traffic out of our intake form. Without it, the bot-check can’t complete and the form won’t open.
Lifetime: session-scoped; cleared when you close the tab.
Vidual chat widget
The on-site chat widget (provided by vidual.app, a separate product we operate) sets a small identifier so that if you come back later, the conversation you started is still there. Nothing in it identifies you beyond what you’ve typed into the chat yourself.
Why it’s here:so the chat works. If we couldn’t store the conversation thread, the chat couldn’t resume across pages or visits.
Lifetime: persistent, up to one year.
Sanity Studio (staff only)
Routes under /studioare the private content-management system used by WBD staff. When a staff member logs in, Sanity stores an authentication session cookie. You will only ever encounter this if you log in to the Studio, which public visitors can’t.
Why it’s here:so a logged-in admin doesn’t have to re-authenticate on every page.
Lifetime: as configured by Sanity for the session.
Fly Away Paul (page-view counting)
The site counts page views using Fly Away Paul, an analytics product we built and operate. It sets no cookies. Each page view sends us the address of the page and the page you arrived from, and that’s all — no advertising identifier, nothing that follows you to another site. Private client pages — quotes and Discovery briefs — are excluded from counting entirely.
You’ll be asked about it on your first visit. Until you answer, counting carries on but nothing at all is written to your device — a worse measurement than we could take, and an honest one. Your answer is remembered in local storage as paul_consent, so we don’t ask again. Only a yes unlocks the session storage Paul uses to tell a returning page view from a fresh visit; a no leaves the counting anonymous and unlinked, exactly as it was before you answered.
Why it’s here: so we know which pages get read, without surveilling anyone to find out.
Lifetime: paul_consent stays until you clear your browser storage; the session storage, if you allowed it, goes when you close the tab. Say no and neither is ever written.
What we don't run
To be explicit, the site doesn’t carry: Google Analytics; Facebook, TikTok, Google Ads, or any other advertising pixel; LinkedIn Insight tag or B2B retargeting tools; heat-mapping tools (Hotjar, Microsoft Clarity, etc.); browser fingerprinting libraries; cross-site tracking cookies of any kind. The only measurement on the site is the page-view counter described above.
If any of that ever changes, we’ll update this page first, and we’ll ask for your consent before setting anything non-essential. (An earlier version of this page said that if we ever adopted a privacy-friendly analytics tool, you’d read about it here first. It arrived; this is the update.)
Controlling cookies in your browser
You can clear or block cookies at any time using your browser’s settings. If you block the strictly-necessary ones listed above, parts of the site (the Discovery start, the chat widget) won’t work properly.
Full background on how we handle your data sits in our privacy notice.