Data controls in the OpenAI platform

For the complete documentation index, see llms.txt. Markdown versions of documentation pages are available by appending .md to the page URL.

Understand how OpenAI uses your data, and how you can control it.

Your data is your data. As of March 1, 2023, data sent to the OpenAI API is not used to train or improve OpenAI models (unless you explicitly opt in to share data with us).

Types of data stored with the OpenAI API

When using the OpenAI API, data may be stored as:

Abuse monitoring logs: Logs generated from your use of the platform, necessary for OpenAI to enforce our Usage Policies and agreements and mitigate harmful uses of AI.
Application state: Data persisted from some API features in order to fulfill the task or request.

Data retention controls for abuse monitoring

Abuse monitoring logs may contain certain customer content, such as prompts and responses, as well as metadata derived from that customer content, such as classifier outputs. By default, abuse monitoring logs are generated for all API feature usage and retained for up to 30 days, unless longer retention is required by law, or is reasonably necessary to protect our services or any third party from harm.

Eligible customers may have their customer content excluded from these abuse monitoring logs, subject to the limitations below, by getting approved for the Zero Data Retention or Modified Abuse Monitoring controls. Currently, these controls are subject to prior approval by OpenAI and acceptance of additional requirements. Approved customers may select between Modified Abuse Monitoring or Zero Data Retention for their API Organization or project.

Customers who enable Modified Abuse Monitoring or Zero Data Retention are responsible for ensuring their users abide by OpenAI's policies for safe and responsible use of AI and complying with any moderation and reporting requirements under applicable law.

Get in touch with our sales team to learn more about these offerings and inquire about eligibility.

Modified Abuse Monitoring

Modified Abuse Monitoring excludes customer content (other than image and file inputs in rare cases, as described below) from abuse monitoring logs across all API endpoints, while still allowing the customer to take advantage of the full capabilities of the OpenAI platform.

Zero Data Retention

Zero Data Retention excludes customer content from abuse monitoring logs in the same way as Modified Abuse Monitoring.

Additionally, Zero Data Retention changes some endpoint behavior: the store parameter for /v1/responses and v1/chat/completions will always be treated as false, even if the request attempts to set the value to true.

Besides those specific behavior changes, the endpoints and capabilities listed as No for Zero Data Retention Eligible in the table below may still store application state, even if Zero Data Retention is enabled.

ZDR with Private Safety Processing

Zero Data Retention with Private Safety Processing enables OpenAI to perform automated safety monitoring while preserving Zero Data Retention protections. Endpoint and feature limitations listed on this page still apply.

Customers using ZDR with PSP must configure customer-controlled storage and meet additional technical and operational requirements described in the ZDR with Private Safety Processing guide.

Private Retention with Private Safety Processing (fka Eyes Off)

For customers approved for Zero Data Retention or Modified Abuse Monitoring, we reserve the right to make models ineligible for Zero Data Retention or Modified Abuse Monitoring for specific customers, as notified in advance to the impacted customers in writing. In this instance, customer content will be retained in encrypted abuse monitoring logs in OpenAI-managed infrastructure, but such content will be excluded from human review unless required by applicable law. For additional information, see Appendix A of the Private Safety Processing technical whitepaper.

For customers who have executed an OpenAI Business Associate and Healthcare Addendum, once your org ID is provisioned with Private Retention with Private Safety Processing, BAA-eligible endpoints can be used for processing PHI, even if data is retained. Endpoint and feature limitations listed on this page still apply.

Safety Retention

For customers approved for Zero Data Retention or Modified Abuse Monitoring, we reserve the right to make models ineligible for Zero Data Retention or Modified Abuse Monitoring for specific customers if reasonably necessary to investigate or prevent severe risk activity, as notified in advance to the impacted customers in writing. In this instance, we may retain and human review customer content when using these models that our classifiers detect as potentially violating our Usage Policies or your agreement. Otherwise retention will not be affected. For customers who have executed an OpenAI Business Associate and Healthcare Addendum, once your org ID is provisioned with Safety Retention, BAA-eligible endpoints can be used for processing PHI, even if data is retained.

Configuring data retention controls

Once your organization has been approved for data retention controls, you'll see a Data Retention tab within Settings → Organization → Data controls. From that tab, you can configure data retention controls at both the organization and project level.

Organization-level controls: Choose between Zero Data Retention or Modified Abuse Monitoring for your entire organization.
Project-level controls: For each project, select default to inherit the organization-level setting, explicitly pick Zero Data Retention or Modified Abuse Monitoring, or select None to disable these controls for that project.

Storage requirements and retention controls per endpoint

The table below indicates when application state is stored for each endpoint. Zero Data Retention eligible endpoints do not retain any customer content for application state, subject to the limitations below. Zero Data Retention ineligible endpoints or capabilities may retain application state when used, even if you have Zero Data Retention enabled.

Endpoint	Data used for training	Abuse monitoring retention	Application state retention	Zero Data Retention eligible	Private Retention with PSP and Safety Retention eligible
`/v1/chat/completions`	No	30 days	None, see below for exceptions	Yes, see below for limitations	Yes, see below for limitations
`/v1/responses`	No	30 days	None, see below for exceptions	Yes, see below for limitations	Yes, see below for limitations
`/v1/decisions`	No	30 days	None, see below for exceptions	Yes, see below for limitations	Yes, see below for limitations
`/v1/conversations`	No	Until deleted	Until deleted	No	No
`/v1/conversations/items`	No	Until deleted	Until deleted	No	No
`/v1/chatkit/threads`	No	Until deleted	Until deleted	No	No
`/v1/agents`	No	30 days	Until deleted	No	No
`/v1/assistants`	No	30 days	Until deleted	No	No
`/v1/threads`	No	30 days	Until deleted	No	No
`/v1/threads/messages`	No	30 days	Until deleted	No	No
`/v1/threads/runs`	No	30 days	Until deleted	No	No
`/v1/threads/runs/steps`	No	30 days	Until deleted	No	No
`/v1/vector_stores`	No	30 days	Until deleted	No	No
`/v1/images/generations`	No	30 days	None	Yes, see below for limitations	No
`/v1/images/edits`	No	30 days	None	Yes, see below for limitations	No
`/v1/embeddings`	No	30 days	None	Yes	No
`/v1/audio/transcriptions`	No	None	None	Yes	No
`/v1/audio/translations`	No	None	None	Yes	No
`/v1/audio/speech`	No	30 days	None	Yes	No
`/v1/audio/voices`	No	30 days	Until deleted	No	No
`/v1/files`	No	30 days	Until deleted*	No	No
`/v1/fine_tuning/jobs`	No	30 days	Until deleted	No	No
`/v1/evals`	No	30 days	Until deleted	No	No
`/v1/batches`	No	30 days	Until deleted	No	No
`/v1/moderations`	No	None	None	Yes	No
`/v1/completions`	No	30 days	None	Yes	No
`/v1/live/sessions`	No	30 days	None, or 30 days if stored	Yes, with limitations below	No
`/v1/realtime`	No	30 days	None	Yes	No

`/v1/chat/completions`

Audio outputs application state is stored for 1 hour to enable multi-turn conversations.
When Zero Data Retention is enabled for an organization, the store parameter will always be treated as false, even if the request attempts to set the value to true.
See image and file inputs.
Prompt caching may store encrypted key/value tensors in GPU-local storage as application state. This data is stored on the local GPU machines and is not retained after the 24-hour expiration. For gpt-5.5 and gpt-5.5-pro, setting prompt_cache_retention to in_memory returns an error. For GPT-5.6 models and later model families, prompt_cache_options.ttl controls the minimum cache lifetime, not this maximum application-state retention period. To learn more, see the prompt caching guide.

`/v1/responses`

Except as noted below, the Responses API has a 30 day Application State retention period by default, or when the store parameter is set to true. In those cases, response data will be stored for at least 30 days.
When Zero Data Retention is enabled for an organization, the store parameter will always be treated as false, even if the request attempts to set the value to true.
Background mode stores response data to disk for roughly 10 minutes to enable polling. For projects using Modified Abuse Monitoring, including enhanced Modified Abuse Monitoring, foreground requests follow standard retention when store is omitted or set to true. Background responses follow the standard retention period only when the request explicitly sets store=true. If store is omitted or set to false for a background request, the response is deleted after the temporary polling period.
Audio outputs application state is stored for 1 hour to enable multi-turn conversations.
See image and file inputs.
MCP servers (used with the remote MCP server tool) are third-party services, and data sent to an MCP server is subject to their data retention policies.
Hosted containers used by Hosted Shell and Code Interpreter may write temporary application state to the container filesystem (backed by ephemeral block storage) while the container is active. Container data is deleted when the container expires or is explicitly deleted.
Prompt caching may store encrypted key/value tensors in GPU-local storage as application state. This data is stored on the local GPU machines and is not retained after the 24-hour expiration. For gpt-5.5 and gpt-5.5-pro, setting prompt_cache_retention to in_memory returns an error. For GPT-5.6 models and later model families, prompt_cache_options.ttl controls the minimum cache lifetime, not this maximum application-state retention period. To learn more, see the prompt caching guide.
For server-side compaction, no data is retained when store="false".
We support Skills in two form factors, both local execution and hosted container-based execution. Hosted skills follow the same container lifecycle as hosted shell: mounted skills and container files remain available while the container is active and are discarded when the container expires or is deleted.
Data transmitted to third-party services over network connections is subject to their data retention policies.

`/v1/decisions`

By default, abuse monitoring logs are retained for up to 30 days.

The Decisions API supports Zero Data Retention, Private Retention with PSP, and Safety Retention, subject to the eligibility and account configuration requirements described above.

The Decisions API follows the same Private Retention with PSP policy as the Responses API. Flagged content and a sample of requests may be retained for automated safety review. See Private Retention with PSP for details.

The following limitations apply:

Prompt caching may store encrypted key/value tensors in GPU-local storage as application state. This data is stored on the local GPU machines and is not retained after the 24-hour expiration. To learn more, see the prompt caching guide.
See image and file inputs for the CSAM retention exception for image inputs.

The Decisions API is eligible for HIPAA use under an executed OpenAI Business Associate and Healthcare Addendum, subject to the applicable account configuration requirements.

`/v1/assistants`, `/v1/threads`, and `/v1/vector_stores`

Objects related to the Assistants API are deleted from our servers 30 days after you delete them via the API or the dashboard. Objects that are not deleted via the API or dashboard are retained indefinitely.

`/v1/images`

Image generation is Zero Data Retention compatible when using gpt-image-2.5-sunburst, gpt-image-2.5-sunburst-2026-09-08, gpt-image-2.5-flare, gpt-image-2.5-flare-2026-09-08, gpt-image-2, gpt-image-1.5, and gpt-image-1-mini.

`/v1/files`

Files can be manually deleted via the API or the dashboard, or can be automatically deleted by setting the expires_after parameter. See here for more information.

Historical Videos API retention

Before the September 24, 2026 shutdown, the Videos API documentation specified 48 hours for downloading generated videos, followed by 30 days of retention for abuse monitoring. These periods describe the policy documented before shutdown; they do not promise download access after shutdown. See the Videos API shutdown notice.

Image and file inputs

Images and files may be uploaded as inputs to /v1/responses (including when using the Computer Use tool), /v1/chat/completions, and /v1/images. Images may also be uploaded to /v1/decisions. Image and file inputs are scanned for CSAM content upon submission. If the classifier detects potential CSAM content, the image will be retained for manual review, even if Zero Data Retention, Modified Abuse Monitoring, or Private Retention with PSP is enabled.

Web Search

Web Search with live internet access is not HIPAA eligible and is not covered by a BAA. Web Search in offline/cache-only mode (external_web_access: false) is eligible to be covered by a BAA when used with an API key from a ZDR-enabled project within a ZDR organization. This HIPAA/BAA guidance applies only to the Responses API web_search tool. Note: Preview variants (web_search_preview) ignore this parameter and behave as if external_web_access is true. We recommend using web_search.

<span id="how-does-data-residency-work" className="scroll-mt-[var(--docs-scroll-offset)]"

<span id="sub-processors-and-regional-request-processing" className="scroll-mt-[var(--docs-scroll-offset)]"

<span id="additional-requirements-for-non-us-regions" className="scroll-mt-[var(--docs-scroll-offset)]"

<span id="how-to-use-data-residency" className="scroll-mt-[var(--docs-scroll-offset)]"

<span id="select-a-processing-region-per-request" className="scroll-mt-[var(--docs-scroll-offset)]"

<span id="which-models-and-features-are-eligible-for-data-residency" className="scroll-mt-[var(--docs-scroll-offset)]"

<span id="support-by-region" className="scroll-mt-[var(--docs-scroll-offset)]"

<span id="api-endpoint-tool-and-model-support" className="scroll-mt-[var(--docs-scroll-offset)]"

<span id="endpoint-limitations" className="scroll-mt-[var(--docs-scroll-offset)]"

<span id="v1decisions-1" className="scroll-mt-[var(--docs-scroll-offset)]"

<span id="v1chatcompletions-1" className="scroll-mt-[var(--docs-scroll-offset)]"

<span id="v1responses-1" className="scroll-mt-[var(--docs-scroll-offset)]"

<span id="v1livesessions" className="scroll-mt-[var(--docs-scroll-offset)]"

Data residency controls

See the Data residency guide for regional storage and processing options, eligibility, setup instructions, and supported models and endpoints.

Enterprise Key Management (EKM)

Enterprise Key Management (EKM) allows you to encrypt your customer content at OpenAI using keys managed by your own external Key Management System (KMS).

Once configured, EKM applies to any application state created during your use of the platform. See the EKM help center article for more information about how EKM works, and how to integrate with your KMS provider.

EKM limitations

OpenAI supports Bring Your Own Key (BYOK) encryption with external accounts in AWS KMS, Google Cloud (GCP), and Azure Key Vault. If your organization leverages a different key management service, those keys need to be synced to one of the supported cloud KMS providers for use with OpenAI.

EKM does not support the following products. An attempt to use these endpoints in a project with EKM enabled will return an error.

Assistants (/v1/assistants)
Vision fine tuning

guides/your-data.md +54 −178

158 158

159Web Search with live internet access is not HIPAA eligible and is not covered by a BAA. Web Search in offline/cache-only mode (`external_web_access: false`) is eligible to be covered by a BAA when used with an API key from a ZDR-enabled project within a ZDR organization. This HIPAA/BAA guidance applies only to the Responses API `web_search` tool. Note: Preview variants (`web_search_preview`) ignore this parameter and behave as if `external_web_access` is `true`. We recommend using `web_search`.159Web Search with live internet access is not HIPAA eligible and is not covered by a BAA. Web Search in offline/cache-only mode (`external_web_access: false`) is eligible to be covered by a BAA when used with an API key from a ZDR-enabled project within a ZDR organization. This HIPAA/BAA guidance applies only to the Responses API `web_search` tool. Note: Preview variants (`web_search_preview`) ignore this parameter and behave as if `external_web_access` is `true`. We recommend using `web_search`.

160 160

161## Data residency controls161<span

~~162~~ 162 id="how-does-data-residency-work"

163Data residency controls are a project configuration option that allow you to configure the location of infrastructure OpenAI uses to provide services.163 className="scroll-mt-[var(--docs-scroll-offset)]"

~~164~~ 164>

165Contact our [sales team](https://openai.com/contact-sales) to see if you're eligible for using data residency controls. Data residency endpoints are charged a [10% uplift](https://developers.openai.com/api/docs/pricing) for models released on or after March 5, 2026, that are eligible for data residency.

~~166~~

167### How does data residency work?

~~168~~

169When data residency is enabled on your account, you can set a region for new projects you create in your account from the available regions listed below. If you use the supported endpoints, models, and snapshots listed below, your customer content (as defined in your services agreement) for that project will be stored at rest in the selected region to the extent the endpoint requires data persistence to function (such as /v1/batches).

~~170~~

171If you select a region that supports regional processing, as specifically identified below, the services will perform inference for your Customer Content in the selected region as well.

~~172~~

173Data residency does not apply to system data, which may be processed and stored outside the selected region. System data means account data, metadata, and usage data that do not contain Customer Content, which are collected by the services and used to manage and operate the services, such as account information or profiles of end users that directly access the services (for example, your personnel), analytics, usage statistics, billing information, support requests, and structured output schema.

~~174~~

175### Sub-processors and regional request processing

~~176~~

177OpenAI uses [sub-processors](https://openai.com/policies/sub-processor-list/) to provide its services. For requests sent to `us.api.openai.com` or `eu.api.openai.com`, OpenAI uses [Cloudflare Regional Services](https://developers.cloudflare.com/data-localization/regional-services/) so that TLS termination and HTTPS decryption occur within the selected processing region.

~~178~~

179### Limitations

~~180~~

181Data residency does not apply to: (1) any transmission or storage of Customer Content outside of the selected region caused by the location of an End User or Customer’s infrastructure when accessing the services; (2) products, services, or content offered by parties other than OpenAI through the Services; or (3) any data other than Customer Content, such as system data.

~~182~~

183If your selected Region does not support regional processing, as identified below, OpenAI may also process and temporarily store Customer Content outside of the Region to deliver the services.

~~184~~

185### Additional requirements for non-US regions

~~186~~

187To use data residency with any region other than the United States, you must be approved for abuse monitoring controls, and execute a Modified Retention amendment.

~~188~~

189Selecting the United Arab Emirates region requires additional approval. Contact [sales](https://openai.com/contact-sales) for assistance.

~~190~~

191### How to use data residency

~~192~~

193Data residency is configured per-project within your API Organization.

~~194~~

195To configure data residency for regional storage, select the appropriate region from the dropdown when creating a new project.

~~196~~

197For requests to projects with data residency configured, add the domain prefix as defined in the table below to each request.

~~198~~

199#### Select a processing region per request

~~200~~

201As an alternative to creating a region-specific project, you can select regional processing for an individual request by using the prefixed domain with an API key from a project having Global geography.

~~202~~

203Existing eligibility and data retention control requirements still apply. The selected endpoint and model must also support regional processing, as shown in the table below.

204 165

205The following example reuses one client and an API key from a Global project for global, US, and EU requests:166<span

167 id="sub-processors-and-regional-request-processing"

168 className="scroll-mt-[var(--docs-scroll-offset)]"

169>

206 170

207```python

208from openai import OpenAI

209 171

210client = OpenAI()

211 172

212# No processing constraint.

213response = client.responses.create(

214 model="gpt-5.6-terra",

215 input="Reply with OK.",

216)

217print(response.output_text)

218 173

219# US processing and storage.174<span

220response = client.with_options(175 id="additional-requirements-for-non-us-regions"

221 base_url="https://us.api.openai.com/v1",176 className="scroll-mt-[var(--docs-scroll-offset)]"

222).responses.create(177>

223 model="gpt-5.6-terra",

224 input="Reply with OK.",

225)

226print(response.output_text)

227 178

228# EU processing and storage.179<span

229response = client.with_options(180 id="how-to-use-data-residency"

230 base_url="https://eu.api.openai.com/v1",181 className="scroll-mt-[var(--docs-scroll-offset)]"

231).responses.create(182>

232 model="gpt-5.6-terra",

233 input="Reply with OK.",

234)

235print(response.output_text)

236```

237 183

238```ruby184<span

239require "openai"185 id="select-a-processing-region-per-request"

186 className="scroll-mt-[var(--docs-scroll-offset)]"

187>

240 188

241client = OpenAI::Client.new189<span

190 id="which-models-and-features-are-eligible-for-data-residency"

191 className="scroll-mt-[var(--docs-scroll-offset)]"

192>

242 193

243response = client.responses.create(194<span

244 model: "gpt-5.6-terra",195 id="support-by-region"

245 input: "Reply with OK."196 className="scroll-mt-[var(--docs-scroll-offset)]"

246)197>

247puts(response.output_text)

248 198

249response = client.with_options(data_residency: :us).responses.create(199<span

250 model: "gpt-5.6-terra",200 id="api-endpoint-tool-and-model-support"

251 input: "Reply with OK."201 className="scroll-mt-[var(--docs-scroll-offset)]"

252)202>

253puts(response.output_text)

254 203

255# EU processing requires a key from an EU-region project.204<span

256response = client.with_options(data_residency: :eu, api_key: ENV.fetch("OPENAI_EU_API_KEY"), organization: nil, project: nil).responses.create(205 id="endpoint-limitations"

257 model: "gpt-5.6-terra",206 className="scroll-mt-[var(--docs-scroll-offset)]"

258 input: "Reply with OK."207>

259)

260puts(response.output_text)

261```

262 208

209<span

210 id="v1decisions-1"

211 className="scroll-mt-[var(--docs-scroll-offset)]"

212>

263 213

264### Which models and features are eligible for data residency?214<span

215 id="v1chatcompletions-1"

216 className="scroll-mt-[var(--docs-scroll-offset)]"

217>

265 218

266The following models and API services are eligible for data residency today for the regions specified below.219<span

220 id="v1responses-1"

221 className="scroll-mt-[var(--docs-scroll-offset)]"

222>

267 223

268Use **Support by region** to compare regional capabilities and expand the services available in each region. Use **API Endpoint, tool and model support** for complete model lists and a detailed service view. Support for regional storage does not imply support for regional processing.224<span

225 id="v1livesessions"

226 className="scroll-mt-[var(--docs-scroll-offset)]"

227>

269 228

270In Australia, India, and Japan, organizations with active Zero Data Retention can use `gpt-6-luna` for regional processing. These regions support Standard pay-as-you-go only. Use a project in the selected region. The Responses and Chat Completions APIs support text and image inputs and text output. Hosted tools are unavailable for regional processing in these three regions.

271 229

272Fast mode supports EU data residency for GPT-6.1 Sol, GPT-6.1 Terra, and GPT-6 Luna. Fast mode is not available with EU data residency for GPT-6 Astra or GPT-6 Sol. GPT-6.1 Sol, GPT-6.1 Terra, GPT-6 Sol, and GPT-6 Luna support EU data residency with Standard, Flex, and Batch processing. [Ultrafast mode](https://developers.openai.com/api/docs/guides/ultrafast-mode) for GPT-6.1 Sol supports US and EU data residency and global processing. GPT-6 Astra Ultrafast supports US data residency and global processing only.

273 230

274#### Support by region

275 231

276The complete, unfiltered regional support table follows. Model snapshots for each service are listed in **API Endpoint, tool and model support**. When regional processing supports only a subset of snapshots, that subset is included in the processing-services cell.

277 232

279| -------------------------- | ------------------- | :--------------: | :-----------------: | :-----------------: | --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

280| United States | `us.api.openai.com` | Yes | Yes | No | Text, Audio, Voice, Image | `/v1/audio/transcriptions, /v1/audio/translations, /v1/audio/speech` `/v1/batches` `/v1/chat/completions` `/v1/decisions` `/v1/embeddings` `/v1/evals` `/v1/files` `/v1/fine_tuning/jobs` `/v1/images/edits` `/v1/images/generations` `/v1/moderations` `/v1/live/sessions` `/v1/realtime` `/v1/realtime/transcription_sessions` `/v1/realtime/translations` `/v1/responses` `/v1/responses File Search` `/v1/responses Web Search` `/v1/vector_stores` `Code Interpreter tool` `File Search` `File Uploads` `Remote MCP server tool` `Scale Tier` `Structured Outputs (excluding schema)` `Supported input modalities` | `/v1/audio/transcriptions, /v1/audio/translations, /v1/audio/speech` `/v1/batches` `/v1/chat/completions` `/v1/decisions` `/v1/embeddings` `/v1/evals` `/v1/fine_tuning/jobs` `/v1/images/edits` `/v1/images/generations` `/v1/moderations` `/v1/live/sessions` `/v1/realtime` `/v1/realtime/transcription_sessions` `/v1/realtime/translations` `/v1/responses` `/v1/responses File Search` `/v1/responses Web Search` `Code Interpreter tool` `File Search` `Remote MCP server tool` `Scale Tier` `Structured Outputs (excluding schema)` `Supported input modalities` |

281| Europe (EEA + Switzerland) | `eu.api.openai.com` | Yes | Yes | Yes\*\* | Text, Audio, Voice, Image\* | `/v1/audio/transcriptions, /v1/audio/translations, /v1/audio/speech` `/v1/batches` `/v1/chat/completions` `/v1/decisions` `/v1/embeddings` `/v1/evals` `/v1/files` `/v1/fine_tuning/jobs` `/v1/images/edits` `/v1/images/generations` `/v1/moderations` `/v1/live/sessions` `/v1/realtime` `/v1/realtime/transcription_sessions` `/v1/realtime/translations` `/v1/responses` `/v1/responses File Search` `/v1/responses Web Search` `/v1/vector_stores` `Code Interpreter tool` `File Search` `File Uploads` `Remote MCP server tool` `Scale Tier` `Structured Outputs (excluding schema)` `Supported input modalities` | `/v1/audio/transcriptions, /v1/audio/translations, /v1/audio/speech` `/v1/batches` `/v1/chat/completions` `/v1/decisions` `/v1/embeddings` `/v1/evals` `/v1/fine_tuning/jobs` `/v1/images/edits` `/v1/images/generations` `/v1/moderations` `/v1/live/sessions` `/v1/realtime` `/v1/realtime/transcription_sessions` `/v1/realtime/translations` `/v1/responses` `/v1/responses File Search` `/v1/responses Web Search` `Code Interpreter tool` `File Search` `Remote MCP server tool` `Scale Tier` `Structured Outputs (excluding schema)` `Supported input modalities` |

282| Australia\* | `au.api.openai.com` | Yes | Yes | Yes\*\*\* | Text, Audio, Voice, Image | `/v1/audio/transcriptions, /v1/audio/translations, /v1/audio/speech` `/v1/batches` `/v1/chat/completions` `/v1/decisions` `/v1/embeddings` `/v1/files` `/v1/fine_tuning/jobs` `/v1/images/edits` `/v1/images/generations` `/v1/moderations` `/v1/responses` `/v1/responses File Search` `/v1/responses Web Search` `/v1/vector_stores` `Code Interpreter tool` `File Search` `File Uploads` `Remote MCP server tool` `Scale Tier` `Structured Outputs (excluding schema)` `Supported input modalities` | `/v1/chat/completions` (`gpt-6-luna`) `/v1/responses` (`gpt-6-luna`) |

283| Canada\* | `ca.api.openai.com` | Yes | No | Yes | Text, Audio, Voice, Image | `/v1/audio/transcriptions, /v1/audio/translations, /v1/audio/speech` `/v1/batches` `/v1/chat/completions` `/v1/decisions` `/v1/embeddings` `/v1/files` `/v1/fine_tuning/jobs` `/v1/images/edits` `/v1/images/generations` `/v1/moderations` `/v1/responses` `/v1/responses File Search` `/v1/responses Web Search` `/v1/vector_stores` `Code Interpreter tool` `File Search` `File Uploads` `Remote MCP server tool` `Scale Tier` `Structured Outputs (excluding schema)` `Supported input modalities` | None |

284| Japan\* | `jp.api.openai.com` | Yes | Yes | Yes\*\*\* | Text, Audio, Voice, Image | `/v1/audio/transcriptions, /v1/audio/translations, /v1/audio/speech` `/v1/batches` `/v1/chat/completions` `/v1/decisions` `/v1/embeddings` `/v1/files` `/v1/fine_tuning/jobs` `/v1/images/edits` `/v1/images/generations` `/v1/moderations` `/v1/responses` `/v1/responses File Search` `/v1/responses Web Search` `/v1/vector_stores` `Code Interpreter tool` `File Search` `File Uploads` `Remote MCP server tool` `Scale Tier` `Structured Outputs (excluding schema)` `Supported input modalities` | `/v1/chat/completions` (`gpt-6-luna`) `/v1/responses` (`gpt-6-luna`) |

285| India\* | `in.api.openai.com` | Yes | Yes | Yes\*\*\* | Text, Audio, Voice, Image | `/v1/audio/transcriptions, /v1/audio/translations, /v1/audio/speech` `/v1/batches` `/v1/chat/completions` `/v1/decisions` `/v1/embeddings` `/v1/files` `/v1/fine_tuning/jobs` `/v1/images/edits` `/v1/images/generations` `/v1/moderations` `/v1/responses` `/v1/responses File Search` `/v1/responses Web Search` `/v1/vector_stores` `Code Interpreter tool` `File Search` `File Uploads` `Remote MCP server tool` `Scale Tier` `Structured Outputs (excluding schema)` `Supported input modalities` | `/v1/chat/completions` (`gpt-6-luna`) `/v1/responses` (`gpt-6-luna`) |

286| Singapore\* | `sg.api.openai.com` | Yes | No | Yes | Text, Audio, Voice, Image | `/v1/audio/transcriptions, /v1/audio/translations, /v1/audio/speech` `/v1/batches` `/v1/chat/completions` `/v1/decisions` `/v1/embeddings` `/v1/files` `/v1/fine_tuning/jobs` `/v1/images/edits` `/v1/images/generations` `/v1/moderations` `/v1/responses` `/v1/responses File Search` `/v1/responses Web Search` `/v1/vector_stores` `Code Interpreter tool` `File Search` `File Uploads` `Remote MCP server tool` `Scale Tier` `Structured Outputs (excluding schema)` `Supported input modalities` | None |

287| South Korea\* | `kr.api.openai.com` | Yes | No | Yes | Text, Audio, Voice, Image | `/v1/audio/transcriptions, /v1/audio/translations, /v1/audio/speech` `/v1/batches` `/v1/chat/completions` `/v1/decisions` `/v1/embeddings` `/v1/files` `/v1/fine_tuning/jobs` `/v1/images/edits` `/v1/images/generations` `/v1/moderations` `/v1/responses` `/v1/responses File Search` `/v1/responses Web Search` `/v1/vector_stores` `Code Interpreter tool` `File Search` `File Uploads` `Remote MCP server tool` `Scale Tier` `Structured Outputs (excluding schema)` `Supported input modalities` | None |

288| United Kingdom\* | `gb.api.openai.com` | Yes | No | Yes | Text, Audio, Voice, Image | `/v1/audio/transcriptions, /v1/audio/translations, /v1/audio/speech` `/v1/batches` `/v1/chat/completions` `/v1/decisions` `/v1/embeddings` `/v1/files` `/v1/fine_tuning/jobs` `/v1/images/edits` `/v1/images/generations` `/v1/moderations` `/v1/responses` `/v1/responses File Search` `/v1/responses Web Search` `/v1/vector_stores` `Code Interpreter tool` `File Search` `File Uploads` `Remote MCP server tool` `Scale Tier` `Structured Outputs (excluding schema)` `Supported input modalities` | None |

289| United Arab Emirates\* | `ae.api.openai.com` | Yes | Yes | Yes | Text, Audio, Voice, Image | `/v1/audio/transcriptions, /v1/audio/translations, /v1/audio/speech` `/v1/batches` `/v1/chat/completions` `/v1/decisions` `/v1/embeddings` `/v1/files` `/v1/fine_tuning/jobs` `/v1/images/edits` `/v1/images/generations` `/v1/moderations` `/v1/responses` `/v1/responses File Search` `/v1/responses Web Search` `/v1/vector_stores` `Code Interpreter tool` `File Search` `File Uploads` `Remote MCP server tool` `Scale Tier` `Structured Outputs (excluding schema)` `Supported input modalities` | `/v1/chat/completions` (`gpt-5.6-luna`, `gpt-5.5-2026-04-23`, `gpt-5.2-2025-12-11`) `/v1/embeddings` (`text-embedding-3-large`) `/v1/responses` (`gpt-5.5-pro-2026-04-23`, `gpt-5.6-luna`, `gpt-5.5-2026-04-23`, `gpt-5.2-2025-12-11`) |

~~290~~

291\* Image support in these regions requires approval for enhanced Zero Data Retention or enhanced Modified Abuse Monitoring.

~~292~~

293\*\* Requires Zero Data Retention, Modified Abuse Monitoring, Private Retention with PSP, or Safety Retention.

~~294~~

295\*\*\* Regional processing in Australia, India, and Japan requires active Zero Data Retention (ZDR). Modified Abuse Monitoring (MAM) alone is insufficient.

~~296~~

297#### API Endpoint, tool and model support

~~298~~

300| -------------------------------------------------------------------- | ---------------- | ----------------------------------------- | ---------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

302| `/v1/batches` | Batches | All listed regions | United States, Europe (EEA + Switzerland) | `gpt-6-astra`, `gpt-6.1-sol`, `gpt-6.1-terra`, `gpt-6-sol`, `gpt-6-luna`, `gpt-5.5-pro-2026-04-23`, `gpt-5.4-pro-2026-03-05`, `gpt-5.2-pro-2025-12-11`, `gpt-5-pro-2025-10-06`, `gpt-5.6-sol`, `gpt-5.6-terra`, `gpt-5.6-luna`, `gpt-5.5-2026-04-23`, `gpt-5.4-2026-03-05`, `gpt-5-2025-08-07`, `gpt-5.4-mini-2026-03-17`, `gpt-5.4-nano-2026-03-17`, `gpt-5.2-2025-12-11`, `gpt-5.1-2025-11-13`, `gpt-5-mini-2025-08-07`, `gpt-5-nano-2025-08-07`, `gpt-4.1-2025-04-14`, `gpt-4.1-mini-2025-04-14`, `gpt-4.1-nano-2025-04-14`, `o3-2025-04-16`, `o4-mini-2025-04-16`, `o1-pro`, `o1-pro-2025-03-19`, `o3-mini-2025-01-31`, `o1-2024-12-17`, `gpt-4o-2024-11-20`, `gpt-4o-2024-08-06`, `gpt-4o-mini-2024-07-18`, `gpt-4-turbo-2024-04-09`, `gpt-4-0613`, `gpt-3.5-turbo-0125` | None | GPT-6.1 Sol, GPT-6.1 Terra, GPT-6 Sol, and GPT-6 Luna support EU data residency with Standard, Flex, and Batch processing. GPT-6.1 Sol and GPT-6.1 Terra support only US and EU data residency. |

303| `/v1/chat/completions` | Chat Completions | All listed regions | United States, Europe (EEA + Switzerland), United Arab Emirates, Australia, India, Japan | `gpt-6-astra`, `gpt-6.1-sol`, `gpt-6.1-terra`, `gpt-6-sol`, `gpt-6-luna`, `gpt-5.6-sol`, `gpt-5.6-terra`, `gpt-5.6-luna`, `gpt-5.5-2026-04-23`, `gpt-5.4-2026-03-05`, `gpt-5.4-mini-2026-03-17`, `gpt-5.4-nano-2026-03-17`, `gpt-5.2-2025-12-11`, `gpt-5.1-2025-11-13`, `gpt-5-2025-08-07`, `gpt-5-mini-2025-08-07`, `gpt-5-nano-2025-08-07`, `gpt-4.1-2025-04-14`, `gpt-4.1-mini-2025-04-14`, `gpt-4.1-nano-2025-04-14`, `o3-mini-2025-01-31`, `o3-2025-04-16`, `o4-mini-2025-04-16`, `o1-2024-12-17`, `gpt-4o-2024-11-20`, `gpt-4o-2024-08-06`, `gpt-4o-mini-2024-07-18`, `gpt-4-turbo-2024-04-09`, `gpt-4-0613`, `gpt-3.5-turbo-0125` | United Arab Emirates: `gpt-5.6-luna`, `gpt-5.5-2026-04-23`, `gpt-5.2-2025-12-11` Australia, India, Japan: `gpt-6-luna` | Fast mode supports EU data residency for GPT-6.1 Sol, GPT-6.1 Terra, and GPT-6 Luna. Fast mode is not available with EU data residency for GPT-6 Astra or GPT-6 Sol. GPT-6.1 Sol and GPT-6.1 Terra support only US and EU data residency. |

316| `/v1/responses` | Responses | All listed regions | United States, Europe (EEA + Switzerland), United Arab Emirates, Australia, India, Japan | `gpt-6-astra`, `gpt-6.1-sol`, `gpt-6.1-terra`, `gpt-6-sol`, `gpt-6-luna`, `gpt-5.5-pro-2026-04-23`, `gpt-5.4-pro-2026-03-05`, `gpt-5.2-pro-2025-12-11`, `gpt-5-pro-2025-10-06`, `gpt-5.6-sol`, `gpt-5.6-terra`, `gpt-5.6-luna`, `gpt-5.5-2026-04-23`, `gpt-5.4-2026-03-05`, `gpt-5-2025-08-07`, `gpt-5.4-mini-2026-03-17`, `gpt-5.4-nano-2026-03-17`, `gpt-5.2-2025-12-11`, `gpt-5.1-2025-11-13`, `gpt-5-mini-2025-08-07`, `gpt-5-nano-2025-08-07`, `gpt-4.1-2025-04-14`, `gpt-4.1-mini-2025-04-14`, `gpt-4.1-nano-2025-04-14`, `o3-2025-04-16`, `o4-mini-2025-04-16`, `o1-pro`, `o1-pro-2025-03-19`, `o3-mini-2025-01-31`, `o1-2024-12-17`, `gpt-4o-2024-11-20`, `gpt-4o-2024-08-06`, `gpt-4o-mini-2024-07-18`, `gpt-4-turbo-2024-04-09`, `gpt-4-0613`, `gpt-3.5-turbo-0125` | United Arab Emirates: `gpt-5.5-pro-2026-04-23`, `gpt-5.6-luna`, `gpt-5.5-2026-04-23`, `gpt-5.2-2025-12-11` Australia, India, Japan: `gpt-6-luna` | Fast mode supports EU data residency for GPT-6.1 Sol, GPT-6.1 Terra, and GPT-6 Luna. Fast mode is not available with EU data residency for GPT-6 Astra or GPT-6 Sol. GPT-6.1 Sol and GPT-6.1 Terra support only US and EU data residency. |

~~327~~

~~328~~

~~329~~

330### Endpoint limitations

~~331~~

332#### /v1/decisions

~~333~~

334The Decisions API is available in all supported API regions. Regional processing is supported in the United States and Europe (EEA + Switzerland). Availability in a region does not imply that inference is performed in that region.

~~335~~

336- [Extended prompt caching](https://developers.openai.com/api/docs/guides/prompt-caching#prompt-cache-retention) in regions that do not support Regional processing may require that OpenAI process and temporarily store Customer Content outside of the Region to deliver the services.

~~337~~

338#### /v1/chat/completions

~~339~~

340- Cannot set store=true in non-US regions.

341- [Extended prompt caching](https://developers.openai.com/api/docs/guides/prompt-caching#prompt-cache-retention) in regions that do not support Regional processing may require that OpenAI process and temporarily store Customer Content outside of the Region to deliver the services.

~~342~~

343#### /v1/responses

~~344~~

345- [Extended prompt caching](https://developers.openai.com/api/docs/guides/prompt-caching#prompt-cache-retention) in regions that do not support Regional processing may require that OpenAI process and temporarily store Customer Content outside of the Region to deliver the services.

~~346~~

347#### /v1/live/sessions

~~348~~

349GPT-Live sessions are eligible for Zero Data Retention. With Zero Data Retention enabled, `store` is treated as `false`, even if a request sets it to `true`.

~~350~~

351Session storage is disabled by default. For projects with session storage enabled, `store: true` retains the completed session recording for 30 days so that it can be downloaded or used to start a forked session. Stored sessions and their index expire after 30 days. Recording downloads and forking require a data policy that permits persistence and are not available with Zero Data Retention.

~~352~~

353Setting `store: false` on a fork prevents storage of the new session; it does not delete the source recording or remove the authorization required to read it. The API does not provide a public stored-session deletion endpoint.

~~354~~

355GPT-Live supports data residency in the United States and Europe. Delegated backend models and tools have their own data controls; check the applicable endpoint and feature entries on this page.

~~356~~

357#### /v1/realtime

358 234

359Tracing is not currently EU data residency compliant for `/v1/realtime`.235See the [Data residency guide](https://developers.openai.com/api/docs/guides/data-residency) for regional storage and processing options, eligibility, setup instructions, and supported models and endpoints.

360 236

361## Enterprise Key Management (EKM)237## Enterprise Key Management (EKM)

362 238

guides/your-data.md 2026-11-12 22:57 UTC to 2026-11-13 23:58 UTC

Data controls in the OpenAI platform

Types of data stored with the OpenAI API

Data retention controls for abuse monitoring

Modified Abuse Monitoring

Zero Data Retention

ZDR with Private Safety Processing

Private Retention with Private Safety Processing (fka Eyes Off)

Safety Retention

Configuring data retention controls

Storage requirements and retention controls per endpoint

/v1/chat/completions

/v1/responses

/v1/decisions

/v1/assistants, /v1/threads, and /v1/vector_stores

/v1/images

/v1/files

Historical Videos API retention

Image and file inputs

Web Search

Data residency controls

Enterprise Key Management (EKM)

EKM limitations

`/v1/chat/completions`

`/v1/responses`

`/v1/decisions`

`/v1/assistants`, `/v1/threads`, and `/v1/vector_stores`

`/v1/images`

`/v1/files`