What are you sending?
The encryption is the same either way. The only difference is whether a proof survives it.
Just a message
Encrypted in your browser, self-destructing, gone. Like any ephemeral paste, done properly.
A message I will be able to prove
Same message, same destruction. The hash also goes to Polygon and Bitcoin, so in ten years you can still prove what you sent and when.
Both ways: AES-256-GCM in your browser · the key never reaches us
How it works
Your browser encrypts it
The key is generated on your device and travels in the link, after the #. Browsers never send that part, so it does not reach us. We hold noise.
You choose the lifetime
One hour to thirty days. One read, several, or unlimited. A password, if you want one, which also stays in your browser.
It destroys itself
On the read, or at expiry. We delete the bytes, and we say plainly that we cannot prove we did.
The proof stays
If you anchored it, the hash is on Polygon and Bitcoin. Reveal the link and anyone can verify what you sent and when, without trusting us.
What we can prove, and what we cannot
Everyone in this category sells “proof of destruction”. It does not exist. Here is the honest table.
We do not sell proof of destruction. We sell proof of transmission, which is real, and which is the thing you actually need when someone claims you never sent it.