The Freelancer's Guide to Safe Document Sharing
Freelancers share proposals, contracts, and deliverables constantly. Hidden metadata can reveal previous clients, personal details, and editing history.
The freelancer metadata problem
Freelancers share more documents with more parties than almost any other profession. Proposals, contracts, invoices, deliverables, portfolios, case studies — every client engagement generates a stack of files that moves between your machine and someone else's inbox.
The problem: freelancers routinely adapt documents from previous work. A proposal for Client B starts as a copy of the proposal for Client A. An invoice template carries over from engagement to engagement. A portfolio PDF bundles photos from multiple projects. Each adaptation carries forward metadata from the original — and that metadata can reveal information you never intended to share.
What metadata freelancers typically leak
Previous client names in templates
When you create a proposal by duplicating last month's proposal and replacing the content, the file's metadata may still reference the original. The author field, the template path, and the "Title" property in Word documents are all fields that persist through copy-and-edit workflows.
A consultant who sends a strategy proposal to a healthcare startup might not realize the document's properties panel shows "Company: Raytheon Defense" because the template originated from a defense contractor engagement. The new client now knows you work with defense companies — information that may be confidential, irrelevant, or strategically disadvantageous.
Personal identity in author fields
Your computer's user account name populates the "Author" field in every document you create. If your machine is registered to "Daniel J. Morrison" and you are working under a business name like "Morrison Consulting Group," the author field reveals your personal name rather than your brand.
Worse, if you purchased a used computer or inherited a work machine, the author field may show someone else's name entirely — creating confusion about who actually prepared the document.
Editing history in tracked changes
Freelancers who collaborate with subcontractors or editors often use tracked changes in Word. Even after accepting all changes, the revision XML can persist in the file. A deliverable that went through three rounds of editing with a subcontractor may still contain evidence that the freelancer did not write the content alone — which could matter if the contract specified original work by the named freelancer.
GPS in portfolio photos
Designers, photographers, architects, and real estate professionals share portfolios containing photos from project sites. Each photo may embed GPS coordinates revealing client locations. A photographer's portfolio that includes corporate headshots taken at a client's headquarters reveals that client's office location — potentially violating an NDA or simply sharing information the client would prefer to keep private.
Risks by freelancer type
Designers and photographers
Portfolio images are the primary risk. Every photo in a portfolio can carry EXIF data including GPS, camera model, and timestamps. A designer sharing mockup screenshots may inadvertently include metadata showing which design tools and versions they use — which could affect client perception if the tools are considered entry-level.
Copywriters and content creators
Proposals and content deliverables are typically Word documents or PDFs created from Word. The risks are template metadata (previous client names), author fields (personal name vs. business name), and tracked changes (revealing editorial process or collaboration with ghostwriters).
Developers and technical consultants
Documentation, technical specifications, and architecture diagrams often contain metadata. A technical spec exported from Notion or Confluence may carry workspace identifiers. A diagram created in draw.io or Lucidchart may embed the software version and account information.
Management consultants
Slide decks are the primary vehicle. PowerPoint files carry extensive metadata: author, company, last modified by, comments, speaker notes, and hidden slides. A consultant reusing a deck from a previous engagement risks exposing the prior client's name, internal commentary about the analysis, and speaker notes that contain preparation reminders not meant for the audience.
The template cascade problem
Many freelancers maintain a library of templates — proposal template, contract template, invoice template, project brief template. These templates are themselves documents with metadata. Every file created from a template inherits that metadata.
If your proposal template was originally created on your old laptop registered to your personal Gmail account, every proposal you generate from that template carries the original author information — even if you have since switched to a professional email and a new machine.
The fix is not just to clean individual documents but to clean your templates. Strip metadata from every template in your library so that new documents start clean.
The freelancer's pre-send checklist
Before sending any document to a client, check these items:
-
Open File > Properties (or equivalent) and review the Author, Company, and Title fields. Do they show your current professional identity, or something from a previous context?
-
Search for comments and tracked changes. In Word, go to Review > Accept All and then use Document Inspector to verify no revision data remains.
-
Check embedded images. If your document contains photos, each photo may carry its own EXIF metadata including GPS. The document-level metadata clean does not remove EXIF from embedded images.
-
Check the filename. A file named
Acme-Corp-Proposal-FINAL-v2-copy.docxtells the client more about your process than you might want. -
Verify after cleaning. Open the cleaned file and re-check the metadata fields. Manual cleaning can miss fields, especially in PDF files where metadata from the source Word document persists after conversion.
For freelancers handling more than a few documents per week, this manual process does not scale. A tool that automates the scan-clean-verify cycle eliminates the risk of forgetting a step.
Purgit scans your documents and images for hidden metadata — previous client names, personal information, GPS coordinates, editing history — and removes it before you send. Clean every file in seconds.
[Scan a File Free]