Send bank or payment details
Move an account number, payment reference, or billing detail out of the chat used to coordinate the transfer.
Write the sensitive text, set a separate password, and send a link that blocks another reveal after the first successful unlock.
Instead of pasting bank details, account references, recovery codes, or personal identifiers into chat, send a separate password-protected link and deliver its password another way.
Move an account number, payment reference, or billing detail out of the chat used to coordinate the transfer.
Share an initial password, recovery code, or short-lived access phrase without leaving the value in the conversation history.
Send only the minimum identifier the recipient needs, and avoid including sensitive words in the public label.
A LOCK.PUB link separates the sensitive text from the conversation and stops the link from revealing it again after one successful unlock.
Swipe horizontally to compare every column.
| Feature | LOCK.PUB secure share | Plain chat or email |
|---|---|---|
| Sensitive text in conversation history | No—the conversation contains a link | Yes |
| Separate password step | Required | Usually none |
| Access after first successful reveal | Blocked | Message remains available |
| Recipient LOCK.PUB account | Not required | Depends on the service |
| Prevents the recipient from copying | No | No |
It is designed for short text such as account details, references, temporary credentials, or personal identifiers. Share only the minimum information the recipient actually needs.
This tool promises one-time access, not deletion. After the first successful password unlock, LOCK.PUB blocks another reveal through that link.
Yes. One-time access cannot stop a recipient from copying, photographing, or otherwise recording information while it is visible.
Send the link and password through separate channels whenever the information is sensitive. Do not include the sensitive value in the public label.