Guide

EU data sovereignty for team chat: a plain guide from Buzz Messaging

EU data sovereignty for team chat: GDPR transfers, the CLOUD Act, Schrems II, NIS2 and encryption, with a 15-term glossary and a vendor checklist.

Close-up of a bundle of black network cables in a server rack, with one glowing yellow cable in focus.

Last reviewed: 6 November 2026. This guide explains the law in plain terms. It is not legal advice.

EU data sovereignty means a European organisation decides which law governs its data, where that data is stored and who can read it. A vendor's choice of data centre is only one part of it. For team chat this matters more than for most tools, because chat is where contracts, HR issues and customer details actually get discussed.

TL;DR

  • Sovereignty is three questions: which law reaches the vendor, where the data sits, and who holds the keys.
  • "EU-hosted" answers only the second question. A US-owned vendor with EU servers can still receive US legal orders.
  • The rules that matter most are GDPR's transfer rules, the US CLOUD Act, US foreign-intelligence surveillance law (FISA), and the EU's own e-Evidence Regulation, which has applied since 18 August 2026.
  • Hosting location and GDPR compliance are different things: GDPR applies to how data is processed, wherever the servers are.
  • Encryption narrows what anyone can be forced to hand over, but metadata usually stays visible.

What is EU data sovereignty?

EU data sovereignty is the ability of a European person or organisation to keep its data under European legal control, in places it chooses, readable only by parties it allows. In practice you test it with three questions:

  1. Law: which countries' courts and agencies can order the vendor to hand data over? That depends on who owns and runs the company, not on where its servers are.
  2. Location: where is the data stored and processed, including backups, logs, search indexes and AI features? This is data residency (see the glossary below).
  3. Control: who holds the encryption keys, and could the vendor read or switch off your workspace if told to?

A tool that answers all three in Europe's favour is sovereign. Most answer one or two. For which team messaging platforms answer which, see our guide to which team messaging platforms give European companies data sovereignty.

How is data sovereignty different from data residency?

Data residency is a promise about where data is stored. Data sovereignty is about who has legal and technical power over it. An "EU-hosted" label is a residency claim. It tells you the servers' location. It doesn't tell you who owns the vendor, which subprocessors touch your messages, or which law the contract is under.

Neither is the same as GDPR compliance. GDPR applies to organisations established in the EU and to those offering services to people in the EU (Art. 3), wherever their servers are. Storing data in the EU does not make processing lawful, and storing it outside the EU is allowed if a valid transfer tool is in place (Chapter V).

Which laws decide who can reach a company's messages?

Four sets of rules decide who can demand a team's messages, and they don't always agree.

RuleWho can order dataFrom whomDoes storage location matter?Main safeguard
GDPR, Chapter V and Art. 48No one: it limits transfers out of the EUControllers and processors handling EU personal dataYes: transfers out of the EU/EEA need a legal basisAdequacy decisions, standard contractual clauses (SCCs), Art. 48 (a foreign court order is only recognised under an international agreement)
US CLOUD Act (2018)US law enforcement, with a warrant or other legal processProviders subject to US jurisdictionNo: "regardless of whether" data is inside or outside the US (18 U.S.C. § 2713)A provider's motion to quash in conflict-of-law cases (§ 2703(h)); executive agreements (§ 2523)
US FISA (Section 702 and Title I)US intelligence agencies, for foreign intelligenceUS electronic communication service providersNoFISA Court oversight. Section 702, central to Schrems II, expired on 12 June 2026, but court-approved certifications continue until they lapse (up to a year)
EU e-Evidence Regulation (EU) 2023/1543Judicial authorities in EU member states, in criminal casesProviders offering services in the EU, wherever basedNo: orders go to the provider's EU establishment or legal representativeNotification of the enforcing state; a court procedure for conflicts with third-country law (Art. 17)

The CLOUD Act and the e-Evidence Regulation are mirror images: each lets its own authorities reach data held abroad. An EU–US agreement could link the two. Talks were authorised in June 2019, but the European Commission describes them as on hold, and no agreement exists. Until there is one, a provider can face a US order that GDPR Art. 48 does not recognise. What the CLOUD Act means for your team chat and the plain definition in what is the CLOUD Act? covers the practical side.

What changed after Schrems II?

In Schrems II (Case C-311/18, 16 July 2020), the EU Court of Justice struck down the EU–US Privacy Shield, because US surveillance law gave Europeans too little protection and no effective redress. It kept standard contractual clauses as a transfer tool, but only if the exporter checks, case by case, that the destination's law lets the clauses work. That check is a transfer impact assessment.

On 10 July 2023 the Commission adopted a new adequacy decision, the EU–US Data Privacy Framework (Implementing Decision (EU) 2023/1795). It lets data flow to US companies that certify under it. The EU General Court dismissed a challenge to it on 3 September 2025 (Case T-553/23, Latombe). An appeal (Case C-703/25 P) is pending at the Court of Justice, with no judgment as of 6 November 2026. The framework is in force today.

For team chat this means two things. A US vendor's certification makes transfers to it lawful under GDPR while the framework stands. It does not shield data from US legal orders: certification and the CLOUD Act are separate questions.

What does GDPR require from a team chat vendor?

When your company uses a chat tool for work, your company is usually the controller and the vendor is a processor. GDPR Article 28 then requires a written contract, a data processing agreement, that says among other things:

  • the vendor processes data only on your documented instructions, including on transfers outside the EU;
  • its staff are bound by confidentiality, and it applies appropriate security measures (Art. 32);
  • it uses other processors (subprocessors) only with your authorisation, and tells you about changes so you can object;
  • it helps you answer people's data requests and report breaches;
  • it deletes or returns the data when the contract ends, and lets you audit it.

If the vendor or any subprocessor processes data outside the EU/EEA, Chapter V applies: an adequacy decision, SCCs (Implementing Decision (EU) 2021/914) or another valid tool, plus a transfer impact assessment where SCCs are used.

Do NIS2 and Chat Control affect business messaging?

NIS2 (Directive (EU) 2022/2555) is in force and member states had to transpose it by 17 October 2024. It covers medium and large organisations in listed sectors, plus some others. Article 21 requires them to manage cybersecurity risks, including supply-chain security: the security of their direct suppliers and service providers. If your company is in scope, your chat tool is a supplier you have to assess. NIS2 does not set rules for where data is stored.

Chat Control is the common name for the Commission's proposed permanent regulation on preventing and combating child sexual abuse (COM(2022) 209; procedure 2022/0155(COD)). It is a proposal, not law. As of 6 November 2026, co-legislators have published no adoption decision. National officials examined draft texts on 3 November with no public outcome. A next political trilogue is reported for 8 December 2026; the Council's own note only schedules it "tentatively" for December — treat that day as unconfirmed. A 4 November LIBE vote concerned a separate CSA directive, not this regulation. No obligation under the permanent proposal applies to business messaging tools today. For the business-user angle, see what Chat Control means for business messaging.

What can encryption protect, and what can't it?

There are three common layers:

  • In transit: data is encrypted between your device and the server. The server can read it.
  • At rest: data is encrypted on the server's disks. The provider holds the keys, so it can still read it, and can be ordered to hand it over.
  • End-to-end (E2EE): only the participants' devices hold the keys. The provider stores data it cannot read.

Encryption matters for sovereignty because the CLOUD Act reaches data in a provider's "possession, custody, or control". A provider can only disclose content it can read. With E2EE, or with keys the customer holds, an order can still produce metadata, but not readable messages.

Encryption does not hide everything. Metadata (who talked to whom, when, from which device and IP address, group membership) is usually visible to the provider. It is also personal data. Sovereignty and encryption are separate: an encrypted service run by a company under foreign law still answers to that law for whatever it can access.

How do you check a team chat vendor?

Ask five questions and get the answers in writing:

  1. Owner and law: who owns the company, where is it established, and which law governs the contract?
  2. Regions per data type: where are messages, files, backups, logs, search indexes and AI processing located?
  3. Subprocessors: is there a published list, with locations, and how much notice do you get of changes?
  4. Transfers: which transfer tool covers each processing outside the EU/EEA (adequacy, the Data Privacy Framework, SCCs)?
  5. Keys and exit: who holds the encryption keys, and can you export and delete everything when you leave?

For a side-by-side of named vendors, see the table in our guide to sovereign team messaging.

Glossary: 15 EU data sovereignty terms

  • CLOUD Act: a 2018 US law that lets US authorities, with legal process, require providers under US jurisdiction to disclose data they control, wherever it is stored (18 U.S.C. § 2713).
  • Chat Control: the common name for the EU's proposed regulation on child sexual abuse online, COM(2022) 209; still under negotiation, not law.
  • Customer-managed keys (BYOK/HYOK): encryption where the customer, not the vendor, controls the keys. With "hold your own key", the vendor never has them.
  • Data residency: where data is stored and processed. A location promise, not a statement about which law applies.
  • Data processing agreement (GDPR Art. 28): the contract a controller must have with each processor, setting out instructions, security, subprocessors, audits and deletion.
  • e-Evidence Regulation: Regulation (EU) 2023/1543, applying since 18 August 2026. It lets EU judicial authorities order providers that offer services in the EU to produce or preserve electronic evidence.
  • End-to-end encryption (E2EE): encryption where only the communicating devices hold the keys, so the provider cannot read the content.
  • EU–US Data Privacy Framework (DPF): the 2023 adequacy decision that allows transfers to certified US companies. In force; an appeal against it is pending at the Court of Justice.
  • FISA Section 702: the US law that authorised programmatic foreign-intelligence collection from US providers. It expired on 12 June 2026; existing court certifications run until they lapse.
  • Metadata: data about communications rather than their content: who, when, where, how often.
  • NIS2: Directive (EU) 2022/2555 on cybersecurity for essential and important entities, including supply-chain security.
  • Schrems II: the 2020 Court of Justice judgment (C-311/18) that struck down Privacy Shield and required case-by-case checks for SCCs.
  • Standard contractual clauses (SCCs): model contract terms adopted by the Commission (2021/914) for transfers outside the EU/EEA.
  • Subprocessor: a processor engaged by your vendor to process your data, such as a hosting or AI provider. Needs your authorisation under Art. 28.
  • Transfer impact assessment (TIA): the exporter's documented check that the destination country's law lets the chosen transfer tool work, as set out in EDPB Recommendations 01/2020.

FAQ

FAQ

No. EU hosting answers where data is stored. Sovereignty also asks which law reaches the vendor and who holds the keys.

It can. It applies to providers under US jurisdiction for data in their possession, custody or control, regardless of where it is stored. A provider can challenge an order that conflicts with foreign law.

Yes, as of 6 November 2026. The General Court upheld it in September 2025; an appeal is pending at the Court of Justice.

NIS2 applies to organisations in scope, not to tools. If your company is in scope, it must assess the security of suppliers, including its chat provider.

Usually not. It protects message content; who talked to whom and when is typically still visible to the provider.

The CLOUD Act lets US authorities reach data held abroad by US-reachable providers. The e-Evidence Regulation lets EU authorities do the same with providers offering services in the EU.

Where does Buzz Messaging fit?

Buzz Messaging, which publishes this guide, is a messaging app built in Europe for small teams and communities. It is hosted on Google Cloud, with the primary region in Germany and a second region in the UK, and it is subject to GDPR and UK GDPR. Google Cloud is a US company, and the UK is outside the EU. That hosting is phase 1 of our infrastructure plan, our bootstrap stage: in phase 2 we'll move to an EU-based cloud partner, and in phase 3 we'll run our own infrastructure. To see how it compares with a US tool, read how Buzz Messaging compares with Slack or how startups use Buzz Messaging. Company details are on our About page.

Try Buzz Messaging

Buzz Messaging is on the App Store for iPhone. Teams is free for up to 5 seats; from the 6th seat, every seat is €4 per seat per month.