Privacy information.
How this router deployment handles account details, request records, and inquiry submissions.
Account and access data
Account records include your email, display name, role, and account status. Sessions and API keys are stored as hashes. A newly created API key is shown once; ordinary account views expose its prefix and metadata.
If an enabled identity provider is used to sign in, it participates in authentication under its own terms. Only configured login methods are available on the sign-in page.
Inference requests
Request content is sent to the eligible providers needed to serve it. The metering database stores request identifiers, model and protocol, token counts, settled charges, status, timing, and sanitized error codes. Its request and attempt tables do not store prompt or response bodies.
Provider-side processing and caching can have their own retention rules. Responses requests must use store: false; that setting does not establish a universal provider zero-retention guarantee. Verified ZDR routing is not currently available.
Saved experiments and optional caching
Experiment prompts, variants, allocation settings and feedback you explicitly save are stored with your account. Exact response caching is disabled by default. If enabled, eligible response text is stored for reuse within the account; prompt text is not stored in that cache. Cache entries stop being served after 15 minutes. Expired entries are removed during subsequent cache writes, and disabling the technique clears stored responses. Explicit experiment settings override the account default, so an experiment with caching enabled can create new entries until it is paused or that setting is changed. Each account is limited to 100 entries of at most 256 KiB each.
Prompt Studio
Starting an optimization explicitly saves the task description, baseline, candidate state and optimized prompt content with your account for up to 30 days. It sends model requests billed to your selected key within the run’s cost cap. Internal scores are model-generated signals and do not establish real-world effectiveness. Deleting a run clears its content, not billing records. Account zero data retention blocks new runs, cancels active runs and clears saved Studio server content; a model request already sent may still settle. Legacy browser-only drafts are not imported into server history and can be removed using the browser’s site data controls.
Inquiries and abuse prevention
Enterprise, capacity, and privacy inquiries store the fields you submit so the operator can review them. These forms do not send an email automatically. A short-lived digest of a network address or email may be used to limit repeated submissions; expired rate-limit records are removed during subsequent submissions.
Browser storage
Session cookies keep you signed in. The selected theme is saved locally in your browser. An API key entered into the documentation request builder remains in that page’s memory and is not saved to local storage by the builder.
Retention and requests
An automatic deletion schedule for account, billing, and inquiry records has not been configured. Contact the operator before submitting data that requires a specific retention period. Use the form below to request access, correction, or deletion; identity may need to be verified before account data can be changed.
Do not include passwords, API keys, or sensitive prompt content.