Can an employer use an NDA to claim intellectual property rights over my personal coding projects?

Can an employer use an NDA to claim intellectual property rights over my personal coding projects?

An NDA (Non-Disclosure Agreement) is designed to protect trade secrets, not to transfer ownership of your personal work. However, employers often bundle NDAs with 'Invention Assignment' clauses. If your contract contains an overly broad assignment clause, your employer may legally claim ownership of your side projects if they are deemed related to the company's business or developed using company resources.

The Distinction Between NDAs and IP Assignment Clauses

It is critical to distinguish between the two legal instruments often found in your employment contract. An NDA restricts you from sharing proprietary information, while an Invention Assignment clause dictates who owns the code you write.

The Role of the NDA

An NDA is a defensive document. It prevents you from leaking company data. It does not inherently grant the company rights to your personal code unless that code incorporates the company's protected trade secrets. If you write a personal app that has nothing to do with your employer's tech stack, an NDA provides no legal basis for them to claim ownership.

The Danger of Invention Assignment Clauses

The real threat to your side projects is the Invention Assignment clause. These clauses often state that any work created during your employment—or even work created on your own time—belongs to the employer. You must look for language that defines 'Inventions' as anything 'related to the company's business, products, or anticipated research.' If this definition is broad, it can effectively swallow your personal projects.

Key takeaway: Always check your contract for an 'Invention Assignment' section. If it lacks a specific carve-out for personal projects, you are at higher risk of an ownership dispute.

Criteria for Employer Ownership

Courts and arbitrators typically evaluate four specific factors to determine if an employer owns your personal code. If you meet these criteria, your employer has a strong legal claim.

• Use of Company Resources: Did you use a company-issued laptop, cloud credits, or proprietary software licenses?
• Temporal Proximity: Was the code written during your standard 9-to-5 working hours?
• Business Relevance: Does the project compete with your employer’s current products or future roadmap?
• Use of Trade Secrets: Did you incorporate any internal company algorithms, databases, or proprietary methodologies?

Jurisdictional Protections: The California Exception

If you reside in states like California, Washington, or Illinois, you have statutory protections that limit an employer's ability to claim your personal work. For example, California Labor Code Section 2870 prevents employers from claiming ownership of inventions developed entirely on your own time without using company resources, provided the invention does not relate to the employer's business.

1. Verify if your state has a 'Labor Code 2870' equivalent.
2. Check if your contract attempts to waive these statutory rights.
3. Document your development environment to prove no company resources were used.

How to Protect Your Personal Projects

To ensure your side projects remain yours, you must create a clear 'firewall' between your professional and personal work.

1. Maintain Strict Separation

Never push personal code to a company-managed GitHub or GitLab account. Use a personal repository and ensure your local development environment is entirely distinct from your work machine.

2. Review Your Employment Agreement

Before starting a significant project, read your contract. If the assignment clause is overly broad, consider requesting a 'Prior Inventions' disclosure. Most companies allow you to list existing projects that are excluded from the assignment clause.

3. Keep Detailed Records

Maintain a log of when you worked on your project. If a dispute arises, having a timestamped history of your development process can be the difference between retaining your IP and losing it to your employer.

Key takeaway: If you are unsure about the scope of your assignment clause, do not assume you are safe. Consult a legal professional or use automated analysis tools to identify problematic language before you commit significant time to a side project.

Automated Contract Analysis with TermScore

Navigating complex legal jargon in employment contracts is difficult, but you don't have to do it alone. TermScore uses advanced AI to instantly scan your employment agreements, highlighting aggressive Invention Assignment clauses and identifying potential risks to your personal intellectual property. By uploading your contract to TermScore, you can gain clarity on your rights and ensure your side projects remain yours, allowing you to innovate with confidence.