Devolutions Send Standalone

Devolutions Send Standalone features a secure method to generate a link to share secrets instead of using insecure email to send sensitive data.

Despite sharing the same underlying architecture, slight differences exist between the feature set of the standalone and in-app versions of Devolutions Send.

• Unique short-lived (24-hour) link encrypted on the client side.

• 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.

1. Go to the Devolutions Send Standalone website.

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.

4. Add a Passphrase for extra security (mandatory if the recipient does not have a Devolutions Account, optional otherwise).

5. Read and agree to our online services terms.

6. Click on Create secure link to get your in-browser encrypted, 24-hour short-lived link.

1. Click on the received encrypted link.

   A Devolutions Send Standalone secret will always start with `https://send.devolutions.com/receive/`.

2. Enter the Passphrase the sender provided (if necessary) and click on Decrypt.

3. Click on Unmask text.

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

   

4. Once done, click on Delete Now.

5. Click Yes.

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.

• Devolutions Blog - How organizations can safely share confidential information with Devolutions Send