Privacy & Security
Explain the security boundary around API keys, request metadata, and provider handling.
Security first
Keep API keys in server-side environment variables or a protected credential store. Do not embed keys in browser code, mobile applications, public repositories, screenshots, or shared chat messages. Revoke and replace a key immediately if it may have been exposed.
Operational metadata
The console may show request ID, timestamp, model, status, latency, usage, charge, error type, and other information needed for security, troubleshooting, and billing. The fields available for an individual request can vary by protocol and model.
Provider boundary
Requests are routed to the provider serving the selected model. Data retention, moderation, regional processing, and feature behavior can differ by provider and model. Review the applicable provider terms and your own compliance requirements before sending confidential, personal, or regulated data.