Data residency law is more than a flag.

Physical location, corporate jurisdiction, international transfer rules, government powers, encryption, and operational access are related controls. None substitutes for the others.

Scope: this is product context, not legal advice or a compliance determination. Sources were reviewed on 2 September 2026. A qualified adviser should test the facts of a particular controller, processor, dataset, contract, and request.

The GDPR regulates transfers. It is not a universal EU-storage mandate.

Inside the EEA

EU plus Iceland, Liechtenstein, and Norway

The GDPR is incorporated into the EEA framework. Iceland is therefore inside the EEA data-protection area even though it is not an EU Member State. The controller's wider GDPR duties still apply.

EFTA and Icelandic sources ↓

Outside the EEA

Chapter V needs a lawful path

GDPR Articles 44–49 govern transfers to third countries and international organizations. Depending on the destination and parties, the path may be an adequacy decision, appropriate safeguards, or a narrow derogation.

GDPR source ↓

Transfer assessment

A contract may not be enough

EDPB guidance calls for assessing whether destination-country law and practice undermine the chosen transfer tool and, where needed, adopting effective supplementary measures.

EDPB source ↓

What this means for a receipt

A residency receipt can document where Privatefile put durable copies and whether fallback occurred. It cannot determine controller roles, lawful basis, purpose limitation, minimization, retention, data-subject rights, or the validity of a transfer mechanism.

Storage location and international transfer are not the same test.

Remote access

Bytes can stay put while a transfer occurs

The European Data Protection Supervisor states that remote access from a third country to personal data qualifies as a transfer; the data does not have to be stored in that third country. An EU storage boundary therefore does not settle support, administration, or other access paths.

EDPS source ↓

Non-personal data

The EU generally favors free movement

EU rules generally allow non-personal data to be stored or processed anywhere in the Union, with limited public-security exceptions to localization restrictions. A legitimate authority request can still require access across an internal EU border.

European Commission source ↓

EU Data Act

Unlawful third-country access has safeguards

Chapter VII adds conditions and safeguards for third-country government access to non-personal data held in the EU by data-processing services. It does not ban every lawful request or turn EU residence into immunity.

European Commission source ↓

Customer requirement

A contract can be narrower than the statute

A customer, sector rule, grant, or procurement term may still require an exact country or region even where a general data-protection law does not. The operative text—not a generic “GDPR hosting” label—sets the requirement.

Iceland, Switzerland, the EU, and the US are not interchangeable.

Selected legal facts relevant to Privatefile's declared catalog; not a risk ranking.
PlaceData-protection positionAccess and alliance context
Iceland EEA state; GDPR entered into force in the EEA and is implemented alongside Iceland's Act No. 90/2018. Absent from the cited Five/Nine/Fourteen Eyes lists. Icelandic law nevertheless provides investigative powers, including court-authorized telecommunications measures under stated conditions.
Switzerland Outside the EU and EEA; governed by its Federal Act on Data Protection. The European Commission recognizes Switzerland as adequate for EU transfer purposes. Absent from the cited Eyes lists. Swiss criminal procedure still permits specified surveillance subject to legal conditions and oversight. The FDPIC cloud guidance keeps foreign-authority access and subprocessors in the risk analysis.
European Union GDPR applies across Member States. A strict EU zone avoids placing the durable copies themselves in a third country, but remote access or other processing can still create a transfer and does not settle compliance. The EU is not one intelligence-alliance member. A European Parliament resolution listed France in Nine/Fourteen Eyes and Germany in Fourteen Eyes; EU treaty text leaves national security to each Member State.
United States No general EU adequacy finding for the country. The EU–US Data Privacy Framework decision applies to US organizations that participate and are certified under it. Five Eyes member. US provider obligations can include the Stored Communications Act as amended by the CLOUD Act. Title VII, including Section 702, was repealed effective 12 June 2026, subject to transition rules for existing authorities.

Privatefile-specific boundary: for every placement, public ingress, authorization, metadata, receipts, and encrypted transient spool operate in Nuremberg, Germany. The selected placement governs durable primary and qualified replica objects.

The CLOUD Act and Section 702 are different—and current status matters.

18 U.S.C. § 2713

CLOUD Act location rule

A covered provider must preserve, back up, or disclose responsive data within its possession, custody, or control regardless of whether the data is inside or outside the United States. The Department of Justice notes that the provider must first be subject to US jurisdiction; corporate control and the validity or challenge of a demand are fact-specific.

Statute · DOJ explanation ↓

FISA Title VII status

Section 702 lapsed; transition rules remain

The official US Code shows Title VII, including Section 702, repealed effective 12 June 2026. Section 404 transition rules allow specified existing orders, authorizations, and directives to continue until they expire and keep Title VII applicable to them for defined purposes. It is not a claim that every US-hosted file is accessed—or that the former authority can be described as generally current.

Repeal status · Transition rules ↓

Key distinction: putting bytes outside the United States may change the facts, but it does not by itself remove every US nexus. Conversely, a US nexus does not establish that a particular authority applies or that a particular demand is lawful.

“Eyes” labels are context, not a privacy score.

Five Eyes

Australia, Canada, New Zealand, the UK, and the US

The UK Intelligence and Security Committee describes Five Eyes as a long-standing intelligence partnership among these five countries.

UK ISC source ↓

Nine Eyes

Five Eyes plus Denmark, France, the Netherlands, and Norway

This public shorthand appears in a 2014 European Parliament resolution discussing surveillance arrangements.

European Parliament source ↓

Fourteen Eyes

Nine Eyes plus Belgium, Germany, Italy, Spain, and Sweden

The same European Parliament resolution associated this list with the SIGINT Seniors Europe arrangement.

European Parliament source ↓

  • Membership does not prove that a named provider, account, or file is accessible to every member.
  • Absence from a list does not prove that a state has no intelligence-sharing, mutual-assistance, law-enforcement, or diplomatic relationships.
  • The Nine and Fourteen Eyes labels are public shorthand, not a complete, transparent statement of every current capability or arrangement.
  • Legal authority, technical access, provider control, encryption keys, oversight, remedies, and the facts of a request matter more than a flag-based ranking.

What can be said—and what cannot.

Supportable

  • A location constraint can support a contract, policy, transfer analysis, or voluntary jurisdiction choice.
  • A country placement can constrain durable copies while the control plane operates elsewhere, if both are disclosed.
  • Provider identity, corporate control, subprocessors, and lawful access need separate analysis.
  • Signed operational evidence is useful, but narrower than a legal certification.

Not supportable

  • “Stored in Europe” means GDPR compliant.
  • A non-Five-Eyes location is government-proof or free of intelligence cooperation.
  • A European data centre prevents the CLOUD Act from ever being relevant.
  • Residency creates anonymity, legal immunity, absolute sovereignty, or guaranteed deletion from every backup and log.

Read the governing text, not the slogan.

Official sources reviewed 2 September 2026. Privatefile separately reviews storage-target evidence against its narrower placement contract before any destination can accept real writes.

  1. General Data Protection Regulation, especially Articles 44–49 — EUR-LexRules for transfers to third countries and international organizations.
  2. Rules for transfers outside the EU — European CommissionOfficial overview of adequacy, safeguards, and derogations.
  3. Recommendations 01/2020 on supplementary measures — EDPBTransfer-tool assessment and supplementary-measure guidance.
  4. International transfers — European Data Protection SupervisorRemote third-country access can be a transfer even without storing data in that country.
  5. Free flow of non-personal data — Your EuropeEU location choice, exceptional localization restrictions, and legitimate authority access.
  6. Data Act explained, Chapter VII — European CommissionSafeguards concerning unlawful third-country government access to non-personal data held in the EU.
  7. GDPR entered into force in the EEA — EFTAEEA application, including Iceland.
  8. Iceland Act No. 90/2018 — Data Protection AuthorityEnglish translation of Iceland's data-protection act.
  9. Iceland Code of Criminal Procedure No. 88/2008, Articles 80–84 — Government of IcelandConditions and court-order requirements for specified telecommunications measures.
  10. Data processing in the cloud — Swiss FDPICController responsibility, provider selection, subprocessors, and foreign-authority risk.
  11. Cross-border transfer of personal data — Swiss FDPICSwiss transfer requirements and adequacy context.
  12. Adequacy decisions — European CommissionCurrent official list, including Switzerland, and scope of EU–US Data Privacy Framework coverage.
  13. Swiss Criminal Procedure Code, Articles 269–279 — FedlexConditions, protected interests, authorization, and notice for telecommunications surveillance.
  14. 18 U.S.C. § 2713 — US House Office of the Law Revision CounselPossession, custody, or control rule regardless of data location.
  15. Promoting Public Safety, Privacy, and the Rule of Law Around the World: The Purpose and Impact of the CLOUD Act — US Department of JusticeOfficial explanation of provider jurisdiction, control, comity, and executive agreements.
  16. 50 U.S.C. § 1881a, preliminary edition — US House Office of the Law Revision CounselCurrent codification records repeal of Title VII effective 12 June 2026.
  17. FISA Amendments Act of 2008, as amended through Public Law 119-87 — GovInfoOfficial compilation of the repeal date and Section 404 transition procedures.
  18. International partnerships — UK Intelligence and Security CommitteeOfficial UK parliamentary description of the Five Eyes members and partnership.
  19. European Parliament resolution of 12 March 2014 on surveillance programmesPublicly cited Nine Eyes and Fourteen Eyes country lists and SIGINT Seniors Europe context.
  20. Treaty on European Union, Article 4(2) — EUR-LexNational security remains the sole responsibility of each Member State.
  21. Commission Implementing Decision (EU) 2023/1795 — EUR-LexEU–US Data Privacy Framework adequacy decision and its scope.