5 Red Flags in NDAs You Should Never Ignore

You're about to share your business idea with a potential investor. Or maybe you're negotiating with a vendor who wants to see your customer list. Either way, they slide over an NDA—a non-disclosure agreement—and ask you to sign.

You skim it. It looks standard. You sign.

Then six months later, you realize you've accidentally bound yourself to obligations that make it impossible to hire the right people, pivot your business, or even remember what you learned without legal consequences. This happens more often than you'd think, and it's almost always because the NDA contained clauses that seemed reasonable on the surface but had teeth hiding underneath.

NDAs aren't inherently bad. They serve a real purpose: protecting legitimate business secrets. But many are written so broadly or with such harsh terms that they become weapons instead of shields. Here are five red flags that should make you pause before signing.

1. Confidential Information Defined So Broadly It Captures Everything

A solid NDA defines what counts as "confidential information" with reasonable specificity. But some NDAs define it so loosely that nearly everything discussed could fall under the umbrella.

Watch out for language like: "any information disclosed in connection with the relationship" or "any non-public information." These definitions are dangerously vague. Under such language, even casual conversation could be deemed confidential, and you'd be legally bound not to use it.

Here's a concrete example: You meet with a software vendor who mentions they use AWS for infrastructure and Stripe for payments. Seems like general industry knowledge, right? But under a broad confidentiality definition, you might technically be prohibited from using those same tools without violating the NDA. That's absurd, but it's exactly what overly broad language creates.

Better NDAs include carve-outs that exclude information that is: already public, independently developed, received from a third party without confidentiality obligations, or becomes public through no fault of yours. If the NDA doesn't include these exceptions, you're signing up for unlimited liability.

2. Perpetual Confidentiality Terms That Never Expire

Confidential information loses value over time. Trade secrets eventually become less secret. Market conditions shift. But some NDAs impose confidentiality obligations that last forever—literally "in perpetuity."

Perpetual terms sound like they're protecting the other party forever, but they're actually a trap for you. Imagine signing an NDA in 2020 about a business strategy. It's now 2025, that strategy is common knowledge in your industry, and yet technically you're still bound by confidentiality. If you accidentally reference it in a new venture, you could face a breach claim.

Reasonable confidentiality periods depend on context. Trade secrets might warrant 3-5 years of protection. Customer lists might deserve 2-3 years. But perpetual terms? That's overreach. Push back and propose a sunset clause—something like "confidentiality obligations expire five years from the date of disclosure, or upon public release of the information, whichever comes first."

If the other party insists on perpetual terms for certain truly sensitive information (like genuine trade secrets), try to carve out that category separately and keep everything else time-limited.

3. Residuals Clauses That Restrict What You Can Remember

This one is insidious because it's not always obvious. A "residuals clause" (sometimes called a "residual knowledge" clause) says something like: "We understand that our employees may retain general impressions or ideas in unaided memory, but you may not use these in your work."

Sound reasonable? It's actually asking you to do the impossible—to forget information you've absorbed. It's also potentially unenforceable in many jurisdictions, but that won't help you if you're sued anyway.

A real scenario: You meet with a competitor's employee who describes their customer segmentation strategy. You retain a general sense of "they focus on mid-market B2B clients." Later, you implement a similar strategy. Under a residuals clause, you could be liable even though you didn't copy anything—you just remembered what you heard.

If you see a residuals clause, push to remove it entirely. If the other party won't budge, at minimum make sure it's narrowly tailored to actual trade secrets, not general business knowledge.

4. Hidden Non-Compete Language Buried in the NDA

Sometimes non-compete restrictions sneak into NDAs disguised as confidentiality protections. You're focused on the confidentiality terms and miss language that actually restricts your ability to work in your industry.

Look for phrases like: "you agree not to compete with us during the term and for X years after," or "you may not solicit our customers or employees," or "you agree not to use the information to develop competing products."

Non-competes are serious legal instruments. They restrict your ability to earn a living. Some jurisdictions (California, for example) heavily disfavor them. Yet they sometimes appear in NDAs almost as an afterthought, and people sign without realizing they've just agreed not to work in their field.

If you see non-compete language in an NDA, recognize it for what it is: a separate, major restriction that deserves its own careful review and negotiation. Don't let it hide under the confidentiality umbrella.

5. Missing Carve-Outs for Independently Developed Information

This is the flip side of red flag #1. Even if the definition of confidential information is reasonable, the NDA should explicitly protect information you develop on your own, without using anything disclosed under the NDA.

Without this carve-out, you're in a dangerous position: If you develop a similar solution independently, the other party could argue you actually used their confidential information. Proving you developed something independently is hard, and you'd bear the burden.

Good NDAs include language like: "Nothing in this Agreement prevents you from using information or techniques you develop independently, without reference to the Confidential Information." This protects both parties and reflects reality—people in the same industry often have similar ideas.

If this carve-out is missing, add it. It's a reasonable request and any legitimate party should accept it.

What You Should Do Before Signing

NDAs are contracts, and contracts matter. Before you sign:

1. Read the whole thing. Yes, really. Skim is not enough. Non-compete language hides in unexpected places.

2. Identify the specific information you're sharing. Be concrete about what's actually confidential. This helps you negotiate reasonable terms.

3. Propose modifications. Most NDAs are starting points, not final offers. Suggest time limits, carve-outs for independent development, and narrow definitions.

4. Push back on perpetual terms and residuals clauses. These are almost never necessary and often unenforceable anyway.

5. Separate non-competes from confidentiality. If the other party wants both, they should be in different documents with clear, separate terms.

6. Use a tool to flag issues. Contract analysis software can catch problematic language you might miss in a quick read.

The Bottom Line

NDAs protect legitimate business interests, and you should respect that. But you shouldn't sign an NDA that restricts your ability to work, remember information, or develop your own ideas. The five red flags above—overly broad definitions, perpetual terms, residuals clauses, hidden non-competes, and missing carve-outs—are where most problems hide.

Take the time to review carefully, negotiate the terms that matter, and don't be afraid to ask questions. The other party will respect you more for it, and you'll sleep better knowing you haven't accidentally trapped yourself.

Have a contract to review? Try KlausClause.

This article is for informational purposes only and does not constitute legal advice.