Is an NDA Enforceable?

Usually, yes. A non-disclosure agreement is a contract, and a properly formed, reasonable NDA is enforceable in court like any other contract. That's the answer most people are looking for, and it's correct.

But "enforceable" is not a property the document is born with. I've seen plenty of signed NDAs fall apart in litigation, not because NDAs aren't enforceable in general, but because that particular one was drafted or handled in a way that gave the other side a way out. Enforceability is decided years after signing, by a judge, based on things most people never think about when they sign. So the better question is: what makes an NDA hold up, and what makes one fail?

The baseline: an NDA is a contract

To be enforceable, an NDA needs what any contract needs, an agreement between the parties, supported by consideration (something each side gives or promises), for a lawful purpose. In a typical commercial NDA between two companies, this is rarely the problem. Each side promises to protect the other's information, or one side gets access to information in exchange for its promise of secrecy. That's enough.

Where formation gets interesting is employment. An NDA an employee signs as part of getting hired is supported by the job itself. An NDA an employer asks an existing employee to sign mid-employment, with nothing new offered in return, is on shakier ground in some states, a number of courts require some additional consideration (a raise, a promotion, sometimes continued employment) to make a mid-stream agreement stick. If you're rolling out NDAs to people who already work for you, that timing detail matters more than the wording.

So the threshold is usually met. The failures happen above it, and they cluster into four areas.

Failure 1: A definition so broad it's unenforceable

The single most common reason an NDA underperforms in court is a definition of "confidential information" that tries to cover everything. When the definition sweeps in information that's public, trivial, or already known, a court has two unattractive options: enforce an unreasonable restriction, or refuse to enforce it. Many choose the second, or they narrow the definition down to what's actually protectable and let the rest go. Overbreadth doesn't make your NDA stronger. It hands the other side an argument. (More on getting this right in What Counts as "Confidential Information"?.)

Failure 2: An unreasonable term or scope

Courts test NDAs for reasonableness. An obligation that lasts forever on all ordinary business information, or a restriction so sweeping it effectively stops someone from working in their field, invites scrutiny, and a restriction that functions as a de facto non-compete can get analyzed under the much tougher rules courts apply to non-competes, which vary dramatically by state and have been getting more restrictive. The defensible structure is a finite, reasonable period for ordinary information, with indefinite protection reserved for genuine trade secrets, which the law already treats that way. (See How Long Should an NDA Last?.)

Failure 3: It collides with public policy

This is the one that surprises people, and it's where an overreaching NDA can do more than fail. It can create liability. An NDA cannot lawfully be used to:

• Stop someone from reporting a crime or cooperating with law enforcement.
• Gag whistleblowers from reporting suspected violations to government agencies. Federal law protects an individual's ability to disclose a trade secret in confidence to a government official or attorney to report a suspected legal violation, which is exactly why a well-drafted NDA includes a trade-secret immunity notice rather than pretending the right doesn't exist.
• Silence claims of sexual assault or sexual harassment through pre-dispute confidentiality or non-disparagement clauses. Federal law has limited the enforceability of those provisions in that context.
• Bar reports to regulators like the SEC or EEOC.

A court won't enforce a provision that runs into these limits, and an NDA that tries to can expose the party who insisted on it. If the NDA in front of you reads like it's trying to buy someone's silence about wrongdoing, that's not a strong NDA. It's an unenforceable, and potentially dangerous, one.

Failure 4: The disclosing party didn't act like the information was secret

Here's the litigator's-lens point that ties it all together. When an NDA is tested, the fight often isn't about the words on the page at all. It's about conduct. Did the party claiming breach actually treat the information as confidential? Did they mark it, limit who saw it, restrict access? Or did they email it around freely, post pieces of it publicly, and only remember it was "confidential" once a dispute arose?

This matters doubly when trade secrets are involved, because information only qualifies as a trade secret if its owner took reasonable steps to keep it secret. An NDA is evidence of those steps, but it's not a substitute for them. I've watched confidentiality claims collapse not because the NDA was bad, but because the party trying to enforce it had treated the "secret" carelessly for years. The contract was fine. The behavior wasn't.

So how do you make an NDA that actually holds up?

The same four areas, turned around:

• Define confidential information specifically, enough to be enforceable, not a blanket claim over everything.
• Keep the term and scope reasonable, with trade secrets carved out for as long as they stay secret.
• Stay clear of the public-policy lines, include the whistleblower/immunity carve-outs rather than trying to write around them.
• Treat the information as confidential in practice, mark it, limit access, and be consistent. The best clause in the world won't save information you handled like it was public.

Get those right and your NDA isn't just "signed". It's defensible.

Is the NDA in front of you actually enforceable?

The honest problem: you can't tell, by reading it once, whether an NDA has an overbroad definition that a court would narrow, an unreasonable term, or a public-policy problem hiding in it. Those are exactly the weaknesses that look like normal contract language until someone tests them.

That's what YayNDA checks. Drop in the NDA you were sent, alongside your own or one of our free templates, and the tool compares them clause by clause, flagging the overbroad definitions, unreasonable terms, and one-sided provisions that are most likely to fail or to work against you. You see where the agreement is solid and where it's brittle, and you choose stronger language before you're the one trying to enforce it.