A practical, architecture-first comparison of private photo storage: who holds the decryption keys, what the provider can analyse, and which services are genuinely zero-knowledge.
Three private surfaces. Same zero-knowledge architecture.
Everything else — face grouping, "memories", text search inside pictures, duplicate detection, smart albums — follows from the answer. Those features exist because the service can read the pixels. A service that cannot read the pixels builds those features on your device or not at all.
If a service satisfies the first three but stores your file names and locations in clear text, a surprising amount of your private life is still legible.
Neither column is "bad". They are two different products. The mainstream column is the right answer for holiday snapshots you would happily post. The right-hand column is the right answer for sensitive personal photos, private albums, family documents and anything you would not want an automated classifier to touch.
If a service offers full zero-knowledge encryption and server-side content search and effortless password recovery, at least one of those three claims is doing something other than what you assume.
Honest zero-knowledge answers: on my device; no; yes; no key material; ciphertext.
The result is deliberately plain: we store ciphertext, and we cannot open your albums.
| Provider | Zero-knowledge | Client-side encryption | Provider cannot decrypt | No plaintext analysis | User-controlled keys |
|---|---|---|---|---|---|
Google Drive Provider-managed encryption. Content accessible to provider-side systems. | |||||
DRIVUNOYou Encrypted on your device before upload (Argon2id + X25519 + XChaCha20-Poly1305). |
Provider-managed encryption. Content accessible to provider-side systems.
Encrypted on your device before upload (Argon2id + X25519 + XChaCha20-Poly1305).
| Provider | Zero-knowledge | Client-side encryption | Provider cannot decrypt | No plaintext analysis | User-controlled keys |
|---|---|---|---|---|---|
iCloud Drive End-to-end only when Advanced Data Protection is enabled. Default keeps some keys server-side. | |||||
DRIVUNOYou Encrypted on your device before upload (Argon2id + X25519 + XChaCha20-Poly1305). |
End-to-end only when Advanced Data Protection is enabled. Default keeps some keys server-side.
Encrypted on your device before upload (Argon2id + X25519 + XChaCha20-Poly1305).
| Provider | Zero-knowledge | Client-side encryption | Provider cannot decrypt | No plaintext analysis | User-controlled keys |
|---|---|---|---|---|---|
Dropbox Server-side keys held by Dropbox. Provider-side content analysis possible. | |||||
DRIVUNOYou Encrypted on your device before upload (Argon2id + X25519 + XChaCha20-Poly1305). |
Server-side keys held by Dropbox. Provider-side content analysis possible.
Encrypted on your device before upload (Argon2id + X25519 + XChaCha20-Poly1305).
Three private surfaces. Same zero-knowledge architecture.