How do I know if the definition of proprietary information in my employment NDA is legally too broad?

How to Identify Overly Broad Proprietary Information Definitions

An NDA definition is legally too broad if it fails to distinguish between legitimate trade secrets and your general professional knowledge, skills, or public information. If the definition encompasses everything you learn or do, it is likely unenforceable and acts as an unreasonable restraint on your future employability.

The Red Flags of Overly Broad Definitions

When reviewing your employment agreement, look for language that attempts to capture information that is not actually confidential. If the definition lacks specific boundaries, it is a major red flag.

• Lack of Specificity: The definition uses vague terms like "any and all information" or "everything learned during employment" without defining categories.
• Inclusion of Public Knowledge: The clause fails to exclude information that is already in the public domain or generally known in your industry.
• Restriction on General Skills: The definition attempts to claim ownership over the "know-how" or "general skills" you developed while on the job.
• No Time Limitation: The definition implies that information remains proprietary indefinitely, even if it becomes obsolete or public knowledge.

Key takeaway: If you cannot clearly identify what is considered "proprietary" versus what is "general industry knowledge," the definition is likely too broad to be enforceable in most jurisdictions.

Action Item: Highlight any clause that does not explicitly exclude "information generally known in the industry" or "skills acquired during the course of employment."

Comparing Reasonable vs. Overly Broad Definitions

Legal Standards for Enforceability

Courts evaluate the reasonableness of an NDA based on the "legitimate business interest" test. To be enforceable, the definition of proprietary information must be narrowly tailored to protect the employer's actual competitive advantage.

The "General Knowledge" Doctrine

In jurisdictions like California (under Business and Professions Code Section 16600), courts are extremely hostile toward NDAs that prevent employees from using their general knowledge. If your NDA definition effectively prevents you from working for a competitor by claiming your "experience" is proprietary, it is likely void.

The "Public Domain" Requirement

A standard, enforceable definition must explicitly exclude information that:

1. Is or becomes part of the public domain through no fault of the employee.
2. Was already in the employee's possession prior to employment.
3. Is rightfully obtained from a third party without a breach of confidentiality.

Action Item: Check your contract for a "Carve-out" section. If it is missing the three points above, the definition is legally suspect.

How to Assess Your Risk

If you suspect your NDA is too broad, follow these steps to evaluate your exposure:

1. Audit the Definitions: Compare the definition against your actual job duties. Does it cover your daily tasks or only specific, sensitive data?
2. Check Jurisdiction: Research your state's stance on restrictive covenants. Some states, like California, have much stricter rules than others.
3. Consult Counsel: If the definition is broad, it may be a sign that the employer is using the NDA as a tool for intimidation rather than legitimate protection.

Key takeaway: A broad definition is often used to discourage employees from leaving. Do not assume a signed contract is automatically enforceable if it violates public policy regarding your right to earn a living.

Action Item: Create a list of the specific projects you worked on and compare them to the definition. If the definition is so broad it covers your general emails or meeting notes, it is likely overreaching.

Automated Analysis for Contract Clarity

Manually parsing complex legal definitions is time-consuming and prone to error. TermScore uses advanced AI to instantly scan your employment agreements, flagging overly broad definitions and comparing them against industry standards to ensure you understand exactly what you are signing before you commit.