Data & GDPR Verified

Data Residency (EU vs US)

aka data localisation, EU data centres, data sovereignty

Where customer personal data is stored and processed. Storing inside the EU/EEA simplifies GDPR compliance; processing in the US triggers transfer-mechanism obligations under Schrems II.

Last reviewed April 2026

Definition

Data residency is the answer to 'in which legal jurisdiction does this software actually store and process my customer data?' Under the GDPR, transferring personal data outside the European Economic Area (EEA) requires a valid transfer mechanism, typically the EU-US Data Privacy Framework (DPF) for US-based recipients certified under it, Standard Contractual Clauses (SCCs), or Binding Corporate Rules. The Schrems II ruling (Case C-311/18, 2020) made all transfers to the US conditional on supplementary measures and a Data Transfer Impact Assessment (DTIA) demonstrating an essentially equivalent level of protection. The EU-US Data Privacy Framework adopted in July 2023 partially restored simpler transfers to certified US recipients, but it remains under legal challenge and could be invalidated. Many SaaS providers offer a regional EU instance (Frankfurt, Dublin, Amsterdam) that keeps data inside the EU; others process exclusively in the US or offer 'data at rest in EU, processing globally', which is a different legal posture. Some processors (notably HR and payroll, which handle special-category data) effectively require an EU-only stance for Irish controllers.

Why it matters for software choice

EU-only data residency reduces GDPR transfer obligations to near zero. US or 'global' processing requires SCCs, a DTIA, vendor cooperation, and willingness to defend the choice if Schrems III invalidates the DPF. Ask vendors to confirm in writing exactly where data is stored, replicated, and accessed from.

Authority sources

Software categories this affects

Vendors covered by this term

Related terms