Privacy policy · Kottos AI

Kottos AI, Inc. ("Kottos AI", "we") runs the website at kottos.ai, the gateway at api.kottos.ai, the account pages and MCP server at data.kottos.ai, and the account MCP server at account.kottos.ai. This policy covers all of them. Chat Brawlers has its own policy. If your company has signed an agreement with us, that agreement takes precedence where the two differ. Questions go to [email protected].

The short version

We do not store the text of your prompts or of the replies. The gateway passes them between your client and the providers your route names, and records metadata about each request: times, sizes, models, providers, token counts and costs.
We do not store your provider keys. Each request carries its key, the gateway forwards it to the provider, and the key is cleared from memory when the request ends.
We do not sell your data or share it with advertisers.

What we collect for your account

Data	Why
The email address you sign in with. Sign-in runs through Cloudflare Access, with a one-time code sent to that address or with a Google or GitHub account.	To identify your account and write to you about it.
Your account number and the date you created the account.	To keep your records together.
A SHA-256 hash of your Kottos AI token, never the token itself.	So the gateway can recognise your token. We show a token once and cannot show it again, and a token your agent makes on your computer never reaches us at all: only its hash does.
Your credit history: the starting credit, top-ups and the fees taken.	To work out your balance.
Your Stripe customer ID.	To link your top-ups to your account. Stripe collects your card details, not us.
Hourly usage summaries: requests, tokens, cost at provider list prices, fees, delivery outcomes, time-to-first-token histograms and the comparisons on your account page, plus your last 10 requests.	To show your usage, balance and comparisons.
The campaign tags (such as utm_source) and Google Ads click ID on the link that brought you to sign in, saved once when the account is created. For an account your agent creates, the name its client gives for itself (such as claude-code) instead.	To learn which links, ads and agents bring sign-ups.
What you write to us by email.	To answer you.

What we record for each request

The gateway writes one record per request to our request log, which we call the tape. A record holds:

when the request arrived, its size in bytes, and how long each stage took, including the provider's time to first token;
the model your request named and the model the provider says it served, the provider and region that served it, the service tier, and the provider's own request ID;
token counts, the cost at the provider's list price, and our fee;
errors, retries, failover and the details of the routing decision;
the run ID and step name your client sends to label requests, stored as sent;
on routes that keep a conversation with one provider, a hash of 16 hexadecimal digits computed from the start of the request, which tells the turns of one conversation apart. It is a hash, not the text.

Every field is described on the request record page, and your account page offers your own records as one file per day.

A record holds no prompt or reply text, no API key or token, and no IP address. The gateway's operational log notes the IP address of a connection only when it refuses a request that fails authentication or a permission check. Keep personal information out of run IDs and step names, since they are stored as sent.

On our website

Analytics. Pages on kottos.ai send PostHog the pages you view, your clicks and scrolling, time on page, a recording of the session with everything typed into fields masked, the referring site and campaign tags, your browser and device type, and an approximate location derived from your IP address. The data goes through kottos.ai/ingest to PostHog's US cloud. The script stores nothing on your device, neither cookies nor local storage, so every page load counts as a new anonymous visitor.
Where you came from. If you arrive on a link with campaign tags or a Google Ads click ID, a small script keeps them in your browser's local storage for 30 days and adds them to the sign-in links. They reach us only if you create an account.
Fonts. The website and the account pages load fonts from Google Fonts, so your browser contacts Google, which sees your IP address.
Comments. The Claude Code demo page embeds a public discussion thread hosted on GitHub through giscus. What you post there is public and handled under GitHub's terms.

The account pages run no analytics. Cloudflare Access sets cookies on data.kottos.ai that keep you signed in for up to 12 hours, and the account page keeps campaign tags in the tab's session storage until your account is created. We use no advertising cookies.

The public demo

Requests sent with the public demo key from the Claude Code demo go to one shared demo account. Their records appear on a public dashboard at data.kottos.ai/trial, pooled across everyone who uses the demo: the time, model, provider, size, timing and cost of each request. The run ID is withheld. Do not use the demo for work you would not want counted in public.

The MCP servers

The MCP server at data.kottos.ai/mcp lets AI agents read the list prices and probe timings this website publishes, and needs no account. Each day we count its requests by the name the client gives for itself (such as claude-code), whether it speaks the current version of the protocol or an earlier one, the method and tool it calls, and the model it matched in our price list, with how many failed. We store no IP address and nothing else a request sends. To enforce its rate limit, the server keeps a count per IP address in memory and clears it every minute.

The account MCP server at account.kottos.ai/mcp lets an agent you connect work on your own account. You sign in to it through Cloudflare Access with the same methods as the account page, and the agent keeps that sign-in for up to 14 days. It answers from your account's records (your balance, usage, recent requests and daily request files) and creates your account with its starting credit, and records your token's hash, when you ask it to. What it returns goes to your agent and, through it, to the AI provider your agent runs on, whose terms apply, as does the token's hash your agent sends it; neither ever includes your Kottos AI token or a provider key. Its requests are counted the same way, with the model a route matched in place of the price list's, and the counts name no account.

Who handles your data

The AI providers your routes name: Anthropic, OpenAI, Amazon Web Services (Amazon Bedrock), DeepInfra, Together AI, Fireworks AI and Baseten. The gateway sends them your requests, text included, under your own account with each provider and with the key your request carries. Their terms and privacy policies apply to what they receive. A route can send one request to more than one of its providers: it can race two of them, retry on another after a failure, or send the start of a long request to one provider and then move it to another. Amazon Bedrock routes marked global can be served from AWS regions outside the United States.
Hetzner hosts the gateway server in Ashburn, Virginia, which holds the request log and the operational logs. Requests to api.kottos.ai go straight to that server over TLS.
Cloudflare delivers the website, runs sign-in through Cloudflare Access, and hosts the account pages, their database and your daily request files, and runs both MCP servers. Cloudflare logs each sign-in with your email address, IP address and time.
Stripe processes payments.
Resend sends account emails, such as the welcome message and the notice when your token changes.
PostHog provides the website analytics.
Google and GitHub sign you in if you choose them. Google also serves the fonts and runs the ads that may bring you here.
Hostinger hosts the website's files.

How we use request records

To charge our fee, show your usage, build your daily files, answer support requests and investigate failures.
To route requests: the gateway watches how each provider is doing and routes around failures and slow providers.
Combined across all accounts, without names or email addresses, to measure providers' speed, errors and prices, to improve routing, and to produce the estimates on account pages. The time-to-first-token comparison on your account page, for example, pools recent requests from all accounts.
We may publish statistics built from many accounts' records, such as a provider's median time to first token. We do not publish one account's records, and published statistics do not name or single out any account or company.

Sharing

We do not sell your personal information and do not share it with advertisers. We share it with the services above to run Kottos AI, when the law requires it, or with a buyer or successor if Kottos AI is sold or merged, who must keep to this policy.

Where your data is kept

Our server is in Virginia, United States. Cloudflare, Stripe, Resend and PostHog are US companies, and PostHog stores our analytics in its US cloud. If you use Kottos AI from outside the United States, your data is transferred there.

How long we keep it

Data	How long
Account data, credit history, usage summaries and daily request files	While your account exists.
Your last requests on the account page	The newest 10.
Request records in the tape	We keep them as the evidence behind the fees we charge. They carry your account number, not your email address. We have not yet set a date after which they are deleted, and this page will say when we do.
Operational logs on the gateway server	Up to 90 days.
Payment and credit records	As long as tax and accounting law require. Stripe keeps its own records.
Website analytics	As long as our PostHog plan retains them.
MCP servers' request counts	No set limit. They name no person and no account.

If you ask us to delete your account, we delete your email address, token hash, usage summaries, recent requests, campaign tags and daily request files. We keep the payment and credit records the law and our accounting require, and request records stay in the tape under your account number.

Your choices and rights

Your account page shows your balance and usage and lets you download your request records. You can replace your token there at any time.
Write to [email protected] from the address on your account to get a copy of your data, correct it, or delete your account. We reply within 30 days.
Depending on where you live, for example in the European Union, the United Kingdom or California, you may have the right to access, correct, delete or export your personal information, and to object to or restrict how we use it. You can also complain to your local data protection authority. Using these rights will not change how we treat you.

For people in the European Union and the United Kingdom, we rely on our contract with you to run your account and your requests; on our legitimate interests to keep the service secure, measure providers, improve routing, run the website analytics and learn which links bring sign-ups; and on our legal obligations for payment records.

Security

Every connection uses TLS: your client to the gateway, the gateway to each provider, and your browser to our pages. Tokens are stored only as SHA-256 hashes. Provider keys are never stored or logged, and the gateway clears them from memory when a request ends. The gateway never reads the billing database, which sits outside the request path. Access to our systems is limited to the people who run Kottos AI. No system is perfectly secure: report a problem to [email protected].

Children

Kottos AI is for businesses and for people aged 18 and over. We do not knowingly collect data from anyone younger.

Changes

If we change this policy, we update the date above. We will tell account holders about a material change by email before it takes effect.

Contact

Kottos AI, Inc. · [email protected]