AI/TLDR

OpenAI · 2026-08-19 · major

Private Safety Processing — OpenAI's abuse check that stores no customer data

Private Safety Processing is an OpenAI preview that looks for abuse across several linked conversations without storing customer content. Zero Data Retention stays on, and OpenAI receives only a narrow safety signal.

OpenAI CEO Sam Altman in profile against a plain white background
Getty Images via TechCrunch

OpenAI previews an abuse check that reads across many conversations while storing none of them.

Quick facts

MakerOpenAI
NamePrivate Safety Processing
StatusPreview with select customers
Who it's forCustomers approved for Zero Data Retention
What OpenAI receivesA narrowly defined safety signal
ScopeMultiple related conversations, not one at a time
AnnouncedAugust 19, 2026

What is it?

Private Safety Processing is a new OpenAI monitoring service, in preview with select customers, that looks for abuse patterns spread across several related conversations. It runs while Zero Data Retention is on, so the prompts and responses it inspects are never stored. OpenAI announced it on August 19, 2026.

How does it work?

Rather than judging each request on its own, the service reviews the inputs and outputs of several conversations together — what OpenAI describes as "long-horizon safety monitoring that assesses the inputs and outputs of multiple conversations — not just one." When it spots something suspicious it hands OpenAI a narrowly defined signal instead of the underlying text. Customers can opt to share more information if they want to.

Why does it matter?

Companies with strict security duties have had to pick between Zero Data Retention and the abuse checks a vendor wants before granting frontier-model access. That trade-off is what Private Safety Processing is meant to remove for the customers in the preview. TechCrunch reports Anthropic retains data for 30 days on certain models, so the two labs are now offering visibly different deals to the same buyers.

Who is it for?

enterprise API teams with strict data rules

Frequently asked questions

Does Private Safety Processing change OpenAI's Zero Data Retention promise?
No. OpenAI says Private Safety Processing runs while Zero Data Retention stays in force, so prompts and responses are still not stored. The monitoring happens automatically and passes OpenAI only a narrowly defined signal when something looks like abuse. Customers who want to send more detail can choose to share it.
How is this different from what Anthropic asks of customers?
TechCrunch reports that Anthropic keeps customer data for 30 days on certain models so it can run safety checks. OpenAI is taking the other route with Private Safety Processing: the abuse check still spans several conversations, but nothing from those conversations is retained, which is why TechCrunch framed the preview as a direct answer to Anthropic.
Can I turn Private Safety Processing on today?
Not yet for everyone. OpenAI is previewing Private Safety Processing with select customers, so it is not a self-serve toggle. Zero Data Retention itself, which the preview builds on, already requires OpenAI approval first; approved organizations then switch it on under Settings, Organization, Data controls at the organization or project level.
Which OpenAI endpoints can run under Zero Data Retention?
OpenAI's data-controls guide lists /v1/responses, /v1/chat/completions, /v1/embeddings, /v1/completions, /v1/moderations, /v1/realtime, the image generation and edit endpoints, and the audio transcription, translation and speech endpoints. Stateful endpoints such as /v1/assistants, /v1/threads and /v1/vector_stores are not eligible and may still store application state.

Try it

https://developers.openai.com/api/docs/guides/your-data

Sources · 3 outlets

Tags

  • openai
  • zero-data-retention
  • privacy
  • enterprise
  • api
  • safety
  • abuse-monitoring
  • security
  • compliance

← All releases · Learn AI