A one-time secret link gives someone one chance to read a password, API key, or private note without leaving it in chat or email history.
Paste the secret, turn on burn-after-read, set a short expiry, and share the generated link. The recipient reads it once; the encrypted paste is then deleted. Use textdrop.sh to make the link in your browser, then share the link instead of the sensitive text.
Burn-after-read is enabled. Your browser encrypts the text before it is stored, then the first successful read deletes it.
Messages and credentials often outlive the moment they were needed. They remain in inboxes, chat exports, backups, and search results, widening the consequences of a future account compromise.
A one-time secret link is for a narrow handoff: a sender encrypts the secret in the browser, the recipient opens it, and the stored ciphertext is removed after the first successful read. It reduces stored copies, but it cannot control a recipient who copies or screenshots what they see.
It is a URL that gives a recipient one opportunity to retrieve a secret. With burn-after-read enabled, the encrypted paste is deleted after the first successful read.
No. It removes the server-stored paste after retrieval, but it cannot stop a recipient from taking a screenshot, copying the text, or using an infected device.
Treat an unexpectedly consumed link as a possible exposure. Do not resend the same secret; rotate or revoke it when possible, then create a new link.
Slack caps messages at 40,000 characters and collapses anything over a few thousand into a snippet. Here is how to share a long log, transcript, or document as a single clean link.
AES-256-GCM, PBKDF2 key wrapping, and what zero-knowledge actually means here.