Skip to content
Guide

GDPR Compliance Guide for Website Analytics

Everything you need to know about running GDPR-compliant analytics.

What is GDPR?

The General Data Protection Regulation (GDPR) is a European Union regulation that governs how personal data of EU residents must be handled. It applies to any organization that processes data of EU residents, regardless of where the organization is based.

For website analytics, GDPR is particularly relevant because most traditional analytics tools collect personal data like IP addresses, device fingerprints, and behavioral data that can identify individual users.

Key GDPR Requirements for Analytics

Lawful Basis for Processing

You need a legal justification to collect data. For analytics, this is typically either consent or legitimate interest (though legitimate interest is increasingly challenged for tracking).

Data Minimization

Only collect data that's necessary for your stated purpose. Don't collect personal data if aggregate statistics would suffice.

Purpose Limitation

Data can only be used for the specific purpose it was collected for. You can't collect data for "analytics" then use it for advertising.

Data Subject Rights

Users have rights to access, rectify, and delete their data. They can also object to processing and request data portability.

The Problem with Google Analytics

Several EU Data Protection Authorities have ruled that using Google Analytics violates GDPR. Key rulings include:

  • Austria (2022): DSB ruled Google Analytics illegal due to US data transfers
  • France (2022): CNIL ruled Google Analytics violates GDPR
  • Italy (2022): Garante ruled Google Analytics unlawful
  • Denmark (2022): Datatilsynet ruled against Google Analytics

The core issues are:

  • Data transfers to the US without adequate protection
  • Collection of personal data (IP addresses, device fingerprints)
  • Use of cookies requiring consent
  • Data being accessible to US intelligence agencies

How to Run GDPR-Compliant Analytics

Option 1: Use Privacy-First Analytics (Recommended)

Privacy-first analytics tools like Invoker are designed around data minimisation:

  • No cookies or device storage by default (Invoker's Privacy mode)
  • No third-party cookies, no advertising profiles
  • No names, emails or other directly identifying data
  • Visitor IP addresses never stored
  • No cross-site tracking
  • No third-party data sharing

When no identifier is stored on or read from the device, as in Invoker's default Privacy mode, the ePrivacy rule on device storage generally isn't triggered, so in most cases the analytics can run under legitimate interest without a banner. Tools that keep an ID in the browser (including Invoker's optional Enhanced mode) need consent in the EU.

Option 2: Use Traditional Analytics with Consent

If you choose to use Google Analytics or similar tools:

  • Implement a proper cookie consent banner
  • Don't load analytics until consent is given
  • Allow users to withdraw consent easily
  • Enable IP anonymization
  • Disable data sharing with Google
  • Sign a Data Processing Agreement
  • Accept that many users will opt out

Note: Even with these measures, some DPAs have ruled this approach insufficient due to US data transfers.

When Do You Need Consent?

Under GDPR, you need explicit consent when:

  • Setting non-essential cookies (like Google Analytics cookies)
  • Collecting personal data without another lawful basis
  • Tracking users across websites
  • Building user profiles

You may not need consent for analytics when (depending on your jurisdiction):

  • Nothing is stored on or read from the visitor's device (cookies, localStorage), or a national analytics exemption applies
  • No personal data is collected, or you have another lawful basis such as legitimate interest
  • Data is aggregated and anonymized
  • The analytics is strictly necessary for the service

Note that the ePrivacy rules on device storage apply to localStorage as well as cookies, so "cookieless" does not automatically mean "consent-free".

What Makes Analytics "Privacy-First"?

Analytics that is genuinely privacy-first should:

  • No third-party cookies: Keep any identifiers first-party and per-site
  • No invasive fingerprinting: Don't build precise device fingerprints
  • IP anonymization: Don't store full IP addresses
  • No cross-site tracking: Don't track users across domains
  • No data sharing: Don't share data with third parties
How Invoker Supports GDPR Compliance

Invoker Analytics is designed from the ground up to minimise data:

  • Cookieless by default: In Privacy mode the script stores nothing on the visitor's device. Visitors are recognised for one day with a server-side hash whose salt is deleted daily. No fingerprinting and no third-party cookies.
  • Optional Enhanced mode: Turn it on per site for returning visitors; it keeps a random first-party ID in your site's localStorage
  • No directly identifying data: We don't collect names or emails of your visitors
  • No stored IPs & DNT: Visitor IP addresses are never stored, and each site can honour Do Not Track
  • Local GeoIP: Locations come from a local DB-IP database, with no third-party lookups
  • No tracking across sites: We don't track users across sites or build ad profiles
  • No third parties: We don't sell data or share it with advertisers

Privacy mode is designed so you don't need a cookie banner for Invoker. If you turn on Enhanced mode, load the script only after consent. This isn't legal advice; check with your counsel if you're unsure. See our cookie policy, privacy policy and DPA.

Ready for GDPR-Compliant Analytics?

Switch to privacy-first analytics with no third-party cookies, no ads and no cross-site tracking. 14-day free trial of Starter, no credit card required.

Try privacy-first analytics on your own site.

No cookies by default, no ads, no cross-site tracking. Every feature on every plan.

Start free trial

14-day free trial of Starter · No credit card