Last March, an IT administrator at a regional hospital emailed a new hire's VPN credentials to their personal Gmail address. The subject line read "Your login details." The password was in the body. Plain text. No encryption. That email now lives in three places: the sender's sent folder, the recipient's inbox, and the hospital's Exchange server backup tape. Nobody will ever delete it on purpose. It will sit there for seven years until the backup rotation finally expires.
This is how most organizations share passwords. It is broken.
Why Email Is the Wrong Tool for Password Sharing
Email was never designed to be private. Every message you send passes through multiple servers before it reaches the recipient. Each hop can be logged, cached, or intercepted. Even with TLS in transit, the message sits unencrypted at rest on every server it touches.
The numbers are grim. A 2024 Verizon Data Breach Investigations Report found that 68% of breaches involved a human element — someone clicking, someone mis-sending, someone reusing a password they received in an email. The problem is not just attackers. The problem is the medium.
Think about what happens when you email someone a password. That message is now permanent. You cannot unsend it. You cannot revoke access. The recipient can forward it, screenshot it, or leave their inbox open on a shared computer. You have zero control after you hit send.
What a One-Time Self-Destructing Link Actually Does
A one-time link works differently. You type the password or credential into a secure form. The service encrypts the content and generates a unique URL. You share that URL with the recipient through any channel — Slack, SMS, even email. The key difference is what happens next.
When the recipient clicks the link, the content is decrypted and displayed in their browser. Then the server deletes it. Immediately. Not after 30 days. Not after the recipient closes the tab. Right then. If someone else finds that link later — in a chat log, in an email thread, in a browser history — they see nothing. The message is gone.
This is called a one-time access pattern. The link works exactly once. After that first view, it is dead.
Real Scenarios Where This Matters
Consider a freelance designer handing off a WordPress admin account to a client. The client needs the password once, changes it immediately, and never needs the original again. A self-destructing link is perfect. The designer sends the link, the client reads the password, the link dies. Even if the client's email is compromised a week later, the password is not there.
Or think about a DevOps engineer who needs to share a database root password with a contractor for a one-time migration job. The contractor needs access for two hours. After that, the password gets rotated. But the original shared password is still sitting in a Slack DM. With a temporary password sharing link, the message self-destructs on first read. The Slack message contains a dead link. Useless to anyone who finds it.
Another scenario: a law firm needs to send a client portal password to a new client. The client is not tech-savvy. They will check email on a hotel business center computer. A one-time link means the password is not sitting in their inbox when the next hotel guest sits down at that same machine.
How to Share a Password One Time Link Step by Step
The process takes about 20 seconds. Here is what it looks like with NovelCrypt's self-destructing notes:
1. Navigate to the secure sharing page 2. Type or paste the password into the message field 3. Optionally set an expiration time as a backup (e.g., 24 hours) in case the link is never opened 4. Click create — the service generates a unique URL 5. Copy the link and send it to the recipient through any channel 6. The recipient opens the link, reads the password, and the content is destroyed
That is it. No account required. No password to remember. No persistent storage.
The backup expiration matters. If you send a link and the recipient never opens it, you do not want it sitting around forever. A 24-hour fallback expiration ensures the link dies even if nobody clicks it.
What to Avoid When Sharing Passwords
Do not paste passwords into Jira tickets. Do not drop them in Confluence pages. Do not put them in Google Docs with "anyone with the link" access. All of these create permanent copies that outlive their usefulness by years.
Do not use "secure" email services that claim to encrypt messages if the recipient still has to set up an account, download an app, and manage decryption keys. The friction means people will fall back to plain text email. The security has to be invisible.
Do not reuse the same password across services just to avoid sharing a new one. If one service leaks it, every service using that password is compromised. Generate a unique password, share it once with a self-destructing link, and move on.
The Threat Model: What This Protects Against
A one-time self-destructing link does not protect against an attacker who is actively intercepting the recipient's network traffic in real time. If someone is performing a man-in-the-middle attack on the recipient's browser session, they could theoretically capture the decrypted content during the brief window it is displayed.
What it does protect against is the far more common threat: after-the-fact discovery. The intern who finds an old email. The attacker who breaches an email archive. The coworker who scrolls through a shared Slack channel. These threats depend on the password persisting somewhere. A self-destructing link removes that persistence.
For truly high-stakes credentials, combine the one-time link with a separate channel for any additional authentication factor. Send the password through the self-destructing link and the username through a phone call. Splitting the credentials across channels means an attacker would need to compromise both to gain access.
Making Secure Password Sharing a Habit
The hardest part of any security practice is adoption. If the tool is cumbersome, people revert to email. If the tool requires an account, people revert to email. If the tool takes more than 30 seconds, people revert to email.
Self-destructing links work because they are faster than email. You paste, you click, you copy. The recipient clicks, reads, and the content vanishes. No friction. No learning curve. No reason to fall back to the old way.
Start using them for every credential you share. Every API key. Every database password. Every temporary access code. Once it becomes routine, you will wonder why anyone ever emailed a password.,