How to tell if an NDA's definition of proprietary information is too broad to be enforceable?

How to determine if an NDA definition is overly broad

An NDA's definition of proprietary information is legally overbroad if it fails to distinguish between protectable trade secrets and your general industry knowledge, skill, or experience. If the definition captures information that is already public, commonly known, or independently developed, it is likely unenforceable.

Key takeaway: If an NDA definition covers 'all information disclosed,' it is a red flag. Enforceable definitions must be tethered to specific, non-public business interests.

The anatomy of an overbroad definition

Courts generally view NDAs as restrictive covenants. When a definition is too broad, it acts as a de facto non-compete agreement, which many jurisdictions (such as California under Business and Professions Code Section 16600) view with extreme skepticism.

Common red flags in NDA definitions

• Lack of specificity: Phrases like 'any and all information' or 'everything discussed' are legally insufficient.
• Failure to exclude public domain: The definition must explicitly exclude information that is already public or becomes public through no fault of the recipient.
• No 'Marked as Confidential' requirement: Without this, the recipient is forced to guess what is protected, creating an impossible compliance burden.
• Indefinite duration: While trade secrets can be protected indefinitely, general business information should have a defined sunset period (typically 2–5 years).

Action item: Review your NDA for an 'Exclusions' section. If it is missing, the definition is almost certainly too broad.

Comparison: Enforceable vs. Unenforceable Definitions

Jurisdictional considerations

The enforceability of an NDA is highly dependent on state law. In states like California, the threshold for 'proprietary' is high; you cannot contract away your right to use your own professional expertise. In contrast, Delaware courts are more likely to uphold broad definitions if they are part of a negotiated commercial contract between sophisticated parties.

Steps to evaluate your risk

1. Identify the 'General Knowledge' carve-out: Ensure the contract explicitly states that your general skills and experience are not proprietary.
2. Check for 'Independent Development': Confirm the NDA allows you to use information you develop independently without using the disclosing party's data.
3. Assess the 'Public Domain' clause: Ensure the definition excludes information that is or becomes public through no fault of your own.

Key takeaway: If you are an employee, any NDA that restricts your ability to work in your chosen field by labeling your 'general knowledge' as proprietary is likely void as a matter of public policy.

How to negotiate a narrower definition

When you encounter an overbroad definition, you should propose specific amendments. Request that the definition be limited to 'information that is marked as confidential at the time of disclosure' or 'information that a reasonable person would understand to be confidential.' This shifts the burden of identification back to the disclosing party, where it belongs.

Action item: If you are presented with an NDA, ask the counterparty to provide a list of the specific categories of information they consider proprietary. If they cannot, the definition is likely too broad to be enforceable.

Leveraging technology for contract analysis

Manually auditing NDAs for overbroad definitions is time-consuming and prone to human error. TermScore uses advanced AI to instantly scan your contracts, flagging overly broad definitions, missing exclusions, and clauses that conflict with local labor laws. By automating the review process, TermScore ensures you identify unenforceable language before you sign, providing you with the leverage needed to negotiate fairer terms.