How do I determine if my NDA's definition of confidential information is unenforceable?
An NDA's definition of confidential information is unenforceable if it is overly broad, vague, or includes public knowledge. Use TermScore to audit your NDAs.
An NDA's definition of confidential information is unenforceable if it is overly broad, lacks reasonable specificity, or attempts to restrict information that is already in the public domain. Courts will strike down clauses that prevent employees or partners from using general skills, knowledge, or publicly available industry data.
The Legal Standard for Enforceability
For a definition of confidential information to hold up in court, it must be narrowly tailored to protect legitimate business interests. If the definition is a "catch-all" that includes everything disclosed during a business relationship, it is likely to be deemed an unreasonable restraint on trade.
Key Indicators of an Overly Broad Definition
- Lack of Categorization: The contract fails to specify types of information (e.g., source code, customer lists, financial projections) and instead uses vague terms like "all information disclosed."
- Public Domain Inclusion: The clause fails to explicitly exclude information that is already public or becomes public through no fault of the receiving party.
- Duration Issues: The definition implies that information remains confidential indefinitely, even after it loses its commercial value or becomes common knowledge.
Key takeaway: If your NDA does not explicitly carve out "publicly available information" or "information independently developed," it is legally vulnerable in almost every jurisdiction.
Action Item: Review your NDA for an "Exclusions" section. If it is missing, the definition of confidential information is likely too broad to be enforceable.
Comparing Enforceable vs. Unenforceable Definitions
| Feature | Enforceable Definition | Unenforceable Definition |
|---|---|---|
| Specificity | Lists specific data types (e.g., "customer lists") | Uses "any and all information" |
| Public Domain | Explicitly excludes public knowledge | Silent or claims "all information" |
| Scope | Limited to proprietary business data | Includes general industry knowledge |
| Duration | Defined term (e.g., 2-5 years) | "Perpetual" for non-trade secrets |
The "Reasonable Specificity" Test
Courts apply the "reasonable specificity" test to determine if a party had fair notice of what they were prohibited from disclosing. If an employee cannot reasonably distinguish between their own general professional experience and the company's "confidential" data, the definition is unenforceable.
How to Audit Your Definition
- Identify the Core Assets: Does the definition specifically mention the actual trade secrets of your business?
- Check for "General Knowledge" Carve-outs: Does the contract allow the receiving party to use their own "general skills and knowledge" acquired during the term?
- Assess the "Public Knowledge" Clause: Is there a clear statement that information known to the public is not confidential?
Key takeaway: A definition that prevents a professional from using their own "general knowledge and experience" is a classic example of an unenforceable restraint on trade.
Action Item: Highlight every instance where the contract uses the word "all" or "any" to describe information. These are high-risk areas that require narrowing.
Jurisdictional Nuances
Enforceability varies significantly by state. For example, California (Business and Professions Code Section 16600) has a very strong public policy against restraints on trade, making overly broad NDAs particularly difficult to enforce. Conversely, states like Delaware allow for more flexibility in commercial contracts, but even there, "reasonableness" remains the gold standard.
- California: Extremely strict; definitions must be precise to avoid being seen as a de facto non-compete.
- New York: Focuses on whether the information is truly a "trade secret" rather than just "confidential."
- Texas: Requires that the information be "reasonable" in scope to protect the employer's interest.
Action Item: If you operate in multiple states, ensure your NDA includes a "severability" clause. This allows a court to strike the unenforceable parts of your definition while keeping the rest of the contract intact.
Automating Your NDA Review
Manually auditing contracts for these nuances is time-consuming and prone to human error. TermScore uses advanced AI to instantly analyze your NDAs, flagging overly broad definitions, missing exclusions, and clauses that fail the "reasonable specificity" test. By identifying these risks before you sign, TermScore helps you ensure your agreements are both protective and legally enforceable.
Check a suspicious clause
Paste a sentence or clause from your employment & nda to get an immediate statutory risk audit.
TermScore Legal Intelligence Group
Audited for 2026 StandardsResearched and cross-referenced against statutory codes, judicial rulings, and TermScore's proprietary Corpus of 100,000+ analyzed contracts. Our intelligence unit continuously audits contract enforceability and predatory clause variance across all 50 US jurisdictions.
Get the contract red-flag checklist
Join landlords and freelancers getting clause breakdowns and benchmark data. No spam.
Keep reading
Employment & NDA
How to determine if my employment NDA's definition of 'confidential information' is legally overbroad?
Employment & NDA
How to tell if an NDA's definition of confidential information is legally too vague to enforce?
Employment & NDA
Is it a breach of employment NDA to mention specific software frameworks on a public resume?
Employment & NDA
Does an employment NDA cover personal side projects created on weekends without company equipment?
Employment & NDA
Can an employment NDA legally restrict discussing technical project methodologies in job interviews?
Employment & NDA
Can an employer enforce an NDA to claim ownership of side projects built on your own time?