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

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

In most jurisdictions, an employment NDA or Proprietary Information and Inventions Agreement (PIIA) cannot legally claim ownership of open-source contributions developed 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 creates significant legal risk.

The Legal Framework of IP Ownership

The enforceability of restrictions on your personal time depends heavily on state-specific labor codes. While federal law provides a baseline, states like California, Washington, and Illinois have specific statutes that protect employee inventions.

Key Statutory Protections

• California Labor Code Section 2870: This is the gold standard. It explicitly states that an employer cannot require an employee to assign rights to an invention developed entirely on their own time without using the employer’s equipment, supplies, facilities, or trade secret information.
• Washington RCW 49.44.140: Similar to California, this statute prevents employers from claiming inventions that do not relate to the employer’s business or anticipated research.
• Illinois Employee Patent Act: Provides similar protections, ensuring that personal projects remain the property of the employee unless they directly relate to the employer's current or demonstrably anticipated business.

Key takeaway: If your contract claims ownership of 'all inventions conceived during the term of employment,' it is likely overbroad and potentially unenforceable in states with strong protective labor codes.

Action Item: Check if your state has an 'Employee Invention Act.' If it does, your contract must explicitly state that the assignment of IP does not apply to inventions covered by that statute.

Red Flags in Your Employment Agreement

When reviewing your contract, look for specific language that attempts to bypass statutory protections. These clauses are often used to intimidate developers into silence.

Common Contractual Traps

• The 'Related to Business' Trap: Employers often define 'business' so broadly that any coding project could be argued as 'related.'
• The 'Company Resource' Trap: Using a company-issued laptop, VPN, or even a company-provided Slack account to discuss your open-source project can give the employer a legal hook to claim ownership.
• The 'Duty of Loyalty' Argument: Even without an IP clause, some employers argue that contributing to open-source projects creates a conflict of interest if the project competes with their product.

Action Item: Audit your contract for the phrase 'related to the employer's business.' If it is not defined, request a written clarification or an addendum that excludes your specific open-source projects.

How to Protect Your Open-Source Contributions

If you are concerned about your personal projects, you must be proactive. Do not wait for a legal dispute to arise.

1. Segregate Hardware: Never use your work laptop for personal coding. Use a dedicated machine for your open-source contributions.
2. Request an IP Waiver: Ask your employer to sign a 'Prior Inventions' disclosure form, listing your existing open-source projects as excluded from the agreement.
3. Use Personal Accounts: Ensure your GitHub, GitLab, or other repositories are tied to personal email addresses, not your work email.
4. Review the 'Scope of Employment': Ensure your job description is clearly defined. If you are a frontend developer, it is harder for an employer to claim ownership of a backend database tool you built on the weekend.

Key takeaway: A written 'Prior Inventions' disclosure is your strongest defense. It creates a clear, documented boundary between your professional duties and your personal intellectual property.

Action Item: Create a document listing all your current open-source projects and provide it to your HR or legal department for signature during your onboarding or as an amendment to your contract.

The Role of AI in Contract Analysis

Navigating the nuances of IP assignment clauses is complex, and standard legal advice can be prohibitively expensive. TermScore provides an AI-powered solution that automatically scans your employment agreements to identify overbroad IP assignment clauses, restrictive covenants, and potential conflicts with state labor laws. By highlighting these risks in plain language, TermScore empowers you to negotiate better terms and protect your personal intellectual property before you sign.