Are restrictive definitions of proprietary information in NDAs legally binding?

Are restrictive definitions of proprietary information in NDAs legally binding?

Yes, restrictive definitions of proprietary information in Non-Disclosure Agreements (NDAs) are legally binding provided they are reasonable in scope, duration, and necessity. Courts will enforce clear, specific definitions, but they routinely invalidate overbroad clauses that attempt to classify general industry knowledge or public information as confidential.

The Legal Standard for Enforceability

For a definition of proprietary information to hold up in court, it must pass the 'reasonableness' test. Judges evaluate whether the definition is narrowly tailored to protect legitimate business interests without imposing an undue burden on the receiving party or stifling competition.

Key Criteria for Enforceable Definitions

• Specificity: The definition must clearly identify what constitutes confidential information (e.g., specific algorithms, customer lists, or internal financial projections).
• Exclusions: The contract must explicitly exclude information that is already in the public domain, independently developed, or rightfully obtained from third parties.
• Duration: While trade secrets can be protected indefinitely, other proprietary information should have a defined sunset period (typically 2 to 5 years).
• Legitimate Interest: The information must provide the disclosing party with a competitive advantage.

Key takeaway: If your NDA defines 'proprietary information' as 'any and all information disclosed,' it is likely unenforceable in most jurisdictions. Always use a tiered or categorized definition structure.

Action Item: Audit your current NDA templates to ensure they contain a 'Carve-outs' section that explicitly lists what is NOT confidential.

Common Pitfalls in NDA Drafting

Many companies fall into the trap of 'over-drafting' to ensure maximum protection. However, overly broad definitions often backfire, leading courts to strike down the entire confidentiality provision rather than 'blue-penciling' or rewriting it.

The 'Public Domain' Trap

A frequent point of litigation is whether information that is technically 'public' but difficult to find can be protected. Courts generally rule that if information is accessible through public records, reverse engineering, or general industry practice, it cannot be defined as proprietary. Attempting to restrict this information can be viewed as an anti-competitive restraint of trade.

Action Item: Review your definition of 'Confidential Information' to ensure it does not include information that is 'generally known' or 'readily ascertainable' by proper means.

Jurisdictional Variations

Enforceability is highly dependent on state law. For example, California (Business and Professions Code Section 16600) has a strong public policy against restraints on trade, making courts there particularly hostile toward broad definitions that prevent employees from using their general skills and knowledge.

1. California: Extremely strict; definitions must be very narrow.
2. Delaware: More flexible; courts tend to respect the 'freedom of contract' between sophisticated parties.
3. New York: Balanced; focuses on whether the information constitutes a protectable trade secret under the Uniform Trade Secrets Act (UTSA).

Key takeaway: Always include a 'Severability' clause. This ensures that if a judge finds one part of your definition overbroad, the rest of the agreement remains intact.

Action Item: If you operate in multiple states, create a 'choice of law' provision that selects a jurisdiction favorable to your specific industry's protection needs.

Best Practices for Drafting Proprietary Definitions

To maximize the likelihood of enforcement, move away from catch-all phrases. Instead, adopt a modular approach to defining proprietary information.

• Define by Category: Use bulleted lists to define technical data, business strategies, and personnel information separately.
• Marking Requirements: Where possible, require that written information be marked 'Confidential' to trigger protection.
• Oral Disclosures: Include a requirement that oral disclosures must be summarized in writing within 30 days to be considered proprietary.

Action Item: Implement a 'Marking Protocol' for your internal teams to ensure that only truly sensitive information is treated as proprietary, which strengthens your position in court.

TermScore can automatically analyze your existing NDAs to identify overbroad definitions, missing exclusions, and clauses that are likely to be struck down in specific jurisdictions. By using AI to flag these risks before you sign, you ensure your proprietary information remains protected without the risk of unenforceable contract language.