# What leaves your machine

**Niro builds and answers from the graph on your computer.** A few things are sent to Niro's services. This page lists each one, what is in it, and what decides whether it is sent.

## The short version

Niro shows this text in `niro status` and `niro plan`:

> Your code stays on this machine, except, for each line the audit flags, the method that holds it and one line for each name it uses, which are sent with secrets masked. A record of which Niro tools your assistant used is also sent, to improve Niro and to show you its value. Niro's tools answer your assistant from the graph on this machine and never send the contents of your files.

When **Help improve Niro** (code sharing) is on for your account, one more thing is sent, by itself: the code of every folder Niro indexes on your computer, redacted first. `niro plan` shows which way it is:

```
Help improve Niro  on
✓ Your code is indexed and answered on this machine
✓ Sent in the background: a record of which Niro tools ran, and the methods the audit flags with the lines they reference (secrets, author and company names removed)
✓ Code shared in the background: the files Niro indexes, redacted here, deleted after processing, never used to train AI

```

With sharing off, the last line reads `✗ Code sharing is off`, and no code is shared.

## Everything that is sent

| What | Where to | What is in it | When |
| --- | --- | --- | --- |
| **Sign-in** | Niro's account service | Your sign-in through the browser | When you run `niro start` or `niro login` |
| **Your account details** | Niro's account service | Your sign-in, to read your account's email and identity | When you run `niro whoami` |
| **Sign-out** | Niro's account service | Your sign-in token, so the service withdraws it | When you run `niro logout` |
| **Old hosted projects check** (only on a computer that used hosted Niro before) | Niro's account service | Your sign-in, to list your hosted projects. For a hosted project that list no longer has, its id and its repositories' ids, to ask whether they still exist. No code | Every 6 hours, by the background watcher, while old hosted registrations are still listed in `~/.niro/projects.json` |
| **Licence check** | Niro's billing service | A random number and your engine's version, with your sign-in | Each time the engine starts, and when its licence is renewed |
| **Engine download** | Niro's billing service, then a download link | Nothing about your code. The download is checked against its published fingerprint (SHA-256) | When `niro start` or `niro engine install` installs the engine |
| **Coverage audit** | Niro's audit service | For each line the build could not read: the file's path inside the repository, the method that holds the line, and one line per name it uses. Every other line is blank, and secrets are masked, in the path too. Separately, a list of the libraries and kinds of files the build saw, which carries no file names or paths | Every 5 minutes, on every plan. See [Coverage audit](https://help.niroai.dev/cli/coverage-audit-and-consent/) |
| **Tool-usage record** | Niro's assistant service | Which tools your agent used, how long they took, failures, a short task summary, and the names, paths and search text asked about. Free text is masked first | Every 5 minutes |
| **Shared code** (only while Help improve Niro is on) | Niro's indexing service | The files Niro indexes in each indexed folder: the source files it parses and the config, build and text files it reads. Never a file your `.gitignore` covers (unless git tracks it), a real `.env`, a key or key store, a tool's token file, or `node_modules` and other build output. Secrets are masked and author and company names removed first. The first time, a folder's whole indexed set; after that, only files that changed, and a note of files that were removed | Every 5 minutes, by the background watcher, only while your account's lease says sharing is on. A lease that cannot be read sends nothing. A folder you exclude with `niro share exclude <folder>` is never sent. See [Licence and plans](https://help.niroai.dev/cli/licence-and-plans/) |
| **Whole repository** (only if you ask) | Niro's indexing service | The same files and the same redaction as shared code, for one folder. This is how you send a repository to Niro for support | Only when you type `niro audit-push-repo` and answer yes. It works with code sharing on or off, on every plan. For a folder you excluded with `niro share exclude`, it also asks "Send it anyway?" and sends only on yes |

## What is not sent

- **The contents of your files, when your agent asks Niro a question.** The engine on your computer answers.

- **Your code to a language model (an LLM).** This release does not include LLM documentation.

- **The files of folders you once set up for hosted Niro.** A computer that used hosted Niro still lists those folders in `~/.niro/projects.json`. The background watcher never syncs them in this release: it uploads none of their files, also when that list changes. A folder the engine on your computer indexes is built there instead.

- **Anything not in the table above.** The table lists every call `niro` makes to Niro's services in this release. How long each `niro start` step took is kept on your computer only. `niro upgrade` makes no check call of its own: it runs npm, which talks to the npm registry.

## How secrets are hidden

Everything that leaves is masked on your computer first: secret values are replaced with placeholders. In audit snippets and in shared code, the names of authors and companies are replaced with `<author>` and `<company>`. See [Secrets and masking](https://help.niroai.dev/cli/secrets-and-masking/).

## Niro's Data Processing Agreement

Niro's Data Processing Agreement (DPA) sets out how Niro handles customer data. Version 3.0 is dated 2026-08-16. In short:

- **No training on your content.** Niro does not use your code to train or fine-tune an AI model. (Clause 10.1.)

- **Outside AI providers.** Where Niro uses an outside AI provider, the provider is set up so that it does not keep your content or train on it. A masking step removes secrets and common personal data first. The DPA says this is best effort, not a guarantee. (Clause 10.2.)

- **Small extracts kept to fix parsing.** To fix a parsing defect, Niro may keep a small extract of code, masked, for at most 90 days. (Clause 10.3.)

- **Usage signals.** Niro records whether its answers were useful. Niro may use these signals to improve the service, including its own models. (Clause 10.4.)

- **Opting out.** You can ask in writing to switch off the extracts in 10.3 and the signals in 10.4. Niro confirms within 10 business days. (Clause 10.5.)

- **Breaches.** Niro tells you within 72 hours of learning about a data breach that affects your data. (Clause 7.1.)

- **When you stop using Niro.** You can ask for your data back within 30 days. After that, Niro deletes it within 30 days. Copies in backups stay protected until the normal backup cycle deletes them. (Clause 8.)

- **Account data** is deleted 90 days after the account is closed. (Annex 1.)

To delete your account, email **[help@niro.ai](mailto:help@niro.ai)**. Ask the same address for a copy of the DPA.