Account

What new tool do you want?

Security & Privacy

Share a Password Securely (One-Time Link)

Share a password or API key with a one-time, end-to-end encrypted link that self-destructs after viewing — instead of pasting it into email or chat.

How to use

  1. 1Enter (or generate) the password, plus optional site and username.
  2. 2Create the link — it works once and expires within a day by default.
  3. 3Send the link; send the username through a different channel.

Frequently asked questions

Why not just email the password?

Emails and chats are stored forever in inboxes, backups and logs. A one-time link leaves nothing behind after it's opened.

Is it encrypted?

Yes — in your browser with AES-256-GCM. The key never reaches our server.

What if someone opens it before the recipient?

The recipient will see it's already been viewed — a clear sign to change the password.

How the server can host it without being able to read it

Your browser generates a random AES-256-GCM key, encrypts the password locally, and sends only the ciphertext to the server to store. The key itself never gets sent — it's packed into the generated link after the "#" character (a URL fragment), and fragments are a part of the URL that browsers never transmit to a server by design, even when you click a fragment-containing link. So the server ends up storing an encrypted blob it has no way to decrypt; the decryption key only ever exists in the two browsers that see the full link — yours, briefly, and the recipient's.

A worked example of the view-burning mechanism

Create a link set to "Once" and send it. When the recipient opens it, the page first calls a read-only check (does this ID still exist?) without consuming anything, which is why an accidental double-tap on the link doesn't destroy it. Only pressing "Reveal password" fires the actual read request, which the server treats as consuming one view — it returns the ciphertext once and, if that was the last allowed view, deletes the stored record immediately afterward. Anyone who opens the same link again gets "this password link has already been viewed" rather than the password itself, because there's nothing left on the server to return.

Why chat-app link previews don't burn your one view

Messaging apps often auto-fetch a preview of any link you paste, which could in theory open a one-time note before the real recipient does. It doesn't here, because the preview fetch only loads the page's HTML — it doesn't execute the page's JavaScript or click the "Reveal" button, and burning a view requires that explicit action. The existence check that does run automatically on page load is read-only and doesn't consume anything, so a link preview can confirm the note exists without destroying it.

Why this beats pasting a password into email or chat

A password typed into an email or Slack message lives forever in that account's history, every backup of it, and every device that syncs it — exactly the kind of long-lived copy you don't want for a credential. A one-time link leaves nothing meaningful behind after it's read: the server deletes the ciphertext, and the key was never stored anywhere to begin with. Pair it with the tool's own advice — send any username through a separate channel — and an attacker who intercepts just the link still doesn't have a complete, usable credential.

Related tools

More: Security & Privacy