FoddoLearn
Chapter 7 of 13 · Hands-on · 8 min

Tags travel with files, so strip them before delivery.

Scan a phone photo, count the EXIF and GPS tags riding along, strip them with a canvas re-export, and verify zero. All local.

Before you start

Your mission in this chapter

  1. Learn

    Remove accidental location and device clues without losing track of the delivered asset.

  2. Try

    Scan a camera image, inspect its tag groups, strip it, and verify the export before sharing.

  3. Prove

    You can distinguish metadata hygiene from pixel-level leak attribution.

Loading the interactive demo for "Tags travel with files, so strip them before delivery."… The lesson text below is already here. The hands-on part loads next (requires JavaScript).

Before a single pixel is watermarked, the file is already talking. A phone photo carries where it was taken, what took it, and what touched it since. Email attachments deliver all of it byte-identical.

Scan above with a real camera photo. The tag count is the lesson; the strip-and-verify loop is the habit.

Which tags hurt

GPS coordinates hurt immediately: home studios, shoot locations, travel patterns. Device serials hurt slowly: they link separate releases to one shooter across leaks.

Software and edit history hurt reputationally: clients see your toolchain, revision count and sometimes your username.

Why 'the platform strips it' is not a policy

Some routes strip on re-encode. Others preserve everything: email, file-mode transfers, original downloads. The table above is community-reported, not guaranteed, and apps change pipelines silently.

Strip at the source and platform-specific metadata behavior matters less. That is the most durable policy when pipelines change. Still compare the cleaned export: a canvas re-export can change color profiles, alpha, bit depth, animation, or file size.

Takeaways

  • Camera JPGs carry GPS, device IDs and edit history by default.
  • Screenshots often strip tags; 'send as file' is more likely to preserve them: know your route.
  • Strip-then-verify beats trust: re-scan the export before sharing.

Check yourself

Optional, local, instant. 0/2 answered.

  1. Which transfer preserves EXIF/GPS most reliably?
  2. Stripped metadata protects you against…
Evidence checkpoint

Prove the metadata boundary

Lab first

Confirm what metadata hygiene protects and what it cannot protect.

  1. File-mode transfers and screenshots have different evidence behavior.

  2. Stripped EXIF can protect location privacy while doing nothing to trace pixels.

  3. Metadata is only one part of an export pipeline.

For your niche

Photographers

Location data in client shoots is the classic disaster: home addresses in wedding galleries. Strip before the gallery link exists.

Subscription creators

Shooting under a pseudonym with GPS on has ended anonymity. Scan every batch; one tagged file in a hundred is enough.

Illustrators & designers

Software tags leak your toolchain and sometimes your licensed name. Harmless until a dispute makes it evidence.

Demo transcript

Questions creators ask

Keep handyLearn glossary11 recurring terms
Carrier
The image content that offers texture or edges where a watermark can be tested.

A carrier estimate is not a survival result.

Delivery ID
An identifier for one particular delivery event or copy.

Keep it separate from the stable recipient ID.

DCT
A transform that represents image blocks as spatial-frequency coefficients.

The Learn visualization is illustrative.

LSB
Least-significant-bit hiding: changing the smallest binary bit of pixel values.

It is fragile under common re-encodes.

Metadata
Attached file information such as EXIF, GPS, software, color, and creation tags.

Metadata hygiene does not protect pixel payloads.

Payload recovery
Successfully reading the hidden identifier from the exact leaked file.

This is different from visual similarity or carrier capacity.

Re-encode
Decoding and saving an image again, often with a different format or quality setting.

It can change pixels, metadata, dimensions, and color behavior.

Recipient ID
A stable opaque identifier for the person or account receiving a copy.

Never recycle it between recipients or releases.

Release ID
An identifier for a batch, edition, or release of content.

One recipient may receive multiple releases.

Similarity
A visual or perceptual comparison suggesting whether two files resemble each other.

It is triage, not attribution.

Stable map
A validated delivery record connecting a recovered ID to one unambiguous recipient.

Duplicate IDs break attribution.