Zero-Data-Retention by Default: Architectural Privacy and Encrypted Auditability
How Zopyr protects proprietary source code and customer data through metadata-only request logging, AES-256-GCM envelope encryption, and data_collection="deny" routing.
1. Metadata-Only Request Logs by Default
When an engineering team routes production traffic through an AI gateway, prompt payloads often contain proprietary source code, financial records, or personally identifiable information. By default, Zopyr never stores prompt messages or model completions on disk.
Default request logs record only operational telemetry: generation ID, timestamp, model slug, token counts, latency (TTFT and total), HTTP status, and nano-USD cost. Prompt and response capture is strictly opt-in per API key, and when enabled for debugging, payloads are sealed using AES-256-GCM envelope encryption.
2. Fine-Grained API Key Guardrails
Every Zopyr API key can be restricted by allowed model slugs, CIDR IP allowlists, per-minute request and token rate limits (RPM/TPM), expiration timestamps, and hard USD credit ceilings—ensuring that a compromised staging key can never drain production funds.