Are there specific state limits on NDA confidentiality duration for tech employees in Maryland?

Are there specific state limits on NDA confidentiality duration for tech employees in Maryland?

Maryland law does not establish a fixed statutory time limit for non-disclosure agreements (NDAs). Unlike non-compete agreements, which face strict scrutiny, confidentiality clauses are governed by the common law standard of "reasonableness." An NDA is enforceable only if it is narrowly tailored to protect a legitimate business interest, such as trade secrets or proprietary software code, without imposing an undue hardship on the employee.

Key takeaway: Because there is no "bright-line" rule, the enforceability of your NDA depends entirely on the nature of the information being protected. If the information is public or general industry knowledge, a long-term NDA is likely unenforceable in Maryland courts.

The Legal Framework: Reasonableness in Maryland

Maryland courts evaluate the validity of restrictive covenants based on their necessity. For tech employees, this means the duration of the NDA must correlate directly with the "shelf life" of the information being protected. In the fast-paced tech sector, information often becomes obsolete quickly.

Factors Courts Consider

• Nature of the Information: Is it a trade secret (e.g., source code, proprietary algorithms) or general professional skill?
• Business Necessity: Does the employer have a legitimate need to keep this information secret for the specified duration?
• Scope of Restriction: Does the NDA prevent you from using your general knowledge and experience, or is it limited to specific proprietary data?
• Duration: Is the time frame excessive relative to the industry standard for the specific type of technology?

The Trade Secret Exception

Under the Maryland Uniform Trade Secrets Act (MUTSA), information that qualifies as a trade secret can be protected indefinitely. However, the burden of proof lies with the employer to demonstrate that the information is not generally known or readily ascertainable by proper means. If the "secret" becomes public knowledge, the NDA's protection for that specific information effectively terminates, regardless of the contract's written duration.

Action Item: Review your NDA to see if it distinguishes between "Confidential Information" and "Trade Secrets." If the agreement treats all information as a perpetual secret, it may be overly broad and vulnerable to legal challenge.

Red Flags in Tech NDAs

Tech employees should be wary of "over-breadth" in their employment contracts. Maryland courts are increasingly skeptical of agreements that function as de facto non-competes by restricting an employee's ability to work in their field.

• "Perpetual" Clauses: NDAs that claim to protect all information forever are often viewed as unreasonable unless they are strictly limited to genuine trade secrets.
• Broad Definitions: If the definition of "Confidential Information" includes everything you learned during your employment, the clause is likely unenforceable.
• Lack of Carve-outs: A robust NDA should explicitly exclude information that is already public, independently developed, or rightfully obtained from third parties.
• Conflict with Non-Competes: If your NDA effectively prevents you from working for a competitor by defining all industry knowledge as "confidential," it may violate Maryland's public policy regarding employee mobility.

Action Item: If you encounter a clause that defines confidential information as "anything learned during the course of employment," request a narrowing amendment that limits the scope to proprietary company data.

How to Assess Your NDA Risk

If you are concerned about the duration or scope of an NDA, follow these steps to evaluate your position:

1. Categorize the Data: Identify exactly what information the company considers confidential. Is it truly proprietary?
2. Check for Severability: Ensure your contract contains a "severability clause," which allows a court to strike down an unreasonable portion of the NDA without invalidating the entire agreement.
3. Compare to Industry Standards: Research typical NDA durations for your specific role (e.g., software engineer vs. product manager).
4. Consult Legal Counsel: If the NDA feels restrictive, seek a professional review before signing.

Key takeaway: Never assume an NDA is "standard." In the tech industry, companies often use aggressive templates that may not hold up under Maryland's reasonableness standard.

TermScore provides an automated, AI-driven analysis of your employment contracts, identifying overly broad confidentiality clauses and potential risks to your career mobility. By comparing your agreement against thousands of similar contracts, TermScore highlights exactly where your NDA deviates from reasonable standards, allowing you to negotiate with confidence.