Metadata is not one single field
People often use “metadata” to mean the title or author shown in a viewer's Properties panel. PDF can carry information in several places: the document information dictionary, XMP metadata streams, annotations, embedded files, form fields, optional content, JavaScript actions and application-specific structures. A privacy review therefore cannot stop at one properties dialog.
Common information worth checking
- Title, author, subject, keywords, creator and producer fields.
- XMP metadata, which may duplicate or extend document information.
- Comments, sticky notes and review annotations that can include author names and timestamps.
- File attachments embedded inside the PDF.
- Form field values, including values that are not obvious on the current page view.
- Links and actions.
- Layer names or optional-content groups in complex design files.
Redaction is not the same as metadata sanitisation
Correctly redacting a paragraph should remove the sensitive page content, but the same secret could still appear in a title, comment, attachment or form value. That is why high-risk disclosure workflows often use both content redaction and a separate sanitisation/review step.
Creator and producer fields are not automatically a problem
Many PDF applications identify the software that created or last processed a file. That can be useful for troubleshooting. The privacy question is whether a field exposes information you did not intend to share, such as a personal name, internal project title or organisation-specific path.
Incremental saves deserve special attention
Some PDF software appends new revisions rather than rewriting the entire file. That can leave earlier objects in older sections of the file even when the latest view no longer references them. This is one reason secure redaction software should not merely draw a rectangle over text and append a new revision.
A practical pre-share checklist
- Open document properties and review title, author, subject and keywords.
- Open the comments/annotations panel and remove review notes you do not intend to share.
- Check for attachments.
- Review form fields.
- If you redacted anything, test copy/paste and text extraction from the redacted area.
- For sensitive files, inspect the result with a second tool and keep the original separate.
Local processing reduces one privacy risk, not every risk
Processing a document in the browser can avoid uploading the file to an application server, which reduces network exposure for supported workflows. It does not magically remove metadata already present in the document, and it does not replace careful handling of the exported file afterward.