Can an employer use an NDA to claim intellectual property rights over code written on my personal equipment?
Can an employer claim code written on your personal device? Learn how IP assignment clauses work and how to protect your side projects with TermScore.
Can an employer claim code written on your personal equipment?
Yes. An employer can claim ownership of code written on your personal equipment if your employment agreement contains a broad Intellectual Property (IP) assignment clause. Ownership is determined by the scope of your contract and state-specific labor laws, not merely by the hardware used to write the code.
Key takeaway: The physical ownership of the laptop is rarely the deciding factor in court. The legal nexus between your work duties and the code you created is what determines ownership.
The Legal Mechanics of IP Assignment
Most employment contracts for software engineers include an 'Invention Assignment' clause. This clause acts as a pre-emptive transfer of rights. When you sign it, you are essentially agreeing that any 'work product' created during your tenure belongs to the company.
The Three Pillars of Employer Ownership
Employers typically assert ownership if the code meets any of these three criteria:
- Scope of Employment: The code relates directly to the company’s current or anticipated business, research, or development.
- Use of Resources: You used company-provided software, proprietary APIs, or confidential data to build the project.
- Time Allocation: The code was developed during your compensated working hours.
Action Item: Review your employment contract for the definition of 'Inventions' or 'Work Product.' If the definition is overly broad—covering 'any and all ideas'—you are at high risk.
Jurisdictional Protections: The California Exception
Not all states treat IP assignment clauses equally. California, for example, provides statutory protection for employees under California Labor Code Section 2870.
| Jurisdiction | Protection Level | Key Requirement |
|---|---|---|
| California | High | Must be developed on own time without company equipment/trade secrets. |
| Washington | Moderate | Must not relate to employer's business or anticipated research. |
| General (Most States) | Low | Contract language usually overrides common law protections. |
In states like California, an employer cannot force you to assign rights to an invention developed entirely on your own time without using the employer’s equipment, supplies, facilities, or trade secret information, unless the invention relates to the employer’s business.
Action Item: Check your state’s labor statutes regarding 'Employee Invention Assignment' to see if you have statutory carve-outs that override your contract.
Red Flags in Your Employment Agreement
When reviewing your contract, look for these specific red flags that signal an aggressive IP grab:
- 'Any and All' Language: Clauses that claim ownership of anything created during the term of employment, regardless of relevance to the business.
- 'Anticipated Business' Clauses: Language that claims ownership of code related to what the company *might* do in the future.
- Lack of Exclusions: The absence of a 'Prior Inventions' schedule where you can list projects you owned before joining the company.
Action Item: If you have pre-existing side projects, ensure they are explicitly listed in an 'Excluded Inventions' exhibit attached to your contract.
How to Protect Your Personal Projects
To ensure your side projects remain yours, you must maintain a strict 'firewall' between your professional and personal work.
- Use Separate Hardware: Never use your work laptop for personal coding. Even if the code is unrelated, the company may claim you used their 'environment' (IDE settings, VPN, or security software).
- Document Everything: Keep a timestamped log of when you work on your personal projects to prove they were done outside of business hours.
- Avoid Company IP: Never use company-licensed libraries, proprietary code snippets, or internal documentation in your personal projects.
- Negotiate Early: If you are a prolific builder, negotiate an 'IP carve-out' before signing your offer letter.
Action Item: Create a 'clean room' environment for your personal projects. Use a personal machine, a personal GitHub account, and personal cloud storage to avoid any commingling of assets.
Conclusion
The assumption that 'my laptop equals my code' is a dangerous legal fallacy. Employers rely on broad contract language to capture the value of your innovation. By understanding the specific clauses in your agreement and maintaining a clear separation of resources, you can safeguard your intellectual property.
TermScore can automatically analyze your employment contract to identify aggressive IP assignment clauses and highlight potential risks to your personal projects. Upload your agreement today to get a clear, plain-English breakdown of your rights and obligations.
Check a suspicious clause
Paste a sentence or clause from your employment & nda to get an immediate statutory risk audit.
TermScore Legal Intelligence Group
Audited for 2026 StandardsResearched and cross-referenced against statutory codes, judicial rulings, and TermScore's proprietary Corpus of 100,000+ analyzed contracts. Our intelligence unit continuously audits contract enforceability and predatory clause variance across all 50 US jurisdictions.
Get the contract red-flag checklist
Join landlords and freelancers getting clause breakdowns and benchmark data. No spam.
Keep reading
Employment & NDA
Can my employer claim ownership of my personal side projects if I didn't use company resources?
Employment & NDA
Can an employer use an NDA to restrict listing specific software frameworks on a resume?
Employment & NDA
Can an employer enforce an NDA to claim ownership of side projects built without company resources?
Employment & NDA
Does an employment NDA prevent me from contributing to open source projects on my personal time?
Employment & NDA
Does an employment NDA prevent me from working on personal side projects during my off-hours?
Employment & NDA
What are the legal risks of signing an employment NDA that lacks a specific expiration date?