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

An NDA's definition of proprietary information is legally overly broad if it fails to distinguish between protectable trade secrets and general business knowledge. If the definition lacks specific categories, fails to exclude public domain information, or attempts to cover all communications, it is likely unenforceable.

The Anatomy of an Overly Broad Definition

A standard, enforceable definition of proprietary information must be narrow enough to allow the receiving party to understand their obligations. When a contract uses "catch-all" language without boundaries, it creates a "chilling effect" on the recipient's professional activities.

Red Flags in NDA Language

• Lack of Categorization: The NDA defines information as "any and all data shared," rather than specifying technical data, customer lists, or financial projections.
• Absence of "Marking" Requirements: The agreement fails to require that written information be marked "Confidential" or that oral disclosures be summarized in writing within a set timeframe (e.g., 30 days).
• Infinite Scope: The definition includes information that is generally known in the industry or that the recipient already possessed prior to the agreement.
• No Exclusions: The contract fails to explicitly carve out information independently developed by the recipient or received from a third party without a confidentiality obligation.

Key takeaway: If you cannot identify exactly what information you are prohibited from sharing, the definition is too broad. Always demand that the definition be limited to information that is not generally known to the public.

Comparing Reasonable vs. Overly Broad Definitions

Legal Standards for Enforceability

Courts in jurisdictions like California (under Business and Professions Code Section 16600) and Delaware apply strict scrutiny to confidentiality agreements. If a definition is so broad that it effectively functions as a non-compete agreement, it may be struck down entirely.

The "Reasonableness" Test

1. Specificity: Does the definition allow the recipient to know what is confidential?
2. Legitimate Interest: Does the information actually provide a competitive advantage?
3. Public Policy: Does the definition prevent the employee from using their general skills and knowledge acquired during employment?

How to Negotiate a Narrower Definition

When you encounter an overly broad definition, you must propose specific amendments to protect your interests. Use the following steps to negotiate:

1. Request a "Marking" Clause: Require that the disclosing party mark all confidential documents as such. This shifts the burden of identification to the owner of the information.
2. Insert Standard Exclusions: Add language stating that information is not confidential if it is: (a) already in the public domain, (b) becomes public through no fault of the recipient, (c) is rightfully received from a third party, or (d) is independently developed.
3. Limit the Duration: While trade secrets may be protected indefinitely, general business information should have a sunset clause, typically 2 to 5 years.

Key takeaway: Never sign an NDA that lacks a "public domain" exclusion. This is a non-negotiable standard in commercial law that protects you from being sued for discussing common industry practices.

The Role of AI in Contract Review

Manually auditing NDAs for overbreadth is time-consuming and prone to human error. TermScore automates this process by instantly scanning your contracts against industry-standard benchmarks, highlighting vague definitions, and suggesting precise, legally defensible language to ensure your agreements are both fair and enforceable.