Zero Data Retention
Zero Data Retention (ZDR) is an optional arrangement for approved workspaces using direct inference. It is not a request parameter or a feature enabled automatically by creating an API key or subscribing to a plan.
Request and activate ZDR
Scale customers can request ZDR; customers on other plans may also ask, subject to approval. Modaic reviews the request, provides a separate ZDR agreement for signature, and confirms the approved workspace, route, base models, supported content types, and effective date in writing after technical activation. Each additional workspace needs its own approval and activation. Until you receive confirmation, standard retention terms apply.
Read the Privacy Policy and the optional ZDR Addendum for the terms governing your agreement.
Covered requests
After activation, ZDR covers confirmed direct calls to
POST /v1/systemone from the
approved workspace: use an enabled base model such as mo-fast and send your
questions inline. Coverage applies only to the models and content types in your
activation confirmation, and only to content submitted on or after its effective
date. For covered calls, request inputs and outputs, including supported images
and files, are not retained or backed up. Usage metering may still retain token
counts; account and billing information are outside the covered content.
A saved workspace/model call is not covered even when it uses the same
endpoint and an approved workspace. Saved-model inference, captured examples,
model training and alignment, and batch decisions use standard retention.
Setting capture: false on a saved-model call skips example capture; it does
not turn that call into ZDR inference.
Retries
For covered ZDR direct inference, an Idempotency-Key header is accepted but
ignored: responses are not saved for replay, and each call is a new operation.
A retry can run inference and incur usage again, so do not rely on that header
for deduplication. Outside covered ZDR direct inference, the usual
idempotency behavior still applies; batch
decisions and alignments continue to require keys.