Is the note text sent to the server in plain text?
The site encrypts the note in the browser before the share package is built.
FAQ
Short answers to the questions people usually ask first.
These answers are intentionally direct. The point is to make the tool easier to use correctly, not to wrap it in vague security language.
Should I add a passphrase every time?
Not always, but it is worth using when the link alone should not be enough to open the note.
Is this the same thing as true one-time destruction?
No. This build is about browser-side encryption and careful sharing, not server-enforced burn-after-read logic.
What kinds of notes fit this tool?
Short private messages, setup instructions, temporary credentials, routing details, and one-off admin information.
What should never go into a simple shared note?
Highly regulated records, full account archives, or anything that requires compliance workflows or audited access controls.
Why not just email the note?
Email is often convenient, but it leaves the text in plain view across inboxes, forwards, and archived threads.