diff --git a/_articles/send/send-encryption.md b/_articles/send/send-encryption.md
index c0377f67..ec71f4a4 100644
--- a/_articles/send/send-encryption.md
+++ b/_articles/send/send-encryption.md
@@ -35,3 +35,18 @@ When you access a Send link:
 6. The Web Vault client locally decrypts the Send using the encryption key.
 
    {% callout success %}If your send is [password-protected]({{site.baseurl}}/article/send-privacy/#send-passwords), decryption of the Send will be **blocked by authentication**. The server validates the password and only returns the Send if the password is correct. This should not be confused with the password being used for decryption.{% endcallout %}
+
+## Send Security
+
+When transmitting a Bitwarden Send link, there are optional steps you can take for additional security:
+
+1. Add a password to the Send and share the password via a separate channel.
+2. Send the link without the key (everything before the last forward slash) and send the key via a separate channel.
+3. Leverage both of the above options.
+
+{%callout success%}
+
+When reassembling a Send URL, be sure to include both the Send ID and the encryption key.
+
+Example: `https://vault.bitwarden.com/#/send/send_id/encryption_key`
+{%endcallout%}