Articles · Privacy & Trust
Send a secret that should not live in email forever
Passwords, one-time codes, and “here is the Wi-Fi” notes do not belong in a mailbox that is backed up forever. A secure note encrypts in the browser, stores ciphertext on the server, and puts the key in the URL fragment so DevNestro never has the plaintext. Recipients open the link; burn-after-reading notes disappear after the first successful read.
Why this is worth doing in the browser
Chat apps keep history. Email is discoverable. The DevNestro Encrypted One-Time Secure Note is for a small secret with a short life. It is not a password manager, not a file locker (use File Share for files), and not anonymous infrastructure. It is a better envelope than a raw Slack message.
How to use the tool
Type the note, pick expiry or one-time read, create the link, and send it through a channel you already use. Tell the recipient not to forward the full URL if the note should stay with them. Use Privacy Redactor if you are sharing a longer document that still needs masking.
- Write only the secret, not a biography around it.
- Choose burn-after-reading when the value is a one-time credential.
- Send the link; do not paste the plaintext into the same chat “just in case.”
- Assume anyone with the full URL can read the note until it expires or burns.
Privacy
Encryption happens in your browser. DevNestro stores ciphertext, IV, and expiry metadata, not the plaintext or the fragment key. Notes are removed when they expire or are burned.
If the text should not be searchable in a year, do not email it. Open Secure Note, encrypt it, and send a link that can die.