Security
On every plan, because charging for a security posture is charging twice for the same product.
Everything on this page is on every plan. Charging for a security posture is charging twice for the same product, so we do not.
In transit and at rest
TLS 1.3 to the gateway, mutual TLS between the gateway and every replica. Prompts and completions are never written to disk on the inference path. Nothing you send is retained after the response is delivered unless you explicitly enable request logging on the project, which is off by default and scoped to seven days when on.
Training
We do not train on your data. We do not have a research team that could. There is no opt-out toggle here because there is no opt-in.
Residency
Region pinning with residency: strict means a request that cannot be served inside the regions you listed fails rather than routes elsewhere. The region that actually served the request is returned in a response header on every call, so the guarantee is verifiable from the client rather than taken on trust.
Access
SSO through any SAML or OIDC provider, SCIM for provisioning, and an audit log of every key issued, rotated and revoked — exportable, and streamed to your own sink if you would rather not read ours. Keys are scoped to a project and to a region set.
Incidents
Anything that breaches the availability target gets a public postmortem, including the ones that were entirely our fault and especially those. The incident feed is RSS, so you do not have to visit a page to find out.