Data Retention and Residency
What zero data retention (ZDR) and data residency actually guarantee on Anthropic, OpenAI, Google (Gemini API and Vertex AI), Azure and Bedrock: which stores survive ZDR, which features break it, how regional processing differs from regional storage, and where DPAs and BAAs fit.
Contents
Zero data retention (ZDR) is a vendor commitment that your prompts and outputs are not written to storage after the response is returned. Usually it is a contract amendment or an approved account setting, not an API parameter. Data residency is a commitment about where your data is, and it covers two different things: where data is stored at rest and where inference runs (the GPUs that process your prompt). Each one bounds only a few of the places where a request’s data can persist. A request touches abuse-monitoring logs, application state (stored responses, files, threads), caches, tool sandboxes, third-party websites, trust-and-safety holds and your own observability stack. ZDR removes some of these, residency pins some of them to a region, and neither covers them all. This page explains, per vendor (as of 2026-11), what each control actually covers, what it leaves out, and how to build a deployment that a privacy reviewer can verify. For the wider enterprise rollout see Enterprise LLM deployment; for redaction and GDPR mechanics see PII and data privacy.
Three separate questions
Customers often treat “Is it ZDR?”, “Is it EU-hosted?” and “Do we have a BAA?” as one question. They are three:
| Question | Control | What it bounds |
|---|---|---|
| How long does the vendor keep my data? | Default retention, ZDR / modified abuse monitoring, retention modes | Abuse logs, application state, caches |
| Where is my data stored, and where is it processed? | Regional endpoints, deployment types, inference profiles, inference_geo | Storage location, inference location (separately) |
| What legal terms govern the processing? | DPA (processor terms), BAA (HIPAA), ZDR addendum | Liability, permitted use, sub-processing, PHI handling |
Synthesis: a design can satisfy one of these and fail another. An Azure Global deployment keeps data at rest in your geography but may run inference anywhere (Azure). An Anthropic ZDR organization still keeps Batch inputs for 29 days if it calls the Batch API (Anthropic). A BAA on Anthropic’s API comes with HIPAA safeguards rather than deletion, so it does not imply ZDR (Anthropic).
Where request data can persist
Synthesis: the stores below are drawn from the vendor pages cited in each row. The diagram shows which control applies to each one.
flowchart LR APP["Your app"] --> GW["Your gateway / traces<br/>(your retention)"] GW --> API["Vendor API endpoint<br/>(region = inference location)"] API --> INF["Inference<br/>(stateless model)"] API --> ABUSE["Abuse-monitoring logs<br/>(removed by ZDR / MAM / mode none)"] API --> STATE["Application state<br/>(stored responses, files, threads, batches)<br/>NOT removed by ZDR"] API --> CACHE["Caches<br/>(prompt cache, schema grammars)<br/>usually allowed under ZDR"] API --> TOOLS["Server-side tools<br/>(code sandboxes, grounding logs, fetched sites)"] ABUSE --> HOLD["Trust-and-safety holds<br/>(flagged content, survives ZDR)"]
| Store | Typical default | Under ZDR |
|---|---|---|
| Abuse-monitoring logs | OpenAI up to 30 days (OpenAI); Gemini API 55 days (Gemini); Anthropic has no separate figure, and its API data is deleted within 30 days by default (Anthropic) | Removed (OpenAI ZDR/MAM, Anthropic ZDR, Azure modified abuse monitoring, Bedrock mode none) |
| Application state | Kept until deleted or for a feature-specific window | Not removed: you must avoid the feature, or OpenAI forces store=false |
| Prompt / KV caches | Hours (OpenAI up to 24 h; Vertex and Gemini implicit cache 24 h) | Generally treated as compatible with ZDR (details below) |
| Grounding / search logs | Vertex Search grounding 3 days; Gemini API and Maps grounding 30 days | Cannot be disabled; avoid the feature |
| Trust-and-safety holds | Flagged content kept for review | Survive ZDR: Anthropic up to 2 years; OpenAI keeps flagged content even under ZDR/MAM |
| Your own logs and traces | Whatever you configure | Out of the vendor’s scope entirely |
Per-vendor mechanics
Anthropic (Claude API)
- Default: API inputs and outputs are deleted on the backend within 30 days, with exceptions for longer-lived features, agreements, usage-policy enforcement and legal requirements (source).
- ZDR: prompts and responses are not stored at rest once the response is returned. The account team enables it per organization, and each new organization needs it enabled separately. It covers the Messages and Token Counting endpoints for eligible features, and Claude Code used with Commercial-org API keys. It does not cover the Console, Managed Agents (except self-hosted), consumer plans or the Teams/Enterprise chat products. ZDR organizations cannot call the API from a browser, because CORS requests are rejected (source).
- Ineligible features are not blocked. Batch (29-day retention), the Files API, code execution and programmatic tool calling (container data up to 30 days), Agent Skills, the MCP connector and message threads are marked ineligible. Calling one under ZDR takes that data outside ZDR rather than returning an error. Under HIPAA readiness, ineligible features return a 400 (source).
- “Qualified” features keep a small artifact. Structured outputs and strict tool use cache the compiled JSON schema for up to 24 hours after last use. Cache diagnostics keep a brief fingerprint of hashes and token counts. Prompt caching holds KV representations in memory for the cache TTL only. Web search and web fetch are eligible, but their dynamic filtering is not, and the websites you fetch can log the request under their own policies (source).
- Covered Models: Claude Fable 5, 5.1 and 5.2 and Mythos 5, 5.1 and 5.2 require 30-day retention and are unavailable under ZDR unless Anthropic authorizes it. A ZDR organization can turn on retention for one non-default workspace to reach them (source).
- Residency:
inference_geois"global"(default) or"us", set per request or as a workspace default and enforced byallowed_inference_geos. US-only inference costs 1.1x on Claude 4.6 and later, and earlier models return 400 if the parameter is sent. The response’susage.inference_georeports where inference actually ran. Workspace geo (storage at rest and endpoint-side processing such as code execution) is fixed at workspace creation and is only"us"today (source). - Processor: Anthropic is the data processor for its first-party API, Claude Platform on AWS, Anthropic-managed Claude on Google Cloud and Claude in Microsoft Foundry. The cloud provider is the processor for Bedrock and Google-managed Vertex, so those platforms’ controls apply instead (source).
OpenAI API
- Default: no training on API data since 2023-03-01 unless you opt in. Abuse-monitoring logs are kept up to 30 days. Responses whose
storeis omitted or true are kept at least 30 days (source). - Two tiers, both by approval: Modified Abuse Monitoring (MAM) removes customer content from abuse logs (with rare exceptions for image and file inputs) and keeps every feature. ZDR does the same and also forces
store=falseon/v1/responsesand/v1/chat/completions, even when the request setstrue. Both are set per organization, and each project can override the setting (source). - Eligible endpoints: chat completions, responses, decisions, image generation, embeddings, audio, moderations, completions and realtime. Not eligible: conversations, assistants, threads, vector stores (so hosted file search), agents, files, fine-tuning, evals, batches and audio voices (source).
- Edge cases: background mode writes response data to disk for about 10 minutes for polling. Prompt-cache tensors can stay in GPU-local storage up to 24 hours. Flagged content may be kept even under ZDR or MAM, and image and file inputs are scanned for CSAM (source).
- BAA: the same page ties PHI use to an executed Business Associate agreement. Live-internet web search is not covered by the BAA. Offline web search can be covered, but only in a ZDR-enabled project inside a ZDR-enabled organization (source).
- Residency: regional domains such as
eu.api.openai.com. US, Europe and UAE store and process in-region. Australia, Japan and India process in-region only for a narrow model and feature set. Canada, Singapore, South Korea and the UK are storage-only, so inference may run elsewhere. The region is fixed per project at creation. Models released on or after 2026-03-05 cost 10% more on residency endpoints.store=trueon chat completions is not allowed outside the US, and in storage-only regions extended prompt caching may process and store data out of region (source).
Google: Gemini Developer API versus Vertex AI
Google runs two surfaces with very different data terms. Choosing between them is the most important privacy decision on Google.
- Gemini Developer API (AI Studio keys). On Unpaid Services, inputs and outputs may be used to improve Google products and read by human reviewers. On Paid Services they are not, and processing falls under Google’s processor DPA. Apps offered to users in the EEA, Switzerland or the UK may use only Paid Services (terms). The abuse-monitoring policy keeps prompts, context and outputs for 55 days and lists no exemption (policy). Google’s ZDR page lists features to avoid instead of offering a switch: Search and Maps grounding (30 days, cannot be disabled), Interactions API
store(default on), Live API session resumption (24 h), Files and explicit caches. For guaranteed ZDR it points to Vertex AI (ZDR page). AI Studio project logs are a further store: on by default for Interactions API calls and for projects created on or after 2026-10-26, kept 7 to 55 days (logging). - Vertex AI (Gemini Enterprise Agent Platform). No training without permission. For ZDR you take specific actions. Abuse-monitoring prompt logging applies to customers on the Google Cloud Platform Terms of Service. Request-response logging to BigQuery is off by default and must stay off. Set Interactions
store=falseexplicitly, because it defaults totrue. Avoid Search grounding (logs kept 3 days, cannot be disabled) in favour of Web Grounding for Enterprise. Maps grounding keeps data 30 days. Implicit caches are deleted within 24 hours and can be disabled per project withdisableCache. Models under the Advanced AI Safety Addendum carry extra logging, and ZDR may not be possible for them. Partner OpenAI models are logged up to 30 days in theusmulti-region until a project is approved for ZDR, andstore: falsealone does not enable ZDR for them (source). - Residency on Vertex: regional endpoints, multi-region
us/euendpoints, orglobal. Google states that endpoints alone do not guarantee residency. Multi-region endpoints are the option for keeping ML processing in the US or EU.globaldoes not support residency for partner models (locations). VPC Service Controls add exfiltration protection, but inside a perimeter they disable request/response logging and URL-context fetching (VPC-SC). - Inconsistency to flag: Google’s Gemini API ZDR page describes paid abuse logging only as “a limited period”, while the usage-policy page says 55 days (ZDR page, policy). Synthesis: plan for 55 days.
Azure (Foundry Models sold by Azure, including Azure OpenAI)
- Isolation: prompts and outputs are not available to OpenAI or other model providers, and are not used to train foundation models without permission. The models run in Azure and do not call OpenAI’s services. Processing is governed by the Microsoft Products and Services DPA (source).
- No product called ZDR. The equivalent is modified abuse monitoring. Customers who meet extra Limited Access criteria apply by form, and some advanced models have stricter criteria. Once approved, storage of flagged traffic and human review stop, but automated (LLM) review continues. You can verify this on the resource: the
ContentLoggingcapability showsfalse, and the property is absent otherwise (data privacy, abuse monitoring). - Stateful features (Responses API storage, Assistants threads, stored completions, files, batch, fine-tuning) store data in your resource’s geography. It is AES-256 encrypted, optionally with customer-managed keys, and you can delete it (source). Synthesis: Azure keeps state in your tenant, under your encryption and deletion controls, rather than banning it under a retention mode.
- Residency by deployment type: Standard processes within your geography. DataZone processes anywhere in the zone (the US, or any EU member state). Global processes wherever the model is deployed. Data at rest, including the abuse-monitoring store, stays in your geography in all three cases. Batch is a Global deployment type. Human reviewers for EEA deployments are located in the EEA. Preview features may not honour these commitments (source).
Amazon Bedrock
- Isolation: each Region has an AWS-operated model deployment account per provider, and providers cannot see prompts, completions or logs (source).
- Retention is an ordered mode, set per Region at account or project level:
none(zero retention) <default(the model’s own policy) <aws_review(AWS may keep data and have humans review it inside AWS) < legacyprovider_data_share. The effective mode is the first non-inheritvalue among project, account and model default. Settings do not propagate across Regions (source). - The mode decides which models you can call. If a model’s minimum mode is above your effective mode, the model is unavailable or the call fails with
ValidationException. Claude Fable 5, 5.1 and 5.2 requireaws_review, which keeps data up to 30 days inside AWS. ZDR for them is limited to accounts eligible for the Enterprise Frontier Safeguards program, evaluated per account and model.store=falsealone does not mean zero retention; only modenonedoes. SCPs onDataRetentionModecan enforcenoneacross an organization (source). - Residency: cross-Region inference profiles let Bedrock pick the destination Region per request: geographic profiles (US, EU, APAC) stay inside the geography, while global profiles go to any commercial Region at roughly 10% lower price. CloudTrail’s
inferenceRegionfield records where each request ran. Data retained under a non-nonemode is stored in the destination Region (CRIS, retention).
Comparison (as of 2026-11)
| Anthropic API | OpenAI API | Gemini Developer API | Vertex AI | Azure Foundry | Bedrock | |
|---|---|---|---|---|---|---|
| ZDR mechanism | Org-level, via account team | ZDR or MAM, by approval, org + project | None; avoid features, paid tier only | Configuration plus account team for some models | Modified abuse monitoring (Limited Access form) | Retention mode none (self-serve, SCP-enforceable) |
| Stateful features under ZDR | Allowed but leave ZDR (400 under HIPAA) | store forced false; ineligible endpoints listed | Must be avoided | Must be off (store=false, no BigQuery logging) | Allowed, stored in your resource | store=true rejected under none |
| Frontier models gated by retention | Covered Models need 30 days | Not stated | Not stated | Advanced AI Safety Addendum models | “More stringent criteria” for some | Models needing aws_review |
| Inference residency | inference_geo: "us" (+10%) | Regional domains; some regions storage-only | None documented; paid-tier data may be stored transiently in any country with Google facilities | Regional / us/eu multi-region | Standard / DataZone | Region or geographic profile |
| HIPAA path | BAA + HIPAA readiness (irreversible) | BAA, eligible endpoints | Not covered by the Google Cloud HIPAA page | Google Cloud BAA | Not covered by the sources used here; check Microsoft’s HIPAA offering | AWS BAA; Bedrock eligible |
Sources: each vendor section above; HIPAA rows from AWS, Google Cloud, Anthropic, OpenAI.
Contracts: DPA, BAA and the ZDR addendum
- DPA (data processing addendum). It makes the vendor a processor acting on your instructions. Google’s Paid Services and Azure’s models sold by Azure are explicitly processed under processor DPAs. Google’s Unpaid Services are not, which is why the Gemini terms forbid them for EEA/UK/Swiss end users (Gemini terms, Azure). Synthesis: a DPA governs how data is handled, not how long it is kept. Retention is still whatever the product does.
- BAA (business associate agreement). Required before PHI. Anthropic’s HIPAA readiness needs a signed BAA, applies safeguards (encryption, access control, audit logging) rather than deletion, cannot be turned off once enabled, and forbids PHI in JSON schemas because compiled grammars are cached outside PHI protections (Anthropic). On AWS, Bedrock and Bedrock AgentCore are HIPAA-eligible under the AWS BAA with no feature exclusions (AWS). Google Cloud’s BAA covers Gemini Enterprise Agent Platform and Generative AI on Agent Platform but excludes pre-GA offerings, and the HIPAA page does not mention the Gemini Developer API (Google Cloud).
- ZDR addendum or approval. On Anthropic and OpenAI, ZDR is granted per organization by the vendor. On Bedrock it is a setting you control (except for gated models). On Azure it is an application. Synthesis: ask for written confirmation of the scope (which org IDs, projects and endpoints), because a new org or project created later may not inherit it.
Failure modes
- Silent exit from ZDR. Under Anthropic ZDR a Batch, Files or code-execution call works normally while its data follows standard retention. Synthesis: block those endpoints at your gateway rather than relying on the vendor to refuse them (Anthropic).
- "
store=falsemeans ZDR". It does not on Bedrock (only modenone) or on Vertex partner OpenAI models (Bedrock, Vertex). - Defaults that flip on. The Vertex and Gemini Interactions API
storedefaults to true. AI Studio logging is on by default for projects created on or after 2026-10-26 (Vertex, Gemini logging). - Grounding is a retention leak. Search and Maps grounding logs cannot be disabled on either Google surface (Gemini ZDR, Vertex). Third-party sites you fetch keep their own logs (Anthropic).
- Storage-only residency. OpenAI’s Canada, Singapore, South Korea and UK regions, and Azure Global and Batch, keep data at rest locally while inference may run abroad (OpenAI, Azure).
- Global routing for capacity. Bedrock global profiles and Vertex
globalare cheaper or more available but break residency (CRIS, locations). Synthesis: a fallback or gateway rule that retries in another region on a 429 can quietly do the same. - Frontier lockout. Strict ZDR can make the newest Claude tiers unavailable on both Anthropic and Bedrock (Anthropic, Bedrock). Synthesis: settle this during model selection, not after legal sign-off.
- Trust-and-safety holds outlive ZDR. Anthropic keeps flagged content up to 2 years, and OpenAI keeps flagged content even under ZDR (Anthropic, OpenAI).
- Your own stack. Vendor ZDR says nothing about your traces, observability exports, OpenTelemetry spans, vector stores or agent memory. Synthesis: these are often the largest copy of the prompts.
Practical guidance
Synthesis, drawn from the failure modes above:
- Write the data-flow inventory first. List every store in the table above for each feature you plan to use. Then pick controls. Note that batch, hosted file search, code execution, stateful Responses and grounding each need an explicit decision.
- Pick the surface by data class. Regulated or EU personal data: use Vertex rather than the Gemini Developer API, Bedrock or Azure in a pinned region, or Anthropic or OpenAI with ZDR plus regional processing. Paid tiers only, never free tiers.
- Enforce at the organization level, not in code. Use Bedrock SCPs on
DataRetentionMode, Anthropicallowed_inference_geos, OpenAI per-project retention settings, and VertexdisableCacheor VPC-SC. Block ineligible endpoints at the gateway. - Verify, don’t assume. Check Azure’s
ContentLogging=false, Anthropic’susage.inference_geo, Bedrock’s CloudTrailinferenceRegion, and the Vertex Model Garden “Zero Data Retention active” banner for partner models (Azure, Anthropic, CRIS, Vertex). Synthesis: put these checks in a deployment test. - Budget for residency. Expect about 10% more for US-only inference on Anthropic and on newer OpenAI models on regional endpoints, and to give up global-profile discounts and availability on Bedrock and Vertex.
- Keep ZDR, BAA and DPA separate in the security review. State which applies to which surface, org and project, and record the date, because the vendors change these terms often (every number on this page is as of 2026-11).
Related: AI governance and compliance · Amazon Bedrock · Google Vertex AI · Azure AI Foundry · Gemini API · Anthropic Messages API · Prompt caching · Forward deployed engineering
Sources
- Anthropic API and data retention · Anthropic data residency
- OpenAI data controls · OpenAI data residency
- Gemini API zero data retention · Gemini API abuse monitoring · Gemini API additional terms · Gemini API data logging
- Vertex AI data governance · Vertex AI locations · Vertex AI VPC Service Controls · Google Cloud HIPAA
- Azure Foundry data privacy · Azure Foundry abuse monitoring
- Bedrock data retention · Bedrock data protection · Bedrock cross-Region inference · AWS HIPAA eligible services