- Denmark has two regimes that run side by side: the cookie order (supervised by the Danish Agency for Digital Government, DIGST) and the GDPR (supervised by Datatilsynet). Their May 2025 joint guidance says visit statistics need consent as a rule. Denmark has no analytics carve-out like France’s.
- Datatilsynet’s September 2022 statement said Google Analytics could not be used lawfully without supplementary measures. In July 2023 it added that the new EU-US framework fixes one issue only and that it had not ruled Google Analytics lawful.
- As of 2 October 2026 the EU-US Data Privacy Framework (DPF) adequacy decision is still in force. A US Supreme Court ruling in June 2026 has prompted the EDPB to ask the Commission to assess it. I found no suspension or withdrawal.
- “EU hosting” answers where data sits. The EDPB treats remote access from a third country as a transfer, so who can reach the data matters as much as where it is stored.
- This is general information, not legal advice. Confirm your setup with your DPO or a Danish privacy lawyer.
“Is Google Analytics legal in Denmark?” The honest answer has moved several times since 2022. This post goes to the regulators’ own pages, dates every claim, and ends with a table you can use on a real site. It belongs to our privacy series; the hub is Consent Mode v2 on WordPress.
This is not legal advice. I summarise what authorities and courts have published, with links, and I translate Danish sources myself. Your lawful basis, contracts and vendor choices depend on facts only you and your counsel know. All status statements below are “as of October 2026”; I checked each against the page linked beside it.
Two regimes, two supervisors
The Danish joint guidance of May 2025, written by Datatilsynet and DIGST, starts from a simple split. The cookie order applies when you store or access information on a visitor’s equipment. The data protection rules apply when you process personal data in the process. Both are technology neutral, and DIGST supervises the first while Datatilsynet supervises the second (joint guidance, sections 1 and 2). Our post on whether server-side tracking bypasses consent covers why moving a call to the server changes neither.
What the cookie order says
Section 3 of the order (Bekendtgørelse nr. 1148 of 9 December 2011, as published in Lovtidende; check Retsinformation for the current consolidated text) forbids storing or accessing information in an end user’s equipment, or letting a third party do so, unless the user consents after receiving adequate information. Section 4 allows two exceptions: storage or access solely to transmit a communication, or required to deliver a service the user explicitly requested. Section 5 makes violations of section 3 punishable by fine.
The joint guidance then applies this to analytics, and this is where Denmark differs from France:
- You must obtain consent if you use cookies and similar technologies for purposes such as generating visit statistics or showing personalised ads (section 3.1, my translation).
- Technically necessary technologies such as login, shopping carts and user-chosen settings are exempt. The guidance does not list statistics among them.
- Consent is also needed where third parties collect information on your service, even if you do not get access to what they collect (section 2.1).
- Personal data includes IP addresses, advertising IDs and other identifiers that are unique to a user, whether or not you know their name (section 2.2.1).
France’s CNIL, by contrast, publishes conditions under which strictly limited audience measurement can run without consent. I summarised those in the post on server-side tracking and compare them with the Danish position in Do you need a cookie banner for WordPress analytics?. For a Danish site, plan on consent for statistics unless your lawyer has reasoned otherwise.
The Google Analytics story, in dated steps
10 February 2022: the CNIL order
The CNIL’s own page (it has since been taken down from the live site; I read the archived copy) records the first French decision. It followed complaints from the NGO noyb, which filed 101 complaints across the EU and EEA. The CNIL concluded that the data collected via Google Analytics, including a unique visitor identifier, was transferred to the United States in breach of Article 44 and following of the GDPR. Google’s additional measures were, in its view, not enough to exclude access by US intelligence services. It gave the site operator one month to comply, “if necessary” by stopping the tool under current conditions or by using one that involves no transfer outside the EU.
21 September 2022: Datatilsynet
Datatilsynet’s press release (the page is gone from the live site and now returns “Page Not Found”; I read an archived copy) said the authority had looked at the tool and its settings and concluded that “the tool cannot, without more, be used lawfully”. Lawful use required supplementary measures beyond Google’s own settings. It tied this to decisions by the Austrian, French and Italian authorities, handled together in an EDPB working group. Its message to Danish organisations: assess your use; bring it into compliance, or stop. As one possible technical measure it pointed to pseudonymisation through a reverse proxy, as described in CNIL guidance.
This was about transfers to the US when no adequacy decision existed, not about consent, and those conditions have since changed.
10 July 2023: the Data Privacy Framework
The European Commission adopted its adequacy decision for the EU-US Data Privacy Framework on 10 July 2023. Per the Commission, personal data can flow freely from the EU to US companies that participate in the framework (Commission page, press release IP/23/3721).
31 July 2023: Datatilsynet cools the headlines
Media then claimed Datatilsynet had declared Google Analytics lawful again. The authority corrected this: it “has not taken a position on whether Google Analytics is lawful”. The new agreement allows transfers to the US “under certain circumstances”, but before you get there you must satisfy a long list of basic GDPR requirements, including legal basis, the processor setup and agreement, possible joint controllership and data subject rights. That applies to Google Analytics “even if” the transfer to the US can, taken in isolation, be lawful again (Datatilsynet, 31 July 2023; my translation). It said it would update its guidance on cloud, third-country transfers and Google Analytics. I did not find a replacement Google Analytics statement.
That is the most useful sentence in the whole saga. A valid transfer mechanism is a precondition, not a verdict.
Where the Data Privacy Framework stands
A competitor page claims a June 2026 US Supreme Court ruling has undone the framework. Here is what I could verify from primary sources, and what I could not.
- The ruling exists. On 29 June 2026 the US Supreme Court decided Trump v. Slaughter (No. 25-332). It held that the FTC’s for-cause removal protection for its commissioners is contrary to the separation of powers (slip opinion syllabus). The opinion is about US constitutional law. In the text I searched, it does not mention the EU or the framework.
- Why it matters to the EU. The EDPB wrote to Commissioner McGrath on 31 July 2026. It noted that the existence of independent supervisory authorities is a key element of an adequacy assessment, that the Commission’s decision (EU 2023/1795) explicitly refers to the independence of US authorities including the FTC, and asked the Commission to “closely assess whether this development affects the functioning” of the decision (EDPB letter). That is a request for assessment. It is not an instruction to stop transferring.
- The campaigners’ position. On 29 June noyb published a statement, and on 30 June sent a letter, asking the Commission to withdraw the adequacy decision in an orderly way and saying it would file a lawsuit within weeks (noyb). noyb is an advocacy group, and its own page says the decision is “formally in force” until the Commission repeals it or the Court of Justice annuls it. I found no confirmation that a lawsuit has been filed.
- The Commission. I found no suspension, repeal or amendment. Commissioner McGrath said on 22 July 2026 that the EU “remains committed to this Framework” while monitoring it closely (Agence Europe, a secondary report). A September 2026 law-firm note says the Commission is “carefully analysing” the ruling (Faegre Drinker, secondary).
- Court challenges. The General Court dismissed Philippe Latombe’s action against the decision on 3 September 2025 (case T-553/23). An appeal, C-703/25 P, was lodged on 31 October 2025 and, per a September 2026 law-firm note, remains pending. I could not open the Court’s own page for the appeal, so treat the appeal details as reported by secondary sources (Digital Policy Alert).
So the accurate summary for October 2026: the framework is valid and usable, under visible pressure, with an appeal and possible new litigation pending.
What the framework does and does not give you
The EDPB’s FAQ for European businesses (version 2.0, adopted 15 January 2026) is the clearest checklist (PDF). It says, in substance:
- Before transferring you must confirm that the US company holds an active self-certification on the Data Privacy Framework List run by the US Department of Commerce, and that it covers the data in question. Certifications are renewed annually.
- For a certified recipient, you satisfy Chapter V of the GDPR (transfers), but all other GDPR requirements still apply.
- If the US recipient is a processor, you need a data processing agreement under Article 28 whether or not it is certified.
- If it is a controller, you need your own legal basis, and you must tell people about the recipient and the framework in your privacy notice.
- If a recipient is not certified, other tools such as standard contractual clauses (SCCs) can be used instead.
What “EU hosting” does and does not solve
“Our data stays in the EU” sounds like a full answer. The EDPB’s guidelines on transfers (Guidelines 05/2021, version 2.0, February 2023) say it is not, for two reasons you can quote to a vendor (PDF):
- Remote access counts. Remote access from a third country, “even if it takes place only by means of displaying personal data on a screen”, for example for support or troubleshooting, is also considered a transfer. Example 11 describes a non-EU processor remotely accessing data stored in the EU and concludes that this results in transfers.
- Ownership can matter. Where an EU processor is subject to third-country legislation and could receive government access requests, the guidelines recall that controllers may only use processors providing sufficient guarantees (Article 28(1)), and say reliability “may be in doubt” if the processor is subject to third-country law that may prevent it from fulfilling its obligations.
That is the sourced version of the “EU-owned versus EU-hosted” nuance. It does not say that US-owned vendors with EU data centres are unlawful. It says you must look at who can access the data and under which laws, and document the answer. Under the framework an active certification can resolve the transfer question for a US-owned vendor. For a vendor outside it, SCCs or other tools are the route.
What a Danish WordPress site owner or agency should check
1. What data leaves the EU
List every script, plugin and service that sends visitor data somewhere, including fonts, maps, chat widgets and tag managers. The Danish guidance lists third-party tools such as fonts, maps, video players and statistics modules as things that can collect information about your visitors (section 2).
2. Roles and the processor agreement
The Danish guidance works through examples. A company that hosts its own analytics tool is the controller (example 8). A hosting company running the site on your behalf is typically a processor (example 9), and an analytics agency delivering a hosted tool is typically a processor too, usually under a data processing agreement (example 10, section 3.6). Example 11 flips it: if the provider also uses the data for its own purposes, for instance offering the tool free in exchange, the parties may be joint controllers. Check vendor terms for own-use clauses. Agencies should write down in the contract who is processor for what; that depends on the facts, so ask counsel.
3. Transfer mechanism
For each non-EEA recipient: an active DPF listing that covers your data, or SCCs, plus whatever assessment your counsel advises. Date the check. Put it on a calendar, given the status above.
4. IP address handling
The Danish guidance treats IP addresses as personal data. Ask each tool whether it stores full IPs, truncates them, or uses them only for geolocation and then discards them. Ask where that happens. Prefer to receive less. If you do not need city-level data, do not collect it.
5. Retention
Set a period you can defend and check that the tool enforces it. As a reference point only, the CNIL’s guidance for exempt audience measurement recommends a tracker lifetime of 13 months and retention of at most 25 months (CNIL, 4 July 2025). Those figures belong to the French exemption, not Danish law. For GA4 settings see our GA4 retention post.
6. Consent
Under the Danish guidance, a consent banner that gates statistics is the default path. Valid consent must be specific and informed, you need documentation, and a banner that loads tags before the choice defeats the point. Consent Mode v2 is a way to carry the choice to Google tags; it does not decide where the data goes.
Five common setups, three questions
Some notes on the rows:
- GA4 with Consent Mode. Google’s documentation says that in basic mode no data is sent to Google, not even the consent status, until the visitor chooses; in advanced mode tags load and send cookieless pings while consent is denied (Google Ads Help). Which one your site runs is a legal as well as a technical choice, so get it reviewed.
- Self-hosted. Putting a tool on your own EU server removes the third-party recipient. It does not remove your role as controller, your retention duty, or the cookie rule if the tool sets cookies. Whether a tool that sets no identifiers falls outside the cookie order is a case-by-case question (see our server-side consent post).
- EU vendor. A processor agreement is the baseline. Then ask the EDPB’s two questions: who can access the data from outside the EEA, and which third-country laws apply to the vendor.
- Server-side forwarding. Each ad platform is a separate recipient with its own purposes. The same checks apply per destination, and the Danish guidance requires consent for personalised ads.
For a tool comparison, see Best GA4 alternatives for WordPress.
Where Traculo fits
Traculo includes a built-in data processing agreement, which gives you a contract template to start from. The plugin sends visitor IP addresses to Traculo’s API and, for form events, SHA-256 hashes of email, phone and name plus the sanitized submitted values, so treat it as processing personal data. A template is not a statement that any setup is compliant, and this post does not claim that Traculo is “GDPR compliant”. Its DPA lists AWS (EU-West-1, EU-Central-1) as primary hosting, Standard Contractual Clauses for transfers outside the EEA, a public sub-processor list and breach notice within 48 hours. Traculo’s API reads no consent signal and forwards every event the plugin sends.
Frequently asked questions
Is Google Analytics legal in Denmark in 2026?
Datatilsynet has not said either way. Its 2022 statement said the tool could not be used lawfully without supplementary measures at a time when no US adequacy decision existed. In July 2023 it said it had not taken a position on lawfulness, and that the transfer question is only one of many GDPR requirements. The tool is not banned, and “legal” is not a property of the tool alone. It depends on your consent, contracts, configuration and transfer basis.
Does the Data Privacy Framework make US tools safe to use?
It addresses one question: the transfer mechanism, for recipients with an active certification covering your data. Per the EDPB FAQ, all other GDPR duties remain, and a processor agreement is needed regardless. And as of October 2026 the framework is under scrutiny following Trump v. Slaughter and a pending appeal.
Did the US Supreme Court invalidate the framework?
No. The Supreme Court did not rule on the framework. It decided a US constitutional case about FTC commissioners. The EDPB has asked the Commission to assess the effect, noyb has called for withdrawal, and I found no Commission suspension or repeal.
Does hosting my analytics in the EU solve the transfer problem?
Not by itself. The EDPB counts remote access from a third country as a transfer. Pair EU hosting with an answer on access and ownership.
Do I need a cookie banner for analytics in Denmark?
The joint Datatilsynet and DIGST guidance says consent is needed as a rule for cookies and similar technologies used to generate visit statistics. See our cookie banner post for the exemptions authorities describe elsewhere.
Related reading
- Consent Mode v2 on WordPress: the four signals
- Does server-side tracking bypass consent?
- How much data do ad blockers cost a WordPress site?
- Do you need a cookie banner for WordPress analytics?
- Best GA4 alternatives for WordPress
- Client-side vs server-side tracking in WordPress
- Why is your WordPress analytics data missing?
Want website analytics for WordPress with a processor agreement you can read before you sign up? Have a look at Traculo’s website analytics, and ask us the transfer questions above while you are there.