How Password.link One-Time Links Keep Shared Passwords and Files Secure

Password.link protects a shared secret in three layers: the secret is encrypted in the sender's browser before it is sent, the recipient opens it through a link that self-destructs after a single view, and the sender can add expiration time, a link password, CAPTCHA, and an open-count limit. This suits anyone sending a password, API key, or confidential file through a channel where a plain message would linger — email, chat, or a ticket. It is not a replacement for a password manager; it is a way to move one secret to one recipient without leaving it in message history.

The mechanism, step by step

The security model rests on where encryption happens and what happens after the first open.

1. Encrypt in the browser. You enter the secret on the site, and it is encrypted in your browser before it leaves — the page states "Your secret is encrypted in this browser before it leaves." The site describes this as zero-knowledge and AES-256-GCM, hosted in the EU. In practice, the plaintext is not sent to the server as readable content.
2. Create the link. The site returns a shareable link (and optionally a QR code you can download). You send that link to the recipient through whatever channel you already use.
3. Recipient opens once. The link self-destructs after a single view, so a later click — by the recipient, a forwarded copy, or someone reading the message history — does not reveal the secret again.
4. Sender controls the window. Per-link settings let you set an expiration time, require a password to open the link, add CAPTCHA, and choose how many times the link can be opened.

The practical effect: the secret's exposure is bounded by time and by view count, not by whether the recipient remembers to delete a message.

A concrete example

Suppose an IT admin needs to hand a new hire's temporary credentials to a contractor. Instead of pasting the password into email, the admin creates a one-time link, sets it to expire in 24 hours, adds a password sent through a separate channel, and limits it to one open. If the email is later forwarded or the contractor's inbox is compromised after the first open, the link is already dead.

What each setting buys you

The combination matters more than any single setting: a link with a short expiration and a password is far harder to exploit than a one-time link alone, because the attacker needs both the link and the password within the window.

Receiving secrets and other uses

The same mechanism runs in reverse. A Secret Request link lets you ask someone else to send you credentials or documents; they reply through a one-time link only you can open. The site also offers an end-to-end encrypted chat that disappears when closed, bulk link creation from a CSV file (parsed in the browser, so the service does not access the file's contents), and team features such as separate member accounts, centralized settings, and single sign-on.

Limits worth knowing before you rely on it

• One view is one view. If the recipient opens the link and the page fails to load properly, or they close it before saving the secret, the link is spent. For anything the recipient must keep, they should store it in a password manager on first open.
• The link is a bearer token. Anyone who has the link and, if set, the password can open it first. Send the link and the password through different channels.
• Free-tier limits exist. The page shows a "Limit for new Secrets reached" message and notes that creating a free account (no credit card required) unlocks all features, including attachments, branding, and notifications. Plan details are on the site's Plans page; check current terms there rather than assuming a free tier covers volume use.
• It is a transfer tool, not storage. Nothing in the described model suggests the secret remains retrievable after the view limit — which is the point, but it means you cannot recover a secret you sent if the recipient loses it. Keep your own copy.