Link-only mode · no database
Share a secret with no server in the loop
Paste a password or any sensitive text. Secret Sharing encrypts it in your browser and packs the encrypted bytes directly into the shareable link (after the #). Browsers never send the fragment to a server, so no database, no API, and no logs are involved. The recipient decrypts the link locally with a separate four-word passphrase.
No databaseNo server roundtripBrowser-side AES-GCMEncrypted expiry
Encryption happens entirely in your browser. Nothing on this page is sent anywhere - the encrypted result is packed into the link itself. How it works →
How to send a secret securely
- 1
Paste your secret
Your browser generates a 256-bit AES-GCM key locally and encrypts the text in-memory. The plaintext never leaves your device.
- 2
Get a link and a passphrase
The encrypted ciphertext, IV, and salt are packed into the link itself (after the #). You receive that link plus a separate four-word decryption passphrase. No network request is made - nothing is sent to any server.
- 3
Send over two channels
Send the link through one channel (email, chat) and the passphrase through a different one (SMS, phone call, in person). An attacker who compromises one channel still cannot read the secret.
- 4
Recipient decrypts locally
When the recipient opens the link, their browser reads the encrypted bytes from the URL fragment (which is never sent to a server) and decrypts them with the passphrase. After a successful decrypt, the URL is cleared from this tab as a best-effort one-time gesture - but anyone who saved the link before it was opened can still read it.
When to pick link-only vs. stored mode
- Pick link-only when you do not want any server involvement at all - regulatory, philosophical, or air-gap reasons - and you accept that the link is not one-time. The link is the only copy; losing it loses the secret.
- Pick stored mode (the default on the home page) when you want a true one-time read - the server atomically deletes the record the instant it is fetched, and expired records are cleaned up on a schedule.
- Both modes use the same browser-side AES-256-GCM encryption and Argon2id passphrase derivation. The difference is where the encrypted bytes live: a server row, or the URL itself.