Privacy Policy

Last updated October 16, 2026

This policy explains what Klinn collects when you use this website, the console at app.klinn.dev and the API at api.klinn.dev, why we collect it, and who else sees it. Klinn resells access to third-party AI models; the Terms of Service explain how.

The short version. We do not save your prompts or completions, apart from answers a gateway's response cache keeps in memory when you turn it on. To answer them, we send them to third-party AI providers, which handle them under their own policies. Klinn is not private inference, so do not send personal or confidential data. We keep account, billing and usage records and product analytics, and we do not sell personal data.

Changed on October 16, 2026: the console's Settings can take a contact email, verified with a code we mail to it, and we send one welcome message on your first sign-in with an email address (see What we collect, Messages). The console has a Feedback form; what you send through it is stored with your account and emailed to us, and our product analytics record that feedback was sent (see What we collect). The account milestones in our product analytics also include a card top-up left unpaid, and on the landing page our product analytics record a search in the price table (the text typed), the model row you open, and which version of the landing page you saw (see What we collect). Changed on October 15, 2026: we keep a record of each request, without its content, for 30 days, and daily totals per tag for 90 days (see What we collect). Our servers record a few account milestones in our product analytics, such as a new API key or your first API call (see What we collect), and some decision models pass a request to their maker's own service (see Prompts and completions), and a gateway's response cache, when you turn it on, keeps answers in memory for up to 24 hours (see Prompts and completions). Changed on October 14, 2026: the provider that serves a request may pass it on to another provider that runs the model (see Prompts and completions).

What we collect

Account. Your email address, or the Google profile or wallet address you sign in with, and your name if you give it. Sign-in runs through Privy. A contact email you add in Settings, once you have entered the code we mail to it.
Keys and access. Your API keys (we store a hash, not the key itself), agent sessions, wallets you add, and a log of Management API actions: who made them, which endpoint, when, and the result.
Usage. For each request: the time, key, client (if you bill one), model, token counts, our price, how long it took, whether it succeeded and its error code, and the tags, metadata and end-user id you choose to send. We also keep hourly totals per key and daily totals per tag. Not the content. Do not put personal data in tags, metadata or end-user ids.
Billing. Balance changes and top-ups. Stripe handles card details; we never see your full card number. For USDC payments, the paying wallet address, the amount and the transaction reference.
Reseller data. Customers you create (the names and references you give them), their keys, limits, balances and usage, your custom domains and their DNS checks.
Technical data. IP address, browser and device details, and the request logs that our hosting and security systems keep.
Analytics. Pages viewed and clicks on the website and console, through PostHog (EU). On the landing page that includes the text you search in the price table, the model row you open, and which version of the landing page you saw. Our servers also record a few account milestones there: account created, API key created, top-up started, completed or left unpaid, the model of your first API call, and feedback sent from the console (whether you asked for a reply and the page it came from, not the message). These carry no amounts, prices or balances, and nothing you send to a model. When you are signed in, these events are linked to your account id, email and name; milestones from an agent wallet account are linked to that account. Session recording is off.
Messages. What you send us by email, and what you send through the console's Feedback form: your message, the page you were on, the build and your browser family, stored with your account and emailed to us, with your email address when you ask for a reply. What we send you: a verification code when you add a contact email in Settings (kept as a hash for 15 minutes), and one welcome message on your first sign-in with an email address, to your contact email once verified and to your sign-in email until then.

Prompts and completions

We pass the content of each request to the provider that serves it, and stream the answer back to you. We do not save prompts or completions in our database or our logs.

If you turn on a gateway's response cache, our router keeps that gateway's answers in memory, for the time you set (at most 24 hours), to answer the same request again. They are never shared with another account, and a restart of the router empties them.

The provider receives that content and handles it under its own terms. Some providers pass the request on to another provider that runs the model, under that provider's terms too. Providers may log it, keep it, review it for abuse, or use it to improve their services. Some run models on shared or community-operated GPU networks, where independent operators may process the request. Klinn does not offer private inference, zero data retention or a choice of region.

Some decision models send the text and questions through their maker's own service: Jev through TypeSafe, GPT-6 Luna Decisions through OpenAI, Microsoft-Decision-1 through Microsoft Azure, and Kev through Phala and SiliconFlow.

How we use it

To run the service: sign you in, route and answer requests, meter usage, charge your balance and take payments.
To show you your usage, spend and earnings.
To prevent fraud and abuse, and to keep the service secure.
To fix errors and improve the product.
To keep the records that tax and accounting rules require, and to meet other legal duties.
To contact you about your account.

AI model providers receive the content of your requests and the technical details needed to serve them.
Privy runs sign-in and wallet authentication.
Stripe processes card payments, fraud checks and tax, and acts as merchant of record for some purchases.
Coinbase Developer Platform verifies and settles USDC payments on the Base network.
PostHog stores product analytics in its EU cloud.
Hosting providers run the website, the console, the database and the API servers.
Resellers. If you use Klinn through a reseller's brand, that reseller sees your usage and is responsible for its own privacy notice.
Authorities and buyers. When the law requires it, to protect people or our rights, or as part of a sale of the business.

Each of them handles data under its own terms. We do not sell personal data, and we do not use your prompts to train models.

Public blockchain data

USDC payments and wallet sign-ins use the Base network. Wallet addresses and transactions on it are public and permanent. Nobody, including us, can delete them.

Cookies and browser storage

We use cookies and browser storage to keep you signed in, to remember settings, and for analytics. Blocking analytics cookies does not break the service. Blocking sign-in storage does.

Where data is processed

Our service providers and model providers work from several countries, including the United States. Your data may be processed outside your country, including in countries whose data protection laws differ from yours.

How long we keep it

Per-request records: 30 days, then deleted.
Daily totals per tag: 90 days, then deleted.
Account, key and hourly usage records: while your account is open, then as long as we need them for accounting, tax, disputes and security.
Billing records: as long as the law requires.
Analytics events: for the retention period set in PostHog.
Server and security logs: for a short period.
Blockchain transactions: permanently, outside our control.

Security

Connections are encrypted, API keys are stored as hashes, and access to our systems is restricted. No system is fully secure, so keep your keys secret and revoke any key you think has leaked.

Your choices

You can see and edit most of your account data in the console, revoke keys and remove wallets. To get a copy of your account data, correct it, or close your account and delete it, write to hello@klinn.dev. We may keep records that the law requires us to keep, such as billing records.

Sensitive data and children

Klinn is not built for sensitive or regulated data, such as health records, financial account data, or other people's personal data. We do not offer a data processing agreement or compliance certifications.

Klinn is not for anyone under 18, and we do not knowingly collect data about children.

Changes to this policy

We update this policy when what we collect, or who we share it with, changes. The date at the top shows the current version. If a change is significant, we will say so here before it applies.

Contact

Questions about privacy: hello@klinn.dev.