> 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/send/security/how-encryption-works.md).

# How encryption works

Devolutions Send encrypts everything before it leaves the sender: in the browser on the website, or on your Devolutions Server. The Devolutions Send service only stores unreadable data.

Devolutions Send encrypts everything before it leaves the sender: in the browser on the website, or on your Devolutions Server. The Devolutions Send service only stores unreadable data.

## The journey of a message on the website

1. **Key generation.** The sender’s browser generates a random key.
2. **Local encryption.** The message, and the file in chunks, are encrypted in the browser with the Devolutions Crypto library.
3. **Upload.** Only the encrypted data is sent to the Devolutions Send service.
4. **Link creation.** The key is placed in the link, after the `#` sign. Browsers never send that part to the server.
5. **Decryption.** The recipient’s browser reads the key from the link and decrypts the content locally.

{% hint style="success" %}
Result: Devolutions stores the encrypted content, but never has the key to read it.
{% endhint %}

## With a passphrase

A key is derived from the passphrase with Argon2, using parameters and a salt unique to each message. Only those parameters are stored on the server, never the passphrase. On the website, this key adds a second layer of encryption on top of the first: you then need **both** the full link and the passphrase to decrypt. In the Devolutions Password Manager tool, the key derived from the passphrase is used on its own, without a second key in the link.

## Files

Files are compressed, split, encrypted chunk by chunk, then uploaded to Azure Blob storage. The file name is encrypted too.

## Keys and algorithms

| ITEM                                               | VALUE                                                                                                                            |
| -------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| Link key                                           | 64 random bytes, generated by the browser                                                                                        |
| Passphrase derivation                              | Argon2                                                                                                                           |
| Library                                            | Devolutions Crypto                                                                                                               |
| Library                                            | `@devolutions/devolutions-crypto-web` (website), `Devolutions.Crypto.Core` (.NET client)                                         |
| Symmetric encryption algorithm                     | XChaCha20-Poly1305 (Devolutions Crypto ciphertext version 2), with a random 24-byte nonce. The key is first hashed with SHA-256. |
| Encryption for an account (email sends, envelopes) | X25519 key exchange with the account’s public key, then XChaCha20-Poly1305                                                       |

{% hint style="info" %}
Exception: with Devolutions Server, encryption happens on the Devolutions Server before the content is sent to Devolutions Send. See [Devolutions Server](https://docs.devolutions.net/send/in-app/devolutions-server.md).
{% endhint %}


---

# 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/send/security/how-encryption-works.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.
