What zero-knowledge encryption actually means
Zero-knowledge encryption means your files are encrypted on your own device, with a key derived from a password only you know, before they ever reach the provider's servers. The provider stores ciphertext and nothing that can decrypt it. They can't read your files, hand a court a readable copy, or leak one in a breach — because they never held the key. It's a property of the math, not a line in a privacy policy.
Almost every cloud company will tell you your data is "encrypted." Most of them are telling the truth, and it still doesn't protect you from them. The word hides the question that decides everything: who holds the key?
Encryption at rest vs zero-knowledge: the only distinction that matters
When Dropbox, Google Drive, or iCloud say your files are encrypted, they usually mean two things. Your data is encrypted in transit (TLS, the same lock your bank's website uses) and at rest (the files on their disks are scrambled with AES-256). Both are real. Neither makes your data private from the provider.
Here's why. With encryption at rest, the provider generates and stores the keys. The scrambling stops someone who steals a physical drive out of the datacenter. But the keys live on the provider's own servers, right next to the locked data — so the provider, and anyone who can compel the provider, can unlock it at will. Dropbox's standard plans work exactly this way: it holds the keys so it can decrypt your files to power sharing, previews, and recovery. Useful features, real engineering. It just means encryption at rest secures their datacenter, not your files from them.
Zero-knowledge moves the key. It's derived on your device and never leaves it. The server only ever sees ciphertext. There is no copy of your key in the datacenter to seize, subpoena, or leak. That single architectural choice is what separates "encrypted" as a marketing checkbox from encryption as an engineering commitment.
How the key gets made — and why it never leaves your device
The mechanism is simpler than the marketing makes it sound. When you set up a zero-knowledge account, you choose a passphrase. That passphrase runs through a slow, memory-hard key-derivation function — Beebeeb uses Argon2id tuned to 256 MB of memory and 4 iterations — which turns it into a strong encryption key. "Memory-hard" is the point: it makes guessing your passphrase expensive even for an attacker with a rack of GPUs.
That derived key encrypts your files with AES-256-GCM, an authenticated cipher that both scrambles the data and attaches a tamper-check tag, so altered ciphertext fails to decrypt instead of quietly returning garbage. Sharing a file is handled with X25519 public-key cryptography, which wraps a per-file key to the recipient without either of you ever exposing a secret to the server. The passphrase and its derived keys stay on your device, used in memory and then wiped. The server's entire view of your account is a pile of ciphertext it has no way to open. If you want the full picture of how the keys, sharing, and storage fit together, our security architecture page walks through every step.
The honest tradeoff nobody markets
Real zero-knowledge has a cost, and a provider that hides it is lying to you. If a company genuinely can't decrypt your data, it can't reset your password for you either. Lose your passphrase and your recovery phrase and the files are gone — no support ticket brings them back. Beebeeb hands you a BIP39 recovery phrase, the same 12-word standard crypto wallets use, precisely so you hold the only way back in. We say it plainly: we can't recover this. A provider that promises "encrypted, but we can reset your password" is telling you, in the same breath, that it holds a key.
A checklist to test any provider's claim
"Zero-knowledge" has no legal definition, so anyone can print it on a pricing page. Here's how to check whether it's real before you trust it with anything that matters:
- Can they reset your password and restore your files? If yes, it isn't zero-knowledge. A reset that recovers your data means they can decrypt your data.
- Is encryption on by default, or an opt-in setting? Apple's Advanced Data Protection is genuine end-to-end encryption — but it's off until you switch it on, and even on, it leaves Mail, Contacts, and Calendar readable by Apple. Off-by-default protects almost nobody.
- Are the client apps open source? Encryption that happens "on your device" is a claim you can only verify if you can read the code running on your device. Beebeeb's clients — web, CLI, mobile, desktop, and the core crypto library — are open source. Our server and this site are not, and no amount of server code would let you verify client-side encryption anyway.
- Who owns the company, and under which law? A US-incorporated provider is reachable under the US CLOUD Act wherever its servers physically sit. Zero-knowledge is the stronger answer here precisely because there's no readable copy to compel — but jurisdiction still decides what metadata they must hand over.
- Has the architecture been independently audited, and were the findings published? An audit you can't read is a logo, not evidence.
By that checklist, the genuinely private options are a short list. Proton Drive passes it: open-source, independently audited clients with keys generated on your device, hosted in Switzerland — credit where it's due. Dropbox, Google Drive, and iCloud-by-default do not. Beebeeb is built to pass its own checklist — zero-knowledge on every tier, no exceptions, with an independent audit planned and the findings to be published when it's done. We're holding ourselves to the same test we're handing you.
If you've been weighing a move, our honest Dropbox alternatives breakdown runs this exact checklist against the provider most people are trying to leave, and the features list shows what's live today.