The difference is who holds the key
Encryption at rest means your provider scrambles files on their disks but keeps the keys, so it protects their datacenter from a stolen drive, not your data from the provider. End-to-end encryption means the file is encrypted on your device with a key only you hold, so the server stores ciphertext it can never read. Same word, opposite guarantee. The only question that decides whether your files are private: who can decrypt them?
What "encrypted at rest" actually buys you
When Dropbox, Google Drive, or iCloud say your files are "encrypted," they usually mean two specific things. Your upload travels over TLS, so nobody sitting on the network in between can read it. And the bytes parked on their storage are scrambled with AES-256, so a physically stolen disk is useless. Both are real protections. Neither one keeps the provider out.
The reason is mundane: the company that encrypts the data also holds the decryption key. Dropbox documents this directly — files are AES-256 at rest, TLS in transit, and Dropbox manages the keys on your behalf so it can run search, generate previews, and reset your password. Google Drive is the same shape. At-rest encryption is a lock where the landlord keeps a copy of every key. It stops a burglar. It does nothing against the landlord, a court order served on the landlord, or a breach of the landlord's keyring.
Why the economics favor at-rest, not you
This is the industry default, and it isn't malice — it's cost. At-rest encryption is nearly free to operate. The provider already runs the storage layer, so turning on disk encryption costs almost nothing while every server-side feature keeps working on the plaintext underneath: full-text search, deduplication, thumbnail generation, "smart" suggestions. A provider renting space at roughly $0.023 per GB-month on AWS S3 wants to process plaintext, because plaintext is cheap to process. End-to-end encryption breaks every one of those features by design. The server only ever sees ciphertext, so it can't index or dedupe or preview anything. That's a real cost, and most providers bet you wouldn't notice the difference. "Encrypted" became a marketing checkbox precisely because the cheap version satisfies the word without satisfying the promise.
The one test that cuts through the brochure
Strip away the language and every model collapses to a single question. If the provider can decrypt your files — to show you a preview, to answer a subpoena, to recover your account after a forgotten password — then it is not end-to-end encrypted, no matter how many times the page says "encrypted." If it cannot, because the key was derived on your device and never left it, then it is.
That's what zero-knowledge means: the server holds your ciphertext and nothing else. With Beebeeb's key-derivation chain, your passphrase is stretched with Argon2id (256 MB memory, multiple iterations) on your own device, then used to wrap your files with AES-256-GCM. The server in Falkenstein, Germany receives encrypted blobs and encrypted key material. There is no copy of your key there. We can confirm an account exists and how much ciphertext it stores. We cannot open a single file. That isn't a policy we promise to honor — it's a property of the math, and the full chain is published so you can check it instead of trusting us.
Where iCloud, Dropbox, and Google actually land
The honest version matters more than a dunk, and the picture isn't uniform:
- iCloud ships Advanced Data Protection, genuine end-to-end encryption for most categories including iCloud Backup, Photos, and Notes. The catch is that it's opt-in and off by default, so the vast majority of users run standard protection where Apple holds the keys. Mail, Contacts, and Calendar stay outside E2E even with ADP on. And off-by-default has teeth: in February 2025 Apple pulled ADP for UK users under a government order, which a default-on design would have made far harder. iCloud is also genuinely cheaper than Beebeeb at small tiers, and we say so in our honest Beebeeb-vs-iCloud comparison.
- Dropbox is encrypted at rest and in transit, holds the keys, and is not zero-knowledge by default. It has added real end-to-end encryption for team folders — but it's admin-managed, limited to Advanced, Business Plus, and Enterprise plans, leaves metadata in plaintext, and isn't on mobile. A genuine improvement for the folders you flip it on for, not a baseline.
- Google Drive is
AES-256at rest with Google holding the keys. Workspace offers Client-Side Encryption, but it's an admin feature that requires you to stand up a separate external key service — not something a consumer Drive account has or can turn on.
None of these is lying. They use "encrypted" accurately for at-rest, and most readers hear it as "private." That gap is the whole point.
How to test any provider's claim in 30 seconds
You don't need a cryptography paper. Ask four questions of any cloud you're weighing:
- Can they reset your password and still hand back your files? If yes, they hold your key. That's a backdoor, however well-intentioned.
- Can they show a server-side preview or run search across your files? If yes, the server sees plaintext.
- Is it on by default, or do you opt in? Off-by-default E2E protects almost nobody, because almost nobody flips the switch — and a regulator can quietly order it removed.
- Can you read the client code? Client-side encryption is only as trustworthy as the client doing it. Beebeeb's product clients — web app, CLI, and the core crypto library — are open source so the encryption is auditable. Our server and this marketing site are not. An independent security audit is planned, and the findings will be published.
The honest tradeoff lives in question one. True end-to-end encryption means we genuinely cannot recover your account if you lose both your passphrase and your recovery phrase. There is no "forgot password" email that ends with us handing back your data, because we never had the key. That's the cost of a provider that can't read your files, and we built a backstop you control: a BIP39 recovery phrase generated on your device. The feature set assumes you, not us, are the only one who can open anything.
If you'd rather see the difference than read about it, "Encrypted at rest" is a fine thing for a provider to have. It was never the thing you were asking for.