xAI ZDR toggled zero data retention: terms and exceptions
ZDR 0.5 (r) · B
Short answer
Default 30d encrypted storage; ZDR self-serve, confirmed via x-zero-data-retention header. Disables stateful features wholesale; audit event logs continue.
Scope and evidence
| Provider | xAI |
|---|---|
| Service | ZDR toggled |
| Lane | ZDR |
| Origin |  US United States |
| License | proprietary |
| Hosting | Provider-hosted |
| Score | ZDR 0.5 (r) · B Architectural ZDR. Nothing durably written by provider; stateful features blocked/rejected; still third-party plaintext processing |
| Evidence | Public documentation reviewed (B: published documentation) |
| Source-review date | 2026-08-24 (registry) |
Other lanes for xAI
Structured breakdown
- Default posture
- default 30d encrypted storage; ZDR self-serve, confirmed via x-zero-data-retention header
- Exceptions and carve-outs
- disables stateful features wholesale; audit event logs continue
Approval and setup path
Approval and setup path not yet reviewed.
Flags on this record
- r
- revocable: provider reserves unilateral downgrade
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.x.ai
- Security x.ai
Posture ledger
seeded
ZDR 0.5 (r) · B
Seeded from published documentation.
Full key on the scale. Method notes on methodology. Notation is always ZDR 1.0 (s,f,r) · A.