Why you should never send passwords by email or chat
4 min read
Sending a password in an email or a chat message feels harmless: the recipient needs it now, and the conversation is private. In practice, the message becomes a permanent copy of your credential in several places you do not control.
Where the copy ends up
- Mail and chat servers. Messages are stored on the provider's servers and usually backed up.
- Every device. Phones, laptops and tablets of both sender and recipient keep local copies and notification previews.
- Search indexes. Anyone who gains access to a mailbox can search for words like "password" or "login" and find every credential ever sent.
- Forwards and shared channels. A message can be forwarded, quoted in a reply, or posted in a channel with dozens of members.
- Archives and retention rules. Companies often keep messages for years for compliance, long after the password should have been forgotten.
Why this matters
Most account takeovers do not involve breaking encryption. They involve finding a credential that was already lying around. A single compromised mailbox can expose every password that was ever sent to it, and the owner will not notice, because nothing was "stolen" from the sender's side.
A better way
The safest habit is to make sure a credential exists in as few places as possible, for as little time as possible:
- Use a password manager's sharing feature when both sides have one.
- Otherwise, use a one-time link: the secret is encrypted in your browser, can be opened once, and is deleted afterwards.
- Send the link and any extra context (such as which system the password is for) in separate messages, ideally in different channels.
- Choose the shortest expiry that works. An hour is often enough.
- Change the password after the recipient has used it, if it is a long-lived account.
None of this is difficult, and it removes the most common way credentials leak: the thread that nobody remembers to clean up.