Send a password that expires
An expiring link limits how long a stored message can be opened. It does not change the password itself. For temporary account access, also plan when to rotate the password or remove that access.
1. Prepare the message
Use a unique password and avoid placing unrelated account details in the same message. The password generator works locally. If you are giving another person access to a service, check whether the service supports an individual invitation instead of sharing a password.
2. Choose a one-time secret
Open One-time secret and enter the message. Pick the shortest practical expiry. The content is encrypted in your browser before upload. The decryption key is carried after the # in the resulting URL.
3. Add an optional password
If you protect the link with another password, send that password through a separate channel. The recipient needs both the complete link and the additional password. Do not use the sensitive password inside the message as the link password.
4. Send the complete link
Copy the entire generated URL, including the part after #. Missing that part makes the message unreadable. The recipient must deliberately press Open. Opening your own one-time link uses its view, so create a separate harmless example if you want to try the workflow first.
5. Keep the delete capability private
Save the delete link or use My shares for links you saved there. Revoke a link if you sent it to the wrong place. If the message was already opened, deletion does not remove the recipient’s clipboard, screenshot or downloaded copy. Rotate the actual account password when access should end.
What to keep in mind
The server can enforce expiry and view limits for the encrypted stored message. It cannot control copies made after decryption, retrieve a missing fragment key, or reset the password of the service you shared.