Privacy-first analytics without the tradeoffs
Cookieless sessions, hashed identifiers, DNT support, and ingest-time redaction. Compliance and clarity can coexist.
Privacy tooling often arrives as a checkbox at the end of a sales call. We built it into the ingestion path and the project settings instead.
Cookieless by default
The browser tracker does not set cookies. Sessions are derived from a hashed combination of IP address, user agent, and a daily salt. You still get visitor counts, funnels, and top pages without dropping a consent banner for basic analytics.
Controls you can turn on per project
Hash IP addresses and user IDs before storage. Add data-do-not-track="true" on the tracker script to skip users who send a Do Not Track signal. Strip query parameters so UTM tags and sensitive strings never land in your page paths. Hashing and export controls live in dashboard settings under Privacy.
Redaction at ingest
Property keys that look like passwords, tokens, or card numbers are dropped before an event is stored. String values that match email, phone, or card patterns are replaced with a redacted placeholder. You get funnel and traffic data without accidentally building a PII warehouse.
Data export is off by default and can be enabled per project when your team needs CSV downloads. Your legal team and your engineers can both sleep at night.