This document explains when data residency is enforced in each location where Model Armor is available. Data residency lets you specify a geographic region where your data is stored and processed, which helps ensure that your data remains in that location. Model Armor helps provide control over where your data is handled, supporting compliance with various regulations.
Model Armor processes the following types of data:
Core data: The primary data that Model Armor processes, most relevant to data residency, which includes prompts, responses, and input files. Model Armor processes core data but doesn't store it at rest. For more information, see Data handling and storage.
Configuration data: Template and floor setting configurations such as rules, filters, and thresholds that Model Armor uses to scan prompts and responses. Model Armor processes and stores configuration data at rest.
Data residency enforcement for templates
This section indicates the data residency controls enforced by
Model Armor templates for each supported Google Cloud location.
Model Armor maintains data residency at the
jurisdiction level, for example, a specific country like India, or a
multi-region like eu.
The information in this table also applies to all Model Armor integrations—except for the integration with Google and Google Cloud MCP servers, which doesn't support Model Armor templates.
Model Armor works in the following regions. However, Model Armor has limited feature support in some regions to maintain data residency. For information about the regions with full and limited support, see Feature availability by region.
| Region/multi-region | Jurisdiction | At rest | In use | In transit | Feature support1 |
|---|---|---|---|---|---|
asia-northeast1 |
Japan | Yes | Yes | Yes | Limited support |
asia-northeast3 |
South Korea | Yes | No | No | Full support |
asia-south1 |
India | Yes | Yes | Yes | Limited support |
asia-southeast1 |
Singapore | Yes | Yes | Yes | Limited support |
australia-southeast2 |
Australia | Yes | No | No | Full support |
eu |
European Union | Yes | Yes | Yes | Full support |
europe-southwest1 |
European Union | Yes | Yes | Yes | Full support |
europe-west1 |
European Union | Yes | Yes | Yes | Full support |
europe-west2 |
United Kingdom | Yes | Yes | Yes | Limited support |
europe-west3 |
European Union | Yes | Yes | Yes | Full support |
europe-west4 |
European Union | Yes | Yes | Yes | Full support |
europe-west9 |
European Union | Yes | Yes | Yes | Full support |
northamerica-northeast2 |
Canada | Yes | Yes | Yes | Limited support |
us |
United States | Yes | Yes | Yes | Full support |
us-central1 |
United States | Yes | Yes | Yes | Full support |
us-east1 |
United States | Yes | Yes | Yes | Full support |
us-east4 |
United States | Yes | Yes | Yes | Full support |
us-west1 |
United States | Yes | Yes | Yes | Full support |
1The Feature support column is relevant only to Model Armor configurations that use templates. For Model Armor configurations that use floor settings, all features are available but data residency enforcement for data in use and in transit varies by location.
The Jurisdiction column indicates the geographical boundary (for example, a
country or a multi-region like eu or us) within which
Model Armor ensures data residency compliance for the supported
states (at rest, in use, and in transit) as indicated in the table.
The Region/multi-region column lists the specific Google Cloud region or multi-region identifier.
When data residency is enforced for a region in Model Armor, it helps ensure that data remains within a specified jurisdiction while in at least one of the following states:
At rest: Stored data remains within the specific Google Cloud region listed.
In use and In transit: Data residency enforcement for these states within the specified jurisdiction depends on the values in the In use and In transit columns:
- Yes: Data residency is enforced for the In use and In transit states within the listed jurisdiction. This means that the data remains within the boundaries of the listed jurisdiction while being processed or transmitted (not necessarily within that single region).
- No: Data residency is not enforced for the In use and In transit states within the listed jurisdiction. This means that the data might be processed or transmitted outside of the jurisdiction.
Data residency for Model Armor integrations using floor settings
The following sections explain how data residency is enforced for Model Armor floor settings across integrations.
Integration with Gemini Enterprise Agent Platform
If you use floor settings for the Agent Platform integration, all Model Armor features are available in the following locations. However, data residency enforcement for data in use and in transit varies by region.
Integration with Google and Google Cloud MCP servers
Model Armor is a regionalized service, but it's not available in every Google Cloud region where Google and Google Cloud MCP servers operate. If you enable Model Armor for an MCP-supported service in a jurisdiction where Model Armor isn't present, Model Armor is called depending on whether the MCP-supported service uses cross-jurisdictional routing or data residency compliant routing.
Google and Google Cloud MCP servers with cross-jurisdictional routing
For Google and Google Cloud MCP servers with cross-jurisdictional routing, Model Armor is always called if enabled. Cross-jurisdictional calls might impact data residency compliance for in-use and in-transit data.
To see which Google and Google Cloud MCP servers use cross-jurisdictional routing, see Products with Model Armor support.
Google and Google Cloud MCP servers with data residency compliant routing
For Google and Google Cloud MCP servers with data residency compliant routing, Model Armor can be called in any region or multi-region within the European Union and the United States jurisdictions. Data residency is enforced for data at rest, in use, and in transit.
To see which Google and Google Cloud MCP servers use data residency compliant routing, see Products with Model Armor support.
Regional endpoints
Regional endpoints provide access to resources in a specific location. When you use a regional endpoint, your request is routed directly to the endpoint's location.
Each regional endpoint uses the following format:
modelarmor.LOCATION.rep.googleapis.com
Replace LOCATION with a supported location. For
supported locations, see Locations.
To access Model Armor regional endpoints from within a VPC network, you must create a Private Service Connect endpoint to the Model Armor APIs. This is required to prevent certificate errors when regional endpoints are accessed using Private Google Access or VPC Service Controls. For more information, see Troubleshoot Model Armor issues and About accessing regional endpoints through Private Service Connect endpoints.