GET/privacy

Where the measuring stops

The public pages carry two analytics tools. Your workspace carries neither. That line is drawn in the code rather than in a setting, and a test fails if it moves.

The two tools

Both are third parties, so both are named. The ids are public by design: they identify the property, not the account, and you can read them in the source of this page.

Google Analytics 4

G-MTFTN6KKH0

Counts views of the marketing pages, plus the sign-in and sign-up screens. The page address is the entire payload.

Microsoft Clarity

yactzdsd2w

Anonymous session replay and heatmaps, on the marketing pages only. Not on sign-in, not on sign-up, and never inside a workspace.

What is never sent

Reporting works from an allowlist of public pages rather than a blocklist of private ones. A route added tomorrow is silent until somebody puts it on the list deliberately, which is the safe way for that mistake to go.

Anything anyone typed

Email addresses, names, passwords, notes, search terms — no form value reaches either tool.

Which workspace you are in

Workspace names and slugs never appear in a page address we report, because no page address inside a workspace is ever reported.

Identifiers of any kind

Record, task, deal, principal, invite and reset ids stay here. The token in a claim link is a credential, and credentials are not analytics data.

Query strings and fragments

Dropped whole rather than filtered. ?next= on the sign-in screen can carry a workspace path, and a filter is a thing that can be got wrong once.

The boundary

A script loaded into a single-page application keeps running as you move between screens, so switching recording off on arrival would already be too late. Every link from a recorded page into /app reloads the browser instead. The workspace document is built without the tracking code in it, and the recording session from the page before is discarded rather than paused.

None of it runs in local development, in tests, or on a preview deployment. The tags are bound to the live hostname, so the many versions of this site that exist at any moment measure nothing at all.

Both tools load without asking first. If you are visiting from somewhere whose law requires consent before analytics — the EU and the UK among them — that is a gap, and naming it here is better than describing it as a feature. It is the next thing to change on this page.

To have your data removed, write to hello@agentnativecrm.com. For what the product does with the data an agent puts in it, the seven rules are the short answer: it remembers, and it refuses to forget.