Can an employment NDA legally restrict open-source contributions made on personal time?

Can an employment NDA legally restrict open-source contributions made on personal time?

In most jurisdictions, an employment NDA or Invention Assignment Agreement cannot legally claim ownership of open-source contributions created entirely on your own time, using your own equipment, and unrelated to your employer's business. However, poorly drafted contracts often contain overbroad language that attempts to restrict these activities, necessitating careful review.

The Legal Landscape of IP Ownership

The conflict between employment contracts and open-source contributions typically centers on "Invention Assignment" clauses rather than NDAs alone. While an NDA protects trade secrets, an Invention Assignment clause dictates who owns the code you write. In states like California, Washington, and Illinois, statutory protections limit how much an employer can claim.

Statutory Protections (The California Model)

California Labor Code Section 2870 is the gold standard for employee protection. It renders any provision in an employment agreement requiring an employee to assign rights in an invention to an employer unenforceable if the invention meets three criteria:

• Developed entirely on the employee's own time.
• No use of the employer's equipment, supplies, facilities, or trade secret information.
• Does not relate directly to the employer's business or actual/demonstrably anticipated research and development.

Key takeaway: If your contract claims ownership of everything you create during your employment, it is likely overbroad and potentially unenforceable in states with strong labor protections.

Action Item: Check if your state has a "Labor Code 2870 equivalent." If you work in a state without such specific protections, your contract language becomes the primary governing document, making it even more critical to negotiate specific carve-outs.

Red Flags in Your Employment Agreement

When reviewing your contract, look for specific language that signals an attempt to overreach into your personal projects. These clauses are often hidden in the "Proprietary Information" or "Inventions" sections.

Common Contractual Traps

• The "Any Time" Trap: Clauses that claim ownership of anything created "during the term of employment" regardless of whether it was done on company time.
• The "Related to Business" Trap: Definitions of "Company Business" that are so broad they encompass any software development, effectively banning all open-source contributions.
• The "Equipment" Trap: Language that claims ownership if you use any company-provided software, even if it is just a laptop for email.

Action Item: Audit your contract for the phrase "during the term of employment." If it lacks a qualifier like "using company resources," request an amendment to clarify that personal projects are excluded.

How to Protect Your Open-Source Contributions

If you are an active contributor to open-source projects, you must be proactive. Do not wait for a legal dispute to determine your rights.

1. Disclose Prior Inventions: Most contracts include a "Schedule A" or "Prior Inventions" list. Explicitly list your ongoing open-source projects here before signing.
2. Use Personal Infrastructure: Never push code to a personal repository from a company-issued laptop. Use a separate machine for all personal development.
3. Request an IP Carve-Out: If your employer is hesitant, ask for a side letter or an addendum that explicitly permits your participation in specific open-source projects.
4. Avoid Company Trade Secrets: Never use proprietary libraries, internal APIs, or company-specific data in your personal projects.

Key takeaway: Documentation is your best defense. Keep a log of when you work on personal projects to prove they occurred outside of business hours.

The Role of TermScore in Contract Analysis

Navigating the nuances of IP assignment and NDA restrictions is complex, but you don't have to do it alone. TermScore uses advanced AI to scan your employment agreements, identifying overbroad invention assignment clauses and restrictive covenants that could jeopardize your personal projects. By highlighting these risks before you sign, TermScore empowers you to negotiate better terms and protect your intellectual property rights effectively.