# Counts and labels. Never your code.

> What leaves your machine when you use Warden. Signed-in release builds send one usage event per review: counts, labels and one hash. This page shows the event, the data that is never sent, what the code graph does on your machine, and the commands that show or stop it.

Source: https://wardenreview.com/transparency

- Signed-in release builds send one usage event per finished review, scan or delegate run: counts, values from a fixed list, yes or no answers and one keyed hash. The first run shows a notice and sends nothing.
- Never sent: source and diffs, paths and file names, finding text, prompts, commit messages, branch names, repository owners and URLs, git authors, error text, credentials.
- The repository name is off unless you turn it on, and is never sent with an owner, URL, path or branch.
- The code graph is built on your machine and never uploaded. A usage event carries only how many lookups a review made.
- Feedback on findings stays on your machine.
- Turn reporting off: `warden config set usage.enabled false`, `WARDEN_USAGE=off` or `DO_NOT_TRACK=1`.

Signed-in release builds report usage. You can turn it off.

Below is the event Warden sends after each review: numbers, labels, and one hash. Never your source, and never the words of a finding.

## One event per review. It fits on a screen.

It is sent once for each finished review, scan, or delegate run, and only when you are signed in. Every field is a count, a value from a fixed list, a yes or no, or a one-way hash. Free text is never a field.

- **run**: A random id, the time, the CLI version, and the machine type. A retry of the same run is ignored.
- **what ran**: The command, the mode, and the agent. Review, scan, or a delegate pass. Claude, Codex, or neither.
- **model**: A known public model id, or the word custom. A private or internal name is never sent as itself.
- **tokens**: Input, including cached, output, cache reads, and the total. Enough for your own dashboard. Not a transcript.
- **size**: How long it took, how many files were selected, reviewed, skipped, failed, or excluded, and how many lines moved.
- **languages**: Counts on a fixed list, such as go or markdown. Anything unusual is other. A rare extension can name a project, so it is not sent.
- **finding counts**: Only how many findings there were: how many were critical, high, medium or low, and how many in each category. Plus the verdict and the score. Never what a finding says.
- **features**: Yes or no: a prompt, background, the knowledge base, a resume, and the fail-on level. The text you typed stays here.
- **repository**: A hash of the root commit, keyed by a secret in ~/.wardenreview that never leaves the machine. The server cannot turn it back into a name, and it cannot match it to a public repo.
- **code graph**: One count: how many times the review looked something up in the code graph. Only when the graph is on. The graph is built on your machine and never leaves it.

## Never sent.

- source and diffs
- paths and file names
- finding text
- prompts you wrote
- commit messages
- branch names
- repository owners and URLs
- git authors
- error text
- credentials

The same rule covers tool arguments, agent output, environment values, and configuration. Usage events do not store your IP. Hosting logs keep addresses only as long as the provider already does.

One thing is off unless you turn it on: the repository name. With `warden config set usage.share_repo_name true`, or the switch in the dashboard, each event also carries the repository name only, such as `api`. Never the owner, the URL, the path, or the branch. Turning it off deletes every name that was stored.

## The code graph stays on your machine.

Warden can look up who calls a function, what it calls, and what a change affects. It builds that graph from the code on your machine and never uploads it. It is on by default.

Warden does not collect it.

No functions, no files, no calls between them. A usage event carries one number about it: how many lookups the review made. Like any file the review reads, the answer to a lookup goes to the model you chose, never to Warden.

The graph tool is a separate program. The first review that uses it downloads it once, about 16 MB, from Warden's release host, and checks it against a published checksum. About once a day, Warden asks Warden Cloud whether a newer tool build exists. The request carries no account or usage data, but the server sees your IP address, as with any request.

Turn the graph off in the dashboard under Settings, or on one machine with `warden config set graph.enabled false`. The switches under Controls below also stop the download and the daily check. A tool that is already installed keeps working.

## Kept apart.

### The account

Signing in stores what the service needs to know who you are. It is separate from usage events.

- GitHub ID, username, and the email used for billing. The GitHub sign-in token is used once to look you up and is not kept.
- When you signed up, the plan, and whether a trial is active.
- Which login sessions are still active, with the CLI version and when each was last used.
- If you start a plan, payment happens on Dodo Payments' own pages. Warden Cloud keeps the plan status and, for a payment, its id, date, amount, currency, and status. It does not see card details.

### Dashboard settings

What you set in the dashboard is stored with your account, so every machine follows it. None of it is in a usage event.

- Your time zone, and whether usage reporting, repository-name sharing, and the code graph are on.
- File patterns that reviews skip, such as `docs/legacy/**`, for all repositories or for one. A pattern is text you typed. A per-repository list is keyed by the shared repository name, so it needs name sharing, and it is deleted when sharing is turned off.
- Messages you send through the dashboard's feedback form, and any reply.

### Feedback

Finding ids, the explanation you typed, learnings, and useful or not-useful marks stay in files on this machine. Feedback events are not approved for upload.

## You can see it, and you can stop it.

Reporting is on by default in release builds, once you are signed in. The first run shows a notice and sends nothing, so you can opt out before anything is sent. Local and development builds do not report. You can inspect every event and turn reporting off at any time.

### See it

```sh
warden usage
warden usage --what
warden usage --last
```

### Stop it

```sh
warden config set usage.enabled false
WARDEN_USAGE=off
DO_NOT_TRACK=1
```

Any one of these deletes events still waiting to be sent. They also stop the code graph tool check.

`DO_NOT_TRACK=1` follows the [Console Do Not Track](https://consoledonottrack.com/) convention.

### How long

Raw events are kept for 13 months, then deleted. Daily totals are kept while the account exists. `warden account delete` cancels any plan and deletes the account and everything tied to it.

## A small group of friends.

Warden is maintained by a very small group of friends. A bug report or a feature request is welcome. That note is not collected with usage. Write it where people can read it.

[Email us](mailto:neeraj@wardenreview.com)
