Send a file or a note as a single link.
It opens once, then it’s gone.
We can’t read your files or notes: they’re encrypted before they leave your device.
AES-GCM · PBKDF2, 600k iterations · Local or S3 storage · CLI included
Pick a file, or write a note. Either one gets the same treatment.
Set a password. Your browser encrypts the drop before anything is uploaded.
Add an expiry. Optional. When it passes, the drop is deleted, opened or not.
Get one link. It names the drop. On its own, it opens nothing.
Send the link. Send the password another way: a different app, a call.
They prove the password, once. Then the drop downloads once and is deleted from the server. It decrypts on their device.
Four things you can rely on, each with a link to how it works.
Your password derives half the key in the browser via PBKDF2 — 600,000 iterations — and never leaves the device. The other half is a server-held share released exactly once, so a stolen ciphertext alone is dead bytes. Buzzdrop stores ciphertext and metadata; it cannot read the drop.
How the key is splitThe recipient needs no account, only the link and the password, which they prove before anything downloads. A wrong guess gets no second attempt, and once the drop is open, nobody who finds the link later gets in.
How the password is checkedGive a drop a deadline and the link stops working once it passes. The attempt is refused and the copy swept away — whether or not anyone ever opened it.
How expiry deletes a dropBuzzdrop records when the drop was fetched and from which IP, and can email you once, the moment the recipient decrypts it.
How decryption is reportedBuzzdrop is small enough to audit in an afternoon. Explore it, run it on your own box, or drop a star so more people find secure one-time sharing.
buzz CLI to send encrypted drops from your terminal.