MetaPurge

Photo metadata privacy risks: what one file can reveal

A photo can be honest about its subject and careless about everything else. Here are six ordinary situations where the unseen part of the file does the damage — and what each leak actually gives away.

By Rajat Malik Updated 8 min read

The picture shows a bicycle against a wall. The file also records the wall's coordinates, the camera body that shot it, the minute it happened, and the editor that resized it for the listing. None of that is visible in the image, and all of it travels with the file when you upload it.

None of these are exotic attacks. Each is something a normal person does on a normal day. What makes them work is that metadata is invisible, and invisible things are hard to reason about.

Why the file leaks

Metadata is stored as a separate part of the file, not painted into the pixels. Copying a file copies the metadata. Re-saving it in an editor may keep some, drop some, or rewrite it entirely, depending on the editor.

Uploading is copying. Once a file leaves your device, the recipient has whatever tags were in it, whether or not their interface displays them. A platform may strip metadata from the version it shows on a page and still hold the original. That is why the safe assumption is always that the tags are still there.

GPS in marketplace listings

Someone photographs a room they want to rent and posts four images. The phone was set to record location, as phones are by default. The GPSLatitude and GPSLongitude tags point at the building, usually to within a few metres — enough to identify the entrance, the side of the street and often the floor.

The listing may not show an address at all; the photos supply it. A worse variant: the photos were taken at a relative's house and reused for a different listing, so the coordinates describe a home that has nothing to do with the property. Both mistakes are common because the leak is not in the frame.

The fix is to remove location before the first upload, not after. See GPS coordinates in photos for what a coordinate pair actually resolves to.

Serials that link posts

Camera bodies write BodySerialNumber (0xA431) into the EXIF block, and many lenses write a matching lens serial. The value is stable across every photo the camera takes. Post a repair question on one forum, sell a lens on a marketplace, and publish a portfolio on a personal site, and all three can be tied together by a string of digits nobody looked at.

This is the leak people miss most often, because it requires no location permission and no obvious setting. It also survives trips, new hard drives and fresh accounts. The full list of related tags, including OwnerName and ImageUniqueID, is in camera serial numbers in photo metadata.

Timestamps and routine

DateTimeOriginal records when the shutter fired, often to a fraction of a second. A single timestamp is unremarkable. A set of them is a schedule: the hour you walk the dog, the weekday you leave early, the fortnight in which no photo was taken at home.

Combined with GPS, the pattern is stronger than either field alone. A public profile that mixes holiday photos and desk photos, each with location and time, describes occupancy. Someone scrolling a feed is not usually building that picture deliberately, but the data is there for anyone who wants it.

Edit history that disagrees

Software, ProcessingSoftware and the XMP history block record what touched the file. A picture offered as an untouched original can carry a desktop editor's name and a timestamp days after the capture date. A scanned document described as a direct copy can carry a phone editor and a crop step.

This cuts both ways. Metadata is evidence, and evidence can support a claim as easily as undermine it. The practical risk is the mismatch: a file whose tags disagree with the caption invites a question the publisher is not prepared to answer.

Author fields and pseudonyms

Artist, Copyright, OwnerName and the XMP creator fields are meant for attribution, and people fill them in once and forget. An account posting under a handle can therefore ship a real name, a studio name, or an email address in every image. The handle is the disguise; the file is the signature underneath it.

The same fields are useful when they are intentional. The problem is inheritance: a camera bought second-hand may still carry the previous owner's name in OwnerName, and a template exported from a colleague's library may carry theirs.

Newsrooms, courts and files

A source photographs a document and sends it to a journalist. The image carries the coordinates of the room where it was taken, which may be the source's home. A reader submits a photo of a street incident and the file carries the submitter's device serial and the time they were there. In both cases the publication may strip metadata from the published copy and never think about the inbox copy.

Legal exhibits create the opposite tension. A court may want the original file exactly as captured, because metadata can establish when and how an image was made. The right move is to preserve a verified original in a secure location and handle a stripped working copy separately — never to launder the only copy. More on that in metadata for journalists and activists.

SituationTag behind itWhat it hands over
Rental or resale listingGPSLatitude, GPSLongitudeThe building, to within metres, whether or not an address is listed.
Posts across several sitesBodySerialNumber, LensSerialNumberA stable identifier that joins accounts, listings and portfolios.
Holiday and desk photosDateTimeOriginal, OffsetTimeDaily rhythm and periods when a place is empty.
"Unedited" originalSoftware, XMP historyAn edit trail that contradicts the caption.
Pseudonymous accountArtist, OwnerNameA real name or contact address behind the handle.
Tip sent to a newsroomGPS plus serialsWhere the source was, and which device they used.
Removing it after publishing is not removal The first upload is the disclosure. Search engines, caches, scrapers and other people's saved copies do not update when you fix the file on your own site. Strip before the file is shared, and treat any file you received as already shared with whoever sent it.

What to do about it

Check a file before you post it, not after. Look for location, serials, timestamps, software history and author fields, and remove by category rather than one tag at a time. Keep Orientation and the ICC colour profile: they keep the image upright and its colours accurate, and neither describes a person or a place.

Then verify. A second implementation reading the output is the only way to know the tags are gone; verifying metadata removal covers how. MetaPurge reads the container directly and rewrites the file without re-compressing the image, but the habit of checking matters more than the tool.

See what your photos are carrying

Drop an image in. MetaPurge lists every tag, then rewrites the file without touching a pixel.

Open the metadata remover

Rajat Malik Frontend architect and the author of MetaPurge. Builds browser tools that keep files on the device, and writes about the parts of the web that leak by default. rajatmalik.dev