Groq first-party API, default zero data retention: terms and exceptions
ZDR 2.0 · B
Short answer
Possible <=30d reliability and abuse logs unless the ZDR toggle is on. US-region storage for anything retained.
Scope and evidence
| Provider | Groq |
|---|---|
| Service | first-party API, default |
| Lane | API default |
| Origin |  US United States |
| License | open-weight |
| Hosting | Self-host |
| Score | ZDR 2.0 · 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 Groq
Structured breakdown
- Default posture
- possible <=30d reliability and abuse logs unless the ZDR toggle is on.
- Exceptions and carve-outs
- US-region storage for anything retained
Approval and setup path
self-serve console toggle, all customers
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
Trust and security
- Trust Center trust.groq.com
- Security groq.com
Posture ledger
seeded
ZDR 2.0 · B
Seeded from published documentation.
Full key on the scale. Method notes on methodology. Notation is always ZDR 1.0 (s,f,r) · A.