Data residency

This page 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 Assured Workloads folder and select a control package. Later, when you create resources in the folder, Assured Workloads restricts the regions you can select for those resources based on the control package you selected earlier.

To learn how to set up a new Assured Workloads folder, see create an Assured Workloads folder.

Note on Customer Data and 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."

In addition, Google will process Customer Data in use by the configured Service (not including in any user interface) only within the country of the selected Region or within the country or countries of the selected Multi-Region (as applicable). If the selected Region or Multi-Region is located in the European Union, Google will process Customer Data in use by the configured Service only within the European Union (but not necessarily in the same country).

"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