Secure code: verify on GitHub
Vaporised

Help

Vaporised helps you send sensitive information through email. You send part of the information by email, save the other part here, and send only the link. The information is never all in one location.

Send a secret

  1. Send the first part of the information (for example, the username) by email.
  2. On the home page, type the secret (for example, the password), or click Generate a password.
  3. Select a time limit in Delete after.
  4. Set the Maximum views. The maximum is 10.
  5. Optional: type a passphrase. Send the passphrase to the recipient by a different channel, for example by phone.
  6. Click Save the secret.
  7. Copy the full share link, including the part after #, and send it to the recipient.
  8. Keep the delete link private. You can use it to delete the secret before it expires.

We show the share link and the delete link only one time. Copy them before you close the page.

Read a secret

  1. Open the share link that you received.
  2. If the sender set a passphrase, type it.
  3. Click Reveal the secret only when you are ready. Each click uses one view.
  4. Copy the secret and save it in a safe location, for example a password manager.

When is a secret deleted?

We delete a secret at the first of these events:

We keep no copies and no archives. After we delete a secret, nobody can get it back.

Time limits

You can select one of these time limits:

Questions

The link says “Secret not available”. Why?

The secret has expired, has no views left, or the sender deleted it. Ask the sender to save the secret again and send you a new link.

Why is JavaScript necessary?

Your browser encrypts the secret before it sends anything to us, and it decrypts the secret when you read it. Before it saves a secret, your browser also does a short calculation. This check stops automated misuse of the service.

How long can a secret be?

The maximum is 10000 characters.

Can you see my secret?

No. Your browser encrypts the secret before it leaves your device. The encryption key is the part of the share link after #. Browsers never send that part to a server, so our server, our database, and our logs do not have it. We store only the encrypted data and cannot decrypt it.

A passphrase adds to the encryption key. Without the passphrase, the full link is not sufficient to read the secret.

Why does the share link have a # in it?

The part after # is the encryption key. Send the full link. If the recipient opens the link without that part, the page tells them that the link is incomplete.

Is a passphrase necessary?

No, but it adds protection. If a person gets the link, they also need the passphrase to read the secret.

For information about the data that we keep, read the privacy policy.