Zero Data Retention (ZDR)

When ZDR is enabled, the gateway routes requests only through providers that have verified agreements to delete all request data immediately after processing.

Enable per-request

{
  "model": "anthropic/claude-sonnet-4-6",
  "messages": [{"role": "user", "content": "Analyze this sensitive data..."}],
  "providerOptions": {
    "gateway": {
      "zeroDataRetention": true
    }
  }
}

Enable team-wide

Set zdrEnabled: true on your team record. All requests from team members will enforce ZDR. Team-wide ZDR overrides per-request zeroDataRetention: false.

How it works

When ZDR is enabled:

1. Operators are skipped. Operators self-report their backing provider. The gateway cannot verify what provider an operator actually routes through, so operators are excluded from ZDR-compliant routing.

2. LiteLLM is skipped. LiteLLM has its own internal fallback chain that may route to non-ZDR providers. Since we can’t control LiteLLM’s routing decisions, it’s excluded.

3. Direct provider only. The gateway calls the provider API directly, selecting only from verified ZDR providers.

4. BYOK fallback preserves ZDR. If your BYOK credentials fail, the fallback to platform credentials still enforces ZDR filtering.

ZDR-verified providers

Compliance data is managed via the admin API (PUT /api/admin/compliance) and can be updated without code deploys.

Trust model

The Tangle chain verifies operator identity and stake, not behavior. When compliance matters, the gateway routes direct.

Error responses

If no ZDR-compliant provider is available for the requested model:

{
  "error": {
    "message": "No ZDR providers available for model: deepseek/deepseek-chat. Providers considered: anthropic, groq, mistral, ...",
    "type": "invalid_request_error",
    "code": "no_providers_available"
  }
}