Legal

Privacy

Last updated 9 October 2026.

Draft for review.

Who we are

Kontinent AI runs this website and the API at api.kontinentai.com. On this page, "we" means Kontinent AI and "you" means a person who uses the website or the API.

Your prompts go to third-party AI suppliers

To answer a request, we send it to third-party AI suppliers and model providers. They process your prompts and the replies to produce the answer. They can process them in other countries, including countries other than yours.

We send a Messages or Responses request as your tool sends it. If your tool puts an identifier in the request, the supplier receives it too. On chat completions we remove the user, metadata and safety_identifier fields before we send the request.

We do not use your prompts or replies to train models. The suppliers and model providers have their own terms, and we do not control what they do with the data.

What we do not store

We do not write the text of your prompts or of the replies to our database. There is no column for it.

There is one exception. If you send a request that does not stream and that has an Idempotency-Key header, we keep the response for 24 hours. A retry with the same key then gets the same answer and no second charge. After 24 hours we delete it.

Our server logs record errors. An error message from a supplier can sometimes quote part of a request.

We do not store card numbers, mobile money PINs or bank details. You type those on our payment provider's page, not on ours. For each top-up we keep the amount, the currency, the provider's reference and whether the payment succeeded.

What we collect

Your account: your email address. If you sign in with Google, we also keep the name and the profile picture that Google sends. A session lasts 30 days.

Your API keys: we keep a hash of each key, its first characters, its name, when it was last used and how many times. We show a key once, when you make it. We cannot show it again.

Each request we bill: the request id, the time, the model you asked for and the model that answered. We also keep the API format, the supplier route that answered and the number of routes we tried. We record the token counts: input, output, cached input and cache writes. We record what you paid, the official price of the same tokens, what the supplier charged us and how long the request took. We note whether the request streamed, used tools or asked for structured output, and the output limit you set. We keep a daily total for each account and model.

Each request we refuse or that fails: the time, the model you asked for, the status we returned, our error code and the part of the API it reached.

Your balance: each change to your balance, with its type and a short description, and the redemption codes you use.

Where you came from. We record it once, when you make an account: the site that sent you (the domain only), any campaign tag in the link and the first page you opened. We also record the country and city of that request, and whether you used a phone or a computer.

Emails: a record of each email we send you, with its kind and whether the send succeeded. We also note which product emails you received, so that we do not send one twice.

Signups: to stop mass signups, we count signups from each IP address. Each count expires within two days.

If you choose a display currency in the dashboard, we keep that choice on your account.

Counts we keep about the service

For each request we write a count to Cloudflare's analytics store. It holds the model, the result, the token counts and the cost. It also holds the country of the request and a guess at the language of the prompt. These counts carry no account id. We use them to see how the service runs and which models and languages people use.

We also count a few account steps: a signup, a first key, a first request, a spent starter balance and a top-up. These counts carry your account id, so that we can see how many people reach each step.

When you first visit the site, we add one to a count for that day. The count is kept by the campaign tags in the link you followed (utm_source, utm_medium, utm_campaign and utm_content), the first page you opened, and whether you use a phone or a computer. It holds no address, no account id and no browser details, so it cannot point to you.

Who else processes your data

Third-party AI suppliers and model providers receive your requests, as described above.

Cloudflare hosts the website and the API. It stores the database, the caches and the analytics counts, sends our emails and runs the bot check on the sign-in and contact forms.

Google receives your sign-in, only if you choose to sign in with Google.

Sentry receives reports of server errors: the request id, the path and the error. We remove authorisation headers and cookies from each report before it leaves.

Slack, our team chat, receives a note for each new signup with the email address, city and country. It also receives the messages you send through the contact form.

Bachs (bachs.io) processes top-ups. When you top up, Bachs receives your email address, your name if your account has one, the amount, and the payment details you type on its page. It tells us whether the payment succeeded.

We do not sell your data, and we share it with no one outside this list.

Cookies

__Host-session holds a random token for your sign-in. Scripts on the page cannot read it, only kontinentai.com receives it, and it expires after 30 days.

ds_attr holds where you first came from. We read it once, if you make an account. It expires after 90 days.

Our pages load the X (Twitter) ads pixel. It tells X that someone who saw our ad visited the site, made an account, created an API key or topped up (with the amount), so we can see which ads work. X may set its own cookies for this, under X's privacy policy. We send X no email, name or prompt.

We load no other analytics script. The bot check on the sign-in and contact forms loads a script from Cloudflare.

How long we keep data

Records of refused and failed requests: 90 days, then we delete them.

Records of the emails we send: 90 days, then we delete them.

Stored responses for an Idempotency-Key: 24 hours.

Expired sessions and sign-in links: we delete them each day.

Your account, your keys, your balance history and your request records: we keep them while your account exists, because they explain your balance.

Your choices

You can ask for a copy of the data we hold about you, ask us to correct it or ask us to delete your account. Write to team@kontinentai.com and a person will answer.

You can revoke an API key in the dashboard at any time. A revoked key stops at once.

Our reminder emails, about your balance and your use, have a link that stops them.

Send questions about this page to team@kontinentai.com.