EU-hosted analytics: what it solves, what it doesn't, and what to check
General information, not legal advice. The facts below were checked on 14 November 2026 against the official sources linked in each section. Court cases and regulator positions change, so confirm the current status before you rely on them, and ask a qualified adviser or your data protection authority if your situation is complex.
Definitions in one minute
- EU-hosted (data residency): the servers that store and process the data are physically in the EU or EEA, for example in Frankfurt, Paris or Stockholm.
- EU-owned (data sovereignty): the company and all its providers are EU entities, so non-EU laws reach them less directly. A tool can be EU-hosted without being EU-owned.
- International transfer: under GDPR Chapter V (Articles 44 to 49), sending personal data to a country outside the EU/EEA, or giving someone there access to it. Remote access from outside the EEA can count, not only copying files.
- Adequacy decision: a European Commission decision that a non-EU country (or, for the US, a certified company) protects personal data to an essentially equivalent level, so data can flow there without extra paperwork.
- SCCs: standard contractual clauses, the Commission's model contract for transfers (Decision (EU) 2021/914), used when there is no adequacy decision.
- CLOUD Act: a US law from March 2018 that lets US authorities require US-based providers to hand over data in their possession, custody or control for criminal investigations, wherever the data is stored.
The short answer
"EU-hosted" answers one question well: *where does the data live?* It does not, by itself, answer two others: *who can reach it from outside the EU?* and *is my use lawful and documented?* Treat EU hosting as a strong starting point that removes most transfer paperwork, then check access, contracts and consent the same way you would for any tool. Our GDPR-compliant analytics checklist covers the full list; this guide focuses on location and transfers.
Why data location became a big question
- 16 July 2020, Schrems II: the Court of Justice of the EU (Case C-311/18) struck down the EU-US Privacy Shield because US surveillance law did not give Europeans protection essentially equivalent to EU law. SCCs stayed valid, but only with an assessment and, where needed, supplementary measures, which the EDPB described in its Recommendations 01/2020.
- August 2020: the privacy group noyb filed 101 model complaints against websites using US tools, many of them about Google Analytics.
- 2022 to 2023, regulator decisions on Google Analytics: several authorities found that specific websites had transferred personal data to the US unlawfully through Google Analytics, because the safeguards in place at the time could not prevent access by US intelligence services. Examples: Austria's DSB (decision published by noyb on 13 January 2022), France's CNIL (decision ordering a website to comply, announced 10 February 2022), Italy's Garante (announced 23 June 2022), Sweden's IMY (3 July 2023, with a SEK 12 million fine for Tele2 and SEK 300,000 for CDON) and Norway's Datatilsynet (2023 decision on telenor.com).
- Important context: those decisions looked at periods before the EU-US Data Privacy Framework was adopted on 10 July 2023. Norway's authority noted that the new rules affect the tool's lawfulness going forward. They are a lesson about transfers, not a ban on any brand today.
Where the EU-US Data Privacy Framework stands (as of November 2026)
- In force: the Commission's adequacy decision (Implementing Decision (EU) 2023/1795) lets data flow to US companies that are certified on the official Data Privacy Framework list. The Commission's EU-US data transfers page also says the US national-security safeguards apply to all transfers to US companies, whichever tool is used, including SCCs.
- First court test passed: on 3 September 2025 the General Court dismissed Philippe Latombe's action to annul the framework (Case T-553/23, press release 106/25).
- Appeal pending: Mr Latombe appealed on 31 October 2025 (Case C-703/25 P). As of 14 November 2026 we found no judgment or Advocate General opinion, and no date has been announced.
- New question in 2026: on 29 June 2026 the US Supreme Court decided Trump v. Slaughter, removing the "for cause" protection for Federal Trade Commission commissioners. The FTC enforces the framework's commercial rules, and the adequacy decision refers to that protection. On 31 July 2026 the EDPB wrote to the Commission asking it to "closely assess" whether this affects the decision. The letter does not suspend anything; the framework remains in force unless the Commission changes it or the Court annuls it.
- What this means for you: US tools that rely on the framework are usable today, but the framework has fallen twice before in other forms (Safe Harbour in 2015, Privacy Shield in 2020). EU hosting and a fallback such as SCCs reduce the disruption if it falls again.
The CLOUD Act: why "EU-hosted" is not the whole story
The CLOUD Act (March 2018) added a rule to US law, 18 U.S.C. § 2713, that requires covered providers to disclose data in their "possession, custody, or control" when lawfully ordered, "regardless of whether" it "is located within or outside of the United States". So if your analytics vendor, or its hosting or database provider, is a US company, data stored in Frankfurt can still be in scope of a lawful US request. Providers often publish how they challenge such requests and how many they receive; that is worth reading. Points to keep in mind:
- This is about who controls the data, not only where it sits.
- Most EU-hosted tools still use some US-headquartered providers (cloud, email, payments). That is common and can be lawful with the right transfer tool, but it should be disclosed in the sub-processor list.
- Collecting less data is the strongest protection: data that was never saved cannot be requested. That is why IP handling and identifiers matter as much as location.
What EU hosting solves, and what it doesn't
| Question | EU hosting helps? | What you still need to check |
|---|---|---|
| Is personal data stored outside the EU/EEA? | Yes, largely | Backups, logs and support tools may sit elsewhere |
| Can people outside the EU access it? | Partly | Vendor support, US parent or sub-processors, CLOUD Act exposure |
| Is there a valid transfer tool where needed? | Less needed | DPF certification or SCCs for each non-EEA recipient |
| Do I need consent under ePrivacy Article 5(3)? | No effect | Depends on what the script stores or reads on the device and on your country's rules |
| Do I have a legal basis and a processor agreement? | No effect | Article 6 basis, Article 28 DPA, privacy notice |
| How long is data kept? | No effect | Retention settings and deletion, including backups |
Consent is separate from location. EU hosting never answers the ePrivacy question on its own, and the rules differ by country. See our country overview on analytics consent in Europe and the plain-language consent banner guide. Never assume that hosting in the EU means you can skip consent.
A short checklist for choosing EU-hosted analytics
- Region: which data centre stores the raw visits, and which processes them? Ask for the exact region (for example AWS eu-central-1, Frankfurt).
- Edge and logs: does traffic pass through a global network first? Are IP addresses written to logs, and where?
- Company and parents: where is the vendor incorporated, and are its key providers US companies?
- Sub-processors: is there a public list with locations and transfer tools, and advance notice of changes? The EDPB's Opinion 22/2024 expects controllers to have this information readily available.
- Transfer tool: for each non-EEA recipient, is it DPF-certified (check the official list yourself) or covered by SCCs?
- Data minimisation: is the IP address stored? Is anything stored on the visitor's device? Is there cross-site or cross-day tracking?
- Retention: what is the default, and can you shorten it?
- Exit plan: if the framework fell tomorrow, what would change for this vendor? A good answer names a fallback.
Outside the EU
Countnest is used worldwide, and we use GDPR as the strictest baseline. Other places have their own transfer and localisation rules: the UK relies on its own adequacy regulations and the UK Extension to the DPF for certified US companies, Switzerland on the Swiss-US DPF, and countries such as Brazil, India and China each have their own regimes. Our privacy rules worldwide overview is a starting point.
How Countnest handles location and transfers
Checked against our own legal pages on 14 November 2026:
- Location: analytics data is stored in the EU. The database and authentication run in AWS eu-central-1 (Frankfurt) via Supabase, and application functions run in Vercel's Frankfurt region. Vercel's edge network, which first receives requests, is global.
- Company: Countnest is made by IDCPH ApS, a company in Copenhagen, Denmark.
- Honest limits: several of our sub-processors are US-headquartered companies and may access data from outside the EEA for support or operations. Those transfers rely on the EU-US Data Privacy Framework where the provider is certified and otherwise on the Commission's SCCs. The current list is in our DPA.
- Less data to begin with: IP addresses are never saved, nothing is stored on visitors' devices, and raw analytics are deleted automatically after 25 months. Our records are pseudonymous, not anonymous in the strict legal sense, so we never claim that consent is unnecessary. You remain the controller and must check your own country's rules.
- Optional features you control: if you turn on conversion forwarding (Growth and Agency plans), conversions from consented visits are sent to the ad platform you choose, under your own agreement with that platform.
Compare options in our Google Analytics alternatives guide and the Countnest vs Google Analytics comparison, or read how privacy-friendly analytics works. You can try Countnest with a 30-day free trial (no card required).
Official sources
- EU: GDPR, Regulation (EU) 2016/679 (EUR-Lex)
- Court of Justice: Schrems II, Case C-311/18 (EUR-Lex)
- General Court: Latombe v Commission, T-553/23, press release 106/25 and the appeal C-703/25 P (EUR-Lex)
- European Commission: EU-US Data Privacy Framework adequacy decision 2023/1795 (EUR-Lex) and EU-US data transfers
- EDPB: Recommendations 01/2020 on supplementary measures and letter of 31 July 2026 on Trump v. Slaughter
- US: Data Privacy Framework list and DOJ CLOUD Act resources and 18 U.S.C. § 2713
- Directory: EU data protection authorities
General information, not legal advice. Checked 14 November 2026. Regulator guidance and court cases change, so confirm current positions before you rely on this.
Questions and answers
What does EU-hosted analytics mean?
It means the analytics data is stored and processed on servers inside the EU or EEA. It is about location. It does not by itself tell you who can access the data from outside the EU or whether your use is lawful under GDPR and ePrivacy. This is general information, not legal advice.
Does EU hosting make an analytics tool GDPR-compliant?
No. It makes the transfer rules in GDPR Chapter V easier, but you still need a legal basis, a processor agreement under Article 28, sensible retention, honest information to visitors, and consent where your country's ePrivacy rules require it.
Is the EU-US Data Privacy Framework still valid in November 2026?
Yes. As of 14 November 2026 the adequacy decision of 10 July 2023 remains in force. The General Court upheld it on 3 September 2025 (T-553/23), an appeal (C-703/25 P) is pending at the Court of Justice, and in July 2026 the EDPB asked the Commission to assess the effect of the US Supreme Court's Trump v. Slaughter ruling. Keep a fallback such as SCCs.
Can the US CLOUD Act reach data stored in the EU?
It can. The CLOUD Act (18 U.S.C. § 2713) requires covered US providers to disclose data in their possession, custody or control when lawfully ordered, regardless of whether it is stored inside or outside the United States. If your vendor or its hosting provider is a US company, EU storage alone does not take the data out of scope. Collecting less data, such as never saving IP addresses, limits what could be requested.
Was Google Analytics banned in Europe?
No general ban exists. Between 2022 and 2023, authorities in Austria, France, Italy, Sweden and Norway found that specific websites had transferred data to the US unlawfully through Google Analytics, for periods before the Data Privacy Framework was adopted in July 2023. Today, transfers to US companies certified under the framework can rely on it; you can check any company on the official list.
Do I still need consent if my analytics is hosted in the EU?
Possibly. Consent under ePrivacy Article 5(3) depends on what the script stores or reads on the visitor's device and on your country's rules, not on where the server is. Check your national regulator and document your reasoning.
Where does Countnest store data?
In the EU: the 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-headquartered, and transfers rely on the DPF and/or SCCs; see the DPA for the current list.
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)
- EUR-Lex: Judgment in Case C-311/18 (Schrems II), 16 July 2020
- EUR-Lex: Commission Implementing Decision (EU) 2023/1795 (EU-US Data Privacy Framework)
- EUR-Lex: Commission Implementing Decision (EU) 2021/914 (standard contractual clauses)
- CJEU press release 106/25: General Court judgment in T-553/23, Latombe v Commission (3 September 2025)
- EUR-Lex: Case C-703/25 P, Latombe v Commission (appeal, OJ C/2025/6610)
- European Commission: EU-US data transfers
- EDPB: Letter to Commissioner McGrath on Trump v. Slaughter (31 July 2026)
- EDPB: Recommendations 01/2020 on measures that supplement transfer tools
- EDPB: Opinion 22/2024 on processors and sub-processors
- Data Privacy Framework Program (US Department of Commerce)
- US Department of Justice: CLOUD Act resources
- 18 U.S.C. § 2713 (CLOUD Act), Cornell LII
- CNIL decision on Google Analytics (February 2022, published by the EDPB)
- noyb: Austrian DSB decision on Google Analytics (13 January 2022)
- Garante per la protezione dei dati personali: Google Analytics (23 June 2022, in Italian)
- IMY: Four companies must stop using Google Analytics (3 July 2023, in Swedish)
- Datatilsynet (Norway): Decision in the Google Analytics case (2023, in Norwegian)
- EDPB: Members (national data protection authorities)