Technical analysis of Privnote's security model, limitations, and best practices.
Privnote uses client-side encryption, meaning your note is encrypted in your browser before being sent to Privnote's servers. The encryption key is embedded in the URL fragment (the part after the # symbol). Because URL fragments are not sent to servers in standard HTTP requests, Privnote's servers receive only the encrypted ciphertext — not the key needed to decrypt it.
When the recipient opens the link, their browser extracts the decryption key from the URL fragment and uses it to decrypt the ciphertext retrieved from Privnote's servers. The decryption happens entirely in the browser. Privnote's servers never have access to the plaintext content of your notes.
The client-side encryption model provides meaningful protection against server-side breaches. Even if Privnote's servers were compromised, attackers would only obtain encrypted ciphertext — not readable note content. This is a genuine security advantage over services that encrypt data server-side.
However, this model has important limitations. You are trusting that Privnote's JavaScript code actually implements this encryption correctly and has not been tampered with. Since Privnote is not open-source, this cannot be independently verified by the public.
The most significant documented security threat for Privnote users is phishing clone sites. These sites serve malicious JavaScript that intercepts notes before encryption, allowing the operator to read all note content. The most documented example is privnotes.com, which has been observed modifying cryptocurrency wallet addresses in notes — a man-in-the-middle attack that causes financial loss.
Protection is simple: always navigate directly to privnote.com by typing it in your browser's address bar. Never follow links to Privnote from untrusted sources. Bookmark the official site.
Self-destruction only prevents re-access via the URL. It does not prevent the recipient from taking a screenshot, copying the text, or recording their screen. Once the note is displayed, the information is in the recipient's control. Only send Privnotes to people you trust.
If someone intercepts the Privnote URL before the intended recipient opens it, they can read the note. The intended recipient will then find the note already destroyed. Mitigate this by using password protection and sending the password through a completely separate channel.