Features · Prove

GDPR and KVKK mode — a switch, not a promise

Standard mode is already cookie-free and consent-free. Strict mode goes further: country, screen size, referrer query strings and cross-day identity are dropped at ingest, and the DNT override cannot be turned off.

Start free Privacy mode docs

Enforced on the server

Anyone can edit a browser script, so a guarantee made in the client is not a guarantee. The policy is applied at ingest, before anything is written.

Per site, not per account

Run a marketing site in standard mode and a health product in strict mode from the same workspace.

The trade-offs are listed

Strict mode costs you the country breakdown, screen-size data and retention. The dashboard names what you gave up rather than showing empty panels.

No data leaves the EU if you do not want it to

Self-host anywhere, or use EU hosting on the cloud plan. A DPA is available either way.

The evidence

What strict mode removes at ingest

strict: {
  country:        dropped
  screen:         dropped
  referrer query: stripped to origin
  identity:       ignored (so: no retention)
  Do Not Track:   always honoured, override disabled
}

Applied in privacy.ts before the row is written. There is no path around it.