Share a secret with a link that works only once

Paste a password, API key or private note. You get a one-time link that opens once, then deletes itself. Free, and no sign-up for you or the person you send it to.

0 / 10,000 characters

Or as soon as it’s opened, whichever comes first.

The recipient must type it to open the secret. Send it through a different app.

Encrypted in your browser. No sign-up needed.

Free. No account to send or to read. We can’t see what you share.

How one-time secret sharing works

Four steps, and your secret never sits anywhere it could be read later.

  1. 1.Paste your secret

    Type or paste a password, key or private note into the box.

  2. 2.It’s locked in your browser

    Your browser encrypts it before anything is sent. We only ever receive scrambled data.

  3. 3.Send the link

    The key to unlock it is inside the link itself. Send it by chat, email or text.

  4. 4.Opened once, then gone

    When your recipient opens it, we delete our copy. The link never works again.

Why not just send it in WhatsApp, Slack or email?

Because a message doesn’t disappear when the person has read it.

Sent in a chat or email

A readable copy stays in:

  • Your phone and theirs
  • Laptops
  • Cloud backups
  • Chat search
  • Admin exports
  • AI assistants reading the workspace

Anyone who later gets into one of those accounts can scroll back and find it.

Sent as a one-time link

After it’s opened, a readable copy stays in:

  • Only the screen of the person who opened it

The chat still shows a link, but the link leads nowhere. There’s nothing left to find.

Questions people ask

No. One-time secret sharing needs no registration. You can create a link without signing up, and the person you send it to can open and read the secret without an account.

How the encryption works

For developers and security teams who want the details.

Encryption in the browser
The Web Crypto API generates a random 256-bit key and 96-bit IV, and the secret is encrypted with AES-256-GCM before it leaves the page.
Key in the URL fragment
The key is placed after the # in the link. Per RFC 3986, fragments are not sent in HTTP requests, so the key never reaches Ennote servers or access logs.
Single-read deletion
The server stores only ciphertext and an expiry. The record is deleted atomically on first retrieval, and any unread record is purged when its expiry passes.
Optional passphrase
A verification hash is derived in the browser with PBKDF2 (100,000 iterations of SHA-256, random 16-byte salt). The recipient must enter the same passphrase to unlock the secret.
Comparison of ways to share a secret
Chat or emailTypical pastebinEnnote one-time link
Encrypted before it leaves your deviceNoRarelyYes, AES-256-GCM
Service can read itYesUsuallyNo, key stays in the link
Deleted after first readNoSometimesYes, always
Optional passphraseNoSometimesYes, PBKDF2
Account neededBoth peopleUsually notNo one

Sharing secrets across a team or into Kubernetes?

Ennote also offers team password vaults and secret delivery to Kubernetes workloads, with no sidecars.