Post a photo of your lunch, and you may have just posted your home address.

Not in the caption. Not in the pixels. In the metadata — a block of text your phone quietly writes into every photo it takes. I build privacy tools for a living, and this is still the leak I see most often, because nobody ever looks at it.

What a single photo carries

Open a photo from your phone in a metadata viewer and you'll typically find:

  • GPS coordinates — latitude and longitude of where the photo was taken, often accurate to a few metres
  • Device make and model — and sometimes the serial number
  • Exact timestamp — date, time, and timezone offset
  • Software — the app that edited or exported the file
  • A thumbnail — a small embedded preview, which can show the original frame even after you crop the photo

That last one surprises people. Crop yourself out of a group photo, and the thumbnail inside the file may still show you standing there.

"But the platform strips it, right?"

Sometimes. Some social platforms strip EXIF data on upload. Some don't. Some strip it from the feed version but not from the downloadable original. Messaging apps differ again — send a photo "as a document" or file attachment and it often travels with every field intact.

The problem with "the platform probably handles it" is that it's a belief, not a test. The only way to know what a file carries is to read the file.

The 30-second check

Before you share a photo anywhere it matters:

  1. Read its metadata first. If you see GPS fields, the file knows where it was taken.
  2. Strip the metadata from a copy — keep your original, with its dates and organisation, in your own library.
  3. Re-read the cleaned copy. A strip you haven't verified is a hope, not a result.

I built PrivacyMetadata for exactly this workflow — it reads and removes metadata from photos, PDFs, documents, audio and video entirely in your browser, so the file never gets uploaded to a server in the first place. That design choice matters: a privacy tool that asks you to upload your private files to clean them has just moved the problem, not solved it.

The short version

  • Metadata is invisible, so it survives every "quick share"
  • GPS is the dangerous field, but device, time and thumbnails leak too
  • Platform stripping is inconsistent — verify, don't assume
  • Clean copies, not your library

Your camera roll is a diary you didn't know you were keeping. Read it before you publish from it.

Originally published at PrivacyMetadata.