Legal · Privacy

Privacy Policy

How KiteRouter handles account information, support requests, payment records, and the security controls around your API gateway workspace.

Privacy posture

We are not interested in your request bodies.

KiteRouter is a routing and billing gateway, not a data-harvesting layer. We keep status, token, cost, latency, key, model, and routing metadata needed to operate the service. Prompt and message bodies pass through to the selected upstream provider (for example: OpenAI, Anthropic, Google, Mistral, Meta, DeepSeek).

No prompt-body logging

We do not store prompts, messages, or request body content in request logs. That reduces database load and reduces sensitive data surface area.

Check upstream provider policies

Your main data-use concern should be the upstream model provider you choose, such as OpenAI, Anthropic, Google, Mistral, Meta, DeepSeek, or other model vendors. Providers have their own retention, abuse-monitoring, and AI-training policies, so review them before sending sensitive traffic.

Storing bodies costs us too

Keeping customer prompt data would mean more database storage, security work, retention tooling, and compliance burden. We do not have a product reason, budget, or appetite to do that.

Questions about privacy?

Contact support or review the service terms for platform rules.

View terms