Keep the mainstream gallery for everyday snapshots. Put private albums, document scans and personal media where the provider has no key.
“Choose per photo, not per company.”
For google photos and icloud users who want a zero-knowledge home for the small share of their library that genuinely needs it.
Argon2id stretches your passphrase locally; the server never receives a key it could use.
No classification, face grouping or content indexing runs on your library, because ciphertext cannot be analysed.
File names, album names and EXIF including GPS are encrypted, not stored as service labels.
Public links are passphrase-gated, carry key material only in the URL fragment, and are capped at 24 hours.
The guarantee does not depend on staying inside one hardware ecosystem: web, desktop PWA and mobile share one key model.
Export your library at any time; encrypted ZIP downloads are assembled and decrypted on your device.
Google Photos encrypts data in transit and at rest with keys Google manages, and documents strict internal controls. End-to-end encryption of the library is not claimed, because search by content, face grouping, memories and safety systems require decryption. That is a deliberate product design, and the opposite of the one described here.
Roughly 3% of a typical library carries almost all of the sensitivity: private albums, identity and medical document photos, financial paperwork, images shared in confidence. Move that subset, disable automatic backup for its source if needed, delete the originals including from the mainstream trash, and keep everything else where it is.
Export or select the sensitive albums, upload them into the vault where they are sealed on the device, verify the batch, remove the originals and their trash copies, then store your recovery kit offline. It is an evening of work, once, and it removes an entire category of exposure permanently.
No. Images are encrypted on your device before upload. Your passphrase is stretched locally with Argon2id, each item is sealed with XChaCha20-Poly1305 under a fresh key, and those keys are wrapped with X25519. Our servers store ciphertext and wrapped keys, with no decryption path.
Both. File names, album names and embedded metadata are treated as content and sealed alongside the pixels. Thumbnails are generated on your device and stored encrypted.
We cannot restore your library — that is the same property that prevents anyone else from opening it. Recovery relies on the recovery kit generated on your device at signup, which you keep offline.
For people with an account, the album key is wrapped for their public key, and removing them rotates it. For everyone else, links carry key material only in the URL fragment, which browsers never transmit to a server; links are passphrase-gated and expire within 24 hours at most.
Yes, using blind indexes. Search tags are computed with HMAC on your device, so the server matches opaque strings and never sees your query or your file names. There is no server-side analysis of image content.
Your encrypted library is replicated to independent EU storage with immutability windows and automatic failover between providers. Those copies are ciphertext as well. We still recommend keeping one offline encrypted copy of anything irreplaceable.
Start free with 1 GB. Zero-knowledge encryption from the first upload — no admin override, no AI scanning, no plaintext on the server.
