Analytics & tracking tools, graded on privacy

A

Cookieless, no PII, with an EU-isolation option and a strong compliance posture (GDPR/CCPA/PECR). No consent banner needed for typical use.

A

Cookieless by default, no personal data stored, EU-hosted and open source. The reference point for privacy-respecting analytics.

A

Tiny, open-source, no-cookie analytics you can self-host. Counts visits with a rotating salted hash rather than a stored identifier, and documents exactly what it keeps.

A

Open source and self-hostable: you own 100% of the data. Cookieless mode, IP anonymization, DNT/consent tooling built in.

A

Netherlands-based, cookieless, no personal data, no cross-site identifiers. Privacy-first by construction.

A

German, cookieless, open-source core. Uses a rotating fingerprint-free hash; no personal data retained.

B

Free, cookieless, no fingerprinting and no cross-site identifiers. The trade-off is structural: data is processed on Cloudflare's global network with no residency control.

B

Free, open-source, self-hostable, cookieless. Minimal collection; you control the database entirely.

B

Enterprise analytics built around consent: a built-in consent manager, EU/US/private-cloud residency, no ad-resale of data.

B

A self-hosted event pipeline that runs in your own cloud — full data ownership, but it collects exactly what you configure it to collect, which can be a lot.

C

Open-source product analytics; self-hostable for full control. Powerful but autocapture and session replay can collect a lot by default.

C

Enterprise tag manager + CDP with mature consent integration — but it is a data router, so privacy depends entirely on how it is configured.

C

Enterprise analytics that does not resell your data, with real residency controls — but it is cookie- and identifier-based, and consent honoring depends on your implementation.

D

Product analytics plus in-app guides, keyed to the visitor ID you pass it — identity-linked by design. US SaaS with an EU hosting option.

D

Powerful SaaS product analytics; data is sent to Amplitude and stitched to user identities. Privacy requires careful config and consent.

D

Session replay and heatmaps with EU hosting and suppression tooling — but recordings are inherently high-collection and need consent plus careful masking.

D

SaaS product analytics with identity-resolved event tracking. EU residency available; consent required and GPC not honored by default.

D

A CDP whose job is to collect identity-resolved data and fan it out to many destinations, including ad platforms. Privacy is entirely a function of configuration and consent enforcement.

D

Ubiquitous and free — because data flows to Google. Consent Mode can model conversions even when consent is denied; no GPC honoring; links into Google's ad ecosystem.

D

Autocapture-by-default product analytics: every click, pageview, and form interaction is recorded to Heap's cloud (US by default) and stitched to persistent user identities.

F

Free session replay and heatmaps — Microsoft's terms allow use of the data for its own purposes, including advertising. Recordings can capture sensitive input unless masked.

F

Advertising/conversion tags whose purpose is cross-site ad measurement and targeting. Enhanced Conversions sends hashed PII to Google; server-side tagging can bypass client-side blockers.

F

Built to send user behavior and hashed identifiers to Meta for ad targeting. The Conversions API moves collection server-side, bypassing browser-based blocking; repeatedly implicated in receiving sensitive data.

F

Advertising pixel that sends behavior and hashed identifiers to TikTok for targeting; a server-side Events API bypasses client-side blocking. Data-governance and residency concerns are well documented.