Devolutions Send Standalone features a secure method to generate a link to share secrets instead of using insecure email to send sensitive data.
The in-app version of Devolutions Send is currently under development and will be progressively deployed in Remote Desktop Manager, Devolutions Server, and Devolutions Hub. More information will come in the future.
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.
Go to the Devolutions Send Standalone website.
Enter the Sender email, which is required and stored with the GUID as part of the “payload” stored in the database.
Enter your Secure message to encrypt.
Add a Passphrase for extra security (mandatory if the recipient does not have a Devolutions Account, optional otherwise).
Read and agree to our online services terms.
Click on Create secure link to get the in-browser encrypted link.
-
Click on the received encrypted link.
A Devolutions Send Standalone secret will always start with `https://send.devolutions.com/receive/`.
-
Enter the Passphrase the sender provided (if necessary) and click on Decrypt.
-
Click on Unmask text.
Make certain to be in a private setting before reading this message if it contains sensitive information.
-
Once done, click on Delete Now.
-
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.