Send a self-destructing message
Send a message that destroys itself after reading: encrypted client-side, readable once and irreversibly deleted on open. No account, no app — the key stays in your browser.
What zero-knowledge gives you
- No lasting traces in chats or inboxes
- Read-once (burn-after-read) link
- Optional expiry for unread messages
- Zero-knowledge: server never sees plaintext
What self-destructing actually means here
Self-destructing is often marketing shorthand for hiding a message in an interface while the server keeps a copy. Here it describes a deletion that is meaningful because of what the server had in the first place: only ciphertext, never the key.
After the first successful read the stored object is removed. A second attempt on the same link finds nothing — which doubles as your signal that someone already opened it. If the link is never used, the expiry you picked (one hour to seven days) clears it regardless.
The honest limit is the window before the first read. Anyone who obtains the complete link during that window can trigger the read and see the content. For messages where that risk is unacceptable, recipient approval closes the gap by requiring your explicit release.
Frequently asked questions
How does a self-destructing message work?
The message is encrypted in your browser and shared as a one-time link. After the first open the server deletes the encrypted content immediately; optionally it expires after a chosen time.
Can it be recovered after reading?
No. After the single retrieval the encrypted data is deleted server-side, and without the key from the fragment it was never readable anyway.
Related pages
Open the secure app at pcpx.one and create your encrypted link.