Beta terms, privacy, and data posture

Paid beta access requires acceptance of the Keiro beta terms and privacy notice through the invite workflow. If you have not received and accepted these documents, contact support before you send paid traffic.

On this page 1 of 5

Data use#

Keiro processes prompts, responses, tool inputs, metadata, and usage records to provide the API, route requests, debug failures, enforce plans and limits, and support billing and abuse prevention.

Do not send regulated, highly sensitive, or contract-restricted data unless your beta agreement explicitly allows that use.

Providers and subprocessors#

Keiro may route requests to upstream model providers or infrastructure vendors needed to provide the API. The beta terms or support channel must identify the active subprocessors for each organization before paid use.

See Subprocessors and data routing for the current public beta posture and DPA process.

Provider data-use terms can vary by provider and by account mode. During paid beta, ask Keiro support to confirm whether your requests use Keiro-managed provider capacity or a customer-approved provider arrangement before you enable sensitive workloads.

Data retention#

Keiro may retain API request metadata, usage records, billing records, abuse and security logs, and operational traces for reliability, billing, security, and support. See Data retention and erasure for the current paid beta retention posture. Deletion and retention periods are those in your accepted beta terms.

Beta users may request an export or deletion review through the support channel. Export and deletion are subject to security, abuse-prevention, accounting, dispute, and legal retention requirements. Keiro exports only supported customer-facing records and excludes credentials, sensitive operational details, and non-public account data.

Support and escalation#

Use the beta support channel for key issues, billing questions, security concerns, and data-handling questions. Include timestamps, endpoint paths, model IDs, HTTP status, whether the request streamed, and request IDs when available.

See Beta SLA and support posture for availability, maintenance, incident-update, and support expectations during the beta.

Do not send API keys, external service credentials, private datasets, or full logs that may contain secrets in support tickets.

During an incident, Keiro posts customer status updates on status.keirolabs.ai and may also contact you through your support channel.

Search Keiro docs

Start typing to search pages and sections.

Start typing to search pages and sections.

Documentation

Console