cipherdrop ~ $ share --encrypt --burn

send a file or note
the server cannot read

it is encrypted in your browser before it leaves. the key rides in the link fragment, which never reaches the server, so all it ever stores is scrambled bytes it cannot read.

cipherAES-GCM 256

keyin the URL #fragment

serverciphertext only

expiry1h · 1d · 7d

burndelete on first read

max100 MB

~/cipherdropencrypt → link → decrypt

expires

the key lives after the # in your link and is generated on this device, never sent.

$ why cipherdrop

> the key never leaves

it is generated on this device and lives after the # in the link, which browsers never send to a server.

> the server holds gibberish

only ciphertext ever lands on disk. if it leaked tomorrow there would be nothing readable on it.

> gone when you want

set an expiry or burn on the first read. expired drops get swept off disk, not just hidden.