A freelance copywriter landed a meeting with a major agency. She sent her proposal as a polished PDF — clean layout, strong rates, solid case studies. The creative director opened it, went to File → Properties, and saw the Author field read a competitor agency's name. She'd adapted a template she'd used for them six months earlier and never cleaned the metadata. She didn't get the contract.
That story isn't unusual. Every PDF you export from Word, Google Docs, or InDesign carries hidden metadata — a data layer your clients can read without any special software. For freelancers, this hidden layer can expose previous client names, your edit history, your real legal name if you trade under a different one, and the exact software you used to build the document.
None of it shows on the page. All of it is readable by anyone who knows where to look. And increasingly, the people you're sending proposals to — in-house legal, procurement, senior creative directors — do know where to look.
What PDF metadata actually exposes
When you export a proposal to PDF, your authoring software embeds a block of metadata into the file. The fields vary slightly by software, but the following are present in almost every PDF created from a word processor or design tool:
| Metadata field | What it typically contains | Risk for freelancers |
|---|---|---|
Author | Your full name from your OS account or Office profile | High |
Creator | The application used — "Microsoft Word", "Google Docs", "Adobe InDesign" | Medium |
Company | Your registered company name from Office settings | High |
Manager | A manager name pulled from corporate Office profile — sometimes a previous employer | High |
Keywords | Internal tags you or a previous user added during drafting | High |
Subject | A document subject field — can contain previous client names if templated | High |
ModDate | Exact timestamp of the last edit | Medium |
CreationDate | When the original document was first created | Low |
Beyond these standard fields, PDFs carry an XMP stream — an XML block embedded in the file that duplicates and sometimes extends all of these fields. Stripping the visible properties in Acrobat doesn't always remove the XMP stream. If you've ever used "Remove Hidden Information" in Acrobat and still seen metadata appear in ExifTool, that's why.
The real risks for freelancers specifically
The risks are different for freelancers than for large organisations. You don't have an IT department enforcing document hygiene before anything goes out. You're working fast, reusing templates, sending files directly from your laptop. That workflow creates specific exposures.
The template leak
You reuse a proposal template originally built for Client A. The Subject field still contains Client A's company name. Client B opens properties and sees it. At best, they wonder about your attention to detail. At worst, if Client A is a direct competitor, you've just created a serious problem.
The rate negotiation problem
Your ModDate timestamp shows the proposal was last edited at 11:47 PM the night before the deadline. A procurement buyer sees this and knows exactly how much pressure you were under. They open negotiation knowing your timeline was tight. The timestamp cost you leverage.
The legal name exposure
You work under a trading name — "Studio North" or "The Copy Collective" — but your Author field shows your full personal legal name from your Windows account. For many freelancers, keeping a personal name separate from a brand identity matters. Metadata collapses that separation silently.
The software credibility issue
You charge premium design rates. Your Creator field says "Microsoft Word 2019." A design-literate client notices. It doesn't matter whether Word is actually the right tool — the perception problem is real. What you built the document in shouldn't be visible in the document.
In Adobe Acrobat Reader: File → Properties → Description. Three clicks. No technical knowledge needed. On macOS: right-click the PDF → Get Info → More Info. On Windows: right-click → Properties → Details tab. Anyone can do this. Many do.
Check what your proposals are leaking
Drop your PDF into FileIntel. See every exposed field before your client does.
Contracts carry the same risk
Most freelancers think about proposals when this topic comes up. Contracts are just as exposed — and the stakes are higher.
A contract you send carries your Author field and ModDate. But it also reveals something more sensitive: the creation date. If a contract's CreationDate shows it was created three years ago and barely modified, a counterparty can infer it's a boilerplate you've used dozens of times. That shifts the negotiation dynamic before a single clause is discussed.
More concretely — if you used a contract template originally drafted by a solicitor or legal service, the Author field may still contain their name and company. You've just inadvertently disclosed your legal provider to a counterparty. Not a catastrophe, but not information you would have chosen to share.
If your contract workflow involves sending and receiving signed versions, consider the full chain. Every iteration of the document accumulates metadata. See our guide on redaction vs metadata removal for how these two operations interact in document exchange workflows.
How to remove PDF metadata from proposals — step by step
The correct workflow is simple. Do it once per document before it leaves your machine.
Export your proposal to PDF as normal
Finish the document in Word, Google Docs, Notion, or InDesign. Export to PDF. Don't worry about metadata at this stage — clean the output file, not the source.
Open FileIntel's PDF Metadata Remover
Go to fileintel.me/pdf-metadata-remover. No account, no upload — the tool runs entirely in your browser. Your file never leaves your device.
Review your Privacy Risk Score
Drop your PDF in. The tool shows a scored breakdown (0–999) of every exposed field — Author, Creator, Company, Keywords, Manager, timestamps. You'll see exactly what a client would see.
Strip and download
Click Strip Metadata. The tool removes all three metadata layers — the Info dictionary, direct field data, and the XMP stream. Download the cleaned file.
Verify before sending
Open the output in Acrobat Reader → File → Properties → Description. Author and Creator should be empty. If you see "FileIntel — fileintel.me" in the Producer field, the strip ran correctly.
The pre-send checklist
Make this part of your standard proposal workflow. Check it every time.
Does any client actually check this?
More than you'd expect. The people most likely to check are exactly the people freelancers most want to impress.
In-house legal and procurement teams deal with documents professionally. They know documents carry metadata. Checking it is standard due diligence in some organisations — particularly in financial services, law firms, and government contractors. A 2023 survey by the International Association of Privacy Professionals found that 68% of legal and compliance professionals had discovered unintended personal data in documents received from external parties.
Senior creative directors and experienced agency buyers have seen enough vendor proposals to know the tricks. Checking metadata takes three clicks and 10 seconds. Some do it habitually. And journalists — if you freelance for publications — make it their job to know what documents reveal.
Stripping metadata before you send signals something positive to clients who notice: you're careful with documents. That's a proxy for being careful with their information, their NDAs, their data. It's a small thing that compounds in the right direction.
The GDPR angle — relevant if you work with EU clients
If you work with clients in the EU or UK, there's a compliance dimension that goes beyond professional polish.
Under GDPR Article 4(1), personal data includes any information relating to an identified or identifiable natural person. Your full name in the Author field of a PDF shared with a third party is personal data. The ICO's data minimisation guidance requires that personal data shared be limited to what is necessary for the purpose. Metadata attached to a proposal serves no contractual function — it's incidental data transferred unnecessarily.
For freelancers this rarely becomes an enforcement issue. But it's worth understanding if your contracts include data protection clauses, or if you work with clients in regulated sectors like healthcare, finance, or legal services. See our GDPR and PDF metadata guide for the full regulatory picture.
Clean your proposals before they go out
Free, private, browser-only. Nothing uploaded to any server.
Frequently asked
This article is for general informational purposes. It is not legal advice. For GDPR compliance questions specific to your situation or jurisdiction, consult a qualified legal professional.