Stay organized with collections
Save and categorize content based on your preferences.
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
organization policy constraint that restricts the location of new
in-scope resources at the organization, project, or
folder level of their resource hierarchy.
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. See
Resource locations supported services
for a list of resources that can be restricted by the Resource Locations
constraint, as some resources may be out of scope and unrestrictable.
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
For more information about Google Cloud's data location commitments, see
the Google Cloud Service Specific Terms.
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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-25 UTC."],[[["\u003cp\u003eData residency refers to where your data is stored at rest, and Google Cloud allows you to control this location to meet data residency requirements.\u003c/p\u003e\n"],["\u003cp\u003eAssured Workloads enables organizations to enforce data residency policies by setting up Resource Locations that restrict where new resources can be created.\u003c/p\u003e\n"],["\u003cp\u003eDuring Assured Workloads setup, selecting a control package determines the regions where resources can be created in the designated folder.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Cloud's data residency commitments apply to Customer Data at rest for services that allow data location configuration, excluding resource identifiers and other data labels.\u003c/p\u003e\n"],["\u003cp\u003eService Data, also known as metadata, is handled separately and its storage locations are detailed in Google Cloud's Geography and regions documentation.\u003c/p\u003e\n"]]],[],null,["# Data residency\n==============\n\nThis page provides information about data residency and\nAssured Workloads. *Data residency* describes where your data is stored\nat rest. To help comply with data residency requirements, Google Cloud\ngives you the ability to control where that data is stored.\n\nAssured Workloads and data residency\n------------------------------------\n\nOrganizations with data residency requirements can set up a\n[Resource Locations](/resource-manager/docs/organization-policy/defining-locations)\norganization policy constraint that restricts the location of new\n[in-scope resources](/terms/data-residency) at the organization, project, or\nfolder level of their resource hierarchy.\n\nDuring Assured Workloads setup, you create an\nAssured Workloads folder and select a control package. Later, when you\ncreate resources in the folder, Assured Workloads restricts the regions\nyou can select for those resources based on the control package you selected\nearlier. See\n[Resource locations supported services](/resource-manager/docs/organization-policy/defining-locations-supported-services)\nfor a list of resources that can be restricted by the Resource Locations\nconstraint, as some resources may be out of scope and unrestrictable.\n\nTo learn how to set up a new Assured Workloads folder, see\n[create an Assured Workloads folder](/assured-workloads/docs/create-folder).\n\n### Note on Customer Data and Service Data\n\nAs noted in [Service Specific Terms](/terms/service-terms), our data residency\ncommitments apply to Customer Data at rest for [services](/terms/data-residency)\nthat can be configured for data location. As noted there, \"Customer Data does\nnot include resource identifiers, attributes, or other data labels.\"\n\nIn addition, Google will process Customer Data in use by the configured Service\n(not including in any user interface) only within the country of the selected\nRegion or within the country or countries of the selected Multi-Region (as\napplicable). If the selected Region or Multi-Region is located in the European\nUnion, Google will process Customer Data in use by the configured Service only\nwithin the European Union (but not necessarily in the same country).\n\n\"Service Data,\" also called metadata, refers to the personal data Google\ncollects or generates during the administration of the Cloud Services. Service\nData, such as billing data, is stored as noted in our\n[Geography and regions](/docs/geography-and-regions#internal_services)\ndocumentation.\n\nWhat's next\n-----------\n\n- For more information about Google Cloud's data location commitments, see the Google Cloud [Service Specific Terms](/terms/service-terms).\n- To learn more about data residency in Google Cloud, see the following Identity and Security blog post: [Understanding your options for data residency, operational transparency, and privacy controls on\n Google Cloud](/blog/products/identity-security/meet-data-residency-requirements-with-google-cloud).\n- 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](https://services.google.com/fh/files/misc/072022_google_cloud_trust_whitepaper.pdf)."]]