Can an employer enforce an NDA to restrict open-source contributions made on personal time?
Can employers restrict open-source contributions? Learn how IP assignment and NDAs impact your side projects and how to protect your rights.
Can an employer enforce an NDA to restrict open-source contributions made on personal time?
In most jurisdictions, an employer cannot legally claim ownership of open-source contributions made entirely on personal time, using personal equipment, and unrelated to the employer's business. However, overly broad IP assignment clauses in employment contracts can create significant legal risk, potentially allowing employers to assert ownership or restrict your activity.
The Legal Landscape of IP Assignment
Employment contracts often contain "Invention Assignment" clauses. These clauses are designed to ensure the company owns the intellectual property (IP) you create while employed. The enforceability of these clauses regarding side projects depends heavily on state law and the specific language of your contract.
State-Specific Protections
Several states have enacted "Employee Invention Statutes" that explicitly protect your right to work on projects outside of your employment. For example, California Labor Code Section 2870 provides a statutory shield for employees.
- California (Section 2870): Protects inventions developed on your own time, without company equipment, and that do not relate to the employer's business or actual/anticipated research.
- Washington (RCW 49.44.140): Similar protections for employees, provided the invention does not result from work performed for the employer.
- Illinois (Employee Patent Act): Limits the scope of assignment agreements to inventions that relate directly to the employer's business.
Key takeaway: Even if your contract says the employer owns "everything you create," state law may override that language if your project is unrelated to your job duties.
Red Flags in Your Employment Agreement
When reviewing your contract, look for specific language that signals an overreach. If you find these terms, you should seek clarification or a written waiver.
| Clause Type | Risk Level | Description |
|---|---|---|
| Broad Assignment | High | Claims ownership of all inventions "conceived or reduced to practice" during employment. |
| Non-Compete | Medium | May restrict contributions to projects that compete with the employer's product. |
| Confidentiality | Low | Standard protection for trade secrets; usually does not apply to public open-source code. |
Identifying Overly Broad Language
- "Any and all inventions": This phrasing is often too broad and may be unenforceable in states like California.
- "Related to the business": This is the most contested phrase. If your employer is a cloud provider, contributing to a cloud-related open-source project could be flagged as "related."
- "During the term of employment": This implies 24/7 ownership, which is rarely enforceable for personal projects.
Best Practices for Protecting Your Side Projects
To ensure your open-source contributions remain yours, you must maintain a strict "firewall" between your professional life and your personal coding.
- Use Personal Hardware: Never use a company-issued laptop, tablet, or phone for personal projects.
- Avoid Company Software: Do not use company-licensed IDEs, compilers, or cloud accounts (like AWS or Azure) for your personal code.
- Document Everything: Keep a log of your development hours. If you are challenged, proving you worked on the project on weekends or evenings is critical.
- Request a Carve-Out: If you have a significant side project, ask your employer to sign an "IP Exclusion Agreement" or a "Prior Inventions Disclosure" form.
Key takeaway: If you use company resources, you have likely forfeited your claim to the IP. Always maintain a clean separation of assets.
When to Seek Legal Counsel
If your employer explicitly demands you stop contributing to an open-source project, or if they claim ownership of a project you have already published, you are in a high-risk scenario. You should consult with an employment attorney who specializes in technology law to determine if your specific contract language is preempted by state law.
How TermScore Can Help
Navigating the nuances of IP assignment and restrictive covenants is complex. TermScore uses advanced AI to automatically analyze your employment contracts, identifying overly broad IP assignment clauses and potential conflicts with your open-source contributions. By highlighting these risks before you sign, TermScore empowers you to negotiate better terms and protect your personal intellectual property.
Check a suspicious clause
Paste a sentence or clause from your employment & nda to get an immediate statutory risk audit.
TermScore Legal Intelligence Group
Audited for 2026 StandardsResearched and cross-referenced against statutory codes, judicial rulings, and TermScore's proprietary Corpus of 100,000+ analyzed contracts. Our intelligence unit continuously audits contract enforceability and predatory clause variance across all 50 US jurisdictions.
Get the contract red-flag checklist
Join landlords and freelancers getting clause breakdowns and benchmark data. No spam.
Keep reading
Employment & NDA
Can an employer enforce an NDA to claim ownership of side projects built on personal time?
Employment & NDA
Can an employment NDA restrict my right to contribute to open source projects on my own time?
Employment & NDA
Can my employer use a confidentiality agreement to block my participation in open-source projects on personal time?
Employment & NDA
Does an employment NDA prevent me from working on personal open source projects during weekends?
Employment & NDA
Can an employer use an NDA to claim ownership of code written on personal equipment?
Employment & NDA
Does an employment NDA cover personal side projects created on my own time without company equipment?