Metadata can reveal location, device details, authors, revision history, and timestamps, but it can also provide valuable provenance. There is no one-line answer here: it depends on evidence from the source, the specific properties named below, and the destination's real requirements.
A safe workflow considers who may process the file, what hidden data it contains, how long copies persist, and who can retrieve the result. Before anything else in “When - And when not - To remove file metadata,” weigh this observation: Photo EXIF may contain precise GPS coordinates.
Three findings that guide this choice
The core distinction
Photo EXIF may contain precise GPS coordinates.
The practical trade-off
Office properties can expose author and organization names.
The verification test
Removing metadata from archival masters can erase evidence and rights information.
A practical decision for this workflow
Strip sensitive metadata from delivery copies while retaining a controlled master where provenance matters.
Use removing metadata from archival masters can erase evidence and rights information. as the acceptance test on a representative source before committing an entire archive, publication, or delivery batch.
The privacy & workflows mistake to avoid here
Applying destructive metadata removal to the only archival copy.
That failure conflicts directly with the recommendation for “When - And when not - To remove file metadata”: Strip sensitive metadata from delivery copies while retaining a controlled master where provenance matters.
Review checklist before delivery
- ✓The file is approved for the selected processing environment.
- ✓Personal, location, revision, and author metadata were reviewed.
- ✓Temporary and saved-copy retention is understood.
- ✓The result is shared only through an authorized destination.
Judge “When - And when not - To remove file metadata” by whether the result passes these specific checks, not by whether a new file merely opens.