Zero Data Retention (ZDR): What It Means for AI APIs

Zero Data Retention (ZDR) is a provider-side policy under which eligible AI inference endpoints process prompts and return responses without persistently storing either afterward, though data still travels to and is processed by the provider. It differs from no-training policies, data residency, and self-hosting: a provider may avoid training on data while retaining it temporarily, regional routing controls processing location rather than storage, and self-hosting is needed when third-party processing itself is prohibited. On OpenRouter, ZDR can be enforced through account privacy settings, guardrails, or the per-request `provider.zdr` control, while `data_collection: "deny"` can additionally exclude endpoints that non-transiently store data or may train on it. ZDR does not cover request metadata retained by OpenRouter, application logs, external tools and plugins, legal or abuse-review retention, or response caching, which must be assessed separately; in-memory provider prompt caching is considered compatible because it is not persistent storage. Organizations should verify claims at the endpoint level, examine coverage for files, tools, identifiers, caches, and metadata, use enforceable routing controls rather than manual selection, and monitor current endpoint policies as they change.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.