Uncle Lee, keeper of secrets, shushing

Share secrets secretly.
Then watch them .

Sealed inside your browser before it leaves. Nobody can peek, not even the admin with the biggest towel.

How can I trust this? โ†’
AES-256-GCM in your browserBurns after readingMade in Singapore ๐Ÿ‡ธ๐Ÿ‡ฌ

๐Ÿฉด Quick mode: no account needed. One look, gone within 1 hour, text up to 6 KB. Same encryption as everyone.

Sign in for files, 14 days & more โ†’
Uncle Lee cannot peek. He checked. Very sad.
0.0 / 6 KB
็™ฝ white dragon
what we see: nothing
The link you share
secretl.ee/s/Xk2P9q#vT8mQ2rL0aZโ€ฆโ†‘ sent to serverserver gets thisโ†‘ never sentstays in your browser
What our database holds

9f3a c1e0 7b44 e2d9 05aa 3c71 b8f0 6d12 ae94โ€ฆ

AES-256-GCM256-bit key0 bytes of plaintext

Zero-knowledge, for real

Encryption happens before upload, and the key rides after the # in the link, which browsers never send to any server. A hacked database is just confetti.

ไธญ red dragon
straight to the fire

Burns properly

Reveal is an explicit click, so Slack's link previews can't torch it. The burn is atomic: two people racing for the last view can never both win.

็™ผ green dragon
huat ah, business

Run your house

Orgs with roles and branding, an audit trail of every create, view and burn, plus API tokens and a CLI. Admins see metadata, never contents.

Apps

Uncle Lee, everywhere

See all apps โ†’
Terminallee, paste, done. Never in your shell history.RaycastSeal your clipboard in two keystrokes.Slack/lee keeps credentials out of chat history.
Uncle Lee squinting at scrambled ciphertext

Don't trust Uncle Lee. Check him.

Your secret is scrambled with a key your browser invents on the spot, and that key never travels to us. Watch the whole trip animated, poke at the real crypto in a live lab, or read the whitepaper if you're that kind of person. (We are.)

Watch how it works Read the whitepaper