Privacy policy
What we keep, and why.
Last updated 12 November 2026.
Kovan is local-first: your code stays in your checkouts and your agents run on your machines. The Kovan server keeps what a team needs to work together. This page says what that is, why we keep it, who else processes it and how to have it corrected or deleted.
Who we are
Kovan is run by Alper Kayan in Turkey (“we”). We decide how the data described here is used. Write to kovan@alperkayan.dev about anything on this page.
What stays with you
- Your repository. The server never keeps a copy of it. Teammates sync through your own Git remote with your own credentials. The parts of the code a shared session works on do reach the server, encrypted: see session transcripts and session changes below.
- Git credentials, SSH keys and folder paths. They stay on your computer, except the checkout paths of machines you register to run agents (below).
- Your provider keys and MCP server secrets. They stay in your operating system’s keychain.
- Card details. They go straight to Stripe’s hosted page.
What we collect
- Your account: name, email address, profile picture and, if you sign in with GitHub, your GitHub username. GitHub access tokens are encrypted before they are stored. Sign-in sessions are stored only as hashes.
- Team data: organizations, workspaces, members, roles and invitations.
- Coordination data: sessions, plans, file locks, comments, notes, activity, AI teammates, Swarm runs and snapshot metadata (commit, branch and time, never file contents).
- Session transcripts: what an agent says and does in a shared session, so teammates can follow it. This includes code the agent read or wrote. Secrets are redacted by pattern and the text is encrypted before it is stored.
- Session changes: in a shared session, each member’s changes against the base branch (a diff, new files included), so teammates and the phone app can review them. When the session ends only its final diff is kept. Secrets are redacted and the diff is encrypted before it is stored.
- Usage records: which model ran, how many tokens it used and what it cost.
- Billing, if you use Kovan billing: your allowance, your consent to be charged, invoices and the Stripe customer they belong to.
- Phone notifications, if you use the mobile app: a device token from Apple or Google so we can send them.
- Error reports: an error message, where in the code it happened, the app version and platform. Prompts and code are not included. You can turn this off in Settings → Privacy.
- Machines you register to run agents unattended: their name, platform, the agent programs they have, the repositories they hold with the folder each is in, and when they last reported. When such a machine fetches or pushes, its Git traffic passes through the server, which adds the workspace’s GitHub token; it is passed on, not stored.
- Integrations you set up: API keys (only a hash of each), webhook addresses with their signing secrets (encrypted), and a two-week record of workspace events and their deliveries.
- Security records: an audit log of account and team changes, with the IP address they came from, and short-lived rate-limit counters.
We do not use advertising or analytics trackers, we do not set tracking cookies and we do not sell data.
Why we use it
- To provide Kovan: accounts, shared sessions, the team’s live context and notifications. This is needed to perform our agreement with you.
- To charge for Kovan billing you chose, and to keep invoices as the law requires.
- To keep Kovan secure and working: the audit log, rate limits and error reports. This is our legitimate interest, and error reports can be turned off.
- To email you sign-in links, invitations and notices about your account.
Who else processes it
- The model provider you choose. When an agent runs, your prompt and the code it reads go to that provider: through your own key, through the coding agent you connected (such as Claude Code or Codex), or through Kovan billing. Their own terms apply to what they receive.
- OpenRouter carries model calls made with Kovan billing.
- Stripe handles payments for Kovan billing.
- Apple and Google deliver notifications to the mobile app.
- Our hosting provider runs the server in Turkey. Email is sent from our own mail server.
Some of these providers are outside Turkey and the European Union. Data sent to them is limited to what each one needs to do its job.
How long we keep it
- Session transcripts and the final diffs of ended sessions: 90 days, or the period your organization sets (1 to 3650 days). A live session’s changes are replaced as work goes on and removed when it ends.
- Audit log: 400 days.
- Workspace events and webhook deliveries: 14 days.
- Machines: until they are removed, or the key they report with is revoked.
- Your account and team data: until you delete your account or the team removes it.
- Invoices: as long as tax law requires, even after the account is deleted.
- Encrypted database backups: 14 days.
Your rights
You can ask to see the data we hold about you, have it corrected, receive a copy, have it deleted or object to how it is used. You can delete your account yourself in the app, in the mobile app or on your account page. For anything else, write to kovan@alperkayan.dev; we answer within 30 days.
You can also complain to a data protection authority: in Turkey the Personal Data Protection Authority (KVKK), in the European Union the authority where you live.
Children
Kovan is not meant for anyone under 16, and we do not knowingly collect their data.
Changes
When this policy changes, we update this page and its date. If a change affects how your data is used, we tell you by email or in the app before it applies.