Plain-English guides on what's hidden in your files and how to get rid of it — privately, on your own device.
Bug-report screenshots carry hidden EXIF, device and sometimes GPS metadata too. Here's what rides along and how to strip it before you attach one to a ticket.
W-2s, 1099s and tax PDFs can carry device info, author names and timestamps alongside your most sensitive numbers. Here's what's actually in them, and the honest scan-vs-clean split.
Field photos from volunteers and staff can carry GPS and device data that puts the people in them at risk. A short checklist before photos reach a donor or the public.
Your thumbnail is a regular image file, and it can carry the same hidden EXIF, GPS and editing metadata as any photo. Here's what's in it and how to clean it before you upload.
Invoices and deliverables can carry author names, old client names, software fingerprints and edit history. Here's what's actually in there, and the honest scan-vs-clean split for PDFs.
Rental photos can carry GPS coordinates, device info and timestamps — a bigger issue than most landlords realize when a unit is still occupied. Here's what to check before posting.
Screenshots, sample images and docs bundled into a release can carry hidden metadata that lives in a repo's history forever. A short pre-release checklist for maintainers.
A screenshot dropped into a team channel or a support ticket can carry hidden metadata, and the frame can show more than you meant. Here's what to check before you post.
Scanned patient files can carry device serial numbers, author fields and timestamps that have nothing to do with the chart. Here's what's actually in the file, and the honest scan-vs-clean split.
A C2PA manifest is removable metadata. A robust watermark like SynthID is baked into the pixels. Here's the honest split, and why the two get confused.
PowerPoint and Keynote files carry author names, speaker notes, and edit history you didn't mean to share. Here's what's in a deck before you post or present it.
IPTC is the caption, credit and licensing metadata block photojournalism and stock photos carry. Here's what's actually in it, and how to check.
Portfolios, work samples and writing clips carry author names, file paths and edit history you didn't mean to send. Here's what to check first.
GPS, timestamps, and gear data ride along in every wedding gallery you deliver. Here's why it matters for private-venue shoots and how to strip it locally.
KYC uploads of your ID or passport can carry GPS, device info and timestamps that add nothing to verification. Here's what's actually in the file.
Mac screenshots aren't automatically metadata-free once an app, editor, or sync tool has touched them. Here's what to check before you share one.
Adoption listings and classifieds ads posted from home often carry embedded GPS pointing straight at your address. Here's what's in the file, and how to check first.
XMP is the editable metadata block Adobe and other tools write into files — author, captions, edit history. Here's what it is, and how to see and remove it.
Claim photos carry GPS, timestamps and device info that can help or complicate a claim. Here's what's actually embedded, and how to check before you submit.
Screenshots committed to a repo carry hidden metadata that lives in history forever, even after you delete the file. Check it before you push.
WhatsApp's compression strips some EXIF as a side effect — not a promise, and not if you send as a document. Here's what actually survives.
One photo's GPS tag is a small risk. A feed full of them is a pattern. A pre-post checklist for creators and influencers.
A negotiated contract PDF can carry an author name, an internal file path, or a negotiation timeline in its metadata. Here's what to check before you send it.
Attachments carry more than what's on the screen — metadata, tracked changes, invisible characters. A practical pre-send checklist.
Your phone writes GPS coordinates into every photo by default. How to turn it off, and what to do about photos already tagged.
A terminal or IDE screenshot can carry hidden file metadata — and often something more revealing sitting in plain sight in the frame. Check both.
Expense files aren't just numbers — scans and PDFs can carry device info, timestamps and author fields. Here's what's actually inside.
Scanned pages can carry a device serial number, timestamp — and some color printers add invisible tracking dots to the paper itself. Here's the honest split.
Profile photos can carry the exact GPS coordinates of your home in hidden metadata. Check and strip it before you upload.
An invisible character with a real name, U+200B — how it gets into pasted text, why it can matter, and how to find it.
Accepting changes and turning off tracking doesn't guarantee old edits are really gone from the file. How to check before you send.
Video files carry device, timestamp and sometimes GPS metadata too. What's actually in there, and what scrub covers today.
Some platforms strip some metadata on upload — inconsistently, and only after your original already left your device. Clean it yourself first.
GPS, camera info and edit history can ride along in listing photos. A short checklist for agents before photos hit the MLS.
Fragile watermarks: yes. Robust pixel-level and statistical text watermarks: no, by design. Here's the honest split.
EXIF is the hidden data block every photo carries — camera model, date, sometimes GPS. Here's what's actually in it.
A plain-English map of how data gets hidden inside photos, text and documents — and what's actually worth checking for.
A short, reusable checklist to run before any document goes out — metadata, tracked changes, hidden text and more.
Author, producer and XMP fields ride along in every PDF. Here's what's really in there and how to check before you send one.
A résumé file can carry your home address, its edit history, and even where you wrote it. Check before you apply.
Photos you post to sell something can carry your home's GPS. Here's how to strip it before you list.
Every photo your phone takes is tagged with the exact location. Strip it before you post pictures of your family.
Remote work means sending a lot of files to a lot of people. A quick check stops hidden data going out with them.
A Cyrillic "а" looks exactly like a Latin "a". How scammers use look-alikes — and how to catch them.
That "invoice" in your inbox might carry a macro — code that runs when you open it. How to check before you trust it.
Screenshots can carry metadata and capture edges you didn't mean to share. Here's how to check.
A black box over text often hides it without deleting it. Why redaction fails, and how to verify.
Editing and AI tools embed a signed provenance record in images. Here's how to strip it from your own work.
One file's metadata can point back to a source. The habit every reporter should have before sharing a document.
AI tools, cameras and editors now attach a signed provenance manifest to images. Here's what it is, and how to remove it.
A black box in a PDF viewer doesn't delete the text underneath. Here's why naive redaction fails, and how to check a document before you send it.
Every photo you post can reveal where and when it was taken. Here's how to strip it — losslessly, without uploading it anywhere.
Tracked changes, comments, hidden text, author names and macros travel with documents you send. Here's how to find them.
Zero-width and look-alike characters can watermark or fingerprint text you paste. Here's how to spot and clean them.