> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/cli/guides/understand/privacy.md).

# What data Devolutions CLI sends

What Devolutions CLI sends over the network, the telemetry preference, and where your contexts and sign-in sessions are stored on your computer.

Devolutions CLI itself talks to the workspaces you sign in to, and keeps its configuration on your computer, in your user account. This page explains what leaves your computer, what's stored locally, and how to control both.

## What goes over the network

<table><thead><tr><th width="220">WHEN YOU USE</th><th>DEVOLUTIONS CLI CONTACTS</th></tr></thead><tbody><tr><td><strong>A Devolutions Cloud context</strong></td><td>The Devolutions Cloud address you signed in to. With a browser sign-in (<code>--oauth</code>), also Devolutions Account (<code>login.devolutions.com</code>), to sign you in and renew your session.</td></tr><tr><td><strong>A Devolutions Server context</strong></td><td>The Devolutions Server address you signed in to. With a username and password or Windows authentication, the sign-in request also includes your computer name, your local user name, and your operating system platform.</td></tr><tr><td><strong>A local profile context</strong></td><td>No address of its own. A local context only points at a profile folder on your computer.</td></tr></tbody></table>

## The telemetry preference

Telemetry is **off** until you turn it on. To see the current preference:

```bash
devo config telemetry get
```

To change it, pass `true` or `false` and confirm with `--yes`:

```bash
devo config telemetry set false --yes
```

The preference is saved on your computer, in the Devolutions CLI configuration folder.

## What's stored on your computer

Devolutions CLI keeps its configuration in one folder for your user account:

* By default: a `Devolutions/CLI` folder in your user's local application data folder.
* If your system has no local application data folder: `.devolutions/cli` in your home folder.
* If `DEVO_CLI_CONFIG_HOME` is set: that folder. See [Move the configuration folder](#move-the-configuration-folder).

When Devolutions CLI records its background process, it restricts this folder to your account and the system account on Windows, and to your account only on macOS and Linux.

`devo context list` shows the path of the context file on its `Store:` line.

<table><thead><tr><th width="220">WHAT</th><th>WHERE AND HOW</th></tr></thead><tbody><tr><td><strong>Contexts</strong></td><td>Their names, the workspace address or profile folder, and which one is current, in JSON files of the configuration folder. On macOS and Linux, the files themselves are also readable and writable by your account only.</td></tr><tr><td><strong>Browser sign-in sessions</strong></td><td>In your operating system's secure store: protected with your Windows user account on Windows, the Keychain on macOS, and the Secret Service (libsecret) on Linux. Without a supported secure store, browser sign-in isn't available.</td></tr><tr><td><strong>Application secrets, API keys, and passwords</strong></td><td>Never saved. The context keeps only the <strong>name</strong> of the environment variable or the <strong>path</strong> of the file you gave at sign-in, and reads the value again each time it's needed.</td></tr><tr><td><strong>Devolutions Cloud application key</strong></td><td>Saved in the context file, with the pointer to its secret.</td></tr><tr><td><strong>Telemetry preference</strong></td><td>In the configuration folder.</td></tr></tbody></table>

`devo logout` clears the sign-in of a Devolutions Cloud or Devolutions Server context but keeps the context. `devo context delete` removes the context and, for a Devolutions Cloud or Devolutions Server login, its stored session too. See [Switch between workspaces](/cli/guides/connect/switch-workspaces.md).

## Move the configuration folder

Set the `DEVO_CLI_CONFIG_HOME` environment variable to use another folder, for example an isolated folder on a build agent:

{% tabs %}
{% tab title="PowerShell" %}

```powershell
$env:DEVO_CLI_CONFIG_HOME = "<folder>"
```

{% endtab %}

{% tab title="Bash" %}

```bash
export DEVO_CLI_CONFIG_HOME=<folder>
```

{% endtab %}
{% endtabs %}

Every `devo` command started with this variable reads and writes its contexts in that folder. When you don't select a local profile, Devolutions CLI also uses an `rdm` subfolder of this folder as its default profile folder. See [Install Devolutions CLI on build agents](/cli/for-devops-and-administrators/automate/install-on-runners.md).

## Export your configuration

`devo config export` writes your local profile contexts, the name of the current context, and the telemetry preference to a `.json` file. It never includes a sign-in session or a secret value.

```bash
devo config export --out-file <file>.json --yes
```

Add `--no-contexts` or `--no-tooling` to leave out the contexts or the telemetry preference, and `--force` to replace an existing file.

## Next

* [What stays hidden, and what doesn't](/cli/guides/understand/security-model.md)
* [Environment variables](/cli/reference/environment-variables.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/cli/guides/understand/privacy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.