Password.link is a service that makes delivering passwords over insecure media, like email and chats, easy and secure. All passwords are both encrypted and decrypted in the user's browser using a strong, industry standard AES 256 bit encryption and are accessible only using a special, unique link that is computed when a user submits a password to the service. This in effect means that we never see the actual password or the encryption key used to encrypt it - it is only possible using the special password link.

After the link has been accessed we delete the data from our database so that decrypting the password is no longer possible, even using the original password link. This further enhances the security: if the password link you received does not work, you know it has been already accessed by someone else and should immediately let the password link sender know about it. Additional features, like password view notifications, are available for registered users.

The service is being developed by a Finnish company Refic Oy (VAT ID FI27358926).

How does it work?

When you submit the password for secure delivery first two 18 characters long random strings are generated - let's call them public and private encryption key parts. The password is then encrypted right in your browser using the Stanford Javascript Crypto Library (SJCL) using AES 256 bit in GCM mode. The actual encryption key used in the password encryption is a concatenation of the public and private encryption key parts. The public encryption key part is stored in the unique password link that your browser generates and is never seen by us. The private encryption key part is sent to our servers along with the ciphertext returned by SJCL.

Once the unique password link is accessed, our servers send the private encryption key part with the ciphertext and then the actual password is decrypted in the viewer's browser using the public encryption key part in the link and the private encryption key part from our database. After this our servers wipe the private encryption key part and the ciphertext from our database making the accessed password link completely void. Our servers will never see the public encryption key part because it is stored in the URL as a fragment identifier (#...). A browser does not send the fragment identifier to a server.

As the whole service uses HTTPS only, you can be sure that the password can not be seen by anyone else than those who have access to the original, unique password link. If, however, someone accesses the password link before the actual recipient, the link will show a message that the password has already been seen and actions should be taken. Notifications can also be sent when a password is viewed (read more about the additional features).

We deliberately have strict limits for the service usage for unregistered users. If you need raised usage limits or more features, consider creating a free account or subscribing to one of our paid plans.