Send a note that
burns after reading
Share a message, password, or snippet that permanently deletes itself the instant it's opened. Add a password and expiry for an extra layer. Free and anonymous.
One view only
The note is wiped from the server the moment it's read. There's nothing left to leak, cache, or subpoena afterwards.
Optional password
Require a password before the note reveals itself, so even the right link needs the right key.
Expiry backup
Set a time limit too — if the note is never opened, it still self-deletes automatically.
When to use a burn-after-reading note
Some things shouldn't linger in a chat history or inbox. A burn-after-reading note is perfect when you want to hand something over once and have it disappear:
- Sending a teammate a temporary password or API key.
- Sharing a private message you don't want stored anywhere.
- Passing along a recovery code or one-time link.
- Delivering sensitive config that shouldn't sit in Slack forever.
How it works
When you set a paste to burn after reading, KuickPaste deletes the record from the database during the very first successful view. The reader sees it once; any later visit to the same link returns a “not found” page because the content no longer exists. Pair it with a password and the reader must authenticate before the single reveal happens.
Burn-after-reading is about minimizing exposure, not replacing dedicated secret managers. For anything long-lived, rotate the secret after you share it.
You can also set a plain unlisted paste with an auto-expiry if you'd rather it last a fixed time instead of a single view.
Burn-after-reading FAQ
What is a burn-after-reading note?
It is a paste that is permanently deleted the moment it is opened. The first person to view it sees the content once; after that the link shows a “Paste not found” message because the data is gone.
How do I create a self-destructing message?
Paste your message on KuickPaste, set Privacy to “Burn after reading”, and press Create Paste. Share the link or 6-character code. As soon as the recipient opens it, the note is destroyed.
Can I add a password too?
Yes. Combine burn-after-reading with a password so the recipient must enter the password to reveal the note — and it still self-destructs after that single view.
Is this secure enough for passwords and API keys?
Burn-after-reading is great for reducing exposure of one-time secrets, and pastes are served over HTTPS. For long-lived credentials, treat it as a convenience layer and rotate the secret after sharing as a best practice.
What happens if the link is opened by the wrong person first?
Whoever opens it first triggers the burn. If a note is opened unexpectedly, assume it was seen and re-issue the secret. Adding a password reduces the risk of accidental exposure.
Share something that disappears
Create a self-destructing note in seconds — free, no account.
Create a burn note