01

A three-step privacy check

First confirm whether precise coordinates are present. Second, create a new file with GPS and related identifying fields removed. Third, analyze the output as a separate file.

Key points
  • Keep the original offline
  • Use a descriptive -clean filename
  • Verify latitude, longitude and altitude are absent
  • Check XMP location fields as well as EXIF GPS
02

Metadata is only one layer

Street signs, faces, reflections, landmarks and the file name can reveal information independently of EXIF. Metadata cleaning reduces one risk; it is not a complete anonymity tool.

03

Check more than two familiar GPS tags

Latitude and longitude are the clearest location fields, but a metadata set may also include altitude, direction, destination coordinates, GPS time or XMP location names. A useful privacy result checks the supported location group rather than hiding only one row.

Some photo libraries display a place from their own database even after the exported file is clean. Analyze the actual file you plan to share, not only the thumbnail or library information shown by the phone.

Key points
  • EXIF latitude and longitude
  • Altitude and direction
  • XMP location fields
  • Library data outside the file
04

What the reparse test confirms

All three controlled inputs began with a readable coordinate. The cleaner created new outputs, and the same parser returned no supported GPS fields afterward. The selected originals were never overwritten.

This is a focused metadata result. It does not remove a house number in the pixels, a landmark, a face, a vehicle plate or a revealing filename. The conclusion is intentionally limited to the tested embedded fields.

05

Use a two-pass sharing checklist

First inspect and clean metadata. Second, view the whole image at a readable size and check visible information. Crop or redact a new copy, then review the final export because editing software can add its own author, software or date fields.

For repeated workflows, keep a private master folder and a separate sharing folder. That simple separation reduces the chance of attaching the original by mistake and gives you a consistent file to recheck.

What this does not prove

A metadata result describes the fields and structures that the supported parser could read. It does not, by itself, prove authenticity, intent, authorship or the truth of the visible scene.

Sources