Zero data retention
Zero data retention is an arrangement in which a service does not keep covered customer content after it finishes the required processing. The exact meaning depends on the contract and technical scope: it may cover call audio and text while excluding account settings, billing records, or limited operational metadata.
How zero data retention works
During a live request, a service may need to hold information briefly in memory so it can produce a response. Under a zero-retention arrangement, the covered content is discarded after that processing rather than written to persistent storage for later use. The design may also disable features that depend on saved content, such as replay, transcript review, or historical analysis.
The word “zero” should not be interpreted without a data inventory. A useful commitment names the covered inputs and outputs, the point at which deletion occurs, and any exceptions. It should address temporary files, queues, error traces, backups, abuse monitoring, and support access. It should also distinguish customer content from service metadata.
Zero retention by one processor does not control the rest of the workflow. A carrier, connected business system, browser, or customer-operated server may create its own record. The customer may also deliberately save a result after receiving it. Each participant needs a separate review.
Why it matters for AI phone calls
An AI phone call can create audio, a transcript, a summary, tool inputs and outputs, and call metadata. A zero-retention requirement may apply to some of those categories but not others. Buyers should ask whether it applies during live processing, after the call, and across every service involved in the call path.
The main benefit is data minimization: content that is not retained cannot later be exposed from that service’s storage. The tradeoff is reduced access to historical material for quality review, dispute handling, debugging, and analytics. Organizations should decide which records are genuinely necessary rather than assuming that maximum retention or no retention is always correct.
Zero data retention is not a complete compliance program. Consent, caller notices, access controls, geographic requirements, and downstream data handling still matter. The enforceable contract and system behavior are more important than the label alone.