Question 1

Is Drop Zero-Knowledge?

Accepted Answer

Your encryption keys are generated locally and never touch our servers. We only store an AES-256-GCM encrypted blob that is unreadable to everyone—including us.

Question 2

What is 'Burn-on-Read'?

Accepted Answer

Secrets self-destruct after being viewed. You can customize the lifespan by setting a higher read count or a specific expiration timer.

Question 3

Can I self-host?

Accepted Answer

Both the API and CLI are entirely open-source. You can audit, fork, or deploy the core API today.

Question 4

What are the limits?

Accepted Answer

Each Drop is capped at a 1MB payload limit—perfect for secure credentials, snippets, or small documents.

Question 5

How does drop --sign work?

Accepted Answer

The --sign flag cryptographically signs your drop using an SSH key pair linked to your GitHub or GitLab account. Recipients can verify the signature against your public key to confirm the drop came from you, without any shared secret or out-of-band communication.