Platform UI is currently English-only. Other languages here track your preference for future translations.

Go to Home

Home

      ◆ Zero-Knowledge  ·  Open Source
    

Share Passwords Securely With Encrypted Links Your Server Never Sees

Shushlink encrypts your secret in the browser and packs it into the URL fragment. No server, no signup, no install — not even ours can read it.

→ Create Secret Link View on GitHub

🔒 Apache 2.0 ✦ Open Source ⚡ No Signup

🔗 shushlink.vibenest.net/#eyJ0eXAiOiJKV1QiLCJhbGciOiJBMjU2R0NNS1ciLCJlbmMiOiJBMjU2R0NNIn0...3Np

// what is shushlink

Zero-Backend Secret Sharing

Shushlink is a password sharing tool for moments when you have to hand a credential — an API key, a database password, a one-off Wi-Fi token, a vault root, an SSH passphrase — to another human, and you want it out of your inbox, off your Slack history, and out of any third party's database.

You type the secret in the browser. The browser encrypts it with a password-derived key. The ciphertext is base64url-encoded and dropped into the URL fragment (the part after #). Browsers do not transmit fragments to servers, so the host that ships the page literally cannot see the secret, the password, or any metadata about it.

Shushlink is not:

× a one-time-view tool (there is no backend to enforce deletion — see the trade-off below)
× a file-sharing tool (URL length caps the payload at ~1.4 KB of plaintext)
× a password manager (it transports a secret; it does not store one)

// how it works

How It Works in 60 Seconds

Three steps. No accounts. No installs. No server-side state.

encryption-flow.sh

sender                           recipient
------                           ---------
secret + password
   │
   ├─ Argon2id(password, salt) → key
   ├─ AES-256-GCM(key, iv, secret) → ciphertext
   ├─ payload = header ‖ salt ‖ iv ‖ ciphertext+tag
   │
   └─→ URL: https://shushlink.app/#v1.<base64url(payload)>
                 │
                 │  (fragment never hits the server)
                 ▼
             recipient opens the link
                 │
                 ├─ password
                 ├─ Argon2id(password, salt) → key
                 └─ AES-256-GCM.decrypt → secret

1

Step One

🔑

Type Your Secret

Open shushlink.app, paste the secret. Use the auto-generated 24-character password (or type your own).

2

Step Two

🔒

Encrypted in Your Browser

AES-256-GCM encryption runs locally. Copy the link and the password — two separate fields, two separate copy buttons. QR code available for in-person handoffs.

3

Step Three

🔗

Share the Link

Send the link via email; password via Signal, SMS, or voice. The encrypted payload lives in the URL fragment — invisible to servers, readable only by the recipient.

// trust model

Server-Blind vs Server-Trusted

Most "share password securely" tools put the encrypted blob — and sometimes the plaintext — on a server. To trust these tools, you must trust that the operator didn't log the plaintext, isn't running modified code, hasn't been ordered to disclose, and will stay online when your recipient clicks.

Shushlink takes that trust off the table architecturally. There is no server-side store. The host serves a static HTML file, and that's it.

⚙️

Zero Backend

Static HTML file, no server-side code whatsoever. Works from disk, works offline, works on a plane.

🕳️

Zero Knowledge

Encryption happens before any data moves. The fragment is never part of any HTTP request — not in access logs, error logs, or Referer headers.

📖

Open Source

Apache 2.0, audit every line on GitHub. Single static file, ~50 KB minified. No third-party scripts — strict CSP blocks remote tags.

🚫

No Signup

No account, no email, no tracking cookies. No analytics, no telemetry. The CSP enforces connect-src 'none'.

What that buys you, concretely:

✓

No server logs