Mutual vs Unilateral NDA: Which Should a Freelancer Sign?
The NDA your client sends you almost certainly only protects them.
That's not unusual or inherently sinister — it's just the default. Clients have legal teams or templates designed to protect their interests. Nobody on their side is thinking about what you might need protected. So the document arrives, you sign it, and the information flow is now completely one-sided: their confidential information is legally protected, yours is not.
For many engagements, that's fine. If you're a developer hired to build a specific feature and the client is sharing internal system architecture with you, a unilateral NDA covering their information is proportionate. You're not sharing anything sensitive.
But sometimes you are. You're sharing your pricing, your proprietary methodology, your client list, your business processes — information that has genuine value and that you'd prefer the client not use or disclose. When that's the case, you should be asking for a mutual NDA. Most freelancers don't know this is an option, and clients count on that.
Here's how the two document types differ, when mutuality actually matters, and how to request it without awkwardness.
What a Unilateral NDA Is
A unilateral NDA — sometimes called a one-way NDA — creates confidentiality obligations that run in only one direction. One party (the Disclosing Party) shares confidential information. The other party (the Receiving Party) agrees to protect it. The obligations are entirely on the Receiving Party.
In a freelance context, the structure looks like this: the client is the Disclosing Party; you are the Receiving Party. You agree not to disclose, use for other purposes, or fail to protect the client's confidential information. The client makes no equivalent promise about anything you share with them.
The language that signals a unilateral structure is usually in the opening recital or definition section:
"Company desires to disclose certain confidential information to Freelancer for the purpose of evaluating a potential engagement. Freelancer agrees to maintain the confidentiality of such information on the terms set forth herein."
Note what's absent: any obligation on the Company's side. The Company can take everything you share during the evaluation — your rates, your process, your approaches — and face no contractual consequence for disclosing or using it.
Unilateral NDAs are entirely enforceable and widely used. The issue isn't that they're illegitimate. The issue is that they're the default even in situations where the information flow isn't one-sided.
What a Mutual NDA Is
A mutual NDA — also called a bilateral NDA or two-way NDA — creates confidentiality obligations that run in both directions. Both parties may be both Disclosing Party and Receiving Party depending on what information they share. Both parties agree to protect the other's confidential information on equivalent terms.
The mutual structure usually appears in the opening like this:
"Each party (as 'Disclosing Party') may disclose certain confidential information to the other party (as 'Receiving Party'). Each party, as Receiving Party, agrees to maintain the confidentiality of the other party's Confidential Information on the terms set forth herein."
This single shift — defining each party as potentially both Discloser and Receiver — creates a symmetric document where the same rules apply to both sides.
Mutual NDAs aren't more complex than unilateral ones. They're often the same length. The obligations are the same in both directions. The main structural difference is that "Company" and "Freelancer" are replaced with "Party A" and "Party B," or the document uses "each party" and "the other party" consistently instead of defining one side as the permanent Discloser.
Which Is More Common for Freelancers?
Unilateral NDAs are far more common in freelance engagements — not because they're more appropriate, but because clients send what their legal team drafted, and legal teams draft to protect their client.
This creates a systematic imbalance: the default document in every freelance NDA exchange is designed exclusively to protect one party. There's nothing stopping you from asking for a mutual NDA — the client may simply never have considered it, and a short conversation can resolve it.
In practice, mutual NDAs are most common in:
- Joint ventures and partnerships where both parties are sharing genuinely proprietary information
- Enterprise vendor agreements where the vendor (your freelance business) is itself a sophisticated entity with trade secrets
- Technology development engagements where you're sharing your own proprietary tools or methods as part of the work
- Consulting relationships where you share frameworks, processes, or client data from your practice
They're less common in short-term project work where the information flow is genuinely one-directional — you're receiving the client's specs, building to them, and the main confidential information is theirs.
The key question is whether you're actually sharing anything worth protecting. If you are, you should have a mutual NDA. If you're not, the asymmetry of a unilateral NDA may not cost you anything in practice.
When to Ask for a Mutual NDA
You should request a mutual NDA when you're disclosing information that has genuine business value — information that, if shared with competitors or used against you, would cause real harm.
Pricing and rate structures. Your rates are business-sensitive information. If a client shares your pricing with competitors, or uses knowledge of your rates to renegotiate future contracts below your floor, that's a concrete harm. A mutual NDA prevents this.
Proprietary methods and frameworks. If you've developed a consulting methodology, an auditing framework, a design system, or a technical architecture you use across clients, sharing it during an engagement gives the client access to your intellectual infrastructure. Without mutual protection, nothing prevents them from reverse-engineering your approach and using it internally or sharing it.
Your client list. Mentioning current or past clients during a pitch or onboarding conversation is normal. Under a unilateral NDA, the client can share that list freely. If you're working in a space where client relationships are competitively sensitive, mutual protection matters.
Business processes and pricing relationships. Your vendor rates, subcontractor relationships, and operational processes are business-sensitive. If you share them as part of onboarding or project planning, a mutual NDA prevents the client from using that information to cut you out of a relationship.
Pre-proposal discovery. During scoping conversations, clients sometimes ask detailed questions about your technical approach or current client work. You're effectively disclosing proprietary information in order to win the project. If you don't win it, that information remains with the client unprotected unless the NDA is mutual.
If any of these apply, open the mutual NDA conversation before the project starts — not after you've already disclosed the information.
What Clients Typically Say — And How to Respond
Clients who receive a mutual NDA request usually respond in one of a few ways. Here's how to handle each:
"We don't share confidential information with freelancers."
"That makes sense — I'm not expecting you to. The mutual structure is standard for engagements where I'm sharing my rates, methodology, or client relationships during scoping. I'm happy to keep the document simple. I just want equivalent protection for what I'm sharing on my side."
Most clients accept this framing. They weren't thinking about what you share — they were only thinking about what they share. Pointing it out gently resolves most objections.
"Our legal team won't sign mutual NDAs — it's our standard form."
"I understand. Could we add a brief clause to your standard form covering the information I'll be disclosing? I don't need to replace your document — just add a paragraph covering my rates, methods, and client references on equivalent terms."
This approach works because you're not asking them to abandon their template — you're asking for a targeted addition. Most legal teams can accommodate a short addendum clause.
"Why does it matter? We're not going to share your information anyway."
"I appreciate that. The mutual structure just puts that commitment in writing. It's not that I distrust you — I use mutual NDAs as a baseline for any engagement where I'm sharing business-sensitive information, the same way you use NDAs as a baseline for sharing yours."
Framing it as a professional standard rather than a trust issue removes the adversarial element. You're not accusing them of anything. You're applying a consistent practice.
"I've never had a freelancer ask for this before."
"It's not common, but it's standard practice in legal and consulting services, and increasingly common in tech. I'm not asking for anything unusual — just that both sides have the same basic protection."
This is true. The asymmetry of unilateral NDAs is a convention, not a legal requirement.
Hidden Risks of Unilateral NDAs for Freelancers
Beyond the obvious information protection gap, unilateral NDAs create two less visible risks worth understanding.
The negotiation signal. Signing a unilateral NDA without comment signals that you're not paying attention to what you're signing. Clients — particularly sophisticated ones — notice. Asking for appropriate protection (or at least asking about it) signals professionalism and legal awareness. This isn't about being difficult. It's about establishing that you read contracts before you sign them.
The scope creep risk. Unilateral NDAs define the Disclosing Party's information as confidential. They don't define what happens when you share information. In practice, some clients treat everything shared in the engagement as "their" confidential information — including work product you created, tools you brought to the project, and insights you generated. Without mutual language defining your information as separate and protected, the scope of "the client's confidential information" can expand informally to cover things that were never theirs.
The IP interaction. In many unilateral NDAs, the Receiving Party (you) is also subject to an IP assignment clause. You're assigned as the Receiving Party for confidentiality purposes, which creates the assumption that you're on the receiving end of the relationship more broadly. A mutual NDA structures both parties as symmetric contributors, which can create a better foundation for negotiating IP terms — particularly around pre-existing tools and work product you bring to the engagement.
Example: Unilateral vs Mutual Opening Clause
Here's what the structural difference looks like in actual contract language.
Unilateral:
"This Non-Disclosure Agreement ('Agreement') is entered into between Acme Corp ('Company') and the undersigned freelancer ('Recipient'). Company desires to disclose certain proprietary and confidential information to Recipient for the purpose of evaluating and performing services. Recipient agrees to hold such information in confidence in accordance with the terms herein."
The Company discloses. The Recipient receives and is bound. No reciprocal obligation exists.
Mutual:
"This Mutual Non-Disclosure Agreement ('Agreement') is entered into between Acme Corp ('Company') and the undersigned freelancer ('Freelancer'). In connection with the parties' evaluation of and work on a potential engagement, each party (as 'Disclosing Party') may disclose to the other party (as 'Receiving Party') certain proprietary and confidential information. Each party, as Receiving Party, agrees to hold the other party's Confidential Information in confidence in accordance with the terms herein."
The language is nearly the same length. The practical effect is entirely different — both parties bear the same obligations for the information they receive.
FAQ
Is it normal to ask a client for a mutual NDA?
Yes, though it's less common than it should be in freelance contexts. In professional services, consulting, and legal engagements, mutual NDAs are standard. In freelance tech and creative work, clients often send unilateral templates as the default, but most are willing to discuss mutuality when asked professionally. The conversation is rarely contentious if you frame it correctly.
Can I convert a unilateral NDA to mutual with a simple addendum?
Yes. If the client won't replace their unilateral template, propose an addendum clause that establishes mutual protection for information you disclose. Something like: "Notwithstanding the foregoing, Company agrees to maintain the confidentiality of Freelancer's rates, methodologies, client relationships, and proprietary processes disclosed in connection with this engagement on equivalent terms to those set forth herein." A short addition like this, signed by both parties, creates enforceable mutual protection without requiring a full document replacement.
Does a mutual NDA give me more negotiating power on other clauses?
Not directly — the NDA type doesn't change the terms of other clauses. But there's an indirect effect: entering the engagement with a mutual document establishes that both parties are treating each other as peers with equivalent interests. That posture can make it easier to negotiate IP carve-outs, portfolio rights, and non-compete scope, because the framing of the relationship isn't inherently one-directional.
If I sign a unilateral NDA and then share sensitive information anyway, am I protected?
No. Information you share without contractual protection has no confidentiality protection regardless of what you intended or what the client promised verbally. If you're sharing sensitive information, get the mutual protection in writing before you share it — not after.
Is a mutual NDA harder to enforce than a unilateral one?
No. Mutual NDAs are enforced by the same legal mechanisms as unilateral ones. If either party breaches, the other party can pursue the same remedies: cease-and-desist, injunction, damages. The mutual structure doesn't weaken the document or create ambiguity — it just ensures both parties have standing to enforce it, rather than only the client.
Reviewing an NDA and wondering whether to ask for mutual terms? Upload it to NDA Guard for a clause-by-clause analysis in 60 seconds — including flags for one-sided obligations.