Can an employment NDA legally claim ownership of personal projects built without company resources?

Can an employment NDA legally claim ownership of personal projects built without company resources?

No. In most jurisdictions, an employer cannot legally claim ownership of personal projects developed entirely on your own time, using your own equipment, and without utilizing company trade secrets or proprietary information. Overly broad assignment clauses that attempt to claim everything you create are often unenforceable.

Key takeaway: While an NDA or IP assignment agreement may contain aggressive language, state laws often override these contracts to protect your right to innovate independently.

The Legal Framework of IP Ownership

Employment agreements often include "Invention Assignment" clauses. These are distinct from NDAs, though they are frequently bundled together. An IP assignment clause dictates that any work product created during your employment belongs to the company. However, this is not an absolute right.

State-Specific Protections

Several states have enacted statutes to prevent employers from overreaching. California is the gold standard for employee protection in this area.

• California Labor Code Section 2870: Prohibits employers from requiring employees to assign rights to inventions developed entirely on their own time without using company resources.
• Washington, Illinois, and Delaware: These states have similar "employee invention" statutes that provide safe harbors for independent work.
• The "Business Relation" Test: Even in states without specific statutes, courts often look at whether the project relates directly to the employer's current business or anticipated research.

Action Item: Check if your employment contract includes a "Notice of Employee Rights" regarding inventions, which is required by law in states like California.

Red Flags in Your Employment Agreement

When reviewing your contract, look for language that attempts to bypass these legal protections. If you see the following, your contract may be overly broad:

Action Item: If your contract uses the phrase "all inventions conceived during employment," request an amendment or a written carve-out for your specific side projects.

How to Maintain Legal Separation

To ensure your personal projects remain yours, you must create a clear, documented "firewall" between your professional duties and your personal innovation.

1. Use Personal Hardware: Never use a company-issued laptop, tablet, or phone for personal development.
2. Network Isolation: Do not use company VPNs, Slack, or internal servers to host code or store project files.
3. Time Management: Document your development hours to prove work was performed outside of your contracted employment hours.
4. Disclosure: If you are unsure, provide a written disclosure to your employer listing your pre-existing projects and explicitly stating they are independent.

Key takeaway: Documentation is your best defense. Keep a log of when and where you worked on your personal projects to provide clear evidence of separation.

The Role of Trade Secrets

The biggest risk to your personal project is not the contract itself, but the accusation that you used "trade secrets." If your personal project uses a proprietary algorithm, a specific dataset, or a unique process you learned at your company, the company may have a legitimate claim to the IP under trade secret law, regardless of what your contract says.

Action Item: Audit your project code to ensure it does not contain any libraries, snippets, or logic that could be construed as proprietary company information.

Protecting Your Future

Navigating the intersection of employment law and intellectual property is complex, and standard contract templates are often written to favor the employer at your expense. TermScore can automatically analyze your employment contracts to identify overly broad IP assignment clauses and potential risks to your personal projects, giving you the clarity you need to negotiate with confidence.