The Free NDA Template That Actually Holds Up in Court

An NDA template is a pre-written non-disclosure agreement you can adapt in minutes instead of drafting one from scratch. Swap in the party names, tighten the scope of what counts as confidential, pick a term length, and you're done. That sounds simple, and it mostly is, except most free templates floating around the internet get one of two things wrong: they're either so vague they don't actually protect anything, or so broad they collapse the moment a court looks at them.

This guide gives you the real thing: a clause-by-clause NDA template with sample wording you can lift directly, the difference between a mutual and one-way agreement, and the scope mistakes that turn a signed NDA into a worthless piece of paper. If you're hiring a contractor, pitching an investor, or opening your books to a potential partner, this is the document that decides whether "confidential" actually means something.

According to Cornell Law School's Legal Information Institute, a non-disclosure agreement is a contract in which the parties agree that certain information passing between them stays confidential. That's the whole point of the document, but "confidential" is doing a lot of work in that sentence, and a template earns its keep only if it defines that word precisely.

At minimum, a usable NDA template needs eight things: the parties, a specific definition of confidential information, clear exclusions from that definition, the receiving party's obligations, a term, remedies if it's breached, what happens to the materials afterward, and which state's law governs a dispute. Skip any one of these and you haven't saved time, you've just moved an argument to later, when it costs more to resolve.

A template is a starting point, not a finished document. The clauses below need your specifics dropped in, not left as placeholder brackets when you hit send.

This is the core of the guide, the actual clauses, in order, with sample language you can adapt. Read each one, then customize the bracketed sections for your situation.

1. Parties

Name both parties using full legal names, not "the Company" and "the Individual." State whether this is a mutual agreement (both sides disclose) or one-way (only one side does).

For a mutual NDA, just relabel both as "Party A" and "Party B," since each one discloses and receives.

2. Definition of confidential information

This clause makes or breaks the whole agreement. Define confidential information by category, not by blanket claim. "Everything Disclosing Party shares" is the single most common reason NDAs get thrown out.

Notice the two-part test at the end: labeled confidential, or reasonably understood to be. That combination gives you coverage even when someone forgets to stamp a document "Confidential" before sending it.

3. Exclusions

Every enforceable NDA needs a list of what's NOT covered. Courts expect this. Leaving it out doesn't make your protection broader, it makes the whole clause look like it wasn't drafted carefully.

Four exclusions, not three, not five, because that's what actually needs covering. Don't pad the list to look thorough.

4. Obligations of the receiving party

Spell out what the receiving party can and can't do with the information. Vague language like "keep it safe" invites disagreement about what "safe" means.

That bracketed purpose matters more than people think. An NDA signed for "exploring a partnership" doesn't cover using the information to build a competing product.

5. Term

Two different clocks run here, and templates that conflate them cause real problems: how long the disclosure period lasts versus how long confidentiality itself lasts once information has already been shared.

That carve-out for trade secrets isn't boilerplate padding. It reflects how trade secret law actually works, more on that in the term-length table below.

6. Remedies

State plainly what happens if the receiving party breaches. Courts want to see that both sides understood, going in, that money alone might not fix a confidentiality breach.

"Irreparable harm" is the legal hook that lets a disclosing party ask a judge to stop the leak immediately, rather than waiting months for a damages trial while the secret keeps spreading. The stakes behind that clause are real: Miller Canfield's review of recent trade secret verdicts lists a $604.9 million compensatory award in one case, a $150 million exemplary-damages verdict in another, and an $81 million jury award in a third, numbers that only happen because the underlying confidentiality obligation was written down and later breached.

7. Return or destruction of materials

Once the relationship ends, what happens to the documents, files, and copies? Leaving this out causes outsized disputes for such a small omission.

That certification line matters. Without it, "we deleted it" is just a claim, not a documented fact.

8. Governing law

Pick a state, and be deliberate about it, not just whichever one happens to sit at the bottom of a template you copied.

Building this out for a hire, a pitch deck, or a vendor relationship? Chaindoc's contract templates library includes a ready-to-use NDA plus dozens of other agreements, so you're not assembling clauses from three different blog posts at 11pm before a meeting.

"NDA" isn't one document, it's two, and picking the wrong one is a common early mistake that shows up more often than you'd expect. A one-way (unilateral) NDA protects information flowing in a single direction, from one party to another. A mutual (bilateral) NDA protects information flowing both ways, since both sides plan to disclose something sensitive to the other.

One frequent mix-up: startups pitching investors often send a mutual NDA when a one-way would fit better, since only the startup is disclosing anything sensitive. Worth knowing going in: most VCs won't sign an NDA at all, they see too many pitch decks for the friction to be worth it, and it's a battle you'll likely lose if that's who you're pitching.

Five fields make or break a copy-pasted NDA, the ones that turn a generic download into a document that actually fits your deal. Get these right before you touch anything else, since everything downstream (the exclusions, the remedies, the term) only works if the fields underneath them are specific rather than left as placeholder brackets.

1. 1
   The purpose statement. "For discussing a potential business relationship" is too vague to be useful later. "For evaluating [Receiving Party]'s potential acquisition of [Disclosing Party]'s software product" actually does something if a dispute ever tests what the information was allowed to be used for.
2. 2
   The definition of confidential information. Generic templates list categories like "financial information" and "trade secrets." Replace them with your actual categories: source code, customer contracts, pricing models, whatever you're really protecting.
3. 3
   The term length. Don't default to "5 years" because that's what showed up in the template. Match it to the information type, see the table below.
4. 4
   Governing law and venue. Pick where you'd actually want to litigate if it came to that, usually wherever your business is based.
5. 5
   Signature blocks. Make sure both parties (or all parties, for a multi-party deal) have a clearly labeled line, with printed name, title, and date.

Skip step 2 and the rest barely matters. A precise remedies clause protecting a vague category of information is a strong lock on a door with no walls around it.

Courts throw out NDAs for a small, predictable set of reasons, and almost all of them trace back to scope. An NDA doesn't fail because a judge dislikes confidentiality clauses in general, it fails because the specific language claims more protection than a court thinks is reasonable to enforce against someone who signed in good faith.

Beyond overbreadth: an NDA with no clear exclusions section, one that tries to restrict information the receiving party already legally knew before signing, or one where the "confidential" label gets stamped on information that's actually public (a company's own published pricing, for instance) all invite the same result, a judge deciding the clause doesn't hold up. None of that means don't bother with an NDA. It means write the scope like you expect someone to actually test it.

Not every category of information deserves the same clock. Trade secrets and routine business details don't behave the same way legally, and a template treating them identically is quietly weaker than it looks, since a court asked to enforce a 2-year clause against something that should have been protected indefinitely (or the reverse) tends to side against whichever party drafted the mismatch.

Trade secrets get special federal backing on top of the NDA itself: the Defend Trade Secrets Act of 2016 (18 U.S.C. § 1836) lets an owner sue in federal court for misappropriation, with a 3-year window from discovery to file, on top of whatever the signed agreement says. Most states layer their own Uniform Trade Secrets Act version underneath that. See the USPTO's trade secret policy for the full economic-value and secrecy-effort test behind trade secret status.

Once the template's filled in, don't let signature logistics slow you down. In the US, e-signatures on an NDA are fully valid under the federal ESIGN Act and state-level UETA, adopted in some form by 49 states plus the District of Columbia. No wet ink, no notarization, no scanning a PDF back and forth for two days while a deal cools off.

Chaindoc's document signing handles this end to end: multi-party signing when more than one person needs to sign on either side, a blockchain-verified audit trail that timestamps who signed and when, and a workflow that gets an NDA out the door in minutes instead of a full afternoon. Deciding between drafting from scratch and starting from a template? Our broader walkthrough on how to create a secure NDA covers the full drafting process step by step.

Here's a wrinkle most NDA guides from five years ago never had to address: pasting NDA-covered material into a public AI tool to summarize it, draft a response, or "just check something quickly" can itself be a breach.

If your team touches confidential material regularly, add a line to the obligations clause restricting public/free-tier AI tools for processing Confidential Information without prior written consent. Most templates still don't include this. Yours should.

Managing contractor relationships in software specifically? Our guide to contractor NDAs for software companies goes deeper into source-code-specific confidentiality language, including how this AI-tool question plays out. And if the NDA is one piece of a broader contractor agreement, our independent contractor agreement template guide covers the rest of that document.