Security

OpenAI Renews Its Promise Not to Keep Your Conversations.

OpenAI says it will keep offering Zero Data Retention for frontier models and previewed Private Safety Processing, which spots risk patterns without viewing conversation content.

· Huuush

OpenAI Renews Its Promise Not to Keep Your Conversations

Key takeaways

  1. 1OpenAI officially reaffirmed that it will keep offering Zero Data Retention for frontier models.
  2. 2The newly previewed Private Safety Processing identifies risk patterns across multiple interactions without employees viewing individual conversations.
  3. 3Images suspected to be CSAM are retained as an exception, even in a ZDR environment, because of legal reporting obligations.
Golden particles scattering and vanishing from a vault door against a deep red background

Conversation records still aren't kept

OpenAI said through its official account that it will keep offering Zero Data Retention (ZDR) for frontier models. According to the official announcement, for ZDR-eligible API customers, prompts and model responses aren't retained after a request is processed, and OpenAI employees can't view that content. Unless the customer explicitly opts in, that data isn't used to train models either.

Exceptions required by law remain. Images suspected to be child sexual abuse material (CSAM) are retained for reporting and review even in a ZDR environment.

Catching risk without viewing conversations

The core of this announcement is the new safety mechanism more than the promise to continue. OpenAI explained that "as AI takes on longer and more autonomous work, safety systems also need to look at risk across multiple interactions." Until now, ZDR-compatible safety systems evaluated each request individually, which means some risk patterns slip through in multistep work such as agentic tasks.

Private Safety Processing is a preview feature meant to solve this problem. OpenAI said it's designed to identify recurring or connected risk signals across related interactions without OpenAI employees looking at individual conversation content. The specific detection algorithms and scope of application haven't yet been detailed in the official documentation.

What this means for enterprise adoption decisions

ZDR has been a deciding condition for enterprise customers who need contracts, certifications, and regulatory compliance when adopting the API. This reaffirmation means that condition continues as agentic features expand, which is worth noting for organizations that handle sensitive data and are considering long-running autonomous work features.

However, since Private Safety Processing is still in preview, detailed specs on what data it actually analyzes and how far it reaches haven't been released. If you're considering adopting it, you'll need to check the contract terms and data processing scope separately before general release.

ZDR and no training on your data are different things

ZDR is a promise to not store data after a request is processed, while not training on it is a promise not to use customer content for model training, regardless of storage. OpenAI said it maintains both, but the two clauses are often specified separately in contracts, so the accurate way to confirm how they apply is to check your own API contract terms.

Frequently asked questions

What does Zero Data Retention mean?
It's OpenAI's policy of not storing eligible API customers' prompts and model responses after a request is processed. OpenAI employees can't access that content either.
What does Private Safety Processing do?
It's a preview feature designed to identify risk patterns across multiple interactions without employees directly viewing individual conversation content. The detailed scope of application hasn't yet been published in the official documentation.
Is any data retained as an exception under ZDR?
Yes. Images suspected to be child sexual abuse material (CSAM) are retained even in a ZDR environment because of legal reporting obligations.
Is my company's data used to train models?
OpenAI said enterprise customer data isn't used to train models unless the customer explicitly opts in. Check the exact scope in your contract terms.

Related articles