This website measures engagement without tracking you.

No cookies for advertising. No advertising pixels. No retargeting. No third-party analytics. No fingerprinting. No A/B testing platform that rewrites the page to chase a conversion. The only thing this website stores on your machine is a session resume identifier for the chat (the same identifier our customers see under Respondent Sovereignty). You control it: clearing your browser ends our knowledge of the session.

We do measure how visitors move through the site, on infrastructure we operate, using an identifier that exists only in your browser’s memory for the length of a single visit. Nothing about that measurement is written to your device, and it is never linked to you across visits or across other sites. Section 03 sets out what it records and what it leaves alone.

This page describes what the site stores, what it measures, what it deliberately omits, and what runs in front of the site for attack and DDoS protection.

The only persistent item we write to your browser is a session identifier the chat uses to resume a conversation if you reload the page. The identifier is a random string. It is scoped to this domain. It points at a server-side entry that holds the messages you and the chat have exchanged in the current session.

Clearing your browser storage ends our knowledge of that session. There is no second copy of the conversation tied to your IP, your device fingerprint, or any other identifier.

We also keep short-lived language and theme preferences (the locale you chose, the dark or light theme) in browser storage. These do not leave your browser. The site reads them to render the page in your chosen configuration on your next visit.

The site does not use:

• Google Analytics, Plausible, Fathom, or any other third-party analytics service.
• Facebook Pixel, LinkedIn Insight Tag, Twitter conversion tracking, Reddit Pixel, TikTok Pixel, or any other advertising attribution pixel.
• Hotjar, FullStory, Microsoft Clarity, or any other session-recording tool.
• Segment, RudderStack, or any customer data platform.
• Cookie-based retargeting, audience-list synchronization with ad networks, or programmatic-advertising integrations.
• Device fingerprinting libraries.
• A/B testing platforms that mutate the page based on visitor segments.

We do not have a tag manager. We do not load third-party JavaScript bundles from CDNs other than the static asset CDN that serves our own application code.

What we do run is a first-party measurement layer on a worker we operate. The next section sets out exactly what it records.

We measure how visitors move through the site so we can see what is useful and what is ignored. The measurement runs on a Cloudflare Worker we operate. It is not a third-party analytics service, and the data is not shared with one.

When you load a page, your browser holds a random identifier in memory for the length of that visit. It is never written to your device, and a new one is generated if you reload or return later. We use it to connect the steps of a single visit, such as which sections you read or which chapters you play, without knowing who you are.

Our server adds a few coarse signals it reads from the connection itself: the country the request came from (country level only, from Cloudflare), whether you are on a phone, tablet, or desktop, and the domain that referred you (the domain alone, never the full address). If you followed a campaign link, we record the campaign tags carried in that link.

We do not store your IP address or your precise location. We do not build a fingerprint of your device, and we do not link this measurement to any identifier that follows you across other websites. Because none of it touches your device, there is no cookie banner to dismiss.

Cloudflare runs in front of this website for attack and DDoS protection. Cloudflare sees your IP address (it has to, to route the response back to you), the URL you requested, your user agent, and the request timing. This is the minimum information needed to route an HTTP request and to identify a DDoS pattern.

We do not use Cloudflare Web Analytics, Bot Management personalization, or any product layer on top of the edge that would build a profile of you. The data Cloudflare holds about your visit is the standard request log every CDN keeps. It expires under Cloudflare’s standard retention.

If you open the chat on this site, the conversation is held server-side under the session identifier we wrote to your browser. We use that conversation to answer your next message in context, and to let our team see the thread if you ask for a human follow-up.

We assign each question a coarse topic label, such as pricing or integration, produced by a small model on our own infrastructure. The label lets us see what visitors ask about most. It sits beside the conversation, adds no new identifier, and writes nothing to your device.

The conversation is not pushed to a marketing tool. It is not associated with your IP across sessions. It is not joined to any external profile. If you close the browser and clear storage, we have no way to associate your next visit with the prior session.

If you ask for a human follow-up and provide an email, the email enters our outreach system under the same consent terms a contact form would. You can ask us to delete the record at any time.

The product runs zero-retention contracts with its partners and processes data inside customer perimeters. A marketing site that profiled every visitor against an ad network would contradict the posture the platform sells. So we measure the site the way the platform handles data. We collect what we genuinely use and keep it on infrastructure we control. We store nothing on the visitor that could identify them later.

That choice has a cost. We can see how sections and chapters perform, but we cannot tie two visits to the same person, retarget anyone, or hand a profile to an ad network. That is the right trade for a company whose product is built on data minimization. The measurement tells us what to improve. It does not tell us who you are.