If you're building on top of any LLM API, knowing what happens to your request data after the response lands is not optional - it's a design decision with compliance implications.
The Mechanism Behind Zero Data Retention
Most API providers, by default, log your inputs and outputs for some window of time - for abuse monitoring, safety evaluation, or model improvement. Zero Data Retention (ZDR) is an opt-in policy available to eligible OpenAI API customers that instructs the platform to not persist request or response data to disk after serving the response. The data moves through memory to generate a reply, then gets discarded. No stored prompt, no stored completion.
This matters most in three situations: you're passing personally identifiable information (PII) through prompts, your use case falls under a regulated industry (healthcare, finance, legal), or your enterprise contract explicitly prohibits third-party data storage. In all three, ZDR changes the answer to the question "does this vendor store our data?" from "yes, briefly" to "no, by policy."
The tradeoff is real: some safety and quality features - like certain content classifiers and abuse-detection pipelines - depend on stored logs. OpenAI is previewing a feature called Private Safety Processing to close this gap, running safety checks in a way that doesn't require retaining the underlying request content. The architecture isn't fully public yet, but the direction is toward keeping safety enforcement and data minimization from being mutually exclusive.
Real Example
If you're on an eligible plan, ZDR is configured at the organization level, not per-request. Here's a minimal API call - the ZDR guarantee applies to the entire session once enabled, so no extra header or flag is needed in the request itself:
from openai import OpenAI
client = OpenAI(api_key="your-api-key")
response = client.chat.completions.create(
model="gpt-4o",
messages=[{"role": "user", "content": "Summarize this contract clause: ..."}]
)
print(response.choices[0].message.content)
The difference from a standard call: zero. That's the point. Your org-level ZDR setting does the work. If you're unsure whether your account has ZDR enabled, it shows up under your organization's data controls in the API dashboard - not in code.
Key Takeaways
- Zero Data Retention means request and response data isn't persisted after the API call completes - it's a policy control, not a cryptographic guarantee
- ZDR is org-level, not request-level - it applies across your account once enabled, requiring no per-call code changes
- Private Safety Processing aims to decouple safety monitoring from data retention, though its implementation details are still emerging
For PMs and builders using LLM APIs with sensitive user data: have you actually checked your org's data retention settings, or are you assuming the default is private?
Sources referenced: OpenAI Blog - Offering Zero Data Retention for frontier models