Sooner or later you have to give someone a password. A new hire needs the Wi-Fi admin login, a contractor needs a staging account, your partner needs the streaming password. The fastest way is to paste it into whatever app you already have open. That's also the worst way.
This guide covers why, and what to do instead.
Why email, Slack and texts are a bad place for passwords
The problem isn't usually that someone intercepts the message in transit. Most of these services encrypt traffic. The problem is that the message never goes away.
- It's stored in many places. Your sent folder, their inbox, both phones, backups, and the provider's servers.
- It's searchable. Anyone who gets into either account later can search for "password" and find it in seconds. Attackers do exactly this after a phishing attack.
- It outlives the password's purpose. The contractor finishes in March. The password sits in their inbox for years.
- It gets forwarded. Messages get forwarded, screenshotted and pasted into tickets.
A password that's been sent in plaintext should be treated as known by anyone who could ever read that conversation.
The options, from best to worst
1. Don't send it: give access instead
The most secure password is one you never share. Many services let you invite someone with their own account: Google Workspace, GitHub, AWS IAM, most SaaS admin panels. Each person has their own login, you can revoke them individually, and you get an audit log. If an invite is possible, use it.
2. Share it through a password manager
If you and the recipient use the same password manager (1Password, Bitwarden, Dashlane, a company vault), share the item there. It's encrypted, it can be revoked, and it updates for them when you rotate it. This is the right answer for credentials a team uses on an ongoing basis.
3. Send a one-time, self-destructing link
For everything else (one-off handoffs, people outside your organization, someone without your password manager) use a one-time secret link. You paste the password into a tool like Dropzone, it gets encrypted, and you get a link. The recipient opens the link once, sees the password, and the data is permanently deleted.
What you send over email or Slack is now a link that stops working after one use. If someone finds it in that inbox next year, it shows nothing.
4. Split it across two channels
If you have no tools at all, send half the password by email and half by text message. An attacker would need both accounts. It's clumsy, and both halves still sit around forever, so treat it as a last resort.
5. Plain email or chat
Don't. If you already did, change the password.
How to send a password with a one-time link
Using Dropzone (no account needed):
- Go to dropzone.sh and paste the password into the text box.
- Leave destruct on download turned on.
- Copy the link and send it to the recipient over any channel.
- They open it and click Reveal. The password is shown once and deleted from Dropzone's servers.
A few details make this safer than it sounds:
- Encryption happens in your browser. Dropzone's servers store only encrypted bytes. The decryption key is in the part of the link after
#, which browsers never send to servers. - Link previews don't burn it. Slack, Teams, iMessage and email scanners fetch links to build previews. Dropzone only opens a drop when a person clicks Reveal, so the recipient still gets it.
- You can tell if someone got there first. If the recipient sees "already opened", someone else opened the link. Assume the password is compromised and change it.
Tips that make any method safer
- Send the username separately, or not at all if the recipient already knows it. A password without the account it belongs to is much less useful.
- Don't say what it's for in the same message. "Here's the AWS root password: [link]" tells an attacker exactly what to prioritize.
- Ask the recipient to change it if the account supports personal passwords.
- Rotate shared passwords when people leave. Sharing safely doesn't help if the password stays valid forever.
- Use a password manager for anything long-lived. One-time links are for handoffs, not storage.
FAQ
Is it safe to send a password over WhatsApp or Signal? Signal and WhatsApp are end-to-end encrypted, which is better than email. But the message still lives on both phones and in any backups until someone deletes it. Disappearing messages help. A one-time link is still cleaner, because it only works once.
Is it safe to email a password if the email is encrypted? Encryption in transit protects the message on the way. It does nothing about the copy sitting in both mailboxes afterwards, which is where most leaks come from.
What if the link gets intercepted? Whoever opens a one-time link first gets the contents. If an attacker opens it, your recipient will see that it was already opened, so you'll know to change the password. That's much better than an email you'd never know was read.
How long does the link last? On Dropzone, a single-use link that's never opened is deleted after 90 days. If you turn off destruct on download, the link can be opened repeatedly and expires after 30 days.
Next: if you're sharing API keys or .env files rather than a login, read How to share API keys securely.