I’m being asked to sign an NDA today—what are the most common red flags (term length, scope, residuals, injunctions)?

Most people are told “it’s just a standard NDA, please sign today,” and then handed a document that quietly shifts a lot of risk onto them. You don’t have time to become a privacy lawyer before 3 p.m.—but you do need a fast way to spot the most common NDA red flags: term length, scope, residuals, and injunctions.

Below is a practical, decision-focused walkthrough you can skim before you sign. It won’t replace legal advice, but it will help you understand what you’re agreeing to and what to push back on.

---

The Quick Overview

• What It Is: A plain‑English explainer of the most important NDA red flags—term length, scope, residuals, and injunctions—plus other common traps.
• Who It Is For: Founders, operators, sales leads, and in‑house counsel under time pressure who need to review an NDA today.
• Core Problem Solved: You’re being asked to sign quickly and don’t know which clauses are truly risky—or how to fix them.

---

How NDA Risk Usually Shows Up in Real Life

In practice, NDA problems rarely show up as a dramatic lawsuit. They show up as:

• A deal partner claiming you breached because your new product “uses our confidential information.”
• An ex‑vendor trying to block your next fundraising by saying your deck violated the NDA.
• Your team being afraid to build anything that overlaps with what they’ve seen, because the NDA is so broad.

Those outcomes often come from four areas:

1. Term length – how long the confidentiality obligation lasts.
2. Scope / definition of “Confidential Information” – what is actually covered.
3. Residuals clauses – what your people can remember and still use.
4. Injunctions and remedies – how hard it is for them to get a court order against you.

Let’s walk each one, with concrete examples and negotiation angles.

---

1. Term Length: How Long Are You Gagged?

What to Look For

Search for phrases like:

• “Term,” “Duration,” “Period”
• “The obligations of confidentiality shall continue for X years after…”

Typical structures:

• Fixed term: “for three (3) years from the date of disclosure.”
• Perpetual: “in perpetuity” or “for an indefinite period.”
• Hybrid: perpetual for trade secrets; X years for everything else.

Why It Matters

• Too short: they may feel unsafe sharing anything important.
• Too long: you may be locking yourself into broad restrictions that outlive the business purpose by a decade.

In fast‑moving industries, a 10‑year NDA covering ordinary commercial info can be excessive. For true trade secrets (like algorithms or source code), longer obligations are more common.

Red Flags on Term Length

• Perpetual obligations for all information (not just trade secrets).
• No way to know when the clock starts (e.g., no clear “Effective Date” or tie to date of disclosure).
• Long survival clause buried at the end:

  “These obligations shall survive any termination of this Agreement”
  without a clear end date.

Reasonable Alternatives

What you might ask for:

• 3–5 years for standard commercial NDAs (sales talks, partnerships, pilots).
• Perpetual only for properly defined “trade secrets.”
• Language like:

  “Recipient’s duty to protect Discloser’s Confidential Information shall remain in effect for a period of three (3) years from the date of disclosure, except that obligations with respect to trade secrets shall continue for so long as such information remains a trade secret under applicable law.”

---

2. Scope: How Is “Confidential Information” Defined?

What to Look For

Find the defined term:

• “Confidential Information,” “Proprietary Information,” or similar.
• It will usually be in quotes and capitalized throughout.

Typical language:

“Confidential Information means all information disclosed by Discloser to Recipient, whether oral or written, that is designated as confidential or that reasonably should be understood to be confidential…”

Why It Matters

Too broad a definition can:

• Block you from using your own know‑how and independently developed concepts.
• Let them label almost anything as confidential after the fact.
• Make you liable for information your team never actually received or understood was confidential.

Red Flags on Scope

1. “All information… whether or not marked” with no reasonableness limit

   • Risk: they treat every conversation, slide, or casual email as confidential, even if it’s generic industry knowledge.

2. No carve‑outs for standard exclusions, like:

   • Information already known to you.
   • Information independently developed by you without use of their information.
   • Information received from another source without breach of an obligation.
   • Information that becomes public through no fault of yours.

3. Retroactive confidentiality
   Language like:

   “including information disclosed prior to the date of this Agreement”
   can be a red flag if you’ve been talking for months and didn’t treat prior disclosures as confidential.

4. Confidentiality of the existence of the relationship

   • Sometimes appropriate (stealth deals), but can be overreaching if you simply want to say you’re “in discussions.”

Reasonable Alternatives

Aim for:

• A definition limited to information that is:
  • Marked as confidential, or
  • Identified as confidential at the time of disclosure.
• Standard exclusions, written clearly. Example:

  “Confidential Information does not include information that (a) is or becomes generally known to the public without breach of any obligation owed to Discloser; (b) was known to Recipient prior to its disclosure by Discloser; (c) is received from a third party without breach of any obligation owed to Discloser; or (d) was independently developed by Recipient without use of or reference to Discloser’s Confidential Information.”

---

3. Residuals: Can People Use What They Remember?

What Are Residuals?

A residuals clause lets your employees use general knowledge, concepts, and know‑how they remember in their unaided memory—even after seeing someone else’s confidential information.

Typical wording:

“Notwithstanding anything to the contrary, Recipient shall be free to use for any purpose the residuals resulting from access to or work with Discloser’s Confidential Information, provided that Recipient shall not disclose the source of such residuals.”

Residuals usually cover:

• Ideas, concepts, and techniques retained in memory.
• Not literal copies of documents or code.

Why It Matters

• If you’re the disclosing party: residuals can feel like a back door to use your ideas.
• If you’re the receiving party: residuals protect your team from being “tainted” and later accused of misusing confidential information when they’re just using their general experience.

Red Flags on Residuals

• Broad residuals rights with no limits, like:

  “Recipient may use residuals without restriction”
  and no carve‑outs for source code, algorithms, or sensitive designs.

• No requirement that use be “unaided” (i.e., they might mix your docs with their own work).
• Residuals granted even to individuals who had full access to your most sensitive materials, such as engineering leadership reviewing your detailed architecture.

Reasonable Alternatives (Depending on Your Role)

If you are disclosing (sharing your information):

• You might push to remove the residuals clause entirely, or:
• Narrow it:

  “Residuals” shall not include any source code, trade secrets, or proprietary algorithms, and Recipient shall not use Discloser’s Confidential Information to develop competing products.

If you are receiving (reviewing their information):

• Residuals can be helpful to protect your team, but you may want:
  • Clear “unaided memory” language.
  • Explicit exclusion of literal copying.
  • A statement that residuals do not override any non‑compete or IP assignment obligations.

---

4. Injunctions: How Quickly Can They Get a Court Order?

What to Look For

Search for “injunction,” “equitable relief,” or “irreparable harm.”

Typical language:

“Recipient acknowledges that any breach of this Agreement may cause irreparable harm to Discloser for which monetary damages may be an inadequate remedy, and that Discloser shall be entitled to seek injunctive relief… without the necessity of posting bond.”

Why It Matters

These clauses:

• Make it easier for them to ask a court to stop you (e.g., halt a launch, block use of a product).
• Can increase your leverage risk in disputes—even before anything is proven.

They are common in NDAs, but worth reading.

Red Flags on Injunctions

• One‑sided right to injunctive relief: only the discloser can seek it, not both parties.
• “Conclusive proof” of breach language, such as:

  “Recipient agrees that any alleged breach shall be deemed irreparable harm…”
  which tries to shortcut the court’s analysis.

• Waiver of all defenses or waiving any right to argue that damages are adequate.

Reasonable Alternatives

You may not be able to remove these clauses entirely (courts can grant injunctions even without them), but you can:

• Ask for mutuality: both parties can seek injunctive relief.
• Remove or soften “deemed” language, for example:

  “The parties acknowledge that a breach of this Agreement may cause irreparable harm for which monetary damages may be inadequate. Accordingly, either party may seek injunctive or equitable relief, in addition to any other remedies available at law.”

---

Other Common NDA Red Flags You Should Scan For

Beyond term, scope, residuals, and injunctions, a quick check for the following can save you from bigger headaches later.

5. Assignment and Change of Control

• Red flag: NDA says you can’t assign it in connection with a merger, acquisition, or sale of your assets without their consent.
• Why risky: an acquirer might need access to information or want clean IP rights, and this clause can complicate due diligence.
• Reasonable tweak:

  “Either party may assign this Agreement without consent to a successor in interest in connection with a merger, acquisition, or sale of substantially all of its assets.”

6. Non‑Compete or Non‑Solicit Hidden Inside

• Red flag: Language that restricts your ability to compete or hire their employees, buried in an NDA disguised as “confidentiality.”
  • Phrases like “shall not develop, market, or sell any products that compete with…” or “shall not solicit or hire…”
• Why risky: you thought you were just agreeing not to leak information, but you’re actually signing a business restriction.
• Reasonable approach:
  • Carve these out into a separate agreement if truly needed (and have counsel review).
  • Or remove them from the NDA entirely.

7. Return / Destruction Obligations

• Red flag: Extremely strict destruction requirements without room for:
  • Routine backups.
  • Legal record‑keeping.
• Reasonable language:

  “Recipient shall, upon written request, return or destroy Discloser’s Confidential Information, except that Recipient may retain copies (a) in backup or archival systems maintained in the ordinary course of business, or (b) as required to comply with legal or regulatory obligations, in each case subject to the confidentiality obligations herein.”

8. One‑Sided Obligations

Check whether the NDA is:

• Mutual – both parties share information and both are protected.
• One‑way – only one side is disclosing.

Red flag: In practice you both expect to share non‑public information, but the NDA protects only the other party.

Reasonable fix: switch to a mutual NDA or add language:

“Where each party discloses information to the other, the terms of this Agreement shall apply equally to each party in its capacity as Discloser and Recipient.”

---

How to Review an NDA in Under 15 Minutes

If you’re under real time pressure, here’s a simple triage checklist:

1. Confirm mutual vs. one‑way
   • Are you protected if you share?
2. Scan term length
   • Is there a clear duration (e.g., 3–5 years)?
   • Is “in perpetuity” limited to trade secrets?
3. Check scope
   • Is “Confidential Information” defined reasonably?
   • Are the standard exclusions included?
4. Review residuals
   • Is there a residuals clause?
   • Does it create risk for your core IP (if you’re disclosing)?
5. Read the injunction / remedies clause
   • Is it mutual?
   • Does it overreach on “deemed” irreparable harm?
6. Look for hidden business restrictions
   • Any non‑compete, non‑solicit, or exclusivity language?
7. Verify assignment and change of control
   • Are you allowed to assign in an acquisition?
8. Check return/destruction
   • Does it realistically fit your systems and legal obligations?

If any of these feel off, that’s your shortlist to send to legal counsel—or to negotiate directly if you don’t have a lawyer available.

---

Where SpeedLegal Fits: See NDA Red Flags in Minutes

Speed matters when someone wants your signature today. This is exactly the type of review workflow SpeedLegal is designed to support.

Upload Your NDA and Get a Red‑Flag Table

You:

• Upload the NDA (PDF, Word, etc.).
• Choose your playbook:
  • Your own standards – upload your existing NDA template or clause positions.
  • Market Standards – SpeedLegal’s defaults, built from tens of thousands of contracts and over a billion data points, fine‑tuned with an expert committee.

SpeedLegal:

• Analyzes the NDA to identify:
  • Term length and survival clauses.
  • Scope and exclusions for “Confidential Information.”
  • Residuals clauses and their breadth.
  • Injunctive relief, non‑competes, non‑solicits.
  • Assignment, change of control, and return/destruction obligations.
• Generates a Red Flag Analyzer that shows:
  • Where the NDA deviates from your standard.
  • Which clauses are non‑standard compared to market norms.

Get Personalized Suggestions You Can Use in Negotiation

For each flagged issue, SpeedLegal:

• Provides Personalized Suggestions—plain‑English recommendations on how to bring the clause closer to your standards.
• Helps you “solve red flags in a single click” by proposing alternative wording you can paste back into your markup or email.

For example:

• If term length is perpetual for all information, SpeedLegal may suggest limiting the duration for non‑trade‑secret information.
• If the definition of “Confidential Information” has no exclusions, it will point that out and propose standard carve‑outs.

You stay in control: it’s still your decision what to accept, push back on, or escalate.

Ask Clause‑Level Questions in Plain Language

With Ask our AI, you can ask:

• “Does this NDA include a residuals clause?”
• “Can they stop us from hiring their employees?”
• “Is the obligation mutual or one‑sided?”
• “How long do we need to keep their information confidential?”

SpeedLegal answers in simple, understandable language so you can make a more informed decision before signing.

Track NDAs After Signature (So You Don’t Forget Them)

Operational misses are real legal risk. Once signed, NDAs in SpeedLegal can be:

• Auto‑categorized by type (e.g., NDA, vendor, customer) and counterparties.
• Searched by:
  • Jurisdiction, effective date, termination date.
  • Clause titles (e.g., “Confidential Information,” “Residuals,” “Injunctive Relief”).
  • Financial values where relevant.
• Monitored with renewal reminders:
  • 7/30/60/90‑day views for NDAs that auto‑renew or expire.
  • Calendar, email, and mobile notifications, so you can renegotiate or let them lapse intentionally.

Human Check for Extra Assurance (Startup/Growth/Enterprise)

For Startup, Growth, and Enterprise users, SpeedLegal adds:

• An optional human review layer on top of the AI analysis (free during Beta).
• A contract specialist who sanity‑checks the red flags and makes sure the suggestions align with your playbook.

SpeedLegal is not a law firm and does not provide legal advice, but it can dramatically compress the time it takes to get a clear, structured view of NDA risks before involving outside counsel—or while your in‑house lawyer is juggling ten other deals.

---

Limitations & Considerations

• Not a substitute for legal advice: For high‑stakes NDAs (M&A, major commercial partnerships, IP transfers), you should still involve qualified counsel. SpeedLegal is a contract reading facilitator, not a law firm.
• Statistical inferences, not guarantees: The “Market Standards” layer is based on patterns across large contract sets. It shows what’s typical, not what’s necessarily right for your specific risk tolerance or jurisdiction.

---

Summary: What to Watch Before You Sign Today

If you’re being pushed to sign an NDA today, focus on:

• Term length: Avoid perpetual obligations for ordinary business information; limit them to true trade secrets where necessary.
• Scope: Make sure “Confidential Information” is clearly defined and includes standard exclusions.
• Residuals: Understand whether people can use what they remember, and whether that’s acceptable given what you’re sharing.
• Injunctions: Prefer mutual, not one‑sided, equitable relief—without overreaching “deemed” harm language.
• Other traps: Look for hidden non‑competes/non‑solicits, assignment restrictions, and unrealistic destruction obligations.

If you’re repeatedly signing NDAs under time pressure, offloading the clause‑by‑clause scan to an AI “contract paralegal” can save hours, reduce oversight mistakes, and give you a consistent, defensible way to review risk.

---

Next Step

Get Started