# Yandex Disk CLI security and privacy (/en/docs/ydisk/security)

Know what `ydisk` keeps on your computer, what it sends and to whom, and how to remove it. What WireCat CLIs share,
such as the keyring, permissions, MCP and what never reaches a log, is on the
[shared security page](/llms.mdx/docs/security/content.md). This page keeps only what is particular to `ydisk`.

**On this page:**

1. [What stays on your computer](#what-stays-on-your-computer)
2. [What goes over the network](#what-goes-over-the-network)
3. [Agents and MCP](#agents-and-mcp)
4. [Run records](#run-records)
5. [File permissions](#file-permissions)

## What stays on your computer [#what-stays-on-your-computer]

| What | Where | How to remove it |
| --- | --- | --- |
| The Yandex token | The system keyring, or a private file where there is none | `ydisk personal session end` |
| The text of the files in the chosen folders, with their names, paths, sizes, dates and MD5 checksums | The local store, `wirecat.db`, shared with the other WireCat tools | `folders remove` with the folder's id from `folders list`, then `sync` |
| Your tags, notes and memories about documents | The local store | `tags remove`, `notes remove` |
| Settings and run records | The folders `ydisk doctor` shows | `ydisk runs list` shows them. They expire after the days in [settings](/llms.mdx/docs/ydisk/configuration/content.md#run-records) |

The files themselves stay on the Disk. A copy of a file is saved only when you run `files download --output`.
Public links (`public_url`) are not kept by the sync. Nothing goes to WireCat: there is no WireCat server and no
account with us.

## What goes over the network [#what-goes-over-the-network]

`ydisk` keeps its settings in `config.json` and its state in the folders `ydisk doctor` shows. It talks to one
service, Yandex Disk's API at `cloud-api.yandex.net`. `session start` keeps the Yandex OAuth token in the OS keyring,
or in a private file where no keyring works. The token goes only into the Authorization header of a request to
`cloud-api.yandex.net`, never into an address, an answer, a run record or the send journal. Downloads and uploads go
to the link Yandex gives (`downloader.disk.yandex.ru`, `*.disk.yandex.net`, `*.storage.yandex.net`) without the token, and those links are
never printed.

Besides Yandex, `ydisk` asks the npm registry once a day whether a newer version exists, unless `update_check` is
`false`. Text goes to an AI provider only when you set one up, such as `embedding_provider` set to `openai` or
`memories extract`. By default search by meaning runs on your computer.

## Agents and MCP [#agents-and-mcp]

Over MCP an agent reads a file's text with `files download` but cannot save it to a path: `--output` is the owner's
only. `files upload` refuses credential files, browser profiles and the WireCat folders unless the owner adds
`--allow-any-file`. `files delete`, `--replace` and the public-link commands ask first at a terminal. Over MCP only
`deny` stops them, so set `files.delete=deny` and `files.share=deny` for an agent that should not, and `files.upload=deny` for one that
should put no local file on the Disk.

`ydisk personal mcp serve --http` listens on `127.0.0.1` only, for browser apps that reach it through your own
tunnel. Each app logs in with a one-time code, and the server keeps a hash of each login it gives, in the state
folder, readable by you only. `ydisk personal mcp revoke` forgets every one of them.

## Run records [#run-records]

A run record keeps the command line as you typed it, so `ydisk runs show` tells you what was run. A secret is still
stored as `[redacted]`: an option named like a token or password, a password in a link, a long opaque string. A
phone number is replaced by `[redacted]` inside the word you typed, message text included: one written with its "+" and
country code, or 11 to 15 digits in a row, so a long id of that length is hidden as well. To keep none of the words
you type, run `ydisk personal config set record_input false`.

A secret is also found by what it looks like, in a run record and in a kept error message: a token in a known
format (GitHub, OpenAI, Slack, AWS, Stripe, npm and the like), a `Bearer` credential, a random-looking string of 20 or
more characters, and a random-looking run of 20 or more lower-case hex characters, such as a hex key or a full commit
hash. The value after a secret name is hidden too, whether it follows `=`, `:` or a space: `password=`, `API_TOKEN=`,
`password hunter2`, `pin 1234`. Some secrets look like ordinary words and stay: a value of letters only after a
secret name and a space (`pin this message` stays), a hex key in upper case, a short commit hash or a UUID, a short
password typed without a secret name before it, and a secret inside a link or a file path unless it is in a known
format or after a secret name.

## File permissions [#file-permissions]

`config.json` is saved readable by you only (`0600`), and its folder is created for you only (`0700`). A file or
folder made by an older version may be open to other users of the computer: `ydisk doctor` lists each under
`files.problems` and prints the `chmod` that fixes it. Windows is not checked. Report a vulnerability as [SECURITY.md](https://github.com/WireCatLabs/ydisk-cli/blob/main/SECURITY.md)
says.
