How I Built Plausible Deniability Into a Browser Notepad

I've been building is a distributed randomness beacon that publishes a new public value every few seconds on a fixed schedule. . Everything is zero-knowledge, client-side, and works without an account. Your passphrase is the only key. There is no password reset, because there is nobody on the server side who could reset it.

Limits (honest)

Plausible deniability defends against an adversary with your ciphertext plus maybe one passphrase. It does not defend against keyloggers, screen recorders, or someone watching your behaviour over time. Your decoy has to be believable — an empty decoy notebook is worse than no deniability.

Try it

· MIT licensed · self-hostable.

Full design doc with threat-model comparisons to VeraCrypt, ProtectedText, and Standard Notes: plausible-deniability-hidden-volumes-explained.

If you spot a hole in the design, tell me — the only way to find flaws in a crypto scheme is for people smarter than me to look at it.