Meta Meta Model API zero data retention: terms and exceptions
ZDR 3.0 · C
Short answer
No-training and encryption claims in launch material; no published retention schedule.
Scope and evidence
| Provider | Meta |
|---|---|
| Service | Meta Model API |
| Lane | API default |
| Origin |  US United States |
| License | open-weight |
| Hosting | Self-host |
| Score | ZDR 3.0 · C No-training. No training, but retention unbounded or unspecified |
| Evidence | Marketing or support claims (C: marketing or support-article claims) |
| Source-review date | 2026-08-24 (registry) |
Other lanes for Meta
Structured breakdown
- Default posture
- no-training and encryption claims in launch material; no published retention schedule
- Exceptions and carve-outs
- No carve-outs recorded on this assessment.
Approval and setup path
none found
Flags on this record
No exception flags on this record.
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
Posture ledger
seeded
ZDR 3.0 · C
Seeded from published documentation.
Full key on the scale. Method notes on methodology. Notation is always ZDR 1.0 (s,f,r) · A.