Encrypted text sharing, without an account
Sometimes you need to send something more sensitive than a note — a password, an API key, a private message. DropText's client-side encryption means the text is scrambled in your browser before it's ever sent anywhere, using AES-GCM with a 256-bit key.
How the encryption works
- Your browser generates a random AES-GCM key locally.
- Your text is encrypted with that key before the network request is made.
- Only the encrypted ciphertext is stored — the key is embedded in the URL fragment (after the
#), which browsers never send to a server. - Whoever opens your link decrypts it locally, in their own browser.
This means DropText's database only ever holds ciphertext it cannot read — not a "we promise not to look" policy, but a structural guarantee.
When to use it
- Sending a one-time password or recovery code to a teammate
- Sharing an API key or secret without pasting it in Slack/email
- Sending sensitive notes you don't want sitting in plaintext anywhere
Pair it with burn after read for a message that both encrypts itself and deletes itself the moment it's opened.