What Kin Router holds
Last updated October 14, 2026
This page lists what Kin Router stores, what only passes through it, and what it does not do. Kin Router is operated by Kin Computing, Inc.
What is stored
Your account
Your email, your name, and a one-way hash of your password. If you sign in with Google or GitHub, also the id they give your account. Sessions are stored as hashes.
Your connections
The service's address, the label and account name you typed, and its key or sign-in tokens.
For a Google connection, also the Google account's email address and Google's id for it, which Google provides at sign-in.
Keys and tokens are encrypted with AES-256-GCM. The encryption key is kept in Google Secret Manager, apart from the database. Each credential is sealed to its own connection.
Tool descriptions
The tool descriptions your connected services publish.
Your permissions
What you set to Allow, Ask me or Block.
Activity
For each attempt: which AI app, which connection and action, the outcome, the time, and how long it took.
Not the arguments. Not the results. Not what was searched for, only a one-way hash of the search text.
For each change, and each request that waits for your approval, also a one-way hash of its arguments, so the same request is recognized and does not run twice.
Approvals
When an action is set to Ask me, its arguments are kept encrypted so you can review them. They are deleted when you decline, or once the approved action has run. A request nobody answers can no longer be used after one hour, and a cleanup that runs every minute while Kin Router is running deletes it.
Large results
When a result is trimmed, the full result is kept encrypted so the AI app can read the rest. It can be read for ten minutes, then the same cleanup deletes it.
Approved results
Approving a request runs it immediately. Results from actions you approve are kept encrypted for up to one hour after the action ends, so the AI app can collect the result again if an answer is lost on the way. The same cleanup deletes expired copies. Backup copies age out under the retention described on this page. The activity record keeps its outcome, without its arguments or result.
Shared directory entries
A public custom server you connect by its address is listed in Explore only if you share it: Keep this private starts ticked, and you untick it when you add the server or later on its page. An AI app you connect can also share a server on purpose. A listed server appears first by its host name and later with its public tool descriptions. We do not name who added it or include account data. Nothing is listed from an account whose email address is not confirmed, and turning on Never list your connections in the directory, in settings, keeps all of yours out.
What passes through without being stored
The arguments and results of actions travel through our server on the way between your AI app and the service. The encrypted approval and result cases above are the exceptions.
Payments
Stripe handles cards. We store Stripe's customer and subscription ids, the price you chose, the subscription status, when the current period ends and, if a payment fails, when it started failing. We never see or store card numbers.
Where it is kept
In a Postgres database on Google Cloud in Iowa, United States. Google backs it up daily and keeps about a week of backups, in the United States.
Logs
Our server logs the method, path, status, timing and network address of each request. It leaves out anything after a "?" in the address, and sign-in headers and cookies.
Google Cloud also keeps its own record of each request, which has the full address, your browser's user agent and the page that linked to it. Addresses that carry a one-time sign-in or pairing code are kept out of that record. Google keeps both for 30 days.
Product analytics
PostHog receives page counts with the campaign tags of the link you arrived on, a few milestones such as signing up, and error reports with addresses, quoted text, email addresses and tokens removed. Your browser sends its part unless it sends Do Not Track or Global Privacy Control; for such a browser our server keeps only hourly counts of visits and sign-ups, with nothing that identifies anyone. Milestones our server records for an account, and errors on our server, are sent either way. None of this uses cookies. People and workspaces are known to PostHog by internal numbers only.
Session recordings, surveys and an id kept in your browser run only if you choose Allow. Recordings cover only public pages and setup steps that show no connected data, hide every word and keystroke, and never include data from Google or any other connected service. Our server refuses a recording from any other page. The privacy policy has the full list.
What we do not do
- We do not sell your data.
- We do not use it to train models.
- Kin Router itself does not run your Google user data through an AI model. The AI apps you connect receive the results of their actions, under their own terms and settings.
Deleting
Removing a connection deletes its credential and, where the service supports it, ends the sign-in on the service's side.
To remove a Google connection, open it in Kin Router and choose Remove. Its tokens are deleted at once. When no other Kin Router connection uses the same Google account, Kin Router also revokes its Google access. You can remove access yourself at https://myaccount.google.com/connections.
Deleting your account deletes it and everything in it from our database at once. Backups age out within about a week.
What other companies already hold stays with them: Stripe keeps its record of your payments, PostHog keeps the analytics already sent, which carry internal numbers only, and Intercom keeps any chat you had with us. Endorsely keeps its record of the partner who referred you. A public server you connected can stay listed in Explore by its host name, with nothing that links it to you.
Who runs it
One person. There is no security certification or outside audit yet.
What it cannot do
- It only governs actions that go through it.
- An AI app with its own separate connection to a service is not covered.
- It cannot stop an AI app from being misled by text it reads, such as instructions hidden in an email (prompt injection). It limits what a misled app can do: changes ask you first by default, you can block any action or make an AI app read-only, and every call is recorded.
- It tells reading from changing by how each service labels its actions, or by an action's name when the service gives no label. If a service labels a change as reading, that change gets your rule for reading. You can set any action's rule yourself.
Other companies involved
- The AI apps you connect, which receive the results of the actions they run.
- Google Cloud, for hosting.
- Stripe, for payments.
- Resend, for account email such as password reset links.
- Cloudflare, for DNS.
- PostHog, in the United States, for product analytics.
- Google and GitHub, if you sign in with one of them. We receive your email address, your name and the id of your account there.
- Intercom, for support chat when you open it. If you are signed in, Intercom also receives your email address and account id, so we know who is writing.
- Endorsely, to credit the partner who referred you, only if you arrived through a partner's link.
Report a security problem
If you find a security problem, write to privacy@kinlab.ai. We reply within 3 business days.
- Test only with an account of your own. Please do not test against other people's accounts or data.
- Tell us how to name you if you would like credit, and we will credit you once it is fixed.