Privacy
Version 30 October 2026.
kelve is run by an individual in the United Kingdom, who decides how the information below is used: the “controller”, in the UK GDPR’s word. Questions, or anything you’d like to ask of your information: hello@kelve.ai.
In short
- The kelve app runs on your computer. What it reads, your code, files and notes, stays there, and goes to no one but your own agent.
- The shared graph knows almost nothing about you: an ID from GitHub or Google, a name it makes up for you, and what you add. Never your email or your name.
- Counts of how you use kelve are sent only if you say yes, with a random ID that isn’t your account.
- kelve.ai has no cookies, no tracking and no analytics.
- Nothing is sold, and nothing is used for advertising.
The kelve app, on your computer
kelve reads what you open with it on your computer, and keeps what it works out there. None of that comes to us. What leaves your computer, and to whom, is listed in full in what goes to the shared graph. In short:
- Your agent (Claude Code, Codex, Cursor or another) does kelve’s reading, on your own plan or key. What it’s given goes to its provider under your agreement with them, not under this policy.
- The shared graph is sent general knowledge only: never file contents, names or paths, never which ideas your work uses, and never your notes. Once you’ve signed in, kelve also asks it for lessons by the first characters of a code made from each library and program name your work uses, so the graph never learns which.
- GitHub is asked once a day whether a newer kelve is out. It sees your IP address and kelve’s version, as it would for any download.
KELVE_UPDATES=offstops it.
The shared graph
What it keeps
| What | Why | How long |
|---|---|---|
| Your GitHub user ID, or Google’s ID for you | To know it’s you when you sign in | Until you delete your account |
A name the graph makes up for you, such as contributor-k3x9q2ma | To credit what you add, never with your own name | Until you delete your account, and on what you added after |
| What you add: entries, lessons, and what came of lessons you were given, with when | It’s the graph. It’s public domain, under CC0 (the terms) | For good, under the made-up name, which stops leading to you when you delete your account |
| Reports that an entry is wrong or didn’t help, with when | To check the entry again | For good. They’re sent with no account, so they never lead to you |
| How many reading tokens your account was given each day, and how much it added | To keep to each account’s daily limits | Until you delete your account |
| Your IP address, in memory only | To limit how fast any one address can call the graph | Moments, never written down |
| Google Cloud’s request logs: IP address, browser or app, time and address asked for | Security, and to fix what goes wrong | 30 days |
What it never has: your email address (Google sends one at sign-in; it’s never read or kept), your GitHub login or name, your code, files, notes or paths, or which reads were yours. Each read spends a single-use token that the graph can’t link to your account.
Why it may use it (the UK GDPR’s lawful bases): to provide the service you signed up for (contract); and, for limits, logs and keeping the graph safe, our legitimate interest in running it reliably and fairly.
Who it goes to
These process information for us, under their own data protection terms:
- Google Cloud runs the graph and its database, in London.
- GitHub and Google sign you in. They tell the graph who you are with them, under your accounts there.
- Anthropic (and, while testing, OpenRouter) run the models that check what’s added before anyone reads it. They get the text being checked: entries, lessons and reports, which should hold no personal information. They’re in the United States; transfers rely on the safeguards in their data processing terms, such as the UK’s addendum to the EU’s standard contractual clauses.
- PostHog, in the EU, holds the anonymous counts described below.
Nothing is sold, and nothing is shared for advertising.
Counts of how you use kelve
kelve asks you once, on its first screen, whether to share anonymous counts of how you use it. If you say yes, and once you’ve signed in to the shared graph, once a week it sends the graph a count of what you opened, read and wrote, and how lessons went, a day at a time: numbers only, with kelve’s version, your computer’s platform, which agent you use, and a random ID made when you said yes. Settings shows exactly what goes, and every week sent.
It never includes your account, name, address, or anything you opened or wrote. The graph keeps the counts with no address and no time finer than the day, and passes them to PostHog in the EU, from its own server, so PostHog never sees your computer. The random ID is deleted when you stop sharing.
Why: your consent. Stop in kelve’s Settings, or set DO_NOT_TRACK=1 or KELVE_TELEMETRY=off where kelve runs.
kelve.ai
The website sets no cookies and has no analytics or tracking. It remembers, in your own browser, whether you chose light or dark. It’s served by Google’s Firebase Hosting, which handles your IP address to send you the pages; we don’t keep logs of visits.
Your rights
You can ask for a copy of what kelve holds about you, and to have it corrected, deleted or restricted, to object to how it’s used, or to have it in a form you can take elsewhere. Where kelve relies on your consent, you can withdraw it at any time.
- Delete your account in kelve’s Settings, under “The shared graph”, or ask us. The graph then forgets the GitHub or Google account you signed in with. What you added stays, as it’s public domain, under the made-up name, which no longer leads to you.
- Anything else: email hello@kelve.ai. We’ll answer within a month.
If you’re unhappy with how your information is handled, tell us first, if you can. You can also complain to the UK’s Information Commissioner’s Office, at ico.org.uk or on 0303 123 1113.
Children
kelve is for people aged 13 and over.
Changes
When this policy changes, the version at the top changes. If a change matters to how your information is used, kelve tells you before it applies.