Open-source · zero-knowledge secret sharing

Share secrets once. Then they disappear.

One-time, end-to-end encrypted links for passwords, API keys, and files. Everything is encrypted in your browser — the server only ever stores ciphertext, and it's deleted after a single reveal.

  • Zero-knowledge
  • AES-GCM in browser
  • One-time reveal
  • Auto-expiry
  • Open source

Create a one-time secret link

Paste the secret, choose when it expires, then send the link.

Limit 1MB
24 chars, A-Z a-z 0-9 symbols
0 bytes used1,048,576 bytes remaining

The encrypted payload is deleted after this time or after the first reveal.

3. Create link

How SnapPwd protects your secrets

Security details

Encrypted before upload

A random AES-GCM key is generated and the secret is encrypted in your browser. Only ciphertext is sent.

Server never receives plaintext

The decryption key lives in the URL fragment after #, which browsers never send to the server.

Deleted after first reveal or expiry

The payload is removed the moment it is read, or when the expiry you set elapses — whichever comes first.

Open-source implementation

The client and server are public. Read the crypto, build it yourself, or self-host the whole thing.

No account required

No sign-up, no email, no tracking. Nothing ties a secret back to you.

Human reveal confirmation

Links wait for an explicit click, so link scanners and chat previews can't silently burn a one-time secret.

How it works

  1. 01

    Paste & encrypt

    Enter a secret and set an expiry. It is encrypted locally before anything leaves the page.

  2. 02

    Share the link

    Send the generated URL. The key is in the fragment, so the server never sees it.

  3. 03

    Reveal once

    The recipient clicks to decrypt in their browser. The payload is then deleted for good.

Common uses

Frequently asked questions