Skip to main content
Product UpdateStable

OpenAI previewed Private Safety Processing and Zero Data Retention for API models

OpenAI has reaffirmed its Zero Data Retention (ZDR) policy for eligible API customers using frontier models and previewed Private Safety Processing. The offering targets enterprise compliance and privacy requirements for sensitive commercial workloads running through OpenAI's developer API. Claims are as reported; this summary makes no determination about accuracy or significance.

First detected
Aug 24, 2026
Last updated
Aug 27, 2026

Moderate confidence

Reported by the organization responsible for the announcement.

Limited corroboration

No independent reporting recorded yet.

What does this mean?

Corroboration measures how many genuinely independent sources support the event. Confidence measures how reliable the available evidence appears.

No material changes recently.

Stable

No recent reporting has materially changed the known facts.

Follow this development to see meaningful updates as new evidence emerges.

Save keeps this for later. Follow tracks meaningful changes as new evidence emerges — it shapes your Following Feed, alerts, and digest eligibility, and doesn't promise an instant notification.

What we know

Why it matters

Data retention practices remain a primary adoption barrier for enterprises operating in strictly regulated sectors such as healthcare, finance, and defense. Offering technical zero-retention mechanisms alongside privacy-preserving safety enforcement reduces compliance overhead. This development forces competing frontier model vendors to match stronger data isolation and automated governance standards to secure enterprise contracts.

Coverage

Primary/vendor sources vs independent reporting

Primary / vendor source: information published directly by the company, organization, government body or project involved. Useful as a primary source, but not independent confirmation.

Independent reporting: reporting or analysis from a source independent of the organization making the underlying claim.

Timeline

  1. Sep 10, 2026

    1. Development status changed

      New → Stable — new reporting is no longer substantially changing the known facts

  2. Aug 24, 2026

    1. Development detected

  3. Aug 19, 2026

    1. New reporting added