Most cloud privacy conversations stop at one word: encryption. If your provider says your files are encrypted, the assumption is your privacy is settled. It usually isn’t.
Encryption protects pixels. Plenty of useful information about you sits outside the pixels.
What metadata travels with every photo
Every photo your phone takes carries a block of metadata called EXIF. You don’t see it in the viewer, but it’s there. A typical EXIF block from a recent phone photo includes:
- Date and time, down to the second
- GPS latitude and longitude
- Camera make, model, and lens
- Exposure, aperture, ISO
- Phone orientation when you took the shot
- Sometimes altitude
One photo gives you a timestamped location. A year of photos gives you a map of where someone lives, works, sleeps, and travels, with timestamps. None of that requires anyone to look at the image.
When you upload to a typical cloud service, this metadata uploads with the photo. It’s indexed and used.
What providers infer beyond metadata
If a provider can read the photo content, and most can, the inference layer goes further than EXIF.
In January 2026, Google updated its Gemini personalization terms with this language about Google Photos:
“Your Google Photos data is used to infer your interests, relationships to people in your photos, and where you’ve been, including by associating your face with corresponding location data and timestamps.”
That’s Google describing its own product, not a critic’s interpretation. It’s a clear summary of what server-side photo access enables: faces linked to people, people linked to places, places linked to times.
The point isn’t that any single photo reveals much. The point is that a library of them, sitting on a server with full read access, becomes a behavioral profile. Metadata gives the skeleton. Pixels fill in the rest.
What “AI features” actually require
Face grouping. Object search. Auto-generated memories. Highlight reels. These are real conveniences, and a lot of people use them.
To run any of them on a server, the provider needs to read your photo content. Not at the moment of access, but routinely, at scale, indexed and stored. The features and the access aren’t separate things. You can’t get one without granting the other.
That’s a reasonable trade if you understand it. The issue is that it’s almost never explained in those terms.
Encryption at rest is not end-to-end encryption
Two phrases get used as if they mean the same thing. They don’t.
Encryption at rest means your photos are encrypted on the provider’s disks. The provider holds the keys. They can decrypt anything they need to, and they do, every time they index a photo or generate a feature.
End-to-end encryption means your photos are encrypted on your device with a key only you hold. The provider stores ciphertext. They can’t read your photos to power features, because they can’t read them at all.
Most consumer cloud services use the first kind. Some offer the second as an opt-in. Very few default to it. The marketing usually says “encrypted” without specifying which.
If you want a longer walkthrough of who holds the keys, we wrote about cloud storage encryption separately.
What Abrio chooses not to know
Most of this post is about what your photos can tell a provider that wants to know. Abrio’s answer is upstream of the question: design the service so we don’t have anything to know.
Photos and videos are encrypted on your device before they leave it. The keys stay with you. There’s no server-side scan of your photo content, because we can’t read it. There’s no inference layer that turns your photos into a profile of who you spend time with, where you’ve been, or what you’re interested in.
Search, organization, and categorization run on your device. The conveniences that don’t require us to read your photos are the ones we offer. The ones that do require it, we don’t.
If you’ve thought about the trade and you want a cloud provider that holds the data without holding the keys, that’s the one we’re building.
Join the waitlist
Be among the first to experience Abrio when we launch.
By signing up, you agree to our Terms and Privacy Policy — both written to be read.