Skip to content
Security & risk

OpenAI Adds No-Retention Option for API Calls to Its Top Models

Short answer

OpenAI has extended Zero Data Retention (ZDR) to frontier models accessed via its API, so eligible customers can process prompts and completions without OpenAI storing that data afterward. This matters because it removes a standing objection — data persistence — that has blocked regulated or privacy-sensitive B2B companies from using top-tier models in production sales and support workflows.

What this means for operators

If your company handles customer PII, contract terms, or support tickets with regulated content, ZDR access changes the calculus on which OpenAI model you can legally route that data through. Previously, many 10-200 person B2B firms either avoided frontier models for sensitive workflows or built custom redaction layers before calls. With ZDR available for eligible accounts, ops and legal teams can revisit those workarounds — potentially simplifying pipelines for support ticket triage, sales call summarization, or CRM enrichment that touch customer data. The catch: ZDR eligibility isn't automatic. It typically requires an enterprise agreement or specific API tier, and it may still exclude certain features (like persistent memory or fine-tuning on your data). Before assuming this unblocks anything, check whether your current OpenAI contract tier qualifies, and confirm which specific models and endpoints the zero-retention policy covers — the announcement does not guarantee blanket coverage across every product surface.

OpenAI announced that Zero Data Retention (ZDR) is now available for its frontier models through the API, for eligible customers. Under ZDR, OpenAI does not retain the content of API requests and responses after they are processed — a stricter posture than OpenAI's standard retention policy, which by default stores API data for a limited period (typically 30 days) for abuse monitoring unless customers opt out.

ZDR itself is not new — OpenAI has offered it for some products previously — but this expansion applies the policy to its most capable, frontier-tier models via the API, closing a gap that had pushed some enterprise customers toward older or lower-tier models when handling sensitive data.

For B2B companies building sales, support, or operations automation on top of OpenAI's API, data retention has been a recurring compliance sticking point, particularly for firms in finance, healthcare-adjacent services, or those with EU customers subject to GDPR data minimization requirements. A no-retention option gives compliance and security teams a cleaner story: prompts containing customer names, deal terms, or support ticket contents are processed and then not stored by the model provider.

Eligibility details are limited in the announcement — it's unconfirmed which specific frontier models, API tiers, or account types qualify, and whether ZDR applies uniformly across features like function calling, file search, or the Assistants API. Companies interested in ZDR should confirm scope and eligibility directly with OpenAI or their account representative rather than assuming coverage.

The move follows a broader industry pattern of AI vendors adding enterprise-grade data controls — retention policies, regional data residency, and audit logging — as a condition for landing larger, more risk-averse customers. For smaller B2B operators, the practical effect is a lower barrier to using frontier-tier models for workflows that were previously restricted to on-premise or heavily redacted data.

Source: OpenAI

Next step

Discovery Sprint

If that argument holds for your operation, the next step is measuring it. Thirty minutes on one process, and we say whether the arithmetic is likely to close.

Put a time in the calendar

Thirty minutes, free. The sprint is what the call is about.

Fee
$2,500
Length
1-2 weeks

Refunded in full if we conclude you should not build.