Zero Data Retention (ZDR)

Definition

An AI operational mode ensuring customer inputs and outputs are processed in memory and discarded without persistent storage, logging, or model retraining

Primary Purpose

Preventing enterprise data leakage, unauthorized model training, and exposure of proprietary prompts

Status and Critique

Described as 'Swiss cheese' due to implementation gaps and potential data leakage vulnerabilities

Alternative Solutions

Localized AI models, on-premise deployments, and AI Sovereignty frameworks

Technical Implementation

Routing requests through logging-exempt paths and purging prompt-response pairs before persistent disk writes

2025-06-03

2026-01-19

Decagon Dialogues 2026 is here. Register today Sign in Get a demo Glossary # Zero data retention AI Zero data retention (ZDR) AI refers to an operational mode offered by AI API providers in which customer prompts, completions, and associated metadata are not stored, logged, or used for any purpose — including model training, abuse monitoring, or product improvement — beyond the immediate API call. Under a zero data retention agreement, the data flows through the provider’s infrastructure to generate a response and is then deleted within seconds, leaving no persistent record on the provider’s systems. For enterprise buyers processing sensitive customer data through AI models, ZDR is often a contractual prerequisite for deployment. [...] ## Zero data retention vs. data anonymization Data anonymization is an alternative approach in which data is retained but stripped of personally identifiable information before storage or use. Anonymization is lower friction operationally — it allows providers to retain useful training and monitoring data — but it introduces residual risk: re-identification attacks on anonymized datasets are a well-documented privacy failure mode. Zero data retention eliminates that risk category entirely by not retaining the data at all. The trade-off is that ZDR limits the provider’s ability to use customer data to improve the model, which can slow quality improvements for customers on ZDR plans. [...] ## How zero data retention is implemented At the infrastructure level, ZDR is implemented through a combination of access controls and processing pipeline modifications. Requests flagged for zero data retention are routed through a logging-exempt path: they reach the model inference layer, generate a response, and the prompt-response pair is discarded before any persistence layer writes. Audit logs typically record only metadata (timestamp, model version, token counts, latency) without the content itself, allowing billing and abuse detection while preserving data minimization commitments.

Zero data retention is a contractual and technical commitment that an AI provider will not store the content of your prompts and the model’s outputs after the request is processed. Inputs are held in memory only as long as needed to generate a response, then discarded. Nothing is written to persistent logs, nothing is available to provider employees after the fact, and nothing accumulates in a store that could later be breached, subpoenaed, or repurposed for training. ZDR is distinct from two commitments it is often confused with: [...] For the API platform, OpenAI’s standard practice has been to retain API inputs and outputs for up to 30 days for abuse and misuse monitoring, then delete them, with business data not used for training by default. Zero data retention is available as a negotiated arrangement for qualifying customers on eligible endpoints, under which prompts and completions are not persisted at all. ZDR eligibility typically involves a trust and safety review, applies to specific endpoints rather than the entire platform, and can be incompatible with features that inherently require storage, such as file uploads, assistants-style threads, or batch processing. Enterprises handling regulated data should get the ZDR designation, the covered endpoints, and the excluded features in writing in the services [...] Every prompt your employees send to an AI model is a disclosure. It may contain customer records, source code, deal terms, health information, or privileged legal analysis, and the moment it leaves your network, a new question attaches to it: how long does the model provider keep it, who can access it, and what happens if a regulator, litigant, or attacker comes looking? Zero data retention, often shortened to ZDR, has emerged as the gold-standard answer to that question, and it is rapidly becoming a line item in vendor security reviews, DPA negotiations, and AI governance frameworks. This guide explains what zero data retention actually means, how the major AI providers implement it, and how to build a defensible zero data retention framework inside a broader privacy program.

What is zero data retention? Zero data retention (ZDR) is a policy in which a software vendor does not persistently store a customer’s data; the platform only accesses data while actively processing it, rather than keeping copies in logs, caches, or databases afterward. Does zero data retention guarantee regulatory compliance? No. ZDR reduces a major source of compliance risk by limiting how much sensitive data sits at rest, but frameworks like HIPAA, GDPR, and PCI-DSS also require access controls, data minimization, subprocessor agreements, and breach notification procedures. ZDR is one component of compliance, not a substitute for it. What’s the difference between zero data retention and encryption? [...] Zero Data Retention (ZDR) in its strong form—a policy that not only excludes certain uses of data, but ensures that it’s not stored at all—cannot simply be retrofitted onto a platform; it must be a foundational design choice. Legacy platforms often accumulate data-at-rest by default, as they are engineered to automatically write session logs, persist caches for performance, and store audit trails for debugging. True ZDR systems are designed for data protection from the start. [...] Senior Data Scientist September 9, 2026 Share When dealing with highly sensitive data like patient or student records, savvy organizations look for software vendors offering zero data retention (ZDR) options. Strong ZDR policies provide a better security guarantee than other vendor agreements, like end-to-end encryption or the promise that they won’t train models on your data. Zero data retention means that the platform does not store your data persistently, thus ensuring that you’re not unknowingly creating copies of the data you’re trying to keep safe.

## So… What Is Zero Data Retention? Zero Data Retention (ZDR) means that your automation platform doesn’t store or persist sensitive data unless explicitly instructed. Instead, it accesses and uses data in real time - then lets it go. In other words: No data is saved to the platform No data is retained after use No data is copied between systems unless your workflow intentionally requires it This approach minimizes your attack surface, reduces compliance scope, and virtually eliminates the risk of data breaches within the automation layer. ## Why ZDR Matters Now Legacy platforms often pull data into a centralized system for processing, which inherently creates copies and expands your risk surface. That model is no longer viable for organizations that need to: [...] Josh Katinger , Senior Product Manager | June 3, 2025 | 4 Min Read If you work in a regulated industry like healthcare or finance, you already know: data is both your most valuable asset and your greatest liability. It’s the key to better decisions, faster workflows, and improved outcomes - but it’s also the source of risk, scrutiny, and sleepless nights. Enter: Zero Data Retention, or ZDR. It’s not just a compliance buzzword. It’s a fundamentally different way of thinking about how your systems interact with sensitive data - and it’s built into the core of Formstack Streamline. ## So… What Is Zero Data Retention?