Security and privacy

InOneAPI uses zero content logging as its standard operating mode. Prompt and completion content is processed and counted in memory, without persistence in request logs. This is not a per-project opt-in setting.

Request metadata

Authentication, billing, routing and diagnostics retain necessary metadata: key/project identifiers, model, provider, status, timing, token counts, cost, retries and X-Gateway-Trace-ID. Metadata is distinct from prompt and completion content.

Files and conversation history

Uploaded files are stored for their documented lifecycle so subsequent requests can reference them. Saved Playground conversations and attachments are separate product data, not gateway content logs. Review the Files guide before uploading sensitive data. Deleting a file does not recall content already sent upstream.

Providers and applications

Inference providers still receive the request and apply their own retention and regional policies. Your application's logs, Agent history and monitoring services may also retain content. Review those policies separately.

Keep keys on the server, use separate keys and budgets per application, and revoke exposed credentials promptly. Never put secrets in browser bundles, public environment variables or request logs. Use trace metadata first when troubleshooting.