The SneakNote Security Model
SneakNote encrypts every note in your browser, stores only the ciphertext, and never receives the key. Here is exactly what that protects, what the server can still see, and what the guarantee costs you.
Key Facts
- Encryption
- AES-256-GCM, in your browser, with a new random 256-bit key for every note. Required for every note.
- Where the key lives
- Only in the link, after the #. Browsers never send that part to the server.
- Password
- Optional. Stretched with PBKDF2-SHA-256 (600,000 rounds) and used to wrap the key. Never sent to the server.
- When a note is deleted
- By default, the moment it is read. Or on a timer of 5 minutes, 1 hour, 1 day, 1 week or 1 month, during which it can be opened any number of times. A note nobody opens is deleted after 1 year.
- What the server records
- When a note was created and opened, its approximate size, the IP address of each request, and your email if you ask for a notification.
1. Your browser
Generates a key and encrypts the note with AES-256-GCM.
2. The server
Stores only the ciphertext. It never receives the key.
3. The recipient's browser
Takes the key from the link after the # and decrypts the note locally.
End-to-End Encryption
Your note is encrypted in your browser with AES-256-GCM before it is ever sent to the servers. The decryption key lives in the link fragment, the part of the URL after the # symbol, which browsers never transmit to the server. That means the server stores ciphertext I cannot read, and only someone with the full link can decrypt the note.
One-Time Access and Self-Destruction
A note set to self-destruct immediately is deleted the moment it is revealed, so it can only ever be read once. If you choose a timer instead, the note stays available until that timer elapses, which means it can be opened more than once in the meantime — pick Immediately after reading if one-time access is what you need. Either way, deletion is permanent: there is no archive, no trash, and no recovery path. If a note is gone, it is gone for everyone, including me.
Optional Password Protection
You can add a password that the recipient must enter before the note can be decrypted. This protects the contents even if the link is intercepted, an extra layer on top of the encryption key in the URL. I never store this password. The server does store a random salt and a verifier derived from it, used to reject a wrong password before a one-time note is burned. Anyone holding that data could test password guesses offline, slowed by 600,000 rounds of PBKDF2, so use a long, unpredictable password.
What I Do Not Do
- I do not store the plaintext of your notes.
- I do not require an account or collect personal profiles to send a note.
- I do not retain one-time notes after they are revealed, or timed notes after they expire.
- I do not sell your data.
What I Can Still See
Not being able to read your notes is not the same as knowing nothing about them, and it would be dishonest to imply otherwise. The server still records when a note was created, roughly how large it is, when it was opened, and the IP address that reached it. If you ask for a notification, it holds that email address too. What it never holds is the note itself, or the key to it.
What This Costs You
The decryption key lives only in the link. If the part after the # is dropped, truncated, or rewritten in transit, the note cannot be opened by anyone, including me. There is no reset and no recovery, because there is nothing on the server to recover from. That is the direct price of the guarantee above, and it is worth knowing before you rely on it.
Responsible Disclosure
No system is perfect, and I welcome scrutiny. If you believe you have found a security issue, please report it so I can address it quickly. You can review the broader privacy commitments in the Privacy Policy.
Want the Plain-Language Version?
For a less technical walkthrough, see how end-to-end encryption works and whether SneakNote is safe.