A development agency has agreed to create a fully customized onboarding workflow for your product, and you’re about to sign an NDA on their paper. When reviewing the agreement, you notice that the NDA only protects the vendor's confidential information: their proprietary algorithms, techniques, and codebase. It’s a one-way NDA, so your pricing, roadmap, customer base, or any proprietary information you share could still be at risk of exposure.
Understanding the implications of a one-way vs. two-way NDA is critical to protecting your business in the short and long term. This article explains the structural differences between mutual and unilateral NDAs, when to use each, and the terms that matter regardless of structure.
What is a unilateral vs mutual NDA?
A unilateral (one-way) NDA is a confidentiality agreement that protects one party’s (the discloser’s) information by limiting how the other party (the receiver) can share or use it. In a unilateral NDA, the receiver is not expected to share confidential information, and the discloser has no responsibility to protect any it does.
By contrast, a mutual (two-way) NDA is often used in scenarios in which two parties share confidential information. It places confidentiality obligations on both.
The main difference between the two types of NDAs is who shares the information and who protects it. The appropriate structure depends more on how the information flows than on the size of the deal.
When to use each type
The choice between a mutual and a unilateral NDA often comes down to a series of questions: Who will share the confidential information? When will they share it? And could the roles flip during the course of the engagement?
Unilateral NDAs fit when there’s a clear receiver and discloser. For example:
- A vendor sharing roadmaps and growth plans with a company not sharing its plans.
- A company sharing sensitive financial information with an investor doing due diligence.
- A third-party vendor onboarded into an internal system with sensitive business data.
Mutual NDAs work when both parties are disclosers and receivers. For example:
- Joint venture discussions between two companies that will both share confidential information about their businesses.
- Product partnerships that require two companies to share roadmaps and technical information.
- M&A discussions where both acquirers and target companies share confidential information such as financial projections and customer lists.
A unilateral agreement works when one party is bearing the risk of exposure. But the lines can blur as partnerships get more complex, and one-way information sharing turns two-way. If it’s likely that the receiver will become a discloser over the course of the deal, err on the side of caution and choose a mutual NDA. Otherwise, you’ll have to amend your unilateral agreement or negotiate a mutual NDA down the line.
Can a unilateral NDA be converted into a mutual NDA later?
A unilateral NDA can be amended to include terms that protect the receiver’sinformation. Amending the agreement lets you maintain continuity between agreements, but it requires negotiating the changes and having both parties agree to and sign them. Alternatively, you can create a new agreement to include bilateral terms.
What counts as confidential information
Regardless of the direction information flows, the nondisclosure agreement must clearly define what’s considered “confidential information.” A definition that's too narrow can leave crucial information unprotected, while one that's too broad can make the agreement hard to enforce. Common categories of confidential information include:
- Intellectual property such as trade secrets that give companies a competitive advantage.
- Technical know-how and proprietary processes used to build a product or deliver a service.
- Product roadmaps that show the planned development of product offerings.
- Customer lists that identify your buyers and contain your customers’ personal information.
- Financials, including revenue reports, audits, cash forecasts, and even planned pricing changes.
Defining what doesn’t count as confidential information is just as important as defining what does. Standard exclusions include:
- Information that is already publicly available, such as company information on a website or published industry knowledge.
- Data, processes, or other information that a team developed independently from a project and without referring to confidential information.
- Proprietary information received from third parties authorized to share it.
Key NDA terms to know
Whether an NDA is mutual or unilateral has little to no bearing on its legal enforceability. Instead, what matters is whether the terms are clearly drafted and reasonably enforceable.
Use, sharing, and protection obligations
These terms draw boundaries around acceptable use and sharing of the confidential information within an NDA:
- Nonuse purpose limits: The limitations around how confidential information can be used. An NDA should clearly limit usage of confidential information to the specific purpose of the engagement.
- Third-party sharing permissions: With whom the receiving party can share confidential information and when. NDAs often allow disclosure to employees and outside advisors who need the information to perform deal work and who are bound to confidentiality obligations. Many NDAs also make the receiving party responsible if those representatives breach the agreement.
- Required standards of care: The expectations and obligations on recipients to keep the information confidential. Some NDAs name specific security measures, while others define what “reasonable care” includes.
Return, disclosure, and survival terms
Return, disclosure, and survival terms outline what happens to the information at the end of a relationship. These terms typically include return-or-destroy obligations that state whether the recipient must return the confidential data to the discloser or erase it, and how. NDAs may also have a compelled-disclosure exception, which protects recipients if they’re legally required to disclose the information.
Also note that some confidentiality obligations survive termination. For instance, limits on sharing non-trade-secret information can last two to five years post-termination, while the time limit on keeping a trade secret can be indefinite (or as long as the trade secret remains secret).
Overlooked terms that shift risk
Some terms don’t make risk visible at the outset. Residuals clauses, for instance, carve out information retained in a person’s unaided memory. While recipients and their teams can’t refer to notes they took or documents shared during the engagement, they may be able to use technical knowledge or procedural know-how they remember.
Affiliate sharing permissions are also worth flagging. If “affiliate” is defined too broadly, recipients can share information with parties they didn’t intend to. Also, look out for hidden IP assignment or license language that can transfer IP usage or ownership rights to the other party.
Drafting pitfalls to watch out for
Common pitfalls businesses overlook when drafting NDAs include:
- Overbroad definitions that leave too much room for interpretation and, therefore, confusion.
- Unnecessary noncompete or nonsolicitation language that creates restrictive covenants in what’s supposed to be a confidentiality agreement. This language can prevent you from working with or hiring certain people long after the deal’s end.
- Excessively long survival terms that extend confidentiality obligations longer than necessary, limiting what information your team can build on or reference for years into the future.
Common mistakes when using a mutual or unilateral NDA
- Role mismatch: An NDA that protects only the discloser (unilateral) when both parties share confidential information, leaving one side exposed.
- Overreach: Expanding an NDA's scope beyond confidentiality to include other restrictions, such as no-poach, nonsolicit, or noncompete, can lead courts to treat the NDA as a backdoor noncompete. Noncompetes are enforceable only in narrow circumstances and are banned in some states, so adding them to an NDA can weaken the agreement.
- Practical handling failures: Violating the NDA's terms, including unauthorized sharing and use, and failing to track when contractual obligations expire.
- Signing without reviewing counterparty terms: The counterparty’s NDA could include problematic residuals or IP language that you’d overlooked but will be held to.
- Treating NDAs as boilerplate: Though NDAs are standard across industries, the specific provisions within each are not. The right terms depend on the type of information being protected and the business relationship. Many NDA problems stem from a mismatch between the signed agreement and how the relationship operates in real life.
Crosby handles the commercial contract review layer
NDAs are a routine part of commercial transactions, from vendor onboarding and partnership discussions to customer trials and contractor engagements. Each NDA brings with it the potential for IP leakage, scope creep (a non-compete included in an NDA), or compromised confidentiality when the structure doesn’t match the deal. Crosby can help you catch these risks.
Crosby’s custom-built AI agents use market data and your preferences to take the first pass on contract redlines, and barred attorneys oversee the work. Median turnaround time is under six hours, and Crosby charges transparent, upfront fees.
Talk to Crosby about your next commercial contract.

