Effective 2026-09-01
Privacy notice
This notice summarizes the information OTRouter uses to provide model access, request visibility, usage records and billing.
- Team data
- OTRouter uses Team details and memberships to organize Router resources.
- Machine credentials
- OTRouter API keys authenticate server-to-server calls. Account owners can revoke keys to stop new calls.
- Model content
- OTRouter does not store prompt or model-output bodies. Language APIs are stateless, so clients resend the complete conversation history for each multi-turn request.
- Operational metadata
- OTRouter stores the Team, API key identity, model, status, timestamps, token usage, published rate and final USD charge. Internal routing records may also contain provider, endpoint, upstream model, egress protocol, upstream status, cost, error, upstream request ID and lifecycle timestamps for settlement, reliability and incident diagnosis. Authenticated Team request details expose only protocol, outcome, upstream HTTP status, error and lifecycle timing from those routing records.
- Model processing
- Model content may be sent to an upstream model service to fulfill a request. Public APIs, the public catalog and request logs do not expose internal credentials, request or response bodies, provider raw payloads, internal routing identity, upstream request IDs or routing cost.
- Payment processing
- Stripe collects payment details on its hosted Checkout page. OTRouter stores payment identifiers, amount, currency, status and related balance changes for fulfillment and reconciliation, but does not receive or store full card details.
- Retention
- Revoking an API key or closing an account preserves request, usage, diagnostic and billing history for account access and reconciliation.