Privacy
Last updated 2026-11-10
This page says what Oonga Studio LTD collects when you use kcode and kcode.sh, and why.
Account
Your email address, used for the codes that register a Mac, sign-in links, billing notices and, if you said yes, tips and kcode news, and the name you give when you register kcode, which your account page shows and support uses to address you. Sign-in tokens and session cookies exist only to keep you signed in. When you ask for a sign-in link, your browser keeps the time you asked until a link signs you in, so a link you open there within the hour signs you in at once. It never leaves your browser.
Registering a Mac
When you register kcode on a Mac, we keep what you entered and what the Mac sends until you type in the code we email: your name and email address, the Mac's device name, the macOS and kcode versions, a hash of the Mac's hardware id (not the id itself), and the IP address the request came from. That record is deleted after seven days, whether or not the code was used.
Devices
For each Mac you register, we keep a device name, a hash of its hardware id, the macOS version, the kcode version, when it was first seen, and when it last checked in. This enforces the one-Mac limit and keeps a Mac to one trial. Your account page shows device details but not the hardware hash. License check-ins carry the same fields and nothing about your code or prompts.
Payments
Paddle, as merchant of record, processes payment and holds card details. We receive the subscription status, the period dates, a customer reference and, for a Groups plan, the number of seats; never the card. When your subscription starts or changes (a renewal, a cancellation, a failed payment, a refund), we email ourselves your email address, your plan and what changed.
Groups
When a group admin gives a seat to your address, we keep the address, when the seat was given, and when a license first came from it. The group's admins see these on their account page, with whether the group's plan pays for the seat. They never see your Macs, a plan of your own, or what you do in kcode. When you hold a seat, your account page shows the addresses of the group's admins. When you leave the seat, or an admin removes it, we delete it, and the admins no longer see it.
When someone makes you an admin of a group, we keep your address and when you were added. The other admins see it, and whether you pay for a Groups plan. If no account holds the address yet, we make one so that you can sign in. Giving a seat or adding an admin emails the address, naming the admin who did it.
Waitlists
kcode runs on Apple silicon Macs. If you use Windows or Linux, you can join the waitlist for kcode on your system from its waitlist page. Joining signs you in to kcode.sh with your email address, and makes an account for it if there is none. For each waitlist you join, we keep which one it is, when you joined, and which version of the page's text you joined from. When kcode for that system is ready, we email you to say so; a waitlist sends no other email. Your account page lists your waitlists. You can leave one there or on its waitlist page, and we then delete your place on it.
Feedback
When you send feedback from the app, we receive the message you wrote, the kcode version, the macOS version, the build id, and, when the Mac is signed in, which device and account it came from. It is stored in a spreadsheet we control, so that we can follow up and reproduce problems.
Tips and news emails
When you sign up in the kcode window, it says kcode will also email you tips for using kcode and kcode news, with a No thanks box you can tick. An account made on kcode.sh is never asked, so it gets none until you say yes. You can change your answer at any time on your account page or in the app's Settings › Account, and every email has an unsubscribe link. We keep your answer, which version of the question you answered, where you gave it, and when.
PostHog, which stores data in the United States, sends these emails. While your answer is yes, PostHog holds your email address, your name and your answer. When the app's analytics include your account, they go on your analytics id, so those events show who you are. Otherwise they go on a separate random id that is used only for email. The emails carry no tracking pixel, and their links do not record clicks.
When you say no, unsubscribe, or delete the account, we take your address, name and answer off at PostHog, and delete the separate id with everything PostHog recorded under it. On your analytics id, PostHog keeps the record of the change that added them, and can show them with the events recorded while they were there, until those events are deleted, as Analytics in the app describes. When you unsubscribe, PostHog keeps your address on its list of addresses that get no more email.
Analytics on kcode.sh
When analytics are enabled the site uses PostHog to see how the site is used. The site never tells PostHog who you are, signed in or not. A banner asks whether the site may use cookies for this; until you answer, and after Decline, PostHog keeps nothing in your browser.
PostHog records an event when you open a page, when you leave it, and when you click something, submit a form, or change a form field. Each event holds the page's address and title, the address of the page that linked you here, your browser and operating system with their versions, the kind of device, your browser's language, the size of your screen and window, and your time zone. The event for leaving a page also holds how long the page was open and how far you scrolled. The event for a click holds the element you clicked: its text, such as a button's label, and where a link points. PostHog does not record what you type into a field.
Before you answer, and after Decline
PostHog counts your visits without a cookie. It works out a code from your IP address, your browser, and a random value it changes every day, and a day's events go under that code. PostHog deletes each day's random value once that day's events are processed, so the code cannot be turned back into your IP address or tied to your visits on another day. It does not store your IP address with these events or work out your location from it.
After Allow
PostHog gives your browser a random visitor id and keeps it in a cookie and in your browser's local storage for up to a year, so that visits on different days count as one visitor, and keeps the current visit in your browser's session storage. Each event also holds the visitor id. PostHog stores your IP address with each event and works out an approximate location from it, such as the country and the city.
PostHog also records your visits, so that we can see how pages are read: the page as it is shown, your mouse movement, your clicks and your scrolling, the page's console messages, and the addresses and timings of the requests the page makes. What you type into a field is hidden before it leaves your browser. The account page, the sign-in pages and the waitlist pages are never recorded, because they show email addresses. PostHog keeps a recording for 30 days.
Your answer stays in your browser's local storage. To change it, use Cookie choices at the bottom of any page. After Decline, the site removes PostHog's cookie and storage from your browser.
Opening kcode.sh/?notrack turns the site's analytics off in that browser. The browser keeps a note of it in its local storage, and the site no longer loads PostHog there. Opening kcode.sh/?track turns them back on.
Error reports on kcode.sh
When error reporting is enabled the site and our API use Sentry to find and fix faults. Sentry stores what it receives in the European Union.
When a script on a page fails, the site sends Sentry the error and where in the code it happened, the page's address, your browser and operating system, and a short trail of what led up to it: the pages you opened, the elements you clicked, the page's console messages, and the addresses of the requests the page made. For some page loads it also sends timings: how long the page and its requests took.
For some visits, and for every visit where an error happens, Sentry records the visit so that we can see what went wrong: the layout of the page, your mouse movement, your clicks, and your scrolling. All text on the page and everything you type is replaced with asterisks before it leaves your browser, and images are left out. To keep one recording across page loads, Sentry keeps an id in your browser's session storage, which your browser clears when you close the tab. It uses no cookie.
Sentry stores your IP address with the reports the site sends.
When our API fails to handle a request, it sends Sentry the error and the address, the method, and the headers of the request, without the headers that hold sign-in tokens, cookies, or your IP address. It does not send the content of the request.
Analytics in the app
A signed-up kcode sends product analytics events to our API, which passes them on to PostHog, which stores them in the United States. They tell us which features and models people use, how often people come back, and where they stop, so that we know what to work on. No event holds your prompts, model replies, code, files, paths, project or branch names, session titles, keys, or the names of your own commands, skills, plugins or MCP servers. Our API checks every event against the lists below and drops anything else.
With your account, or anonymous
When you sign up, kcode asks you to help improve it, and whether its product analytics may include your account. Neither answer is chosen for you, and you can change it at any time on your account page.
- Include my account. Your events go to PostHog under an analytics id we make for you. It is not your account id. They also hold your Mac's device id, its model, and the session id, so that we can see how kcode works for you over time.
- Keep it anonymous. We still get the events, but each goes under a new random id, without the device id, the Mac's model or the session id, so no two events can be tied to each other or to you. Until you answer, events are sent this way.
When you change your answer from yes to no, we delete the events linked to your analytics id from PostHog, and later events are anonymous. When you change it back to yes, you get a new analytics id, so the events after the change are not tied to the ones before.
If you want kcode to send nothing about your use at all, email support@kcode.sh. We record your objection, kcode stops sending analytics events, and we delete the events linked to you.
What the events hold
Every event holds the kcode version, the macOS version, the time, your answer to the question above, your license state (such as trial or active), and how long ago you signed up, as a range such as 2–6 days rather than a date. These are the app's events:
- kcode started: whether it is the first start or the first after an update, the Mac's processor type, its memory, its model (such as Mac15,9), how long kcode has been installed, how many providers have a key, how many plugins you installed and MCP servers you added, and the window layout;
- kcode quit: how long it ran, not counting the time the Mac slept, how many sessions it started or resumed, and how many turns finished;
- kcode crashed: how many of its processes failed since it last started;
- the first turn of a day: on how many of the last 7 and 28 days you used kcode, and how many days it was since the last;
- a first: the first session, the first turn, the first time two sessions worked at once, the first worktree session, and the 2nd, 7th and 30th day of use;
- a session started: the provider and model, whether it was new, resumed, forked or a worktree session, and how many other sessions were open;
- a session ended: how many turns, rounds, tool calls and compactions it had, its cost when every turn had a price, how long it ran, and whether it was stopped, deleted, or ended by quitting kcode;
- a turn finished: the provider, model and effort, whether you typed it or a command, timer, hook or trigger started it, how many rounds and tool calls it took, the input and output tokens, its cost when the model has a price, how long it took, how many other sessions were working at the same time, and whether it finished, was stopped or failed;
- a tool was used: the name of one of kcode's own tools (a plugin's tool is reported as
pluginand an MCP server's asmcp), how many times it was called, and how many calls failed; - the model changed: the provider and model, and whether for one session or as the default;
- a provider was added or removed: the provider, whether by a key, a sign-in or a server you added, and how many providers are ready after the change;
- a slash command ran: the name of one of kcode's own commands, not what you typed after it;
- a compaction ran: whether it was automatic, asked for by you or by the agent, or forced by a full context, and how it shortened the conversation;
- a provider returned an error: the provider, the error code, and whether kcode tried again;
- a project's search index came up to date: how many files it covers and skipped, how many pieces of code and bytes of source it holds, each rounded to two figures, and how long that took, never a file's name or contents;
- a project's search index failed: the error code, whether an older index remains, and how long the attempt took;
- the layout changed: grid, tabs or sidebar, and how many sessions the grid shows;
- a panel opened: which of kcode's own panels (such as the notifications, the command palette or Settings) or Settings sections, and how many times;
- the theme changed: the name of one of kcode's own themes (a theme you made or installed is reported as
custom) and the Appearance setting; - a setting changed: the name of one of kcode's own settings, not its value;
- a permission prompt was answered: whether you allowed the call once or always, allowed everything in the session, or denied it, and how many times, not what the call was or the reason you gave; and the permission mode, when you change it;
- a feature was used: how many times you opened a notification or ran the command it offers, maximized or grouped sessions, attached an image, started dictation, ran a
!command or filed a note, not what any of them held.
A provider or a model that kcode does not list is reported as other or custom, not by its name. Our API also reports what happens on its side:
- a sign-up asked for its code, always anonymously, since there is no account yet;
- a download started from the download page: the kcode version and the processor type, always anonymously and without the site's visitor id;
- a Mac signed up: the license state it got, whether this made a new account, whether the Mac was already on the account, whether it started the trial, and how many Macs the account has;
- you answered the question above: the answer, where you gave it, and the answer before;
- you answered the tips and news email question, or unsubscribed: the answer, where you gave it, and the answer before;
- the license changed: from which state to which, and whether monthly or yearly;
- a subscription changed: it started, renewed, changed period, was set to cancel or kept, a payment was late or came in, it paused or resumed, ended, or was refunded, and whether it is your own plan or a Groups plan you pay for;
- a Mac was removed: from the app, from your account page or by us, and how many Macs are left;
- you pressed Buy in the app, or opened the checkout on your account page: monthly or yearly, for yourself or a group, and for a group the number of seats;
- you opened Manage billing or Cancel plan on your account page, or their group versions: which one, whether for your own plan or a Groups plan, and whether it is monthly or yearly;
- a group admin gave or removed a seat, changed the seat count, or added or removed an admin: how many seats are given and paid for, how many admins the group has, whether the email to the address was sent, and for a new seat count, the count before and after and whether the plan is monthly or yearly. Never the address.
- you joined or left a waitlist: which one;
- you left a group seat, and nothing else about it.
Our API sends PostHog your email address and name only for the tips and news emails you said yes to, and never your IP address. PostHog's location lookup is off for these events. kcode -p sends none.
A kcode that has not signed up sends one event each time it starts, always anonymously: the kcode version, the macOS version, and whether it is the first start, the first after an update, or another. The events it records before you sign up wait on your Mac, the newest 500 at most, and go once it signs up.
Crash bundles and logs stay under ~/.kcode.
Your code and prompts
kcode runs on your Mac. Your prompts, files, and model replies go to the providers you configured, with your keys. They do not pass through kcode.sh.
What the app downloads at launch
kcode can download two kinds of information when it starts, before you do anything. Each is a plain download that carries the kcode version and nothing about you, your code, or your prompts. Like any request, each shows the server your IP address and when kcode runs.
- The model catalog from models.dev (
https://models.dev/api.json, about 5 MB): the providers, models, prices, and context windows kcode offers. kcode downloads it at launch when its saved copy is out of date, and again while the app is open. To stop it, setrefresh = falseunder[models_dev]in~/.kcode/config.toml; kcode then uses the copy it saved last, or the one built into the app. - The update check: the signed list of kcode releases, from our API (
https://api.kcode.sh/v1/release-index), at launch and then every hour while kcode runs. When the list names a newer kcode, kcode downloads it fromhttps://downloads.kcode.shand uses it from its next start. To stop both, setautomatic = falseunder[updater].kcode upgradeand the app's Check for updates still check when you ask.
models.dev is run by others; its own privacy policy covers what it keeps. Both switches are in the settings reference.
Retention and rights
Account and device records last as long as the account. Your email address and name stay at PostHog while your answer to the tips and news question is yes. Analytics events linked to your analytics id stay in PostHog until you change your answer to no, object, ask us to delete them, or delete the account. Anonymous events cannot be tied to you, so we cannot find them to delete them. For a copy of your data, email support@kcode.sh.
Deleting your account
You can delete your account yourself, at the bottom of your account page, by typing its email address to confirm. You can also ask us at support@kcode.sh. Deleting the account ends your subscription at Paddle at once, with no refund for the time left; if a charge is still within the refund window, ask for the refund first. If you pay for a Groups plan that renews, cancel it first: your account page holds the deletion until you do, so that the people on its seats see the end date. A Groups plan you pay for that is set to end then ends with the account, and so do the seats it pays for. Every Mac on the account is signed out, and kcode on it asks you to sign up again the next time it checks in. Deleting can't be undone, and a new account gets no second trial on a Mac that had one.
We delete:
- the account: your email address, your name, and your answers to the analytics and the tips and news questions;
- your email address and name at PostHog, which we take off at once, and the separate id that held them, if there was one;
- each Mac's record, its sign-in token, and the license files we issued it;
- your website sessions and the sign-in links we emailed you;
- the Mac sign-ups made with your address, finished or not;
- your subscription and the billing messages Paddle sent us about it;
- your place as an admin of a group, and the group with its seats when no admin and no plan in force is left;
- your places on the waitlists;
- our records of what you and we did to the account, such as a trial extension;
- the analytics events linked to your analytics id, which we ask PostHog to delete an hour later.
We keep:
- a hash of each Mac's hardware id, with nothing that ties it to you, so that a Mac still gets one trial;
- a seat given to your address, which stays with its group until an admin removes it;
- one record that the account was deleted: when, whether you or we did it, and how many Macs and subscriptions it had, without your address;
- Paddle's own records of your payments, which Paddle keeps as merchant of record under its own privacy policy;
- feedback you sent from the app, in our spreadsheet; ask us and we delete it;
- the emails that told us your subscription started or changed, in our own mailbox; ask us and we delete them;
- analytics events from the site, and anonymous events from the app, which cannot be tied to you;
- an address that unsubscribed from the tips and news emails, on PostHog's list of addresses that get no more email;
- counts of recent sign-in and sign-up attempts, which we delete after two days;
- a message Paddle sends us about the subscription after the account is gone, as it came;
- copies of the emails we sent you, which our mail service, Postmark, deletes after 45 days.
What kcode keeps on your Mac stays there until you delete it: its settings, your sessions and the last license file, all under ~/.kcode.
kcode is made by Oonga Studio LTD, registered in England and Wales, company number 15785523. Registered office: Unit 82a James Carter Road, Mildenhall, Bury St. Edmunds, England, IP28 7DE.