Paste the secret to send
01Fits a server password, database connection string, API Key, or recovery code. 32 KB per item. For a whole file, use File Encryption Box.
01 / Burn-Link
Burn-Link
One-time encryption to share a password
Open and use it—the other person needs no account either. Paste the password, API Key, or recovery code you need to send. This tab builds a one-time encrypted link with AES-256-GCM; the server receives ciphertext only. The decryption key sits after # in the address and does not enter the HTTP request. Better than pasting a passphrase into WeChat for a one-time handoff.
Encrypt locally
Key after #
Burns after read
No account
0 / 32,768 bytes
Unread links are also deleted from the server when they expire
1–10 reads; default burns after 1
Send the other person the full link including #. Without the fragment, ciphertext on the server cannot be decrypted. A lost link cannot be recovered.
Full link
Query
The server can see the ciphertext id, not the key.
Fragment key
Exists only in the browser; it is not sent with the HTTP request.
A lost link cannot be recovered. After the set read limit, the ciphertext is hard-deleted.
[ 02 ] How to send
How to share a password with Burn-Link: paste the secret, create a one-time encrypted link, and send the full string including #.
Set expiry and read limit
02Default is 24 hours and burns after 1 read. You can also pick 1 hour, 7 days, or delete only after a read. Read limit is 1–10.
Send the full link
03Copy the key after # as well. Without the fragment, ciphertext on the server cannot be decrypted. A lost link cannot be recovered.
[ 03 ] How it travels
How a one-time link keeps plaintext off the server: it only stores a piece of ciphertext, then deletes it after a successful read or expiry.
Generate a key and encrypt locally
01The browser draws a 256-bit random key with Web Crypto, then encrypts the text you typed with AES-256-GCM. Plaintext appears only in this tab; it is not sent as a request body.
The server receives ciphertext only
02Upload fields are ciphertext, expiry, and max reads. After an unguessable id is returned, this page attaches the key as the fragment on s.html?id=…#key.
After they read it, the ciphertext is deleted
03The recipient opens the full link, takes the key from the # fragment, and decrypts on this device. After the read count you set, the server hard-deletes the ciphertext; opening again shows it has been burned. The recipient does not need to sign up either.
[ 04 ] Verifiable
What Burn-Link can do—and what it cannot stop
Burn-Link only answers how to send a short secret once. The algorithm, where the key lives, the size limit, and what it cannot do are all on this page.
Algorithm
AES-256-GCM
Uses AES-256-GCM. Ciphertext format is Base64(12-byte IV + ciphertext + 16-byte tag). Computation runs in the browser Web Crypto API.
Key location
# fragment
The key lives only in the URL # fragment, as s.html?id={id}#{key}. The query string has the id only; do not move the key to ?key=—that would land in access logs.
Size and expiry
32 KB
Each item is capped at 32 KB—enough for a passphrase, a key fragment, or a short note. Expiry can be 1 hour, 24 hours, 7 days, or burn after read only. Read count is 1–10. For a whole file, use the File Encryption Box.
Cannot do
Cannot stop screenshots
It cannot stop the recipient from copying, screenshotting, or forwarding. There is also no server-side plaintext backup. It reduces repeat opens and long-term plaintext on the server; it does not replace trust.
[ 05 ] FAQ
Common Burn-Link questions
Burn-Link is a one-time encrypted link: you encrypt a password or API Key on this device with AES-256-GCM; the server stores ciphertext only. The decryption key is appended after
# in the address bar and never enters the HTTP request. After the recipient opens it and the set count is reached, the ciphertext is deleted and cannot be read again.No. The text is encrypted in the current tab with AES-256-GCM; the server receives ciphertext only. The decryption key sits in the link's
# fragment. The browser does not put it in the HTTP request, and it does not appear in access logs.No. Both the create page and the read page are ready to use. The recipient opens the full link that includes
# and decrypts on this device. After the set read count, the server deletes the ciphertext; opening again shows it has been burned.No. It reduces repeat opens and the risk of the server keeping plaintext for a long time. It cannot block copy, screenshots, or forwards. Use it only for a one-time handoff when you trust the recipient to stop after reading. A lost link cannot be recovered.
Chat history and email keep plaintext for a long time. Burn-Link turns the password into a one-time encrypted link: the server stores ciphertext only and deletes it after the recipient opens it and the read limit is reached. It still cannot block screenshots, but it is a better one-time handoff than pasting a passphrase into WeChat.
[ 06 ] Next
Sent
then
→
Send a short text once from this page. Longer prep or a whole file can stay in the browser too. Plaintext, keys, and files are not uploaded by default.