# What goes to the shared graph

> What’s sent, and what never is. Every page of kelve's docs is listed at https://kelve.ai/llms.txt.

kelve runs on your computer. This page lists everything that leaves it, who gets it, and how to stop it. If this page and [kelve's code](https://github.com/kelve-ai/kelve) ever disagree, the code is right. The [privacy policy](/docs/privacy/) says what the shared graph keeps about you, and your rights. The [terms](/docs/terms/) are what you agree to.

## Using kelve at work

Your work goes to no one but your agent. Once you've signed in, the shared graph gets general knowledge, and nothing else:

- Entries your agent writes, from the web and never from your files.
- How ideas relate to each other.
- [Lessons](/docs/lessons/) your agent learns, in its own words. kelve checks each one for your work's names, paths and secrets, then holds it for a day so you can stop it.

The graph never learns who's reading, or which ideas your work uses.

To send nothing at all, don't sign in, or set `KELVE_GRAPH_URL=off`. kelve still works, and your agent writes every entry for you alone. Or [run your own graph](/docs/own-graph/).

## Who gets what

| Who | What they get | When | To stop it |
|---|---|---|---|
| **Your agent** | The files you open, with secrets taken out, to read them for you | When it takes a job | Don't open them in kelve |
| **The shared graph** | A request for the instructions your agent's jobs follow, and for the terms, with nothing about you | Signed in or not | `KELVE_GRAPH_URL=off` |
| **GitHub or Google** | That you're signing in to the shared graph. They tell the graph a number for your account, never your name or email | When you sign in | Don't sign in |
| **The shared graph** | The names of ideas to look up. Each read spends a token that works once, signed so the graph can't tell whose. So a read never says who you are | Once you've signed in, as your work is read | Don't sign in, or `KELVE_GRAPH_URL=off` |
| **The shared graph** | The first few characters of a code made from each library your files import, and from each program your agent runs. kelve uses them to find lessons. The graph sends back every name that starts the same, so it never learns which one | Once you've signed in, as your agent works | Don't sign in, or `KELVE_GRAPH_URL=off` |
| **The shared graph** | Entries your agent wrote, and how ideas relate | Once you've signed in | Don't sign in, or `KELVE_GRAPH_URL=off` |
| **The shared graph** | Lessons your agent learned, a day after it wrote them | Once you've signed in | **Stop** on each, in **Settings**, **Lessons** |
| **The shared graph** | Whether each lesson your agent was given held, and what showed it | Hourly, as your account, so one project counts once | Don't sign in, or `KELVE_GRAPH_URL=off` |
| **The shared graph** | What you said, when you say an entry or how an idea relates is wrong. Which way an entry didn't help, when you say so. Nothing about you | When you say so | Don't say so |
| **The shared graph** | A count for each relation people follow, with nothing about you | Once you've signed in, as you trace down | Don't sign in, or `KELVE_GRAPH_URL=off` |
| **The shared graph, then PostHog** | Anonymous counts of how you used kelve, a week at a time. Numbers only, with kelve's version, your platform, your agent, and a random ID made when you said yes. The graph passes them on to PostHog, in the EU, from its own server | Weekly, only if you say yes, once you've signed in | **Share anonymous counts**, in **Settings**, **What's shared**, or `DO_NOT_TRACK=1` |
| **GitHub** | A request for kelve's newest version, which says the version you have and nothing about you or your work | At most once a day, and when you run `kelve update` | `KELVE_UPDATES=off` |

No one else gets anything.

## The counts

kelve asks once, on its first screen, whether to **Share anonymous counts of how you use kelve**. Nothing is counted for sending until you say yes. Then the counts are:

- How many things you opened.
- How many entries you read, and how many of them were already written.
- How many links you followed.
- How many notes you wrote.
- How many jobs your agent did.
- How lessons went.
- kelve's version.

They never include your work, your name or your account. They're never sent with your account's key or a reading token, so the graph can't tie them to you. The random ID is deleted when you stop.

To see them as they'd go, open **Settings**, **What's shared**, **See exactly what this week's says so far**. `DO_NOT_TRACK=1` or `KELVE_TELEMETRY=off` where kelve runs turns them off, whatever you chose.

## Never sent

- Your code or text.
- The names of your files, or their paths.
- Which ideas your files use, or which libraries.
- The commands your agent runs, or the errors it meets. A lesson may say the error it answers, as your agent wrote it, with names, paths, quoted text and numbers taken out first.
- Your notes.
- Secrets.

## Secrets

kelve never reads files that may hold secrets, such as `.env`, `.envrc`, `.netrc`, `credentials.json`, SSH keys like `id_rsa`, or files ending `.pem`, `.key`, `.p12` or `.tfvars`. Every secret in what it does read is masked as it's read, and masked again before anything goes to your agent or the shared graph. kelve checks a lesson for secrets, paths and names from your work before it's held. The shared graph turns away an entry that seems to hold a secret, or a path on someone's computer.

To keep other files out, list them in a `.kelveignore` in the project, written as a `.gitignore` is. kelve leaves out what `.gitignore` leaves out too.

## Kept on your computer

kelve keeps these on your computer:

- What it reads, and what it marks.
- The entries your agent wrote that haven't been added.
- The lessons waiting to go.
- What you've read.
- Your settings.

The key for adding to the shared graph is sealed with your install's own key before it's kept, and never shown back.

**Delete everything**, in **Settings**, **What's shared**, removes your settings, what kelve keeps for what you've opened, and what's kept for your agent. Your notes, and what's read in each project, are your own files, and stay. It can't be undone.

## When something goes wrong

kelve keeps a short report, with no secrets, no file names and nothing you opened, and sends it nowhere. **Settings**, **What's shared** shows each one exactly. You can **Report it on GitHub**, where you read it again before you post it, or forget it.

## Reporting a security problem

Email [hello@kelve.ai](mailto:hello@kelve.ai) with what you found, how to reproduce it, and what someone could do with it. Don't open a public issue for it. You'll hear back within three working days.
