Mutual or One-Way NDA: Which One Fits the Deal?

A potential customer wants a demo of your product's architecture. A vendor wants to see your data before quoting. A possible acquirer wants your financials. Each of them sends a nondisclosure agreement, and each form is different: some protect only the sender, some protect both sides, and some quietly add terms that have little to do with confidentiality.

This post is for founders and operators at software and AI companies who sign or send NDAs before customer, vendor, partnership or investment conversations. It explains when a one-way NDA fits, when a mutual NDA fits, which terms change between the two, and what to look for in the other side's form. It is general information about contract practice, not a review of any agreement. For the mistakes that can make an NDA hard to enforce, see our post on NDA mistakes that make them unenforceable; this post does not repeat them.

The short answer

A one-way (unilateral) NDA protects information flowing in one direction: one party discloses, the other receives and promises to protect it. A mutual NDA protects information flowing in both directions, with each party acting as both discloser and recipient. Use the form that matches what will actually be shared. If only you are disclosing, a one-way NDA in your favor keeps the obligations clear. If both sides will share sensitive material, a mutual NDA avoids leaving one side's information unprotected. Either way, read the definitions, term, residuals and any add-on clauses, because those terms change the deal more than the label does.

When a one-way NDA fits

A one-way NDA fits when the information flow is genuinely one-sided:

• You are showing a prospective customer or partner your product roadmap, model architecture or source code, and they are sharing little or nothing in return.
• You are hiring a contractor or consultant who will see your confidential information. (For workers, the confidentiality terms usually sit inside a broader agreement; see the section on employees and contractors below.)
• A potential investor or acquirer is reviewing your materials. Some investors decline to sign NDAs at all, so ask before sending one. Our tech M&A due diligence checklist shows the kind of material an acquirer typically asks to see.

If you are the recipient of a one-way NDA, its confidentiality obligations generally run against you. That may fit if you are receiving and not disclosing, but if your team will also share rate structures, technical approaches or customer information during the conversation, check whether the agreement protects that information. A one-way NDA in the other side’s favor may not protect your disclosures, although a separate agreement may do so.

When a mutual NDA fits

A mutual NDA fits when both sides will share material they care about: a joint development discussion, an integration partnership, a reseller arrangement, or a vendor evaluation where you share your data and the vendor shares its security and technical details. A mutual form can also accommodate discussions in which either side may disclose confidential information, but the label alone does not mean the terms are balanced.

The tradeoff is that a mutual NDA binds you, too. If your team receives the other side's information, it must handle that information under the agreement's restrictions, including any limits on internal use and on tools. Our post on what the NDA says when someone pastes the other side's draft into an AI tool covers one common way recipients get that wrong.

What changes between the two forms

Switching from one-way to mutual is not just changing “Discloser” to “each party.” Check that the confidentiality obligations and related rights apply to each party in its role as discloser or recipient. The following terms matter in either form and may need adjustment when making the agreement mutual:

• Definition of confidential information. A discloser-friendly definition may cover information shared in different forms, whether or not marked confidential, subject to the agreement’s exclusions. A recipient-friendly definition may require marking, identification at disclosure, or written confirmation within a set time after an oral disclosure. In a mutual NDA, check whether the same definition applies to both sides; if it does, a broad definition you want for your materials also governs what you receive.
• Who discloses, and for what purpose. The purpose clause limits how the recipient may use the information. A narrow purpose ("to evaluate a potential integration between the parties' products") protects the discloser; a broad one gives the recipient more room.
• Exclusions. Common exclusions cover information that is publicly available through no breach of the agreement, already lawfully known to the recipient without a confidentiality obligation, independently developed without use of the protected information, or lawfully received from a third party without a confidentiality obligation. Check the wording and who carries the burden of showing an exclusion applies.
• Term. Two periods matter: how long the parties will exchange information, and how long the confidentiality obligation lasts afterward. A software company with trade secrets may want protection for trade secrets to last as long as they remain trade secrets, rather than ending after a fixed number of years. Our post on trade secrets and patents discusses trade secret protection, and our post on NDA mistakes covers open-ended terms.
• Return and destruction. Check whether the recipient must return or destroy materials on request, and whether archival and backup copies are carved out.
• Remedies. An NDA may state that a breach could cause irreparable harm and that the discloser may seek an injunction. Check whether that provision applies to both parties when they disclose information. A court will decide whether the applicable requirements for an injunction are met.

Residuals clauses and other add-ons

Some forms include a residuals clause that permits specified uses of information retained in the unaided memory of the recipient’s personnel. Its scope depends on the wording. For a company sharing technical know-how, it can significantly narrow the protection the NDA otherwise provides. If you are the discloser, consider striking it, limiting it to non-technical information, or excluding source code, trade secrets and personal data from it.

Other add-ons to watch for:

• Non-solicitation of employees. Some NDAs add a promise not to solicit or hire the other side's employees. That is a separate restriction from confidentiality, and it may be one-sided even in a "mutual" form. In California, Business and Professions Code section 16600 provides that, except as provided in that chapter, "every contract by which anyone is restrained from engaging in a lawful profession, trade, or business of any kind is to that extent void,"¹ so whether and how such a clause can be enforced is a question to review before relying on it.
• No license and no obligation. An NDA may state that sharing information grants no IP license and does not obligate either party to do a deal. Check whether those provisions apply to both parties and remain consistent with the access or use needed for the evaluation.
• Governing law and forum. A form from an out-of-state counterparty may name its home state's law and courts.
• Feedback clauses. A clause giving the recipient rights to use your "feedback" or "suggestions" can reach further than expected.

Negotiating the other side's form

When a counterparty sends its own NDA, consider whether a focused markup can address the material issues or whether the form needs a broader rewrite. Practical steps:

1. Confirm the direction matches reality. If you will also disclose, ask to make the form mutual.
2. Read the definition and purpose clause first; they set the scope of everything else.
3. Strike or narrow a residuals clause if you will share technical information.
4. Review any non-solicit or other add-on separately from confidentiality, and consider removing it if it is unnecessary or raises enforceability concerns; making it mutual does not resolve those concerns.
5. Check the term, especially for trade secrets.
6. Note what your team must do with the other side's information, and tell them.

If the NDA is a precursor to a larger commercial agreement, check whether the later agreement will replace it. Our post on MSAs and statements of work discusses the main commercial agreement; check its wording to determine whether it replaces the NDA, preserves it, or addresses earlier disclosures.

NDAs with employees, contractors and consultants

When the recipient is your own employee, contractor or consultant, a federal notice requirement applies. Under the Defend Trade Secrets Act, an employer "shall provide notice of the immunity set forth in this subsection in any contract or agreement with an employee that governs the use of a trade secret or other confidential information," and for this purpose "employee" includes "any individual performing work as a contractor or consultant for an employer."² The immunity covers certain confidential disclosures of trade secrets to government officials or an attorney solely to report or investigate a suspected violation of law, and certain disclosures in sealed court filings.² An employer can comply with the notice requirement by including a cross-reference in the agreement to a policy document provided to the worker that sets out the employer’s reporting policy for suspected violations of law.²

If an employer does not give the notice, it may not be awarded exemplary damages or attorney fees under the statute's trade secret remedies against an employee to whom notice was not provided.² The requirement applies to contracts and agreements entered into or updated after the subsection's enactment, which the statutory notes date to May 11, 2016.² This notice requirement applies to covered agreements with employees and individuals performing work as contractors or consultants for the employer, rather than every customer or vendor NDA merely because it addresses confidentiality.² Our posts on employee NDAs and AI tools and contractor classification cover the worker side.

Questions to settle before you sign

1. Who will actually disclose information in this relationship, and does the form's direction match?
2. Does the definition of confidential information cover what you will share, including oral disclosures?
3. Is the purpose clause narrow enough to protect your information?
4. How long do the obligations last, and are trade secrets protected for longer?
5. Is there a residuals, non-solicit, feedback or other add-on clause, and does it work for you?
6. If the recipient is your employee or an individual performing work for you as a contractor or consultant, does the agreement include the immunity notice or cross-reference a reporting-policy document provided to that worker?
7. Does your team know how it must handle the other side's information?

What this post does not cover

This post does not assess whether any NDA is enforceable, whether particular information qualifies as a trade secret, or how to respond to a suspected breach. It does not cover employee confidentiality agreements in detail or noncompete law. For the broader contract set a startup needs, see the contracts every startup needs.

How we can help

Accord & Shield Legal drafts, reviews and negotiates NDAs and the commercial agreements that follow them for companies in Arizona, California and Texas. To better understand the scope of your matter, you can schedule an initial consultation. The consultation is evaluation-only; no legal advice is provided. Representation begins only after an engagement agreement is signed and any required retainer is received. Please do not send confidential or sensitive documents before we confirm that we can assist.

This article is general information, not legal advice. Reading it does not create an attorney-client relationship. What a particular NDA should say depends on the parties, the information and the deal; consult an attorney about your situation.