Data Residency

Requirements or policies specifying the geographic location where data must be stored, processed, or maintained.

On this page

What is Data Residency?

Data residency (or data localization) requirements can arise from regulations, contractual obligations, or organizational policies. Some countries mandate that certain data types (financial, health, government) remain within national borders. Cloud providers offer region-specific data centers to support compliance. Data residency differs from data sovereignty (which adds legal jurisdiction requirements) and data localization (which may be more restrictive). Key considerations include primary storage, backups, disaster recovery sites, and processing locations.

Application to Vendor Screening

Verify where vendors store and process your data, including backups and disaster recovery sites. Ensure vendor data center locations comply with your regulatory requirements and contractual obligations. Cloud vendors should provide contractual commitments on data residency with penalties for non-compliance.

Practical Examples

  • Requiring a vendor to store EU customer data exclusively in EU data centers
  • Verifying that vendor backup and DR sites comply with data residency requirements
  • Mapping vendor sub-processor locations to ensure data residency compliance

Frequently Asked Questions

What is the difference between data residency and data sovereignty?

Data residency refers to where data is physically stored. Data sovereignty adds the dimension of legal jurisdiction, the data is subject to the laws of the country where it resides. Sovereignty requirements are generally more restrictive than residency requirements.

Do cloud vendors guarantee data residency?

Major cloud providers offer region-specific data storage, but guarantees vary. Review the vendor's terms of service, data processing agreements, and sub-processor lists to confirm data residency commitments and any exceptions.

Check the vendor. Keep the evidence.

Start free