Privacy Notice
Last updated 2 November 2026
Who is responsible
The controller for the data described here is Kano-Yufeng, operated by Yu-Feng Huang (黃毓峰). Contact: yufeng.kano@gmail.com.
What we store
To continue a conversation across turns, the proxy keeps some reasoning and tool-call items from replies in memory for up to an hour. They are never written to disk.
- Your Google profile: email address, name, profile picture address and Google account ID, refreshed each time you sign in.
- Your sign-in session: a cookie named kano-proxy_session that lasts 14 days, and its record on our server, deleted when you sign out or it expires.
- Which version of the usage notice and terms you accepted, and when.
- The provider accounts you connect: their access and refresh tokens or API keys, encrypted with AES-256-GCM; the identity the provider reports, such as the account's email address, display name and plan; the latest usage figures it returned; and, for your own endpoints, the address and a masked form of the key.
- Your API keys, kept only as a SHA-256 hash, with the name and the prefix shown on Access. The full key is shown once, when you create it.
- A record of each request: when it ran, the model, the key and account used, the status, token counts, estimated cost and latency. It never contains the prompt or the reply.
- Team data: the team name, its members, invitations by email address, shared accounts and the limits set for members.
- Billing state from Kano Pay: your plan, subscription status, billing period and checkout references. We never receive your card details or billing address.
- CLI devices: the name each device was given, which defaults to its hostname, and when it was last seen. A CLI sign-in request keeps a one-way hash of your IP address; it expires after 10 minutes and is deleted within a day.
- Our web server's access log: the IP address, time, requested address and response status of each request. It records no request or response headers and no sign-in codes, so it never holds API keys or cookies.
Why we use it
To sign you in, send your requests to the accounts you chose, apply your plan, team and key limits, show you your usage, take payments through Kano Pay, and keep the service secure and working. We do not sell data, show advertising, or run analytics or tracking scripts.
Who receives it
The service runs on a server the operator controls. We share data with no one else unless the law requires it.
- The AI providers you connect receive the requests you send to them, under their own privacy policies.
- Google, to sign you in.
- An app you approve on the connect page receives an API key for your account. It is listed on Access, where you can revoke it.
- Kano Pay, our checkout, receives an internal user ID and the plan you chose. Dodo Payments processes the payment as an independent controller under its own privacy policy.
- Your team: an owner sees members' email addresses, names and their usage of the accounts the owner shares; members see the owner's name or email address and the labels of the shared accounts.
How long we keep it
- Request records: 90 days.
- Request allowance records: 90 days, except the current Free month and your latest paid period.
- Payment notification records: one year.
- Subscription and checkout records: kept for billing records, disputes and legal obligations, also after the subscription ends.
- Web server access log: until the server software is next updated.
- Everything else: as long as your account exists. Removing a provider account, API key or CLI device deletes it at once.
Your rights and choices
You can remove provider accounts, API keys, CLI devices and your team yourself at any time. There is no self-service account deletion or export yet: email yufeng.kano@gmail.com to get a copy of your data, correct it, or delete your account, and we will reply within 30 days. Deleting your account removes your profile and the data above, except what we must keep for billing records.
Cookies and local storage
The sign-in cookie is the only cookie Kano Proxy sets. The app keeps cached data and view settings in your browser's local storage, and clears your cached data when you sign out. Your Google profile picture is loaded from Google.
Changes
Changes to this notice are posted on this page with a new date.