Data residency
This topic provides information about data residency and Assured Workloads. Data residency describes where your data is stored at rest. To help comply with data residency requirements, Google Cloud gives you the ability to control where that data is stored.
Assured Workloads and data residency
Organizations with data residency requirements can set up a Resource Locations policy that constrains the location of new in-scope resources for their whole organization or for individual projects.
During Assured Workloads setup, you create an environment and select your compliance regime. Later, when you create resources in the environment, Assured Workloads restricts the regions you can select for those resources based on the compliance regime you chose earlier.
To learn how to set up a new Assured Workloads environment, see Getting started with Assured Workloads.
Note on service data
As noted in Service Specific Terms, our Data Residency commitments apply to Customer Data at rest for services that can be configured for data location. As noted there, "Customer Data does not include resource identifiers, attributes, or other data labels."
"Service Data," also called metadata, refers to the personal data Google collects or generates during the administration of the Cloud Services. Service Data, such as billing data, is stored as noted in our Geography and regions documentation.
What's next
- For more information about Google Cloud's data location commitments, see the Google Cloud Service Specific Terms.
- To learn more about data residency in Google Cloud, see the following Identity & Security blog post: Understanding your options for data residency, operational transparency, and privacy controls on Google Cloud.
- To learn more about how Google Cloud protects customer data throughout its lifecycle,and how Google Cloud provides customers with transparency and control over their data, see the following whitepaper: Trusting your data with Google Cloud.