Can an employer use an NDA to claim ownership of my personal side projects?

Can an employer use an NDA to claim ownership of my personal side projects?

An NDA (Non-Disclosure Agreement) is primarily designed to protect trade secrets, but it is rarely the document that grants ownership of your work. Instead, employers use Invention Assignment Agreements. If your contract includes broad language assigning all 'work product' or 'inventions' created during your employment to the company, your employer may legally claim ownership of your side projects, especially if they relate to the company's business or were developed using company resources.

Understanding the Legal Framework of IP Ownership

In the United States, the default rule under the 'Work Made for Hire' doctrine is that an employer owns what an employee creates within the scope of their employment. However, employers often expand this reach through restrictive covenants in employment contracts. These clauses are designed to capture everything you build, regardless of whether it was done on a weekend or on your own laptop.

The Difference Between NDAs and IP Assignment Clauses

• NDA: Restricts you from sharing company secrets. It does not inherently transfer ownership of your personal inventions.
• Invention Assignment Agreement: A specific contract clause that transfers the legal title of your intellectual property (code, designs, patents) to the employer.
• Proprietary Information Agreement: Often a hybrid document that combines both confidentiality and ownership transfer.

Key takeaway: Always check your contract for an 'Invention Assignment' or 'Intellectual Property' section. An NDA is a red flag that other restrictive clauses are likely present in the same document.

Action Item: Search your employment agreement for the terms 'Inventions,' 'Work Product,' or 'Intellectual Property' to see if the scope is limited to company business or if it is an 'all-encompassing' assignment.

State-Specific Protections for Employees

Several states have enacted laws that override overly broad employment contracts. These statutes provide a 'safe harbor' for employees, provided specific criteria are met. If you live in one of these jurisdictions, your employer cannot claim your side project if it meets the following three-part test:

• The invention was developed entirely on your own time.
• No company equipment, supplies, facilities, or trade secret information was used.
• The invention does not relate directly to the employer's business or actual/demonstrably anticipated research and development.

Action Item: If you reside in a state with these protections, ensure your side project documentation clearly proves you did not use company resources or company time.

Red Flags in Your Employment Contract

When reviewing your contract, look for these specific red flags that indicate your employer is attempting to claim ownership of your personal work:

• 'Any and all' language: Clauses that claim ownership of 'any and all ideas, concepts, or inventions' regardless of when or where they were created.
• 'Related to' ambiguity: Broad definitions of 'related to the company's business' that could encompass almost any software or creative project.
• Lack of carve-outs: The absence of a 'Prior Inventions' list where you can disclose projects you started before joining the company.
• Post-termination reach: Clauses that claim ownership of ideas conceived shortly after you leave the company.

1. Identify the 'Inventions' section of your contract.
2. Draft a 'Prior Inventions' disclosure document if your contract allows for it.
3. Consult with an attorney if the language is overly broad or ambiguous.
4. Maintain a strict separation between your personal hardware and company-issued devices.

Key takeaway: If your contract does not have a 'Prior Inventions' disclosure section, you should proactively create one and send it to your HR department to establish a baseline of what you owned before your employment began.

Action Item: Never use your work laptop for personal coding or design projects. Even if the project is unrelated to your job, the forensic footprint on a company-owned machine can be used as evidence of 'use of company resources.'

How to Mitigate Risk

To protect your side projects, you must maintain a clear boundary. This is not just about legal language; it is about evidence. If a dispute arises, you need to prove that your project was developed independently.

• Hardware Separation: Use a personal computer for all side projects.
• Time Tracking: Keep a log of when you work on your personal projects to prove it occurred outside of business hours.
• Documentation: Keep a repository of your project's development history (e.g., Git commits) that predates or is clearly separated from your work tasks.

TermScore can automatically analyze your employment contracts to identify these high-risk IP assignment clauses, highlighting exactly where your ownership rights may be compromised so you can negotiate with confidence.