What makes an NDA definition of proprietary information overly broad?

An NDA definition is overly broad if it lacks specificity, fails to exclude public knowledge, or attempts to capture general skills and industry experience, rendering it unenforceable under most state laws.

How can I identify vague language in an NDA?

Look for catch-all phrases like 'all information disclosed' without qualification, lack of marking requirements, and the absence of specific carve-outs for independent development.

Can TermScore help identify overly broad NDA clauses?

Yes, TermScore uses AI to automatically scan your contracts for overly broad definitions and suggests precise, enforceable language based on industry standards.

A TermScore is an AI-generated risk rating from 0 to 100 that evaluates the fairness and risk level of any legal document. A score of 86-100 means the contract is highly favorable, while 0-30 indicates dangerous terms you should walk away from.

What types of documents can TermScore analyze?

TermScore analyzes any legal document including freelance contracts, employment agreements, residential leases, NDAs, brand sponsorship deals, SaaS vendor agreements, and rental applications. Upload PDFs, Word documents, or images.

How much does TermScore cost?

TermScore offers a free plan with 3 scores per month. The Team plan is $15/month for 30 scores, and the Professional plan is $50/month for 500 scores with team collaboration features.

Is my document data secure?

Yes. Documents are processed in memory and analysis results are stored encrypted. TermScore never shares your document data with third parties and you can delete your data at any time from your dashboard.

How to tell if an NDA's definition of proprietary information is legally overly broad?

How to Identify an Overly Broad NDA Definition

An NDA definition is legally overly broad if it fails to clearly delineate what constitutes confidential information, effectively attempting to restrict general knowledge, public domain data, or an employee's own professional skills. If the definition lacks specific categories or fails to exclude non-confidential information, it is likely unenforceable.

The Anatomy of an Overly Broad Definition

Courts generally disfavor "blanket" definitions. If a contract defines proprietary information as "anything and everything disclosed by the Disclosing Party," it is a red flag. To be enforceable, the definition must be tailored to the specific business context of the relationship.

Common Red Flags in NDA Definitions

Lack of Marking Requirements: The absence of a requirement that documents be marked "Confidential" or "Proprietary" makes it impossible for the recipient to know their obligations.
Failure to Exclude Public Knowledge: If the definition does not explicitly exclude information that is already in the public domain, it is legally suspect.
Inclusion of General Skills: Clauses that attempt to restrict "general knowledge, skills, and experience" acquired during the term are often viewed as illegal restraints on trade.
Infinite Scope: Definitions that cover "all information, whether oral, written, or electronic, without limitation" are frequently struck down for lack of reasonable specificity.

Key takeaway: If you cannot reasonably determine what information is protected based on the text of the contract, the definition is too broad and poses a significant litigation risk.

Action Item: Review your NDA for a "carve-out" section. If it is missing, you are likely dealing with an overly broad definition that needs immediate revision.

Comparison: Reasonable vs. Overly Broad Definitions

Feature	Overly Broad Definition	Reasonable Definition
Scope	All information disclosed	Specific technical, financial, and trade secret data
Marking	Not required	Required for written materials
Public Domain	Not excluded	Explicitly excluded
Duration	Perpetual	Defined term (e.g., 2-5 years)

Steps to Audit Your NDA Definition

Identify the Purpose: Define the specific project or relationship. The definition should only cover information relevant to that purpose.
Check for Exclusions: Ensure the contract explicitly excludes information known to the recipient before disclosure, information independently developed, and information received from third parties.
Verify Marking Requirements: Confirm that the contract requires the Disclosing Party to identify confidential information, especially for oral disclosures, within a reasonable timeframe (e.g., 30 days).
Assess the "General Knowledge" Clause: Ensure there is a clear statement that the NDA does not prevent the recipient from using their general skills or industry knowledge.

Key takeaway: A narrow, precise definition is more enforceable than a broad, vague one. Courts prefer "reasonable" restrictions that protect legitimate trade secrets without stifling competition.

Action Item: Use a "redline" process to insert standard carve-outs for public knowledge and independent development if they are currently absent from your agreement.

Jurisdictional Considerations

State laws vary significantly regarding the enforceability of broad NDAs. For example, California (Business and Professions Code Section 16600) has some of the strictest protections against overly broad restrictive covenants. In jurisdictions like Delaware or New York, courts may "blue pencil" (rewrite) an overly broad clause to make it reasonable, but you should never rely on a court to fix your contract for you. Always draft for the most restrictive jurisdiction relevant to your business.

Streamlining Contract Analysis

Manually auditing every NDA for overly broad definitions is time-consuming and prone to human error. TermScore automates this process by instantly scanning your contracts against a database of enforceable, industry-standard language. Our AI identifies vague definitions and suggests precise, legally sound alternatives, ensuring your agreements are both protective and enforceable without the need for exhaustive manual review.