Skip to content

Understand security and privacy

Know which information is public, how protection differs by feature, and what sharing controls can and cannot do.

Updated

Protection depends on the feature

A password prompt, encrypted storage and end-to-end encryption describe different things. Choose a feature based on its actual data flow, not only the presence of a lock icon.

For ordinary URL and memo links, the service processes the password and protected content during the supported create or unlock flow. Ordinary outgoing file sharing is also server-accessible: some paid upload flows add browser encryption, but the service receives material needed to provide access. These flows should not be treated as end-to-end encrypted.

Chat, drawing-board and location content is encrypted in the browser before upload. Request submissions have a separate design: submission content is encrypted in the submitter's browser, and the owner uses an unlock password to open the protected private key and decrypt submissions in their browser.

The private Ask inbox uses account-based access and server-managed encryption for questions and private notes. It is not end-to-end encrypted. Its optional submission password controls who can send questions; it is not a decryption password for the inbox.

Read the privacy policy for the service's published data-handling disclosures.

Keep secrets out of public fields

Public notes, titles, descriptions and form labels can appear before content is unlocked. Put confidential text in the intended protected-content field, and use neutral descriptions outside it.

Filenames and operational metadata can remain outside content encryption. Request records can include submitter names, email addresses and filenames as metadata; that does not mean all of them are displayed publicly. Avoid collecting information you do not need.

Link Hub is a public page. Its public blocks are not encrypted, while linked protected items keep their individual access requirements. Review the hub's publishing and search-indexing settings separately from each item.

Keep passwords and keys safe

Use long, unique passwords and store them securely before sharing. Send the link and password separately where practical. Having both is often sufficient to enter an ordinary protected link; it does not verify a person's identity.

Keep a Request owner's unlock password private. Share only the optional submit password with submitters. A forgotten content password cannot be looked up by support.

For API integrations, keep credentials on the server or in a secret manager. Do not put an API key in browser code, a URL, logs or a screenshot. See API setup.

Understand the limits of access controls

Expiry, opening limits and deletion control future access through the service. They cannot erase screenshots, downloaded files, copied text or an external destination address already received.

Protect the original destination separately when sharing a URL. A LOCK.PUB wrapper does not encrypt a file on another service or change that service's sharing permissions.

Anonymous participation is not a guarantee of network anonymity. Poll repeat-vote controls are best effort, and activity logs are not proof of a reader's identity. Verify important requests and recipients through a channel you already trust.

Report a problem safely

Use Contact to report a suspected issue. Describe the affected feature, visible behavior and approximate time. Remove passwords, credentials and private content from any example or screenshot you provide.

Still need a hand?

Describe what you were trying to do. Never send passwords or API keys.

Contact support