Kinoko privacy

This page says what Kinoko stores, where, and why. It is written to be read, and it is short because the system is.

Accounts

Sign-in and organizations are handled by Clerk. Kinoko receives your email address, your name if you set one, and the organizations you belong to, and uses them to decide which environments you can reach. Kinoko does not store your password. API keys are stored as hashes; the key itself is shown once at creation and cannot be recovered afterwards.

Your environments

The code, models, stored rows and uploaded blobs in an environment belong to your organization and live on Cloudflare: code and rows in Durable Object SQLite, blobs in R2, both scoped to the environment and unreachable from any other. The decision log an agent writes (decide) is stored with the environment. Deleting an environment deletes its storage. Kinoko staff do not read environment contents except to investigate a problem you report.

AI calls

When an app calls Cmd.ai.generate, the prompt is sent through Cloudflare AI Gateway to the model provider you named. Kinoko does not train on your prompts or your code.

Deployed apps and cookies

The console uses Clerk's session cookie. A deployed app at <org>.apps.kinoko.sh sets one signed, anonymous viewer cookie so that a visitor's session survives a reload; it identifies a browser, not a person, and it is not shared across organizations.

Operational data

Request logs (path, status, timing) are kept for a short period for debugging and abuse prevention. Kinoko does not run third-party advertising trackers.

Your rights

Ask for a copy of your data or for deletion at marce@dziban.net and we will act within 30 days. This page changes when the system does; the date at the bottom is the date of the last change.