Analytics

What is actually sent

One request per page view, containing the route you are on. That is the whole payload. It carries no query string, no page content, no identifier for you, and nothing typed into a form.

For a Field Notes article the request says which article. It does not say who read it, what they did next, how far they scrolled, or where they came from.

No cookies, and no profile

Nothing is stored in your browser for analytics — no cookie, no local storage entry, no device fingerprint. Because nothing is stored, there is nothing to join two visits together with: we cannot tell that today's reader is yesterday's reader, and we are not trying to.

This is why the site has no cookie banner. A banner asks consent for tracking that does not happen here; adding one would imply we were doing something we are not.

Where it runs, and where it does not

Analytics runs on the public marketing pages only — the home page, About, How It Works, Who We Serve, and Field Notes.

It does not run inside the product. Once you sign in, no page-view counting follows you: the sign-in screen, the dashboards, your documents and your project data are not measured. That separation is structural rather than a setting — the measurement is attached only to the public section of the site.

Who sees it

Vercel, who host this site, provide the counting and hold the aggregate figures. We read the results. Nothing is shared with advertisers, data brokers, or any third party, and nothing is combined with your account or your project data.

If you would rather not be counted

Any content or tracker blocker will stop these requests, and the site works exactly the same without them — no feature depends on the measurement. Browsers with blocking built in, including Brave and Firefox on its stricter settings, already stop them by default.

We would rather tell you that plainly than design around it.