Can an employer enforce an NDA to claim ownership of side projects built on your own time?

Can an employer enforce an NDA to claim ownership of side projects built on your own time?

In most jurisdictions, an employer cannot claim ownership of side projects created entirely on your own time, using your own equipment, and unrelated to the employer's business. However, if your employment contract contains an overly broad 'Invention Assignment' clause, you may be legally vulnerable unless protected by specific state statutes.

The Legal Framework of IP Assignment

Employment contracts typically include an Invention Assignment Agreement. This is distinct from an NDA (Non-Disclosure Agreement), though they are often bundled together. While an NDA protects trade secrets, an Invention Assignment clause dictates who owns the intellectual property (IP) you create.

The Three-Prong Test for Ownership

To determine if you own your side project, courts generally look at whether the work meets these three criteria:

• Resources: Did you use company equipment, software, proprietary data, or facilities?
• Time: Was the work performed during your contracted working hours?
• Scope: Is the project directly related to the employer’s current or anticipated business, or does it result from work performed for the employer?

Key takeaway: If you use your company-issued laptop to code your side project, you have likely handed your employer a legal argument for ownership, regardless of whether you worked on it at 2:00 AM.

State-Specific Protections

Several U.S. states have enacted laws that specifically limit the scope of invention assignment agreements. These statutes generally render contract clauses unenforceable if they attempt to claim ownership of inventions developed on an employee's own time.

If you reside in a state without these specific protections, your contract language is the final word. If the contract is broad, the employer may legally claim your work.

Identifying Red Flags in Your Contract

Review your employment agreement for these common, dangerous phrases:

• 'All inventions conceived during the term of employment': This is a massive red flag. It implies that anything you think of while employed belongs to them.
• 'Related to the business of the Company': This is often defined so broadly that it could encompass almost any software or creative project.
• 'Resulting from any work performed': This can be used to claim ownership of side projects that use similar programming languages or methodologies as your day job.

Action Item: Search your contract for an 'Exclusions' or 'Prior Inventions' section. If it exists, list your current side projects there immediately to create a paper trail of ownership.

Steps to Protect Your Side Projects

1. Strict Separation: Never use company hardware, software licenses, or cloud accounts for personal projects.
2. Document Everything: Keep a log of hours worked on your project. If challenged, you need proof the work occurred outside of company time.
3. Review the 'Scope of Business': Understand exactly what your employer defines as their 'business.' If you are a web developer for a bank, avoid building fintech apps on the side.
4. Negotiate an IP Waiver: If you have a significant project, ask your employer to sign a written waiver acknowledging that the specific project is your sole property.

Key takeaway: An employer’s claim to your IP is only as strong as the contract you signed and the state laws that govern it. Never assume your 'off-the-clock' work is safe without verifying your specific contract language.

How TermScore Can Help

Navigating the nuances of IP assignment clauses is complex, but you don't have to do it alone. TermScore uses advanced AI to instantly scan your employment contracts, highlighting overly broad invention assignment clauses and identifying potential risks to your side projects before you sign. Ensure your creative freedom is protected by letting TermScore provide the legal clarity you need.