OpenAI has expanded Zero Data Retention for frontier models. Eligible API customers can process prompts and responses without that content remaining stored after a request is completed.
The company also previewed Private Safety Processing, a system under development that is intended to detect risk patterns across related interactions without giving OpenAI personnel access to the original content.
Not training and not retaining are different
OpenAI does not use business data or content submitted through its API to train models by default. However, this does not mean that all processed information is immediately deleted.
Under standard settings, abuse-monitoring logs may include prompts, responses, and derived metadata. OpenAI documents a default retention period of up to 30 days, although information may be kept longer when legally required or reasonably necessary to protect its services or third parties.
Zero Data Retention adds another protection. In approved projects, customer content is excluded from those monitoring logs.
What Zero Data Retention changes
The control cannot be freely enabled on any account. An organization must receive prior approval from OpenAI and accept additional requirements related to responsible use, moderation, and applicable obligations.
When ZDR is enabled, OpenAI treats the store parameter as false in Responses and Chat Completions, even if an application attempts to enable it. This reduces the risk of accidentally storing compatible responses through that parameter.
The announcement applies to eligible API customers. It is not an automatic privacy change for every ChatGPT account or every OpenAI product.
Not every endpoint works the same way
Zero retention does not mean that every platform feature is temporary. Some capabilities need to preserve application state so a task can continue or an object can be retrieved later.
OpenAI maintains compatibility information for its endpoints. Organizations should review every tool in use before describing an entire application as a system with no retention.
Safety without showing content to personnel
Some risks only become visible across a sequence of interactions. OpenAI cites repeated attempts to bypass safeguards and agents that continue taking actions after being instructed to stop.
Private Safety Processing is intended to analyze those patterns through automated systems. Its goal is to produce limited safety signals without allowing OpenAI personnel to read the underlying prompts or responses.
OpenAI describes two possible configurations. In one, content remains on infrastructure controlled by the customer. In the other, it is stored on OpenAI infrastructure but encrypted with customer-controlled keys.
Both designs are part of a preview. Their final availability, requirements, and coverage remain to be confirmed.
ZDR does not protect the whole architecture
Zero Data Retention governs processing within compatible OpenAI endpoints. A customer’s application may still save information in databases, server logs, observability systems, backups, or external tools.
The control does not replace encryption, access controls, key protection, or an internal retention policy. Its effectiveness depends on the complete architecture used by each organization.
