Data residency
Residency requirements may come from regulation, contracts, procurement rules, or internal risk policies. They influence cloud regions, backups, disaster recovery, support access, and subprocessors. Data residency is not the same as data sovereignty or complete data control, so teams should document both the physical locations and the legal and operational access model.
What is Data residency?
Data residency describes the geographic location where data is stored and, in some policies, where it is processed.
Why it matters
Residency requirements may come from regulation, contracts, procurement rules, or internal risk policies. They influence cloud regions, backups, disaster recovery, support access, and subprocessors. Data residency is not the same as data sovereignty or complete data control, so teams should document both the physical locations and the legal and operational access model.
Example
A European customer chooses an EU hosting region and requires backups and disaster-recovery copies to remain within approved European locations.