Ship privacy-first analytics with a 10-second install.

We built a privacy-first analytics engine with zero cookies

Why the analytics industry got tracking wrong, and how session-storage hashing eliminates the need for consent banners.

Tracabit team7 min read
Session lifetimes drawn as bars that end when the tab closes.

The analytics industry built its business on a model we think is broken: track everyone with cookies, follow them across the web, and monetize the resulting profile. Consent banners exist because of that model — and so does the friction every site owner pays for it.

We started from a different question: what does a product team actually need? Pageviews, sessions, events, referrers, devices, and the occasional crash report. None of that requires identifying a person. So Tracabit uses sessionStorage for session state, a passive djb2 hash of non-identifying browser attributes for a stable anonymous fingerprint, and no cookies at all.

The result is an analytics layer that behaves like an API rather than a surveillance network: it is installable in ten seconds, reads like JSON, and asks nothing from the visitor. No banner, no profile, no third-party sharing.

We are not arguing that every business should be cookie-free tomorrow. We are arguing that product telemetry never needed cookies in the first place — and that teams deserve a tool that respects their users while still answering their questions.

Tracabit records traffic, events, crashes and web vitals with one script tag, and lets your coding agent read them over MCP.

Start free