Can an employer enforce an NDA to claim ownership of side projects built without company resources?

Can an employer enforce an NDA to claim ownership of side projects built without company resources?

In most jurisdictions, an employer cannot claim ownership of a side project created entirely on your own time, using your own equipment, and unrelated to the employer’s business. While many employment contracts contain broad Intellectual Property (IP) assignment clauses, these are frequently limited by state law, particularly in tech-heavy regions like California, Washington, and Illinois.

Key takeaway: An NDA is a confidentiality agreement, not an IP assignment agreement. If your employer is claiming ownership, they are likely relying on a separate 'Invention Assignment Agreement' rather than an NDA. Always check your contract for an 'Inventions' or 'Proprietary Information' section.

Understanding the Legal Framework of IP Ownership

Employment contracts often include 'Invention Assignment' clauses that attempt to capture everything you create during your tenure. However, these clauses are not absolute. Courts apply a 'nexus test' to determine if the employer has a legitimate claim to your work.

The Three-Pronged Test for Ownership

To retain ownership of your side project, you must generally satisfy these three criteria:

• No Company Resources: You did not use company laptops, servers, software licenses, or proprietary data.
• No Relation to Business: The project does not relate to the employer’s actual or demonstrably anticipated business or research.
• No Work During Hours: The project was developed entirely outside of your compensated working hours.

Action Item: Audit your current project. If you used a company-provided Slack account to discuss the project or a company-licensed IDE (like a corporate IntelliJ subscription), you have created a legal 'hook' for your employer to claim ownership.

Jurisdictional Protections: Why Location Matters

State laws significantly impact the enforceability of broad IP assignment clauses. If you live in a state with strong employee protections, your employer’s contract may be partially void.

In California, for example, Labor Code 2870 explicitly states that any provision in an employment agreement which provides that an employee shall assign their rights in an invention to an employer shall not apply to an invention that the employee developed entirely on their own time without using the employer's equipment.

Action Item: Search your employment contract for a 'Notice' clause. In many states, employers are legally required to provide a written notice explaining your rights under state law regarding invention assignments. If this is missing, the clause may be easier to challenge.

Red Flags in Your Employment Contract

Not all IP clauses are created equal. You should look for these specific red flags that indicate an overreaching contract:

• 'All Inventions' Language: Clauses that claim ownership of 'all inventions conceived or reduced to practice during the term of employment' without qualification.
• Broad Definition of 'Business': Definitions that include 'any business the company may enter into in the future,' which is often used to claim ownership of unrelated side projects.
• Post-Termination 'Tail' Clauses: Provisions that claim ownership of ideas developed within 6–12 months after leaving the company.

Key takeaway: If a contract claims ownership of everything you think of while employed, it is likely unenforceable in states like California. However, it can still be used as a tool for intimidation or to trigger expensive litigation.

Best Practices for Protecting Your Side Projects

To minimize risk, you must create a clear 'firewall' between your professional duties and your personal projects.

1. Hardware Separation: Never perform side-project work on a company-issued laptop. Even if you are 'off the clock,' the forensic footprint on the machine can be used against you.
2. Network Hygiene: Do not push code to personal repositories using a company VPN. Use a separate internet connection.
3. Documentation: Keep a log of your development hours. If a dispute arises, proving you worked on the project on Saturday mornings rather than during your 9-to-5 is your strongest defense.
4. Disclosure: If your project is significant, consider disclosing it to your employer’s HR or legal department to get a written waiver. While this carries the risk of them saying 'no,' it provides absolute clarity.

Action Item: Create a 'Side Project Log' today. Document the start date, the tools used, and a brief description of the project. This serves as contemporaneous evidence of your independent development.

How TermScore Can Help

Navigating the dense legalese of an employment contract is difficult, and missing a single clause can put your intellectual property at risk. TermScore uses advanced AI to scan your employment agreements, identifying overreaching IP assignment clauses and highlighting potential conflicts with your side projects. By providing a clear, plain-English analysis, TermScore helps you understand your rights before you sign or before you start building. Ensure your hard work remains yours by letting TermScore analyze your contract for hidden ownership traps today.