Mutual NDA document pack

An NDA isn't a magic spell. It's a written agreement that two parties will treat each other's secrets like secrets — useful exactly to the extent that both sides actually do.

Who this pack is for

You and another party — a potential business partner, contractor, advisor, or buyer — are about to share information neither of you wants the other to repeat. Maybe you're exploring a partnership, evaluating a contractor, having an early-stage acquisition conversation, or onboarding someone who'll see your customer list, source code, financials, or product roadmap. Both parties are sharing roughly equal amounts of sensitive information (otherwise use the one-way NDA). You want a signed agreement that gives you a legal hammer if the other side leaks, but isn't so heavy it derails the conversation you're trying to have.

When to use it

Sign before any confidential information is shared. The NDA must precede the disclosure, not document it after the fact. Sequence: (1) introduce the topic at high level, (2) sign NDA, (3) share specifics. Common triggers: investor pitches with detailed metrics, M&A diligence, joint venture discussions, contractor onboarding for a sensitive engagement, advisor onboarding, beta testing of unreleased product. NDAs become unnecessary once a more comprehensive contract takes over (an employment agreement, a contractor agreement, an M&A LOI) — those will contain their own confidentiality clauses that supersede the NDA.

What it doesn't cover

An NDA is not a non-compete (those restrict where the other party can work and have their own legal complications, with FTC's 2024 non-compete rule and state-by-state restrictions). It is not a non-solicit (preventing the other party from poaching your employees or customers — separate clause). It does not assign IP — if the conversation produces IP, you need a separate agreement. It does not protect information that was already public, that the receiving party already had, or that they independently develop. And practically: NDAs are very rarely actually enforced in court for low-dollar disputes; their real value is the deterrent effect of having a written agreement and a clear definition of what's confidential.

State-specific notes

Rules vary by jurisdiction. Below are notes for the states where mutual nda runs into the most variance. If your state isn't listed, default to your state's tenant-rights handbook or local legal aid.

California (CA)

California's strong public policy against restrictive covenants (Cal. Bus. & Prof. Code § 16600) does NOT extend to ordinary confidentiality NDAs — those are enforceable. But if your NDA tries to restrict the receiving party from working in your industry, hiring your employees, or using their general knowledge, those provisions will be void in California. Keep the NDA narrowly focused on confidentiality.

Cal. Bus. & Prof. Code § 16600 →

New York (NY)

New York courts enforce reasonable NDAs but increasingly scrutinize NDAs that prevent disclosure of unlawful workplace conduct — the New York Adult Survivors Act and related laws bar NDAs that prevent reporting of harassment or discrimination. For business confidentiality (this pack's purpose), NY enforcement is robust.

N.Y. CPLR § 213-c (Adult Survivors Act SOL) →

Texas (TX)

Texas enforces NDAs as long as they protect a legitimate business interest and are reasonably tailored. Trade secret protection is also available under the Texas Uniform Trade Secrets Act (Tex. Civ. Prac. & Rem. Code Ch. 134A) for misappropriation, often as a parallel claim alongside NDA breach.

Tex. Civ. Prac. & Rem. Code Ch. 134A (TUTSA) →

Delaware (DE)

Delaware is a popular choice for governing law in NDAs even when neither party is based there, due to the Court of Chancery's expertise in business disputes. NDAs governed by Delaware law are enforced as written, with a strong presumption of enforceability between sophisticated commercial parties.

Delaware Court of Chancery →

Common questions

How long should the confidentiality term be?

Two to five years for most business contexts. Shorter for fast-moving information (product roadmaps, market strategy that becomes obsolete in a year). Longer for trade secrets that retain value (formulas, algorithms, customer relationships). Indefinite or 'in perpetuity' is enforceable but increasingly disfavored by courts as overbroad — pick a number, and pick one that matches the actual sensitivity life of the information.

What counts as 'confidential information'?

Whatever the NDA says. Most NDAs (including this one) protect information that is either marked confidential at the time of disclosure or that a reasonable person would understand to be confidential given the context. Marking is more reliable than 'should have known' — for sensitive material, label files 'Confidential' and confirm in writing that what you discussed in a meeting was confidential. Avoid catch-all language like 'all information shared' which courts find unreasonably broad.

What are the standard exclusions?

Information that was: (1) already public, (2) already known to the receiving party before disclosure, (3) lawfully received from a third party with no confidentiality obligation, (4) independently developed by the receiving party without using the confidential information, or (5) required to be disclosed by law (with notice to the disclosing party where allowed). The NDA in this pack covers all five — these are industry-standard and non-negotiable in most contexts.

Should I require return or destruction of materials?

Yes, and put it in writing. After the relationship ends or the purpose is complete, you should be able to demand the other party return or destroy your materials. Be aware that 'destroy' is increasingly a request rather than reality — modern systems back up, snapshot, and replicate data, so 'destruction' usually means deletion from active systems and reasonable efforts to remove from backups over normal retention cycles. The pack doesn't dictate; you can add a return-and-destroy clause specific to the relationship.

What if the other party breaches?

Remedies include money damages (often hard to quantify for confidential info — what's the market price of a leaked customer list?) and injunctive relief (a court order requiring the other party to stop using or disclosing). Most NDAs include a clause acknowledging that breach causes 'irreparable harm,' which makes injunctive relief easier to get. Damages claims for NDA breach typically need to show actual lost business or unjust enrichment by the other side, which is fact-intensive.

Should I sign an NDA the other party drafts?

Read it carefully. Common traps: (1) 'mutual' NDA that's actually one-way (only protects the other party's information), (2) overbroad definition of confidential information (everything you say to them, ever), (3) excessive term (10+ years, perpetual), (4) one-sided remedies clause (only one party gets injunctive relief), (5) forum selection clause requiring litigation in their state. Don't sign before reading; counter-propose with reasonable terms.

What about NDAs for employees vs. contractors?

Employees should be covered by their employment agreement's confidentiality clause, not a standalone NDA. Standalone NDAs for employees are generally fine but redundant. For contractors, the NDA is often combined with the contractor agreement itself (one document covering scope, payment, IP, and confidentiality) — Pike's contractor / subcontractor packs include confidentiality clauses. Use a standalone NDA for parties you're talking to but not yet contracting with.

Pike provides plain-language legal information, not legal advice. State and local rules change. If money, custody, or your housing is on the line, talk to a licensed attorney or your local legal aid office.