DEVELOPER DOCUMENTATION

Privacy & call data

Control sensitive identifiers before your request reaches a provider.

Redact or block

Privacy processing is optional and runs locally in the gateway. Set mode: "redact" to substitute stable placeholders within one request, or mode: "reject" to block a request containing detected identifiers before credit reservation or provider dispatch.

{
  "model": "your-model-id",
  "messages": [
    {
      "role": "user",
      "content": "Contact alice@example.com about Project Cedar."
    }
  ],
  "max_tokens": 64,
  "privacy": {
    "mode": "redact",
    "terms": [
      "Project Cedar"
    ]
  }
}

Patterns cover email addresses, common formatted phone numbers, formatted US Social Security numbers, checksum-valid payment-card numbers and selected API-key formats. Custom terms are literal, case-insensitive matches: up to 100 terms of 2–200 characters. Messages, message names, the user field and stop strings are inspected. The privacy policy and custom terms are removed before forwarding.

The playground offers the same redact/block controls. Receipts contain only category counts; responses include X-GPU-Router-Redacted-Count. Rejection returns HTTP 400 with privacy_violation. Oversized prepared requests or excessive matches are rejected.

Pattern matching can miss names, addresses, context, unusual formats and other identifying information. It can also redact innocent text. Providers still receive the remaining prompt. This feature does not guarantee anonymity or zero retention; assess each serving provider’s policies before using sensitive data.

Call data and retention

Ordinary inference receipts store model, provider, tokens, cost, outcome, timing and redaction counts. The gateway does not persist ordinary prompt or response bodies in its usage ledger. Upstream failure logs omit response details. Activity exports only the loaded request metadata as JSONL; maintain any full prompt/output archive in your own application under your own retention policy.

Deferred requests require persisted content. Their prepared inputs and results are encrypted at rest with AES-256-GCM. Inputs are cleared when work finishes, expires or is cancelled. Results are downloadable for 24 hours after completion and removed by the worker afterward. Batch metadata is removed seven days after its deadline. Gateway operators control the encryption key; backups follow the operator’s separate retention policy. Provider retention is independent.