Privacy-Friendly Analytics: What Makes Them Different

There is no formal certification for "privacy-friendly analytics," but a stable definition has emerged across the industry by 2026. A tool qualifies if it does five things, all by default — not as opt-in features behind configuration:

Cookies are the legal trigger for ePrivacy Directive consent requirements in the EU. Any cookie that is not "strictly necessary" for the service requires opt-in consent before being set. Analytics cookies are explicitly not strictly necessary, so they require consent.

GA4 sets cookies (_ga, _gid) even with consent mode in "denied" state — they just store anonymized signals instead of full identifiers. Under ePrivacy that is still a non-essential cookie and still requires consent. The "first-party cookie" framing some tools use does not change this; first-party vs third-party matters for tracking effectiveness, not for ePrivacy consent.

Privacy-friendly analytics solve this by not setting cookies at all. They identify unique visitors by hashing the IP, user-agent, and a daily salt — a method that produces the same hash for the same person on the same day, but cannot be linked across days or across sites. This is consent-free under ePrivacy because no information is stored on the user's device.

IP addresses are personal data under GDPR. Storing raw IPs in your analytics database creates a compliance obligation (data subject access requests, retention limits, breach reporting). Privacy-friendly tools avoid this by never persisting the IP.

The typical pattern: receive the request, derive country/region from the IP using a geo database, compute a daily-rotating hash of (IP + user-agent + site-secret + day), discard the IP. The hash lets the tool count unique visitors across a day; the rotation prevents the hash from being a stable identifier across days. No IP is ever written to disk or logs.

GA4 does the opposite by default — IPs are processed and used for various purposes including ad personalization. IP anonymization is available as a setting but is not the default state, and the data is still flowing through Google's US-based ad infrastructure either way.

Cross-site tracking is what made third-party cookies controversial — the same identifier following you across thousands of sites builds an advertising profile. GA4 enables some cross-site behavior (Google Signals, advertising features) by default; even with these off, Google's analytics infrastructure can theoretically join data across properties internally.

Privacy-friendly analytics build their architecture so cross-site joining is impossible by design. Each customer's site has its own salt, its own hash space, its own data silo. There is no central identity graph because there is no central identity to record.

For users this means installing Sleek on your blog and on your SaaS app does not let either of those properties be linked to other sites running Sleek. The analytics provider literally cannot do that.

The Schrems II ruling (July 2020) struck down Privacy Shield, the legal mechanism that allowed transfer of EU personal data to the US. Any analytics tool that sends EU personal data to US servers — which includes GA4 by default — operates under unstable legal ground in the EU.

Privacy-friendly tools either store nothing personal (so transfer rules do not apply) or host EU data within the EU. Sleek processes EU traffic on EU infrastructure; Plausible is hosted in Germany; Fathom offers EU hosting.

For EU companies, this is not optional. EU data protection authorities have ruled GA4 illegal in Austria, France, Italy, Denmark, and Norway specifically because of the US transfer issue.

GA4 can be configured closer to privacy-friendly with significant effort — disable Google Signals, anonymize IPs, deploy via consent mode, set up data retention. But the floor of "privacy-friendly out of the box" is what privacy-friendly analytics provide and GA4 does not.

A common assumption is that anonymous tracking must be less accurate. The opposite is usually true.

GA4 traffic numbers are systematically lower than reality because ad blockers (uBlock Origin, Brave's built-in blocker, Firefox Enhanced Tracking Protection) block GA4 pixels as a category. Plausible has measured this at 58% of Hacker News visitors blocking GA. Privacy-friendly analytics, because they do not look like ad-tech, are usually whitelisted or never targeted by these blockers.

In real-world tests on the same site, Sleek and Plausible typically show 15–35% more visitors than GA4. The difference is mostly traffic GA4 was missing — not bots, not double-counting. Privacy-friendly analytics are, in 2026, more accurate than GA4 for sites with technically literate audiences.

Privacy-friendly analytics make legal sense. They also make product sense. No consent banner means a 10–25% conversion uplift for first-time visitors who would otherwise bounce on the cookie wall. Lighter scripts (1–2 KB vs 45 KB for GA4) improve Core Web Vitals, which directly affects SEO ranking. Cleaner data — without ad-blocker gaps — improves decision quality.

These are not edge benefits. Sites that switch from GA4 to a privacy-friendly tool routinely report better page-speed scores, higher measured visitor counts, less time spent on consent management, and zero reduction in marketing decision quality.