Reusing a Word Template for a New Client? What File Metadata Can Still Reveal About the Last One
What NearScrub clears before you send a reused template, and the tracked-changes layer it honestly can't touch.
Practical guides to working with files and getting more from your tools.
What NearScrub clears before you send a reused template, and the tracked-changes layer it honestly can't touch.
FindLaw's consumer-advice blog warns about a different, unaudited photo: the selfie you send a match directly once you're chatting, which could let someone "figure out your exact location and show…
What stripping that metadata before you upload a photo to any auction house, appraiser, or insurer changes — and the camera file format it can't touch.
What that split means for the resale, skincare-progress, and lost-pet subreddits people post photos to daily, and the one common iPhone photo format NearScrub can't scrub before you get there.
What a browser-based scrub removes from that specific, unregulated gap, and what it was never built to touch.
Only one of those two sources is something a photo metadata scrubber like NearScrub ever touches.
What scrubbing metadata before you post actually changes here, and what it structurally can't.
What a browser-based scrub that rewrites the file's structure instead of clearing a reference does differently — and what it still can't touch.
What scrubbing a photo's metadata before you upload it changes when the person who ends up with a copy is an employee with legitimate access, not an outside hacker — and what it can never change.
What a metadata scrubber actually removes from an uploaded ID photo — and why it has nothing to do with the risk that breach demonstrated.
What that means for the one file type this blog otherwise always tells you to scrub before sending: an insurance claim photo, where removing EXIF/GPS/timestamp data works against the person filing…
What scrubbing a file's metadata before you upload it actually removes from that kind of breach — and what it can't touch: account data, OCR text read straight off the image, and files already…
Neither documented case is actually about GPS data hidden inside a photo file — what they're about instead, and the narrower, real place metadata scrubbing fits into a home sale (including a gap in…
A separate, more recent risk (the 2023 Makiivka strike, cited by the Marine Corps Commandant in 2025) is network-level phone tracking, not a file tag — and NearScrub, which only removes embedded…
What NearScrub's EXIF removal covers for JPEG/PNG exports, and where it stops: RAW files and the app's own location field.
The Document Foundation's own October 2025 post says exactly what an OpenDocument file's meta.xml holds — author name, change history, custom properties — and what NearScrub's ODF support clears…
Two camera-identity fields in EXIF, what NearScrub clears from JPEG files, and what it can't touch — the camera's own menu, and RAW files.
Why Arizona's Supreme Court called metadata part of the document, and why scrubbing is a step whose position in the sequence is last.
Which of a PDF's three layers a metadata scrubber reaches, which two it does not, and why property-clearing has to be the last step.
Which copy to keep intact, and which to scrub before it leaves.
Stripped for whom — and what scrubbing before upload actually changes.
What a breach reveals about the three layers of a leaked photo — and the one layer you can close before uploading.
Which of a photo's two location channels a scrubber can actually close, and which one it can't.
How to send full quality without sending where you've been.
Why the patches didn't fix files that already exist, and precisely where NearScrub's PNG rewrite reaches — and where it doesn't.
What the statute's "authority of the copyright owner" clause means for scrubbing your own files — and why other people's files are a different case entirely.
What that advice actually covers — EXIF GPS baked into the photo file — versus what it doesn't (a caption you typed yourself), and what NearScrub clears in the browser before a move-in photo goes…
What a manuscript's Word and PDF properties actually contain, and what NearScrub clears in the browser before a submission goes out.
What's actually in those fields, and what NearScrub clears in the browser before the file is ever uploaded.
What the guides' own recommended workarounds miss, and where a browser-based scrubber like NearScrub fits alongside face-blurring tools like Image Scrubber.
C2PA's FAQ says "any modification—intentional or accidental—will break this cryptographic linkage." Where a C2PA manifest actually lives in a JPEG versus where EXIF/XMP live, and what that means for…
What that guidance actually covers versus what it doesn't — real-time tracking, stalkerware, and visible landmarks a file scrubber can't touch.
What the regulators actually flag — hidden EXIF/GPS data versus what's visible in the frame — and where NearScrub reaches (and where iPhone's default HEIC format means it doesn't, yet).
What a Word or PDF resume's hidden metadata actually contains, and what NearScrub clears in the browser before you send it anywhere.
It's the same problem EFF wrote about after a 2012 hacker arrest — and the fix is the same: strip it yourself before the file ever leaves your device.
What the split means for a Word or PDF file leaving your hands, and where a client-side scrubber like NearScrub reaches — and where it structurally can't.
What to actually check before selling something online.
What journalists' own security guidance says about each layer, and where a browser-based scrubber like NearScrub actually reaches.
What each part actually stores, and what NearScrub can and can't clear.
Three real, documented cases of metadata exposure — John McAfee's 2012 arrest via EXIF GPS, Adam Savage's 2010 geotagged home-address tweet, and the UK's 2003 "dodgy dossier" author metadata leak —…
Two real fixes from scrub-core.js: an unsigned-length coercion for PNG chunks, and a declared-size budget that rejects zip bombs before decompression starts.