When you turn on a photo backup, your cloud backup photo metadata travels with the image. iCloud Photos and Google Photos both upload the original file, EXIF block included, which means every GPS coordinate, timestamp, camera serial number, and lens detail you captured is now sitting on a server and synced to every device on your account. The services do not strip this data; preserving it is the whole point, because it powers the features people actually like.
That is the tension worth understanding. The same metadata that makes "show me photos from Rome last summer" work instantly is also a precise, permanent record of where you have been and when.
What your cloud library actually knows
Open Google Photos and tap the map view, or open the Places album in iCloud. You are looking at your own location history, reconstructed entirely from the GPS tags inside your photos. Zoom in and you can see individual pins on your street, your office, your gym, the school you drop kids at. None of this required a separate tracking feature; it is just your EXIF data plotted on a map.
Both services also read metadata to power search. Type a city, a year, or a landmark and the results come from timestamps and GPS coordinates, sometimes combined with on-device or server-side image recognition. It is genuinely useful. It is also a reminder that the metadata is fully indexed and queryable, not sitting inert.
Removing a photo from your phone after it backs up does not remove the metadata from the cloud copy. The uploaded version keeps its full EXIF block. And when you later share that cloud photo by link or download, the GPS and camera data usually go with it unless you have explicitly turned location sharing off.
iCloud Photos: what Apple keeps
iCloud Photos stores your originals. If end-to-end Advanced Data Protection is enabled, the contents are encrypted such that Apple cannot read them, which is a meaningful privacy win against server-side access. But encryption at rest does not delete the metadata; your own devices still read the GPS and timestamps to build the Places album and power Memories. And the moment you share a photo outside that encrypted envelope, the embedded EXIF is exposed to whoever receives it.
Apple does give you one useful control at the sharing step. When you share via the share sheet, tap Options at the top and you can toggle Location off, which strips GPS from the copy being shared while leaving your library intact. It is per-share and easy to forget, but it works.
Google Photos: what Google keeps
Google Photos uploads originals (or compressed copies in Storage Saver mode) with EXIF preserved. Google has historically used photo metadata and content to improve services, and the location data drives the map and search features directly. Google added a setting to remove geolocation when you share a link, but it is off by default for the link itself in some flows and does not retroactively scrub the stored originals.
The practical takeaway is the same on both platforms: the cloud copy is faithful to the original, metadata and all, and your privacy depends on settings you have to find and on what you do at the moment of sharing.
How to keep control
You do not have to abandon cloud backup to manage this. A few habits cover most of the risk:
- Strip before you share, not before you back up. Keep full metadata in your private, ideally encrypted, library so search and albums still work, but strip the copy you send to anyone else.
- Use the per-share location toggle. On iOS, the share sheet's Options screen lets you drop location. Build the habit of checking it for anything leaving your circle.
- Turn on the strongest encryption available. Apple's Advanced Data Protection puts your library beyond server-side reading. It does not strip metadata, but it limits who can ever see it.
- Audit your map view occasionally. Looking at your own Places map is the fastest way to understand how much location history you are accumulating, and it makes the case for stripping shared copies obvious.
Keep your library, strip your shares
Skrim removes GPS, timestamps, and device data from the photos you send, on-device and full resolution, so your cloud backup stays useful and your shared copies stay private.
Download SkrimThe bottom line
Cloud backup keeps your photo metadata. iCloud and Google Photos store your originals with EXIF intact and turn the GPS tags into a searchable map of where you have been. That is a feature, not a bug, and it is fine for a private library you control. The risk arrives when those metadata-rich originals leave the cloud, through a share link, a download, or a forward. Keep the rich data where it is useful, strip it from anything you send, and check the location toggle before you tap share.