Scan any website to detect trackers, or select manually — get a personalized migration plan to privacy-friendly alternatives.
We scan for tracking scripts, cookies, and pixels, then recommend privacy-friendly replacements.
What to Look for in a Privacy-Compliant Analytics Tool
The privacy analytics comparison below covers five tools you will encounter in any serious evaluation. Before reading the table, it helps to understand the three questions that separate genuinely privacy-friendly analytics from tools that merely claim the label. These come from my time building GA4 pipelines: legal compliance hinges on cookie use, data residency, and identity-data handling — not on marketing copy.
For a deeper look at the theory behind this, see measuring users without identifying them — the pillar article that defines what “privacy-first” actually means at the data level.
Does It Need a Cookie Banner?
Under the EU ePrivacy Directive, any tool that writes a persistent identifier to the user’s device requires prior informed consent — which means a cookie banner. Cookie-free tools (Plausible, Fathom, Cloudflare Web Analytics) derive session counts from server-side data or hashed, anonymized request metadata and do not write anything to the browser. Matomo is cookie-based by default but offers a cookieless mode; GA4 uses cookies and also relies on fingerprinting signals. If eliminating the consent wall is your goal, cookieless-by-default tools are the only clean path. To check whether your current setup legally requires one, use our check if you still need a cookie banner wizard.
Where Is Data Stored?
Data residency matters for GDPR because transfers of personal data to non-adequate countries (including the US) require additional safeguards under Chapter V. Plausible processes data exclusively on EU-based servers (Hetzner, Germany/Finland). Fathom routes EU visitor data through EU infrastructure with US visitors handled separately. Cloudflare Web Analytics aggregates edge data before it reaches any origin server. GA4 routes data through Google’s US infrastructure by default; EU data regionalization is available but does not prevent Google from accessing data for its own purposes. Matomo self-hosted keeps data wherever you host the server.
What Identity Data Does Each Tool Collect?
This is the question most comparison articles skip. “Cookieless” is not the same as “collects no identity-linked data.” The relevant distinction is between IP address handling, fingerprinting, and persistent user IDs. Plausible hashes the IP address combined with a daily salt — the hash is never stored, and the same visitor appears as a new unique the next day. Fathom uses a similar daily-rotating hash with no stored IP. Cloudflare Web Analytics never sends raw IP or user-agent to the origin; aggregation happens at the edge. GA4 collects IP (truncated by default in EU), sets multiple persistent cookies, and can link sessions across sites via the Google ecosystem. Matomo in cookieless mode uses IP + user-agent fingerprinting by default — you can configure anonymization, but it requires deliberate setup. Understanding this distinction is worth reviewing alongside how your analytics tracker works under the hood.
How to Use the Finder
The tool above has three tabs. Use Migration Guide if you are replacing an existing tracker: paste your site URL and the scanner detects which tracking scripts are loaded, then generates a step-by-step replacement plan. Use Compare Alternatives to pick two to four tools and see a side-by-side feature matrix — useful when you have already narrowed the field. Use Cost Calculator when budget is the deciding factor: enter your monthly pageview volume and all pricing tiers are calculated at once.
Privacy Analytics Comparison Table
The table below captures how each tool handles the three evaluation criteria above. Pricing figures are indicative; verify current tiers directly with each vendor before committing.
| Tool | Cookie-free by default | IP / identity handling | Data residency | GDPR consent required | Self-host option |
|---|---|---|---|---|---|
| Plausible Analytics | Yes | Daily-salted hash, never stored | EU only (Hetzner DE/FI) | No | Yes (AGPL) |
| Fathom Analytics | Yes | Daily-rotating hash, no raw IP | EU for EU visitors | No | No |
| Matomo | No (cookieless mode available) | IP anonymization configurable; fingerprinting in cookieless mode | Your server (self-host) or Matomo Cloud EU | Depends on configuration | Yes (GPL) |
| Cloudflare Web Analytics | Yes | Edge aggregation — no IP or UA reaches origin | Cloudflare global edge; EU data stays in EU with data localization | No | No (Cloudflare CDN required) |
| Google Analytics 4 | No | Multiple persistent cookies; cross-site linking via Google ecosystem | US servers by default; EU data regionalization available | Yes (under GDPR) | No |
GDPR Compliance Implications for Each Tool
The table summarizes the data-handling facts; what follows is what those facts mean for your legal position.
Plausible and Fathom are the lowest-friction choices for EU-based organizations. Neither sets cookies, neither stores IP addresses in identifiable form, and both keep EU visitor data on EU infrastructure. Data protection authorities in Germany, France, and Austria have accepted cookieless, IP-anonymizing analytics as not requiring consent — though your DPO should verify this against your specific context.
Cloudflare Web Analytics is functionally similar for GDPR purposes: no cookies, no IP storage, and EU data localization available for Business/Enterprise plans. The constraint is that it only works if your site already runs behind Cloudflare. The free tier aggregates globally without per-region data control.
Matomo occupies a middle position. Self-hosted Matomo with IP anonymization enabled, cookieless mode, and no cross-site tracking configured can meet GDPR requirements without consent for analytics-only use. However, the defaults require changes. Out of the box, Matomo sets cookies and logs truncated IPs. If you use Matomo Cloud, verify data residency matches your requirements — the EU-hosted option exists but must be selected at account creation.
GA4 remains legally contested in EU jurisdictions. Multiple DPAs have found that Google’s access to data for its own purposes — regardless of where that data is physically stored — constitutes a transfer to the US under GDPR’s Chapter V logic. Running GA4 on EU visitors without a consent mechanism is the highest-risk configuration in this comparison. This is true even with IP anonymization and EU data regionalization enabled, because the issue regulators focused on is not storage location but Google’s ability to access and use the data.
Privacy-Friendly vs Privacy-Focused: The Distinction That Matters
The two labels get used interchangeably in vendor marketing, and they should not be. Privacy-friendly analytics describes tools built so that personal data is never collected in the first place — no cookies, no persistent identifiers, IP addresses discarded or hashed before storage. There is nothing to consent to because there is nothing identifying to process. Privacy-focused is the softer claim: the tool collects identity data but handles it more carefully than the default — shorter retention, opt-outs, EU hosting. Those measures reduce risk; they do not remove the consent question.
The practical test is simple: ask what the tool would hand over if someone demanded every record about one visitor. A privacy-friendly tool has no answer to give — visitor records do not exist as identities. A privacy-focused tool has a file. Every recommendation the finder above makes leans on that test, not on what the vendor’s homepage says.
One note if you are migrating off a vendor that has closed: Wide Angle Analytics, one of the EU-hosted privacy vendors, shut down on 31 August 2026. If you are migrating away from it, the criteria on this page apply unchanged — treat it as a forced chance to pick a tool that passes the test above.
Where the finder tells you a consent banner is still required, the next questions are operational: run the GDPR self-assessment to see where your setup stands, check what actually needs consent, and if a visitor exercises their access rights, the DSAR generator produces the request letter. The GDPR fine calculator shows what the alternative costs.
Frequently Asked Questions
- What makes analytics GDPR compliant?
- Three conditions matter: the tool must not transfer personal data to non-adequate countries without lawful basis; if it sets cookies or persistent identifiers, it needs prior consent; and it must process only data that is proportionate to the purpose. Tools that hash or discard IP addresses before storage, use no browser-side persistent identifiers, and host data inside the EU satisfy all three for basic traffic analytics without requiring a consent mechanism.
- Is GA4 GDPR compliant?
- This is disputed in EU law. Several data protection authorities — Austria, France, Italy, Denmark, Sweden — have issued decisions finding that transferring analytics data to Google’s US infrastructure violates GDPL Chapter V, even with standard contractual clauses in place. Google has responded with EU data regionalization, but regulators have questioned whether this prevents Google from accessing data for its own product purposes. Running GA4 without a consent mechanism on EU visitors carries documented legal risk.
- Plausible vs Fathom vs Matomo — which should I choose?
- For the simplest GDPR-safe setup with no cookies: Plausible (if you want EU-only hosting and optional self-hosting) or Fathom (if you want the smoothest migration from GA4 with data import). For feature parity with GA4 — heatmaps, funnels, goal funnels — Matomo self-hosted with cookieless mode configured. The tool above lets you compare all three side by side on your pageview volume.
- Can I run analytics without a cookie banner?
- Yes, if your analytics tool does not set cookies or other persistent identifiers on the device. Plausible, Fathom, and Cloudflare Web Analytics are genuinely cookieless. Matomo requires cookieless mode to be explicitly enabled. GA4 requires cookies and therefore requires a consent mechanism for EU visitors. Cookieless analytics generally provide aggregate session counts rather than individual user journeys, which is sufficient for most traffic reporting needs.
- What is cookieless analytics?
- Cookieless analytics counts visits without writing any identifier to the user’s browser or device. Instead of tracking an individual across sessions, these tools derive aggregate metrics — pageviews, referrers, session duration estimates — from server-side signals like anonymized IP hashes or edge-aggregated request metadata. The trade-off is that cross-session user journeys are not tracked, and the same physical person appears as a new unique visitor each day. For GDPR purposes, this approach avoids the ePrivacy consent requirement because no data is “stored in or retrieved from the terminal equipment.”
- Which analytics tools are EU-hosted and GDPR-safe?
- Plausible Analytics hosts exclusively on Hetzner infrastructure in Germany and Finland. Fathom routes EU visitor data through EU servers. Pirsch Analytics is built and hosted in Germany. Matomo Cloud offers an EU-hosted option that must be selected at signup. Simple Analytics is headquartered in the Netherlands with EU hosting. Self-hosted Matomo, Umami, or Plausible give you direct control over the server location.
- Is there a GDPR-compliant alternative to Google Analytics?
- Yes, several — that is what this finder compares. Cookie-free hosted tools (Fathom, Plausible, Simple Analytics and others) replace GA4 for traffic analytics without a consent banner; self-hosted options (Matomo, Umami) keep every byte on your own infrastructure. The honest caveat: none of them replicates GA4’s advertising integrations — the compliance problem and the ad ecosystem are the same feature. Use the finder above to match a tool to your data-residency and self-hosting requirements.
- What is privacy-friendly analytics?
- Privacy-friendly analytics is web traffic measurement designed so that no personal data is collected: no cookies, no persistent identifiers, no raw IP addresses in storage. Visits are counted through aggregate or short-lived signals, so individual visitors cannot be singled out or re-identified. That design keeps basic traffic analytics outside the scope of GDPR consent requirements — which is different from a tool that collects identity data and merely promises to guard it well.