Most text you share with a link has no password on it, and usually that is fine. The link is unguessable, the content is a build log, nobody cares.
Then one day it is a database credential, a client brief under NDA, or the answer key for tomorrow's exam — and "unguessable" stops feeling like enough. That is the moment people go looking for a password field and discover it is a paid feature.
Why most shared notes have no password
Two reasons, and only one of them is technical.
The technical one: adding a password means storing a hash, adding an unlock screen, deciding what happens to link previews, and handling the case where someone has the link but not the password. It is real work for a feature most pastes never use.
The commercial one is more common. Password protection is an unusually good paywall: it is easy to explain, it maps to a moment of genuine need, and the person who needs it needs it right now. So it tends to land in the paid tier — the same place burn-after-read usually ends up. Several tools in this category do exactly that.
ShareNotes has no paid tier, so there is nowhere to put it. A PIN is just part of the Save dialog.
How PIN-protected notes work here
When you save a note you can set a 4–6 digit PIN, and choose which of two things it gates:
| Mode | Who can read it | Who can change it |
|---|---|---|
| Edit only | Anyone with the link | Only someone with the PIN |
| View + edit | Only someone with the PIN | Only someone with the PIN |
Edit only is the publish-and-protect mode. The note reads like a normal shared page — anyone you send it to just opens it — but nobody can quietly change what it says. This is the one we also call Classroom Mode, because that is exactly the shape of the problem when thirty students have the same link.
View + edit is the one people mean when they say "password protected". The content is not served at all until the PIN is entered.
A PIN is an access gate, not encryption. ShareNotes notes are not end-to-end encrypted — our server can read note contents, and a PIN does not change that. It stops people who have the link from reading the note. It is not the right tool for something that would genuinely hurt you if our database were breached. For that, use a tool built around client-side encryption, or don't put it online at all.
Sending a protected note: the 30-second version
- Open the editor and paste your content.
- Click Share, and tick the PIN option in the Save dialog.
- Enter a 4–6 digit PIN and pick Edit only or View + edit.
- Send the link and the PIN through different channels — link in email, PIN over the phone or a messaging app. A password sent in the same message as the link protects nothing.
No account, no email confirmation, no upgrade step at any point.
Who actually reaches for this
- Handing over credentials. A staging password or API key that the other person needs once. Pair the PIN with a short timer and it cleans itself up.
- Teaching. Edit-only mode lets a whole class read the same shared page while keeping the text under your control.
- Client work. A brief or quote you are happy for the client to read, but not to edit and then quote back at you.
- Anything going into a group chat. Group chats get forwarded. A PIN means the link leaking is not the same as the content leaking.
What happens after the PIN
Protection and lifetime are separate decisions, and they compose:
- Add a self-destruct timer — 1 hour, 24 hours or 7 days — so the note has a deadline as well as a gate.
- Or make it single-use with delete-after-first-read, and the content is destroyed the moment it is opened.
Those two combine in a way worth knowing about: on a view+edit protected note, the PIN gates the content, so a burn-after-read note is consumed when the note is unlocked, not merely when the URL is visited. Someone hitting the link without the PIN does not burn it for the person who has it.
That detail matters more than it sounds. On most burn-after-read tools, the first thing to open your link is not a person — it is Slack's or iMessage's link-preview bot, and the note is gone before the recipient clicks. We handle that case separately and deliberately.
The short version
If you need a password on a shared note, you should not have to sign up or pay for it. Set a PIN, pick whether it gates reading or just editing, send the PIN through a different channel than the link, and add a timer if the content has a shelf life.
Just keep the boundary straight: a PIN keeps out people who have your link. It is not encryption, and we would rather say so than let you find out later.
Open the editor and try it, or see how this compares to the usual pastebins.