Can an employment NDA legally claim ownership of personal side projects built without company resources?
Can an NDA claim your side projects? Generally, no, if built without company resources. Learn how to protect your IP with TermScore analysis.
Can an employment NDA legally claim ownership of personal side projects built without company resources?
In most jurisdictions, an employment agreement cannot legally claim ownership of personal side projects developed entirely on your own time, using your own equipment, and without utilizing company trade secrets or proprietary information. While employers often include broad 'Invention Assignment' clauses, these are frequently limited by state law, most notably California Labor Code Section 2870, which renders such overreaching claims unenforceable.
Understanding Invention Assignment Clauses
Most employment contracts contain a Proprietary Information and Inventions Agreement (PIIA). These clauses are designed to ensure that anything you create while employed belongs to the company. However, these clauses are not absolute. They are legally constrained by the 'nexus' between your work and the company's business.
The Three-Pronged Test for Ownership
To determine if your side project is safe, courts typically look at whether the invention:
- Was developed entirely on your own time.
- Did not use any 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 or development.
Key takeaway: If your side project fails even one of these prongs—for example, if you used a company-issued laptop to write a single line of code—you have created a significant legal vulnerability that could allow your employer to claim ownership.
Action Item: Audit your current contract for the phrase 'related to the business of the company.' If this is not defined, your employer may argue that any software you write is 'related' to their business, regardless of the industry.
Jurisdictional Differences: California vs. The Rest
The legal landscape varies significantly by state. California provides the strongest protection for employees, while other states may lean toward 'freedom of contract,' allowing employers to enforce broader assignment clauses.
| Jurisdiction | Legal Stance | Key Protection |
|---|---|---|
| California | Highly Protective | Labor Code 2870 (Strict limits on assignment) |
| Washington | Moderate | RCW 49.44.140 (Similar to CA, but with nuances) |
| New York | Employer-Friendly | Common law focus on 'scope of employment' |
| Delaware | Employer-Friendly | Strong deference to contract language |
Action Item: Check the 'Governing Law' section of your employment agreement. If your contract is governed by Delaware law, you must be significantly more cautious than if it is governed by California law.
Red Flags in Your Employment Agreement
When reviewing your contract, look for these specific red flags that indicate an overreaching IP clause:
- 'Any and all' language: Clauses that claim 'any and all inventions conceived during the term of employment' are often legally overbroad and potentially void.
- Lack of 'Exclusion' Schedule: If your contract does not provide a space to list 'Prior Inventions,' you are at risk of the company claiming your pre-existing work.
- Broad Definition of 'Business': If the definition of the company's business includes 'any technology related to software or data,' it effectively captures almost any side project.
Best Practices for Protecting Your IP
To ensure your side project remains yours, follow these strict operational protocols:
- Hardware Separation: Never use a company-issued laptop, tablet, or phone for personal development.
- Network Isolation: Do not push code to personal repositories while connected to the company VPN.
- Time Management: Maintain a log of your development hours to prove the work was done outside of business hours.
- Documentation: Keep a written record of the tools, software, and resources used for your project to prove no company assets were involved.
Key takeaway: If you are building a startup, disclose your side project to your employer if your contract requires it, but do so in a way that emphasizes the project's lack of relation to their business and your total independence from their resources.
Action Item: Create a 'Prior Inventions' document today. Even if you haven't started your project, documenting your intent and the scope of your personal work can serve as a defensive shield in future disputes.
How TermScore Protects Your Rights
Navigating the fine print of an employment agreement is complex, and missing a single clause can cost you the rights to your intellectual property. TermScore uses advanced AI to analyze your employment contracts, automatically flagging overbroad invention assignment clauses and identifying potential conflicts with your personal projects. By providing a clear, plain-English breakdown of your obligations, TermScore empowers you to negotiate better terms and protect your creative work before you sign.
TermScore Research
Our legal AI analyzes thousands of contracts to surface market standards, common pitfalls, and actionable insights for anyone who signs agreements.
Get the contract red-flag checklist
Join landlords and freelancers getting clause breakdowns and benchmark data. No spam.
Keep reading
Employment & NDA
Can an employment NDA legally claim ownership of personal side projects built without company resources?
Employment & NDA
Can an employment NDA legally claim ownership of side projects built without company resources?
Employment & NDA
Can an employment NDA legally claim ownership of personal projects built without company resources?
Employment & NDA
Can an employer claim ownership of personal side projects built without company resources via an NDA?
Employment & NDA
Can my employer claim ownership of personal side projects built without company resources?
Employment & NDA
Do employment NDAs automatically cover personal side projects built without company resources?