A one-time link is a simple idea: you send a link, the recipient opens it once, and the content is gone. It is a good fit for passwords, access codes and screenshots that should not sit in a chat history forever. But the method only works well if you use it with a few habits in mind. These seven rules cover the most common mistakes.
With most one-time link tools, the link contains everything needed to open the message. Anyone who sees the full link can read it, so do not post it in group chats, tickets or shared documents where several people have access.
Pick a channel where you are confident about the recipient: a direct message, not a channel with dozens of members. Double-check the contact before you press send.
Tell the recipient what the link is for and what they should do with it, for example “Wi-Fi password for the guest network, please open it on your phone.” Keep the account name, the service and the secret from appearing together in one place.
Ask the recipient to confirm that they could read the message. If they report that the link no longer works or shows a deleted note, treat the secret as exposed: somebody else may have opened it first. Change the password and send a new one.
A message that deletes itself cannot stop the recipient from photographing the screen. Share one-time links only with people you trust to handle the content responsibly.
If a team needs ongoing access to a login, use a password manager with sharing and revocation features. One-time links solve the hand-over, not the lifecycle of a credential. Rotate temporary passwords as soon as the recipient has logged in.
Encryption protects the message in transit and in storage, but the text must be readable on the screen of the sender and the recipient. Malware on either device can capture it. Keep the operating system and browser updated and avoid opening secrets on shared or public computers.
dw Secret Notes follows this approach: the message is encrypted in the browser, the server stores only the encrypted content, and the note is deleted after it has been read. A technical description including the limits of the method is on the How it works page. For a comparison of other ways to share passwords, see How do I send a password securely? 5 methods compared.
More programs by the developer are available at tools-for-you.de.