Why Email Is Not Secure for Sharing Sensitive Info
Email is not secure for passwords, API keys, or private data because every message is copied onto servers you do not control and kept there, readable by the provider, for as long as anyone keeps it. Encryption in transit does not change that. The safer habit is to keep the secret out of the email entirely and send a link that stops working once it has been read.
How Email Actually Works
When you send an email, it does not travel directly from your device to the recipient. It passes through a series of SMTP (Simple Mail Transfer Protocol) relay servers. Your email client sends the message to your provider's outgoing server, which forwards it to the recipient's incoming server, which stores it until the recipient retrieves it.
At each hop, the message may be stored temporarily or permanently. TLS encryption protects messages in transit between servers that support it, but there is no guarantee that every server in the chain does. More importantly, TLS ends at each server: once the email arrives, it is stored on both the sender's and the recipient's mail servers in a form the provider can read.
The Specific Risks
Stored Where the Provider Can Read It
Large providers encrypt mailboxes at rest, but with keys they hold themselves. That protects against a stolen hard drive, not against the provider. Administrators, attackers who breach the system, and law enforcement with a warrant can all read what is in your account. Features like spam filtering, search, and smart replies work precisely because the provider can process the content of every message.
Forwarding and Uncontrolled Distribution
Once you send an email, you lose all control over it. The recipient can forward it to anyone, and you will never know. In corporate environments, emails are routinely forwarded to assistants, team members, or external partners. A password sent via email can end up in dozens of inboxes.
Indefinite Retention
Emails persist essentially forever. Even if you delete an email from your inbox, it likely exists in the recipient's inbox, in server backups, in compliance archives, and in any forwarded copies. Many organizations retain email for years, sometimes indefinitely, for legal and regulatory reasons.
Data Breaches
Email accounts are among the most frequently breached digital assets. The "Collection #1" breach disclosed in 2019 exposed 773 million email addresses and 21 million unique passwords. Every credential, API key, or piece of sensitive data ever sent through a compromised account becomes exposed in a breach.
Phishing and Account Compromise
Email is the primary vector for phishing attacks. If an attacker gains access to an email account, they have access to the entire history of sent and received messages, including any sensitive information shared through it. Searching a mailbox for "password" is usually one of the first things an attacker does.
What About Encrypted Email?
Solutions like PGP and S/MIME exist but have seen minimal adoption due to their complexity. Both require the sender and recipient to manage encryption keys, which is impractical for most users. Services like Proton Mail make end-to-end encrypted email easier, but only fully when both parties use the same service. Even then, the subject line and who emailed whom remain visible, and the message still sits in the recipient's inbox until someone deletes it.
Better Alternatives for Sensitive Information
The right replacement depends on what you are sending and how often. Here is where each option fits.
| What you are sending | Better option | Why |
|---|---|---|
| A password or key someone needs once | Better option: Self-destructing link | Why: The secret is deleted after reading, so a later mailbox breach finds only a dead link. |
| Credentials a team uses every day | Better option: Password manager with sharing | Why: Access is controlled, audited, and revocable when someone leaves. |
| An ongoing private conversation | Better option: End-to-end encrypted messenger | Why: Signal and similar apps keep message content away from the provider. |
| Signed documents or legal records | Better option: Email is fine | Why: Some records are meant to be kept. Email is a filing system, not a vault. |
For one-off secrets, a one-time link is the most practical fix because it still works over email. Instead of pasting the secret into the message body, you send a link the recipient opens once. After reading, the content is permanently destroyed. Even if the email containing the link is later compromised, the link leads nowhere. For a full team workflow, see how to share passwords safely with your team.
Stop Sending Sensitive Data Over Email
The next time you are about to paste a password, API key, or private message into an email, consider using SneakNote instead. Create a note that is encrypted in your browser and self-destructs after reading, with no account needed. It takes seconds and eliminates the risk of that information sitting in an inbox forever.