TL;DR
On this page
A one-way NDA protects only the client's information. A mutual NDA protects both parties equally. Most freelancers sign whatever the client sends without checking which type it is, and most client-provided NDAs are one-way by default.
This matters because if you share proprietary frameworks, tools, or methodologies during a project and only signed a one-way NDA, the client has no legal obligation to keep your methods confidential. They could share them with another freelancer or use them internally without restriction.
According to a Freelancermap survey, 74.7% of freelancers are asked to sign an NDA before starting work. But most never ask which type it is or whether it should be mutual. This guide covers the exact scenarios where each type applies and how to negotiate when the wrong type lands in your inbox.
How Each Type Works
| Feature | One-Way (Unilateral) | Mutual (Bilateral) |
|---|---|---|
| Who is protected | Only the disclosing party (usually the client) | Both parties equally |
| Who has obligations | Only the receiving party (usually the freelancer) | Both parties |
| Complexity | Simpler, shorter document | Slightly longer, more balanced |
| Common in | Standard freelance projects | Partnerships, collaborations, joint ventures |
| Default from clients | Yes -- most client NDAs are one-way | Rare -- you usually have to request it |
pro tip
According to a MoldStud survey, 30% of freelancers successfully negotiate more balanced NDA terms when they ask. The key is explaining why mutual protection benefits both parties rather than framing it as a demand.
6 Scenarios: Which NDA Type You Need
Scenario 1: Client Shares Business Data With You
Use: One-way NDA (standard)
The client shares login credentials, customer lists, financial data, or internal processes so you can do your work. You do not share anything proprietary of your own -- you apply general skills to their specific data.
Examples: Writing blog posts using client's brand guidelines, designing a website using their content, bookkeeping with access to their financials.
A one-way NDA is appropriate here. The client has sensitive information to protect. You do not.
Scenario 2: You Share Proprietary Frameworks or Tools
Use: Mutual NDA
You bring custom tools, proprietary processes, or specialized methodologies to the project. A branding consultant who uses a proprietary discovery framework. A developer who uses custom code libraries. A marketing strategist who shares proprietary audience research methods.
Without a mutual NDA, the client could document your methods and use them without you -- or share them with a cheaper freelancer.
Scenario 3: Joint Product Development
Use: Mutual NDA
Both parties contribute intellectual property to create something new. A freelance developer and a startup co-building a product. A designer and a client collaborating on a new brand identity where both bring creative direction.
This is the clearest case for a mutual NDA. Both parties have something to lose if the other shares prematurely.
Scenario 4: Agency Subcontracting
Use: One-way NDA (from the agency)
An agency hires you as a subcontractor and shares their client's confidential information. The NDA is between you and the agency. It is almost always one-way because the agency is the disclosing party and you are the receiving party.
This is standard and generally fair. The agency needs to protect their client's data. You are performing work under their umbrella.
Scenario 5: Pitch or Discovery Call
Use: Mutual NDA or none
A potential client wants to discuss their project before hiring you. They will share business details. You might share your approach, pricing strategy, or creative ideas.
If both parties are sharing substantive information, a short mutual NDA before the call is reasonable. But for a standard 30-minute discovery call, most freelancers skip the NDA entirely. The risk of idea theft from a brief call is low, and requesting an NDA before even discussing the project can feel heavy-handed.
Practical rule: If the call involves specific trade secrets or detailed technical architecture, use a mutual NDA. If it is a general project discussion, skip it.
Scenario 6: Open Source or Public Work
Use: No NDA
If your work will be publicly visible -- open source contributions, public portfolio pieces, published articles -- an NDA is unnecessary and potentially contradictory. You cannot agree to keep something confidential that is meant to be public.
If a client asks you to sign an NDA for work that will be published publicly, flag the contradiction before signing. They may have sent a boilerplate NDA without thinking about the project type.
How to Negotiate a One-Way NDA Into a Mutual One
Most clients send one-way NDAs by default because their legal team drafted a standard template. It is rarely a deliberate choice to exclude your protection. Here is how to handle it:
Step 1: Read the NDA carefully. Identify which party is the "Disclosing Party" and which is the "Receiving Party." If only the client is listed as the Disclosing Party, it is one-way.
Step 2: Assess whether you need mutual protection. If you are not sharing anything proprietary, a one-way NDA is fine. Do not negotiate for the sake of negotiating.
Step 3: If you do need mutual protection, explain why. Example email:
"I reviewed the NDA and noticed it is structured as a one-way agreement. Since I will be sharing [my proprietary design framework / custom code libraries / research methodology] during this project, I would feel more comfortable with a mutual NDA that protects both of our confidential information equally. I can send over a mutual version if that is helpful."
Step 4: Offer to provide the mutual NDA yourself. This removes friction. The client does not have to redraft anything -- you provide the document. Use our free NDA template as a starting point.
Red Flags in One-Way NDAs
Not all one-way NDAs are fair. Watch for these clauses:
| Red Flag | Why It Is a Problem |
|---|---|
| Perpetual duration | No end date means indefinite obligation. Negotiate to 2-3 years. |
| Overly broad definition | "All information" is vague and may not be enforceable. Push for specifics. |
| No exclusions clause | Without standard exclusions, you could be liable for information you already knew. |
| Non-compete disguised as NDA | Some NDAs include clauses that prevent you from working with competitors. This is a non-compete, not an NDA. |
| Portfolio restriction | Prevents you from showing the work in your portfolio. Negotiate a carve-out. |
For a full guide on NDA red flags, see freelance client red flags. For template sections and customization, see free NDA template for freelancers.
NDA Type Decision Checklist
Create Your NDA in Minutes
FreelanceDesk includes free NDA templates for both mutual and one-way agreements. You can also use the NDA generator to customize and export a professional PDF.
No account required. Your data stays on your device.
References
- Freelancermap. "Non-Disclosure Agreement (NDA) for Freelancers." freelancermap.com, 2026.
- EveryNDA. "Unilateral vs Mutual NDAs." everynda.com, 2026.
- Legislate. "The Key Differences Between Unilateral and Mutual NDAs." legislate.ai, 2026.
- Sirion. "Unilateral vs Mutual NDA." sirion.ai, 2026.
- Adobe. "What Is a One-Way NDA?" adobe.com, 2026.
- MoldStud. "Freelancer NDA Negotiation Survey." moldstud.com, 2025.
- DocLegal. "NDAs for Freelancers." doclegal.ai, 2026.