Three activation levels
Per request
Pass
zdr: true in your body. The gateway checks the target model against the registry. Verified → proceed. Not verified → HTTP 422 with reason.Per account
In
/dashboard/settings → Zero Data Retention enable ZDR per provider group (Anthropic, OpenAI, Google, Others). When a group is on, all org requests to that group are checked.Per guardrail
Guardrails let you configure ZDR per user or per API key. Useful when different teams under the same org need different policies.
Example request
Verified endpoints
| Group | Models | Verified |
|---|---|---|
| Anthropic | claude-opus-4-8, claude-sonnet-4-6, claude-haiku-4-5 | 3 / 3 |
| OpenAI | gpt-5, gpt-4.1, gpt-4.1-mini, o4-mini, tts-1, tts-1-hd, gpt-4o-mini-tts | 7 / 7 |
| gemini-2.5-pro, gemini-2.5-flash | 2 / 2 | |
| Others (DeepSeek, xAI, Moonshot, fal) | — | 0 / 8 |
Rejection format
GDPR — art. 5(1)(e) data minimization
ZDR is part of your GDPR art. 5(1)(e) (storage limitation) compliance posture. If your provider doesn’t retain the conversation, retention at that layer is effectively zero — reducing the scope of your upstream processing obligations.ZDR covers the model provider’s retention. Geek Hub does store billing metadata (model id, tokens, cost, latency) for CFDI/Stripe. Message content is not persisted at the gateway layer.