Is SneakNote Safe?
Yes, for sending a secret once. SneakNote encrypts every note in your browser with AES-256-GCM before upload, and the key stays in the part of the link after the #, which browsers never send to the server. The server holds only ciphertext and deletes it on first read or when the timer runs out. The limits: a recipient can still screenshot the note, and anyone who gets the link first can read it.
End-to-End Encryption
SneakNote uses end-to-end encryption to ensure that your note content is encrypted in your browser before it ever reaches the servers. The encryption key is embedded in the URL fragment (the part after the # symbol), which is never sent to the server. This means I cannot read your notes even if I wanted to.
What Happens If the Server Is Breached?
Because notes arrive already encrypted, the database holds only encrypted blobs. An attacker who copied it would not get readable notes: without the key, which exists only in the shared link, the data is useless. They would get the metadata the server keeps, such as when notes were created and opened and the IP addresses involved.
Is My Note Ever Stored Unencrypted?
At no point in the lifecycle of a note does SneakNote store your content in plaintext. The note is encrypted before transmission, stored encrypted, and decrypted only in the recipient's browser. Server logs do not capture note content, and I do not run analytics or tracking on what you write.
When Is a Note Deleted?
Every note created on SneakNote is designed to self-destruct. By default, a note is permanently deleted the moment it is read. You can instead set a timer from 5 minutes to 1 month, in which case the note can be opened any number of times until the timer runs out, then it is deleted whether or not anyone read it. A note that is never opened is deleted after 1 year at the latest.
Can I Add a Password?
For an extra layer of security, you can add a password to any note. The recipient must enter the correct password before the note can be decrypted. This is especially useful when you send the link through one channel and the password through another, an approach that significantly reduces the risk of interception.
HTTPS and Security Headers
All connections to SneakNote are served over HTTPS with TLS encryption. I also enforce modern security headers including strict transport security, content security policy, and protection against clickjacking and cross-site scripting. These measures ensure that the communication between your browser and the servers is secure.
What Can SneakNote Not Protect Against?
No system is perfectly secure, and honesty is more valuable than false promises. SneakNote cannot prevent a recipient from taking a screenshot or copying the decrypted text. Once someone has the link and any required password, they can view the content. The security model is built on minimizing exposure, not on controlling what happens after decryption. The goal is to ensure that your sensitive information is never stored permanently and is readable only by whoever holds the link.
If you need a safe way to share passwords, credentials, or private messages, SneakNote is built to give you meaningful protection with a simple, no-account-required experience. Try creating a secure note and see how it works for yourself.