> 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/choose-a-region.md).

# Choose a Devolutions Send region

Choose whether Devolutions Send stores encrypted payloads in Canada or Europe (France), from the standalone sites or from product settings.

Devolutions Send is available in two public regions. The region only changes where the **encrypted payload** is stored. Secrets are still encrypted on the client before they leave the browser or application, so Devolutions cannot read the original content in either region.

| Region          | Hostname                                              | Notes                                                   |
| --------------- | ----------------------------------------------------- | ------------------------------------------------------- |
| Canada          | [send.devolutions.com](https://send.devolutions.com/) | Default for standalone use and for most product setups. |
| Europe (France) | [send.devolutions.eu](https://send.devolutions.eu/)   | Use this when the ciphertext must stay in the EU.       |

The picker shown in products lists **Canada** and **Europe** only.

{% hint style="info" %}
A Send link is bound to the region that created it. A Canada link starts with `https://send.devolutions.com/receive/`. A Europe link starts with `https://send.devolutions.eu/receive/`. Recipients must open the exact URL they received.
{% endhint %}

## Standalone

Open the site for the region you want and create the link there:

* Canada: [send.devolutions.com](https://send.devolutions.com/)
* Europe: [send.devolutions.eu](https://send.devolutions.eu/)

No account is required. See [Devolutions Send Standalone](/send/devolutions-send-standalone.md).

## In Devolutions products

Set the region once at the workspace. Connected clients inherit it.

### Devolutions Cloud

Administrators set the region in ***Administration*** – ***System settings*** – ***Advanced***.

### Devolutions Server

Administrators set the region in ***Administration*** – ***System settings*** – ***Secure message***.

### Remote Desktop Manager

* A **Devolutions Cloud** or **Devolutions Server** workspace uses the Send region from the workspace ***System settings***.
* A **local** or **SQL** workspace: go to ***File*** – ***Settings*** – ***Tools*** – ***Devolutions Send*** to choose **Canada** or **Europe**.

Administrators can also force a region with the `ForceDevolutionsSendRegion` Group Policy. That policy overrides both the workspace system setting and a local picker. See [Apply policies (GPOs)](https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/apply-policies-gpos).

### Devolutions Password Manager

When the app is connected to a Cloud or Server workspace, it uses that workspace region. For standalone use, set the region in ***Settings*** – ***General***.

## What the region does not change

* Client-side encryption, passphrase, duration, and view-limit options stay the same.
* Standalone Send remains free, with no license and no required sign-up.
* File attach limits stay at 1 MB for guests and 30 MB for a Devolutions Account or an authenticated Server or Cloud user.


---

# 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/choose-a-region.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.