Burn After Reading.
Share secrets. Not risks.
Share passwords and secrets that self-destruct. Encrypted in your browser, unreadable on our servers, gone after viewing.
Zero-Knowledge
AES-256-GCM encryption in your browser. The key stays in the URL fragment — never sent to our servers.
Burn After Reading
Secrets self-destruct after viewing. Set view limits, time-based expiration, or one-time read. No traces left behind.
Anti-Bot Protection
5-layer defense: grace period, challenge gate, nonces, behavioral analysis, and UA detection.
CLI & API
Full REST API and CLI tool. Integrate secret sharing into your CI/CD pipelines and scripts.
File Sharing
Share encrypted files up to 100MB. Chunked upload with client-side encryption.
Open Source
AGPLv3 licensed. Audit the code, self-host it, contribute. Full transparency.
How It Works
Encrypt in your browser
Your secret is encrypted with AES-256-GCM using the Web Crypto API. The encryption key is generated randomly and never leaves your device.
Store the encrypted blob
Only the ciphertext is sent to our server. We store it with your chosen expiration rules. We cannot decrypt it.
Share the link — it burns after reading
The encryption key is embedded in the URL fragment (#), never sent to the server. The recipient decrypts locally, then the secret self-destructs.
Works Everywhere
$ sharepwd push "db_password=S3cureP@ss!" --burn --ttl 1h Secret created successfully! URL: https://sharepwd.io/s/abc123...#key456... $ sharepwd pull https://sharepwd.io/s/abc123...#key456... db_password=S3cureP@ss! Secret burned. This link is now dead.
Why SharePwd?
| Feature | SharePwd | Others |
|---|---|---|
| Zero-knowledge encryption | ||
| Key never sent to server | ||
| Anti-bot protection | ||
| CLI tool | ||
| File sharing | ||
| Open source (AGPLv3) | ||
| Self-hostable |
Built by the cybersecurity team at JIZO AI.
Start Sharing Securely