> 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/devolutions-send-standalone.md). # Devolutions Send Standalone Devolutions Send Standalone lets you generate an encrypted shareable link in Canada or Europe without installing any Devolutions product. [Devolutions Send Standalone](https://devolutions.net/devolutions-send/) is a free way to generate an encrypted link and share secrets instead of using insecure email. No Devolutions product and no account are required. Standalone Send is available in two regions. Open the site for the region where the encrypted payload should be stored: * Canada: [send.devolutions.com](https://send.devolutions.com/) * Europe (France): [send.devolutions.eu](https://send.devolutions.eu/) See [Choose a Devolutions Send region](/send/choose-a-region.md). ### Features Despite sharing the same underlying architecture, slight differences exist between the feature set of the standalone and in-app versions of Devolutions Send. * Unique link encrypted on the client side. * Valid for a customizable amount of time. * Optional protection via a client-provided passphrase. * Users may be non-Devolutions users (not linked to a Devolutions Account). * Character limit of 10 kb. * A sender email is required and stored with the GUID as part of the “payload” stored in the database. * Encrypted payload stored in Canada or Europe, depending on the site you open. ### How to use Devolutions Send Standalone 1. Go to the standalone site for the region you want: [Canada](https://send.devolutions.com/) or [Europe](https://send.devolutions.eu/). 2. Enter the ***Sender email***, which is required and stored with the GUID as part of the “payload” stored in the database. 3. Enter your ***Secure message*** to encrypt. * A file of maximum 1 MB can be added to the secure message as well. This maximum is increased to 30 MB when using a Devolutions Account. 4. Add a ***Passphrase*** for extra security (mandatory if the recipient does not have a Devolutions Account, optional otherwise). * ***Additional security options***: * The ***Link duration*** can be set to 1 hour, 24 hours, 3 days or 1 week. * The ***View limit*** can be set to Unlimited, Single view or Multiple views. The Multiple views option is useful for setting an exact amount of possible views. * It is recommended to enable the ***Allow recipient to delete message*** option. 5. Read and agree to our online services terms. 6. Click on ***Create secure link*** to get the in-browser encrypted link. 7. Click on ***Copy to clipboard*** and send it to the recipient(s). ### How to receive a Devolutions Send Standalone secret 1. Click on the received encrypted link.

A Canada secret starts with https://send.devolutions.com/receive/. A Europe secret starts with https://send.devolutions.eu/receive/. Open the exact URL you received.

2. Click on ***Unmask text***.

Make certain to be in a private setting before reading this message if it contains sensitive information.

3. Enter the ***Passphrase*** the sender provided (if necessary) and click on ***Decrypt***. 4. Once done, click on ***Delete Now***. 5. Click ***Yes***. ### Technical details The core tenant of Devolutions Send is that Devolutions itself cannot decrypt the user's secret. This is accomplished via client-side (browser) encryption through a Rust program compiled to WASM (WebAssembly) in-browser. Therefore, Devolutions does not hold the encryption key and cannot decrypt the data. #### See also * [Choose a Devolutions Send region](/send/choose-a-region.md) * [Devolutions Send product page](https://devolutions.net/devolutions-send/) * [Devolutions Blog - How organizations can safely share confidential information with Devolutions Send](https://blog.devolutions.net/2024/08/how-organizations-can-safely-share-confidential-information-with-devolutions-send/) --- # 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/devolutions-send-standalone.md?ask=&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.