OpenAI previewed Private Safety Processing, a system meant to detect misuse patterns spanning multiple interactions while preserving zero data retention (ZDR) for eligible enterprise and API customers. The system flags narrowly defined signals to OpenAI without exposing raw prompts or responses to staff, and a second option would store encrypted content on OpenAI infrastructure with keys held only by the customer. This move contrasts with Anthropic, which announced it will require 30-day data retention on its most capable models for safety monitoring, arguing retention is necessary to catch multi-request attacks. Early testers reportedly include Microsoft, Databricks, Glean, and Abridge. The scheme excludes consumer ChatGPT tiers and carries a legal carve-out requiring manual review of suspected CSAM. OpenAI plans to roll out the system in September alongside a technical white paper.
Table of contents
What Private Safety Processing is forWhere the data sitsAnthropic reached the opposite answerWho is testing itWhat the scheme does not coverThe September testQuestions this post answers
What is OpenAI's Private Safety Processing and how does it keep zero data retention intact?
Private Safety Processing is a system OpenAI previewed that detects misuse patterns across multiple related interactions rather than judging each one in isolation, while preserving zero data retention (ZDR). Automated review flags suspicious activity and sends OpenAI a narrowly defined signal naming the activity type, without OpenAI staff ever accessing the underlying prompts or responses. Customers investigate alerts themselves and rollout begins in September, alongside a technical white paper. Enterprises weighing AI vendor data policies can track how these safety-versus-privacy tradeoffs evolve on daily.dev.
How does Anthropic's new data retention policy differ from OpenAI's zero data retention approach?
Anthropic announced it will require 30-day data retention on its most capable models for safety monitoring, reversing the zero-retention expectation many customers had. Anthropic itself acknowledged the policy will be unpopular and could hurt its business, especially if competitors keep offering zero retention, but argued retention is needed to catch attacks that span multiple requests. OpenAI instead built Private Safety Processing to detect the same cross-request threats without retaining customer data. Teams comparing AI provider data policies before signing contracts can follow this debate on daily.dev.
Does OpenAI's zero data retention and Private Safety Processing apply to consumer ChatGPT plans?
No, Private Safety Processing targets eligible enterprise and API customers only, not consumer ChatGPT plans. Data settings for Free, Plus, Go, and Pro tiers remain unchanged, since zero data retention never applied to those consumer tiers in the first place. One exception exists across all deployments: US law requires OpenAI to keep and manually review images flagged as potential CSAM even under zero data retention. Developers building on OpenAI's API can keep tabs on enterprise-versus-consumer policy differences via daily.dev.