How to determine if my employment NDA's definition of 'confidential information' is legally overbroad?
Determine if your NDA is overbroad by checking for vague definitions and lack of exclusions. Use TermScore to instantly flag restrictive clauses.
An employment NDA is legally overbroad if its definition of 'confidential information' is so vague or expansive that it encompasses general industry knowledge, publicly available data, or information an employee already possessed. Courts frequently strike down clauses that fail to distinguish between proprietary trade secrets and an employee's own professional skills.
The Anatomy of an Overbroad NDA
To determine if your NDA is overbroad, you must analyze the specific language used to define protected information. A legally sound definition must be narrow, precise, and clearly identifiable. If the definition is a 'catch-all' phrase, it is likely unenforceable.
Red Flags in Confidentiality Clauses
- Blanket Coverage: Phrases like 'any and all information disclosed' or 'everything learned during the course of employment.'
- Lack of Exclusions: Failure to explicitly exclude information that is already public, independently developed, or rightfully obtained from third parties.
- Subjective Standards: Definitions that rely on the employer's 'sole discretion' to designate what is confidential without a clear, objective standard.
- Skill Restriction: Clauses that attempt to prevent the use of 'general knowledge, skills, or experience' gained while working for the company.
Key takeaway: If your NDA does not distinguish between the employer's proprietary trade secrets and your own professional expertise, it is likely overbroad and potentially unenforceable in court.
Action Item: Review your contract for a 'Carve-Out' section. If it is missing, the definition is almost certainly too broad.
Comparison: Enforceable vs. Overbroad Definitions
| Feature | Enforceable Definition | Overbroad Definition |
|---|---|---|
| Specificity | Lists specific categories (e.g., source code, customer lists) | Uses vague terms like 'all business information' |
| Public Domain | Explicitly excludes public information | Silent on public or industry-standard data |
| Employee Skills | Protects general knowledge and experience | Attempts to restrict use of professional skills |
| Duration | Limited to a reasonable timeframe | Purports to last 'in perpetuity' without exception |
The Legal Standard: Reasonableness and Public Policy
Courts apply a 'reasonableness' test to NDAs. Because NDAs act as a restraint on trade, they must be narrowly tailored to protect a legitimate business interest. If a definition is so broad that it prevents an employee from working in their chosen field, it violates public policy.
Jurisdictional Nuances
- California: Under Business and Professions Code Section 16600, California has the strictest standards. NDAs that effectively function as non-competes by restricting the use of general knowledge are frequently voided.
- New York: Courts look for 'legitimate interests' such as trade secrets or unique services. Overbroad definitions that cover non-proprietary information are often severed or struck down.
- Federal Trends: The FTC and NLRB have increasingly scrutinized NDAs that chill employee rights to discuss working conditions, even under the guise of confidentiality.
Action Item: Check your state's specific statutes regarding restrictive covenants. Many states have passed laws in the last 24 months specifically limiting the scope of confidentiality agreements.
How to Assess Your Risk
If you are concerned about an overbroad NDA, follow this step-by-step assessment process:
- Identify the 'Confidential Information' clause: Locate the specific definition section.
- Test for 'General Knowledge': Ask yourself, 'Does this definition prevent me from using the skills I learned in this job at a future employer?' If yes, it is overbroad.
- Check for Exclusions: Look for a paragraph titled 'Exclusions' or 'Exceptions.' If it is missing, the contract is likely one-sided.
- Evaluate the 'In Perpetuity' clause: Does the confidentiality obligation expire? If it lasts forever, it is often considered unreasonable for non-trade secret information.
Key takeaway: An NDA that does not expire is a major red flag. While trade secrets can be protected indefinitely, general business information should have a reasonable sunset period, typically 1 to 3 years.
Action Item: If you identify these issues, consult with an employment attorney before signing or attempting to leave your current role.
TermScore simplifies this complex legal analysis by automatically scanning your employment agreements for overbroad definitions, missing exclusions, and non-standard restrictive clauses. By highlighting these risks in seconds, TermScore provides you with the clarity needed to understand your obligations and negotiate from a position of strength.
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 tell if my employment NDA is legally overbroad regarding trade secrets?
Employment & NDA
How to determine if an employment NDA is actually a disguised non-compete agreement
Employment & NDA
Can an employment NDA legally restrict me from discussing my daily job duties in a technical job interview?
Employment & NDA
Can an employment NDA legally restrict me from participating in open-source projects on my own time?
Employment & NDA
Can an employment NDA legally restrict me from listing proprietary software tools on my professional resume?
Employment & NDA
Can an employment NDA legally restrict me from discussing the specific software frameworks I used on my resume?