9 Red Flags in an NDA Someone Sent You

Someone just emailed you an NDA and asked you to sign it. It's three pages. It looks standard. You have other things to do.

Here's the pattern I've seen over twenty years of drafting these and litigating them when they break: the clauses that cause real damage are almost never the scary-looking ones. They're the quiet additions buried in the middle, a sentence here, a defined term there. That you skim right past because the document looks routine. The dangerous NDA isn't the one that reads like a threat. It's the one that reads like boilerplate and isn't.

These are the nine red flags worth slowing down for before you sign.

1. A definition of "Confidential Information" that swallows everything

This is the most-litigated clause in any NDA, and the first place to look. Watch for definitions that sweep in "all information disclosed, in any form" with no real limit, where everything is confidential and therefore nothing is clearly protected, and you've effectively agreed to treat the other side's publicly available marketing as a trade secret. Overbroad definitions cut both ways: they're hard to comply with, and courts sometimes refuse to enforce them at all. A good definition draws a workable line, typically by covering information that's either marked or identified as confidential, or that a reasonable person would understand to be confidential given its nature and the circumstances. That second prong matters: a definition that protects only what's stamped "Confidential" can leave genuinely sensitive oral or informal disclosures unprotected. The goal is a definition specific enough to be enforceable and broad enough to catch what actually needs protecting, not one that simply declares everything secret.

2. "Mutual" on the cover, one-way underneath

An NDA can say mutual at the top and tilt hard in the clauses below: a definition written around their disclosures, carve-outs that apply to one side only, remedies that run their way. The label relaxes you; the provisions don't reciprocate. If it's labeled mutual, confirm the definition, the carve-outs, and the remedies actually apply evenly to both parties.

3. Missing carve-outs

A fair NDA lets you off the hook for information that isn't really a secret: things that are publicly available, that you already knew, that you independently developed without using their information, or that you rightfully received from a third party. It should also let you disclose when you're legally compelled, a subpoena or court order, usually with notice to the other side first. If these standard exceptions are missing or one-sided, you've signed up to keep "secret" things you have every right to use. Their absence is a red flag precisely because they're so standard that leaving them out is usually deliberate.

4. A non-solicit or non-compete hiding inside the NDA

This is the one I'd flag hardest. You think you're signing a confidentiality agreement, and tucked into it is a clause saying you won't hire their employees, or won't work with their customers, or won't compete with them for some period. That's no longer an NDA — it's a restrictive covenant, with real consequences for who you can hire and what business you can pursue. These restrictions get smuggled into NDAs constantly because no one expects to find them there. If you see "non-solicitation," "non-competition," or anything restricting who you can work with or hire, stop and treat it as the serious term it is.

5. A residuals clause you didn't notice

A residuals clause says the other side can keep using whatever information is "retained in the unaided memory" of their employees. It sounds harmless. It isn't. It can effectively gut your protection, anything a person remembers, they're free to use, which for ideas, strategies, and concepts is a very large carve-out. Residuals clauses have their place in some technology deals, but you should know it's there and decide on purpose, not discover it later.

6. An IP or "feedback" grab

Look for language assigning ownership of ideas, feedback, or suggestions to the other side, or granting them a license to anything you create. An NDA is supposed to protect information exchange, not transfer intellectual property. If the agreement quietly says any feedback you give becomes theirs, or that they own improvements you contribute, that's well outside what a confidentiality agreement should do.

7. One-sided remedies and fee-shifting

Check how disputes get resolved and who pays. Red flags: the other side gets the right to an injunction but you don't; the loser pays the winner's legal fees but only when you're the loser; or "liquidated damages" set at a number untethered from any actual harm. Remedies should be reciprocal. When they only point one direction, the agreement is telling you who it was written to protect.

8. Governing law and venue in an inconvenient forum

This one reads like pure boilerplate, which is exactly why it slips through. If the NDA says any dispute will be governed by the law of, and litigated in the courts of, a state on the other side of the country, you've agreed that enforcing your rights (or defending yourself) means hiring lawyers and traveling somewhere far away. For a small company, an inconvenient forum can make the agreement practically unenforceable from your side, no matter what it says.

9. A term and survival period that don't make sense

Two failures live here. An indefinite or perpetual obligation on all ordinary information may be challenged as unreasonable. The opposite failure is subtler and more common: a fixed term that terminates every confidentiality obligation on a date certain, which can quietly cut off protection for genuine trade secrets that the law would otherwise protect for as long as they stay secret. A well-built NDA keeps ordinary information protected for a finite, reasonable period and carves out trade secrets to last as long as they remain secret. (More on this in How Long Should an NDA Last?)

The common thread

Notice what these nine have in common: not one of them looks alarming on a quick read. The overbroad definition reads like thoroughness. The missing carve-out reads like nothing at all. The non-solicit reads like one more paragraph. That's the whole problem with reviewing an NDA by skimming, the terms that matter are engineered to look unremarkable.

You don't have to catch all nine by eye. You have to compare the NDA you were sent against one that handles each of these the right way.

Run the NDA you were sent through the list, automatically.

That's exactly what YayNDA does. Drop in the agreement someone sent you, alongside your own NDA or our free balanced template, and the tool compares them clause by clause, definition, carve-outs, remedies, term, and the quiet additions like residuals and embedded non-solicits. It shows you where their version diverges from a fair one, flags the language working against you, and lets you choose the stronger clause or improve on it. The red flags stop depending on whether you happened to notice them.