Use cases

One-time, end-to-end encrypted links fit more situations than passwords. Here are the ones we hear about most.

Last updated: 2026-11-03

DevOps & Engineering: Share credentials and keys, not chat history. API keys, database passwords and private keys end up in chat threads and tickets, where they stay searchable for years. A one-time link keeps them out.
Privacy-conscious users: Share something without leaving a trail. Some things should be shared without anyone, including the site in the middle, learning more than they must.
IT & Onboarding: Hand out first-day credentials safely. A new starter needs a password, a VPN profile and the Wi-Fi key. None of them should sit in an email thread afterwards.
Legal & Regulatory: Send sensitive records without leaving copies. A record sent as an email attachment stays in two mailboxes and every backup of them. A link that is deleted after reading doesn’t.
Personal: Everyday secrets, simply. Not every secret is a production database key. Most are a Wi-Fi password, a door code or a document you’d rather not leave in a chat.
Misc: Gift codes and surprise reveals. A one-time link is a nice way to deliver something that should be seen once: a gift code, a surprise, the next clue.

Wondering how this compares with other tools? See how shhnote compares.