GDPR-compliant analytics: what to check before you choose
General information, not legal advice. GDPR and national rules are applied differently by each regulator, and the facts below were checked on 13 November 2026. If your case is complex, ask a qualified adviser or your data protection authority.
Definitions in one minute
- Controller: you, the website owner. You decide why and how visitor data is processed, and you are responsible for the lawful setup.
- Processor: the analytics vendor that processes visitor data on your behalf under your instructions (GDPR Article 28).
- Sub-processor: a company the vendor uses to deliver the service, such as hosting or a database provider.
- Personal data: any information relating to an identifiable person. GDPR lists online identifiers among the examples, and an IP address can be personal data.
- Pseudonymous vs anonymous: pseudonymous data can still be linked back to a person with extra information and stays within GDPR. Truly anonymous data is outside it, but the bar is high. Be wary of any tool that calls itself anonymous without explaining how.
- ePrivacy Article 5(3): a separate EU rule about storing or reading information on a visitor's device. It applies in addition to GDPR.
The short answer
Think of a GDPR analytics review as two questions: *is my use lawful and documented?* (GDPR) and *does the tool touch the visitor's device?* (ePrivacy). A tool can make both easier by collecting less, but it cannot take the responsibility away from you. The checklist below gives you ten checks you can finish in an afternoon. For each one you get what to look for and what to ask.
The ten-point checklist
1. Data location and international transfers
- Look for: where the data is stored and processed, and whether people outside the EU/EEA can access it (for support or operations).
- Why it matters: GDPR Chapter V (Articles 44 to 49) only allows transfers outside the EU/EEA with a valid tool, such as an adequacy decision, standard contractual clauses (SCCs) or binding corporate rules.
- Ask: In which region is the data stored? Which companies, in which countries, can access it? Which transfer mechanism applies to each?
- Good to know: The EU-US Data Privacy Framework (adequacy decision of 10 July 2023) lets you transfer to US companies that are certified, and you can look up a company on the official Data Privacy Framework list. The General Court dismissed a challenge to it on 3 September 2025 (Case T-553/23). An appeal is pending at the Court of Justice as Case C-703/25 P, so it is worth knowing the vendor's fallback, such as SCCs. EU data storage reduces the transfer question but does not remove it if the vendor or its sub-processors are based elsewhere.
2. IP address handling
- Look for: whether the full IP address is stored, truncated or never saved, and whether it is sent to a third party for location lookup.
- Why it matters: GDPR recital 30 names IP addresses among online identifiers, and the Court of Justice has held that even a dynamic IP address can be personal data in some situations (Breyer, C-582/14).
- Ask: Is the IP stored anywhere, including logs? If it is truncated, to what length and when?
3. Identifiers and fingerprinting
- Look for: what is used to recognise a returning visitor: a stored identifier, a rotating hash, or a mix of browser traits.
- Why it matters: an identifier that lasts across days or sites is a stronger form of tracking. The EDPB's Guidelines 2/2023 (version 2.0, adopted 7 October 2024) say Article 5(3) is not limited to browser storage and also covers other techniques that gain access to information on a device, so fingerprinting is not a loophole.
- Ask: Does a visitor keep the same identifier across days, across your sites or across other customers' sites? Is it combined with any other data set?
4. Retention
- Look for: how long raw visit data and aggregated statistics are kept, and whether deletion is automatic.
- Why it matters: the storage limitation principle (Article 5(1)(e)) says personal data should be kept no longer than necessary. For audience measurement, France's CNIL recommends a maximum of 25 months for collected information and a periodic review of the retention period.
- Ask: What is the default retention? Can I shorten it? What happens to backups when I delete a site or account?
5. Processor agreement (Article 28)
- Look for: a data processing agreement (DPA) you can accept before launch.
- Why it matters: Article 28(3) requires a contract that sets out subject matter, duration, nature and purpose of the processing, the type of data, and obligations including processing only on your documented instructions, confidentiality, security, help with data subject requests, breach notification, deletion or return at the end, and audit information.
- Ask: Is the DPA part of signup or only on request? Does it include the sub-processor list and the transfer mechanism? Does the vendor use visitor data for its own purposes? If it does, that is a red flag for the processor role and for the CNIL exemption (see check 8).
6. Sub-processors
- Look for: a public, current list with company names, services and locations, and a way to be told about changes in advance.
- Why it matters: the EDPB's Opinion 22/2024 says controllers should have the identity details of all processors and sub-processors readily available and should verify that they offer sufficient guarantees, with more checking where risk is higher.
- Ask: Who are all the sub-processors and where are they? How much notice do I get of a new one, and can I object?
7. Data subject rights
- Look for: how the vendor helps you answer access, deletion, objection and other requests (Articles 12 to 22).
- Why it matters: if a tool cannot find one visitor's records, you cannot honestly answer an access request. That is another reason pseudonymous, short-lived identifiers are easier to handle than long-lived ones.
- Ask: Can you find, export or delete the data of one person? If not, how do you document why?
8. Consent interplay (ePrivacy Article 5(3))
- Look for: whether the script stores or reads anything on the visitor's device, and what your country's regulator says about analytics.
- Why it matters: Article 5(3) needs consent unless the storage or access is strictly necessary for a service the user asked for. Regulators differ on analytics. The CNIL says audience measurement can be exempt if it is strictly limited to your own site's statistics, produces anonymous statistics only, does not combine data with other processing, does not pass non-anonymous data to third parties and does not follow people across sites (page updated 4 July 2025). Germany is stricter. See our country overview and the plain-language consent banner guide.
- Ask: Does the vendor reuse data for its own purposes? Does it provide documentation for the CNIL criteria or your regulator's? Remember that the CNIL does not certify tools, so be cautious about any "CNIL-approved" claim.
- Never assume that a tool means you need no consent anywhere. Check your country, and document your reasoning.
9. Security
- Look for: encryption in transit and at rest, access control with multi-factor sign-in, a breach process, and independent audit reports where they exist.
- Why it matters: Article 32 requires security that fits the risk, and Article 33 gives the controller 72 hours to report certain breaches to the authority once aware, so a processor must tell you quickly.
- Ask: How fast will you tell me about a breach? Who can access production data? Can you share a summary of your measures?
10. DPIA and your own records
- Look for: whether your use needs a data protection impact assessment, and whether you have updated your records of processing (Article 30) and your privacy policy.
- Why it matters: Article 35 requires a DPIA when processing is likely to result in a high risk, for example large-scale monitoring of publicly accessible areas or large-scale special-category data. Basic site statistics are usually not high risk, but combining analytics with profiling, advertising or sensitive sites can change that. Your national authority publishes a DPIA list.
- Do: Write down what you collect, why, on which legal basis (often legitimate interest, Article 6(1)(f), for pure statistics, or consent where required), and for how long. Mention your analytics in your privacy policy.
A one-page vendor question list
- Where is data stored, and who can access it from where?
- Is any IP address stored, even briefly?
- How do you recognise a returning visitor, and for how long?
- What is the default retention and can I change it?
- Is your Article 28 DPA available now? Where is the sub-processor list?
- Do you use my visitors' data for your own purposes?
- How do I handle an access or deletion request?
- Does your script store or read anything on the visitor's device?
- What are your security measures and breach timeline?
- Do you provide documentation I can keep for my own records?
How Countnest answers these checks
Verified against our own legal pages and code on 13 November 2026:
- Location: database and authentication run in AWS eu-central-1 (Frankfurt) via Supabase, and application functions in Vercel's Frankfurt region. Some sub-processors are US-based companies, and transfers rely on the DPF and/or SCCs. See the DPA for the current list.
- IP address: never saved. A daily-rotating one-way code (hash of IP, browser type, a secret key and the site ID) is used to count unique visitors, and the key is deleted within about two days.
- Identifiers: nothing is stored on the visitor's device, no cross-day or cross-site tracking, no profiles. Visits from browsers that send Do Not Track or Global Privacy Control are not counted.
- Retention: raw analytics are deleted automatically after 25 months.
- Honest limits: our records are pseudonymous, not anonymous in the strict legal sense, because same-day visits from one browser and network can be grouped. That is why we never claim that consent is unnecessary. You remain the controller and must check your own country's rules.
For more on how it works, see privacy-friendly analytics, Google Analytics alternatives, the privacy rules worldwide overview and the Countnest vs Google Analytics comparison. You can try it with a 30-day free trial (no card required).
Official sources
- EU: GDPR, Regulation (EU) 2016/679 (EUR-Lex)
- EDPB: Guidelines 2/2023 on the technical scope of Art. 5(3) ePrivacy
- EDPB: Opinion 22/2024 on processors and sub-processors
- CNIL: Audience measurement exemption (in French)
- US transfers: Data Privacy Framework programme and Case C-703/25 P (EUR-Lex)
- Directory: EU data protection authorities
General information, not legal advice. Checked 13 November 2026. Regulator guidance and court cases change, so confirm current positions before you rely on this.
Questions and answers
Is there such a thing as a GDPR-compliant analytics tool?
Not by itself. Compliance depends on how the controller, meaning you, configures the tool, documents the legal basis, informs visitors and signs the right agreements. A tool can make compliance easier by collecting less data and by being open about processing. This is general information, not legal advice.
Do I need a data processing agreement with my analytics provider?
Yes, if the provider processes personal data for you. GDPR Article 28(3) requires a binding contract covering things such as documented instructions, confidentiality, security, sub-processors, assistance with rights requests, breach notification and deletion or return of data.
Is an IP address personal data?
It can be. GDPR recital 30 lists online identifiers, and the Court of Justice held in Breyer (C-582/14) that a dynamic IP address can be personal data where the website operator has legal means to identify the person. Ask whether a tool stores IPs, even briefly in logs.
Can I use analytics without a consent banner?
It depends on the country and the tool. ePrivacy Article 5(3) needs consent for storing or reading information on a device unless strictly necessary. France's CNIL describes conditions for an exemption for audience measurement; Germany's regulators are stricter. Check your national regulator, and never assume no consent is needed anywhere. See our country overview for details.
Is the EU-US Data Privacy Framework still valid?
As of 13 November 2026 it remains in force. The General Court dismissed a challenge on 3 September 2025 (T-553/23), and an appeal (C-703/25 P) is pending before the Court of Justice. Ask vendors which fallback, such as SCCs, they use.
How long should analytics data be kept?
GDPR sets no fixed number: it asks you to keep data no longer than necessary. For audience measurement, the CNIL recommends at most 25 months and a periodic review. Choose a period you can justify and document it.
Do I need a DPIA for website analytics?
Often not for basic statistics, but Article 35 requires one when processing is likely to be high risk, for example large-scale profiling or sensitive data. Check your authority's DPIA list and document your reasoning.
Does EU hosting make a tool GDPR-compliant?
No. EU storage helps with transfers, but you still need a lawful basis, processor terms, retention limits, security and honest information to visitors. Also check whether non-EU companies can access the data.
30-day free trial, no card required. Then from $14 a month. Cancel anytime.
Start free for 30 daysSources
- EUR-Lex: Regulation (EU) 2016/679 (GDPR)
- EDPB Guidelines 2/2023 on the technical scope of Art. 5(3) ePrivacy Directive
- EDPB: Opinion 22/2024 on certain obligations following from the reliance on processor(s) and sub-processor(s)
- CNIL: Solutions for audience measurement tools (updated 4 July 2025, in French)
- Data Privacy Framework Program (US Department of Commerce)
- EUR-Lex: Case C-703/25 P, Latombe v Commission (appeal, OJ C/2025/6610)
- EDPB: Members (national data protection authorities)