Replicate Predictions API, not the web UI zero data retention: terms and exceptions
ZDR 2.0 (f) · B
Short answer
API prediction inputs, outputs, files, and logs are automatically removed after one hour by default. Web-interface predictions are kept indefinitely. Fine-tunes are a different store.
Scope and evidence
| Provider | Replicate |
|---|---|
| Service | Predictions API, not the web UI |
| Lane | API default |
| Origin |  US United States |
| License | open-weight |
| Hosting | Self-host |
| Score | ZDR 2.0 (f) · B Bounded retention. Content retained a defined window (<=90d) for abuse monitoring, possibly human-reviewed, then deleted |
| Evidence | Public documentation reviewed (B: published documentation) |
| Source-review date | 2026-08-25 |
Other lanes for Replicate
Structured breakdown
- Default posture
- API prediction inputs, outputs, files, and logs are automatically removed after one hour by default.
- Exceptions and carve-outs
- Web-interface predictions are kept indefinitely. Fine-tunes are a different store.
Approval and setup path
Approval and setup path not yet reviewed.
Flags on this record
- f
- stateful-feature carve-outs (files, batch, threads, caching, grounding)
Practical questions for your agreement
- Does your signed agreement cover this exact service, model set, and feature path?
- Which retention, logging, and human-review exceptions still apply after any ZDR election?
- What configuration evidence (flags, project settings, store defaults) confirms the posture you expect?
- Do your customer commitments match what the reviewed evidence supports?
Does your agreement cover this deployment?
We can review the relevant terms, feature choices, and customer commitments, then help your team identify what to clarify or negotiate.
Sources
Trust and security
- Privacy replicate.com
Posture ledger
seeded
ZDR 2.0 (f) · B
Seeded from published documentation.
Full key on the scale. Method notes on methodology. Notation is always ZDR 1.0 (s,f,r) · A.