About Document Privacy Inspector
Cropping a picture in Word hides part of it rather than removing it, and every incremental save leaves the previous version of a PDF inside the file. Both survive a rename, an email and a forward, so the only way to know what you are sending is to open the container and look.
A Word, Excel or PowerPoint document is a ZIP archive of XML parts, and a PDF is a stack of objects appended to over time. Neither format was designed to forget. Alongside the text and pictures somebody meant to send, both carry the account name that produced them, the software and its version number, a timestamp on every component, and — depending on how the document came together — comments, deleted text, hidden worksheets, and links to folders on the author's own machine.
This opens the container and lists what is in there, item by item, with a note on what each one actually gives away. Saving a clean copy rewrites the property parts and copies everything else across untouched, then runs the same scan over the result and prints whatever is left. That last step matters: the findings that carry the most, tracked changes and cropped pictures among them, cannot be taken out without editing the document itself, and a tool that quietly implied otherwise would be worse than no tool.
The findings a clean copy cannot remove each have a fix inside the authoring application, and they are worth knowing because the report will keep listing them until you apply one. Tracked changes have to be accepted or rejected rather than merely hidden from view, since hiding them only changes the display setting. Comments have to be deleted rather than resolved. A cropped picture stays whole until you compress the pictures in the document with the option to delete cropped areas enabled, which is the only action that actually discards them. Hidden rows, columns and worksheets have to be unhidden and removed. For a PDF carrying earlier revisions, saving it as a new file rather than appending another incremental save is what collapses the history.
Common use cases
- Checking a CV or covering letter before applying, where the author name and template path give away where it was copied from.
- Reviewing a document before it goes to a client, a court or a journalist, when the company field or a comment thread would be awkward.
- Confirming that a redacted PDF really lost the redacted text rather than keeping it in an earlier revision.
- Auditing a deck for cropped screenshots before it is published or shared outside the company.