Share a credential safely
Put the credential in the private note and send the unlock password through another channel.
Write sensitive text, require a password before it can be opened, and share a clean LOCK.PUB link with the recipient.
Use this flow when a recipient must enter a password before sensitive text is revealed, with a separate public label shown before unlock.
Put the credential in the private note and send the unlock password through another channel.
Protect onboarding steps, one-time directions, or internal notes before sharing the link.
Keep sensitive content out of long-lived chat logs while still sending an easy URL.
Competitor features change over time, so this table stays conservative and focuses on the LOCK.PUB product model.
Swipe horizontally to compare every column.
| Feature | LOCK.PUB | Typical private-note tool |
|---|---|---|
| Password before reveal | Required | Optional or unavailable |
| Public label separate from secret | Yes | Varies |
| Dashboard visibility | Yes after account save | Often limited |
| Read receipts | Pro analytics | Varies |
| API creation | Pro API | Varies |
Yes. This tool page requires a password before it calls the LOCK.PUB create API.
No. The public label can appear before unlock, so keep sensitive content inside the private note field only.
Yes, if you create while logged in or save the guest session to an account after creation.
Yes. Pro users can use the LOCK.PUB API for memo and URL link creation with quota tracking.