A8gent
GlossaryBusiness and buying

What is zero data retention?

Also called: ZDR, no data retention, no training on your data

Zero data retention is a provider commitment not to store your API inputs and outputs after processing them, which is distinct from - and stronger than - a promise not to train on your data.

Written by A8gent
Contents
  1. At a glance
  2. What zero data retention means
  3. Why it matters and to whom
  4. The trade-offs
  5. How to verify it
  6. What you should know
  7. FAQ
  8. Related terms

At a glance

Category
Business and buying
Three distinct promises
No training, limited retention, zero retention - in increasing strength
Default at most providers
No training on business API data; retention for a bounded period
Usually requires
An application or approval, rather than being enabled by default
Trade-off
Features depending on server-side state may be limited or unavailable
Does not cover
Your own platform, tracing tool and CRM, which is usually the larger job

What zero data retention means

Zero data retention is a contractual commitment that a provider does not persist your API inputs and outputs after generating a response. The request is processed and nothing is written to storage. It is the strongest of a family of related promises and the one most often conflated with the weaker ones.

Three distinct commitments, in increasing strength. No training: your data is not used to improve the provider's models - now the default for business API tiers at most major providers, though not always for consumer products. Limited retention: data is stored for a bounded period, commonly for abuse and safety monitoring, then deleted. Zero retention: nothing is stored at all.

A provider saying "we do not train on your data" is making the first promise. That is meaningful, and it is not the same as saying nothing is kept.

Why it matters and to whom

For most small businesses, no-training plus bounded retention is proportionate. Zero retention becomes the requirement when a client contract demands it, when the data is genuinely sensitive - health, legal, financial, or a client's own customer data you hold under contract - or when a procurement process specifies it as a condition.

Where it applies, it needs to be in the contract rather than inferred from a marketing page, and it typically has to be requested or enabled rather than being on by default. Providers usually document an application or approval process, and eligibility can depend on your account tier and the specific endpoints you use.

The trade-offs

Zero retention removes capabilities you may be relying on. Providers often cannot offer the same abuse investigation, and features that depend on server-side state - stored conversation history, file stores, some assistant-style APIs - may be unavailable or limited, because they work by retaining data. Read the exclusions carefully rather than assuming the whole product is available under the same terms.

It also does not cover your own systems. If your automation platform stores the conversation, your tracing tool keeps full prompts, and your CRM has a copy of the transcript, then the model provider retaining nothing is only one link in a chain you also control. Auditing your own retention is usually the larger job.

How to verify it

Four steps. Read the provider's current data-usage documentation and trust portal rather than a summary. Get the commitment reflected in your DPA or an addendum, not just an FAQ. Confirm which endpoints and features it covers, since coverage is rarely uniform. And record the date you checked, because these terms change - what was true last year is not automatically true now.

For genuinely strict requirements, the strongest answer remains running open-weight models on infrastructure you control, where retention is a question about your own systems rather than someone else's promise - see self-hosting and data residency.

What you should know

Do not overclaim to your own clients. Saying "nothing is stored" when your provider offers no-training with thirty-day retention, and your own logs keep transcripts for a year, is a statement you cannot support. Describe the actual position: who stores what, where, and for how long. That description is also exactly what a client's security questionnaire asks for, so writing it once serves both purposes.

Zero data retention FAQ

What is zero data retention?

A contractual commitment that a provider does not persist your API inputs and outputs after processing them. It is stronger than a promise not to train on your data, which is now the default at most business API tiers but says nothing about storage.

Is 'we do not train on your data' the same as zero retention?

No, and conflating them is the most common misunderstanding here. No-training means your data is not used to improve their models. Zero retention means nothing is stored at all. A provider can honestly promise the first while retaining inputs for a period.

Do I need zero data retention?

For most small businesses, no-training plus bounded retention is proportionate. Zero retention becomes necessary when a client contract requires it, when the data is genuinely sensitive, or when a procurement process specifies it as a condition of doing business.

What do I give up with zero retention?

Features that depend on the provider storing state - conversation history, file stores, some assistant-style APIs - may be limited or unavailable, and abuse investigation support may be reduced. Read the exclusions rather than assuming the full product is available on the same terms.

How do I verify a retention commitment?

Read the provider's current data-usage documentation and trust portal, get the commitment into your DPA rather than relying on an FAQ, confirm which endpoints and features it covers, and record the date you checked - because these terms change.

Does zero retention at my model provider mean nothing is stored anywhere?

No. Your automation platform may store run data, your tracing tool almost certainly stores full prompts, and your CRM may hold the transcript. Auditing your own retention is usually the bigger job, and it is what a client's questionnaire will actually ask about.

Primary source

OpenAI - how your data is used and retained

Checked August 2026. Anything priced or rate-limited moves, so verify against the source before you budget.

Want this built rather than explained?

Knowing what zero data retention means is one thing; having it running in your business is another. We scope one workflow at a time, quote a fixed price in writing after a free consult, build it, and hand it over with documentation you own.