Find the information a document carries beyond the words on the page.

Hidden context

The visible page is only one layer of a file

Office documents, PDFs, images, and design files may retain author names, timestamps, device or software details, comments, tracked changes, hidden rows, speaker notes, embedded attachments, and previous versions. Some of that information supports collaboration; the same information may be inappropriate in an external delivery copy.

Privacy review is not about deleting every property from every file. It is about understanding which context is necessary for the recipient and which context creates avoidable disclosure.

Clean-copy workflow

Separate the working file from the delivery file

Keep the collaborative original when records or future editing matter. Create a distinct delivery copy, remove comments and unresolved changes, verify hidden content, inspect document properties, and open the result in a fresh viewer. This avoids destroying useful history while reducing what leaves the controlled workspace.

Use a filename that clearly identifies the approved version. Do not rely on labels such as “final-final2” to communicate authority. A simple version and approval convention reduces the chance that the wrong copy is attached or uploaded.

Redaction

Covering text is not the same as removing it

A black rectangle, white font, cropped screenshot, or flattened annotation may leave the underlying content recoverable. Use a tool designed for redaction, apply the redaction, sanitize hidden content where appropriate, and test the exported result by searching, copying, selecting, and inspecting it.

When legal, regulatory, or investigative records are involved, preserve the original and follow the required review process. Privacy cleanup should not silently alter an official record or remove information that must be retained.

Images and scans

Review location, device, and background details

Photos can include location and device metadata. Scans can reveal margin notes, barcodes, signatures, desk contents, or another page beneath the target. Screen captures may include account names, browser tabs, notifications, or internal URLs.

Crop deliberately, inspect the full frame, remove metadata when the use case calls for it, and avoid assuming that converting a document to an image automatically removes all sensitive context.

Distribution

Privacy also depends on where copies accumulate

A clean file can still spread through personal email, chat downloads, desktop folders, cloud-sync clients, browser caches, mobile previews, and backups. Choose a sharing method that limits duplicate copies where possible and has an owner for expiration or revocation.

Pair document review with the encrypted file sharing guide. One protects the file’s hidden context; the other controls the route and audience.

Preflight checklist

Before an external document leaves your control

• Confirm the intended recipient, approved version, and correct filename.
• Resolve or remove tracked changes, comments, notes, hidden rows, hidden slides, and embedded objects as appropriate.
• Inspect document properties and image metadata on a delivery copy.
• Use real redaction tools for content that must be removed and test the result.
• Open the file in a clean viewer and review every page, sheet, slide, and attachment.
• Choose named-recipient sharing, minimal permissions, and expiration for sensitive material.