I need to send a contract to a client and I don’t want the PDF metadata to reveal internal filenames, tools, or editing history.

This feature helps you remove or reduce sensitive PDF metadata before sharing a contract with a client. It protects internal details—such as filenames, software identifiers, and editing traces—so the document looks clean and professional.

When sending contracts externally, PDF metadata can unintentionally expose internal filenames, author names, software tools used to create the file, and signs of prior edits. This feature provides a way to prepare a client-ready PDF by stripping or sanitizing common metadata fields before you share it. You use it as a final step after the contract content is approved, ensuring only the visible document content is delivered. By removing unnecessary metadata, you reduce the chance of leaking internal project naming conventions, tooling, or process details. This is especially useful for legal and sales workflows where professionalism and confidentiality matter. It also supports compliance and privacy practices by minimizing hidden information embedded in the file. The result is a cleaner handoff to clients, vendors, or external counsel. Use cases include sending signature-ready agreements, distributing finalized terms and exhibits, or sharing PDFs with partners where internal context should remain private. The feature is intended to protect metadata only and does not change the visible text of the contract.