OpenAI introduces Private Safety Processing

On August 19, OpenAI released a preview of a system that recognizes abuse patterns across several linked sessions without retaining user content. The idea is that only a narrowly defined safety signal is passed on, without exposing the prompts and responses themselves, which keeps the zero data retention guarantee for paid API customers in force. The target is attackers who split a request across several conversations to avoid detection. The approach is the opposite of Anthropic's policy, which keeps data for 30 days with controlled human review; if you are choosing a vendor for a project with sensitive client data, that difference is worth understanding before you sign. Wider rollout and a technical paper were announced for September.

On August 19, OpenAI released a preview of a system that recognizes abuse patterns across several linked sessions without retaining user content. What it solves Attackers split a request across several separate conversations to avoid detection, so each part looks harmless on its own. Catching that means someone has to observe several conversations together, which collides directly with the promise that content is not kept. How the two are reconciled The system passes on only a narrowly defined safety signal, without exposing the prompts and responses themselves. The zero data retention guarantee for paid API customers stays in force. Why it concerns contractors If you are choosing a vendor for a project with sensitive client data, the retention policy is a line the contract has to reflect. Anthropic keeps data for 30 days with controlled human review, while OpenAI puts non-retention forward as an advantage. Neither is better in itself; it depends on what the client asks you to sign. What is still coming Wider rollout and a technical paper were announced for September. Until then this is an announcement, not proof.