Zero-knowledge note: share a secure note
Create an encrypted note and share it as a temporary link. Encryption happens in your browser; the key stays in the URL fragment after # and is never sent to the server.
What zero-knowledge gives you
- Confidential note sharing over a temporary link
- Client-side encryption, key stays in the fragment
- Optional read-once and expiry
- Verifiable zero-knowledge handling (F12)
Zero-knowledge, stated precisely
Zero-knowledge is used loosely across the industry, so it is worth being exact. Here it means the server never receives the material needed to read your note: encryption happens in the browser, and the key travels in the URL fragment, which is not part of any request the browser sends.
The practical consequence is that a compromised database, a curious administrator or a legal order all run into the same wall. What can be produced is an encrypted blob and technical metadata such as timestamps — not the note itself.
This is a claim you can test rather than trust. Open the network tab, create a note, and check every outgoing request for the part of the URL after the #. It is not there, and that is the whole basis of the design.
Frequently asked questions
What is a zero-knowledge note?
A note encrypted in your browser before upload. The server only stores ciphertext and needs neither plaintext nor the key, which stays in the URL fragment.
How do I verify it?
Open DevTools with F12, go to the Network tab and load a link with a #fragment. The part after # should not appear in any request URL.
Related pages
Open the secure app at pcpx.one and create your encrypted link.