OpenAI Offers Zero Data Retention for Frontier AI Models With Private Safety Processing

OpenAI has announced Zero Data Retention for eligible API customers using its frontier AI models, alongside a new Private Safety Processing system designed to support safety monitoring without exposing customer prompts or responses to company personnel.

Under the Zero Data Retention commitment, OpenAI does not retain customer prompts or model outputs after a request has been processed.

The company also says customer content is not available for employee review. At the same time, enterprise data is not used to train OpenAI models unless the customer explicitly opts in.

The move addresses a major barrier to enterprise AI adoption, particularly for organizations handling financial records, health information, confidential business data, and proprietary research.

Many regulated industries require strict controls over where sensitive data is stored, who can access it, and how long it remains available.

OpenAI Offers Zero Data Retention for Frontier Models

However, OpenAI noted that model misuse may not always be visible in a single prompt or response. As AI systems begin handling longer and more autonomous tasks, potentially harmful activity may only become clear after several related interactions.

Threat actors could repeatedly test safety controls, coordinate activity across accounts, or disguise malicious requests as legitimate research.

Private Safety Processing is intended to address this challenge while preserving the Zero Data Retention model. Existing safety protections for Zero Data Retention deployments generally examine each interaction individually.

The new system is designed to analyze patterns across related interactions using automated processes, without granting OpenAI personnel access to the underlying content.

For customer-controlled Zero Data Retention deployments, content remains on the customer-managed infrastructure. OpenAI is also developing a model in which content can be stored on its infrastructure but encrypted with customer-controlled keys.

OpenAI personnel would not possess copies of those keys and therefore could not access the underlying prompts or responses. When automated systems detect potential misuse, OpenAI receives a limited safety signal indicating the category of risky activity.

The signal can support enforcement decisions, but it does not reveal the original customer content. Customers can investigate alerts using records in their own environments.

They may voluntarily provide relevant data if they want to appeal a decision, clarify legitimate activity, or assist with a verified abuse investigation. The approach has important cybersecurity implications.

Organizations deploying frontier models often need to balance privacy requirements against provider safety controls. In some cases, safety monitoring has required providers to retain sensitive customer data, creating compliance and operational concerns for security teams.

OpenAI’s Private Safety Processing separates automated safety checks from human access to enterprise content, with testing underway and broader rollout planned for September alongside a technical white paper on its architecture and safeguards.

For security leaders, the announcement highlights an emerging model for enterprise AI governance: customer-controlled data, cryptographic protections, automated detection of misuse, and limited disclosure of safety-relevant signals.

Prevent incidents due to slow investigations. Power your Tier 1 with threat intelligence from 15K SOCs: Integrate TI Lookup in your SOC