Metadata Privacy: What Your Video Files Reveal About You

Every video file you shoot on your phone embeds data you probably did not think about: GPS coordinates accurate to a few meters, your device make and model, a unique device identifier, the exact timestamp, the encoding software, and sometimes your name.

This metadata is useful for organizing personal media. It is a liability when you share it. File explorers hide most of it. Social platforms strip some of it — inconsistently. Most video processing tools pass it through untouched.

For professional workflows, metadata has an additional dimension: chain of custody. A production house converting archival footage to 3D needs to know which source file produced which output, what processing was applied, and whether any metadata from the original should be carried forward, stripped, or replaced. This is not paranoia — it is compliance, especially for broadcast delivery and licensed content.

anelo's preflight stage scans every input file for metadata and classifies each field into three categories. Safe fields (codec, resolution, duration, frame rate) are always preserved because they are needed for pipeline configuration. Warning fields (GPS, device ID, creation timestamps) are flagged for user review. Strip-on-export fields are recommended for removal before the processed output leaves the pipeline.

The scan happens before any processing begins. If your input file contains GPS coordinates, you know about it before the first frame is extracted — not after you have published the output.

Most users do not think about metadata until they need to. But metadata incidents — a published file revealing a location, a device, or a timestamp — are common enough that detection should be default behavior, not an afterthought.

The broader principle: a media pipeline that processes your content should not silently pass through information you did not intend to share. Detection is the first step. Control is the goal.