Can an employment NDA legally restrict me from participating in open-source projects on my own time?

Can an employment NDA legally restrict me from participating in open-source projects on my own time?

An NDA alone rarely restricts open-source work, but 'Invention Assignment' clauses often do. If your contract claims ownership of all work created during your employment, your open-source contributions may legally belong to your employer, regardless of whether you used company equipment or worked outside of business hours.

The Critical Distinction: NDA vs. IP Assignment

Employees often confuse Non-Disclosure Agreements (NDAs) with Intellectual Property (IP) Assignment Agreements. While they are frequently bundled in the same document, they serve different legal functions.

• NDA: Restricts you from sharing proprietary information, trade secrets, or client data. It does not inherently stop you from writing code, provided that code does not contain your employer's confidential information.
• IP Assignment Agreement: This is the clause that actually threatens your open-source work. It typically states that any invention, software, or creative work you develop during your term of employment is the sole property of the company.

Key takeaway: Always check your contract for an 'Inventions' or 'Proprietary Rights' section. If it uses broad language like 'all work created during the term of employment,' your open-source contributions are at high risk of being claimed by your employer.

Action Item: Search your employment contract for the word 'Inventions' or 'Assignment.' If you find a clause that does not explicitly exclude work done on your own time, you are potentially assigning your open-source rights to your employer.

Jurisdictional Protections: The California Exception

Some states provide statutory protections for employees that override overly broad employment contracts. California is the most notable example.

Under California Labor Code Section 2870, an employer cannot require 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 directly to the employer's business or actual/demonstrably anticipated research.

Red Flags in Your Employment Contract

When reviewing your contract for open-source compatibility, look for these specific red flags that indicate your side projects are at risk:

• 'Scope of Employment' ambiguity: If the contract defines your scope of employment as 'any software development,' it effectively captures all your coding activities.
• 'Company Resources' definitions: Some contracts define company resources to include 'company time' or 'company-provided equipment' (like a laptop), even if you only use them for personal tasks.
• Lack of an 'Exclusion List': If your contract does not provide a mechanism to list pre-existing projects, you have no legal shield for the work you did before you were hired.

Action Item: If your contract contains these red flags, request an 'IP Exclusion Addendum' that specifically lists your current open-source repositories and declares them as your sole property.

Best Practices for Protecting Your Contributions

To mitigate risk, follow these professional standards when contributing to open-source projects:

1. Use Personal Hardware: Never use your work laptop for personal coding. Even if you aren't using company code, the forensic trail of the machine can be used to argue that company resources were utilized.
2. Separate Networks: Avoid pushing code to GitHub or GitLab while connected to your company’s VPN.
3. Avoid Competitive Domains: If your employer is a database company, contributing to a competing database project is a high-risk activity that could trigger a breach of contract, even if the IP assignment clause is weak.
4. Document Everything: Keep a log of when you work on your projects to prove they were done outside of your 9-to-5 hours.

Key takeaway: The safest route is to obtain written permission from your manager or legal department. A simple email confirmation stating that your employer has no claim to your specific open-source project can serve as a powerful defense in court.

How TermScore Can Help

Navigating the dense legal jargon of employment contracts is difficult, but you don't have to do it alone. TermScore uses advanced AI to scan your employment agreements, highlighting restrictive IP assignment clauses and identifying potential conflicts with your open-source activities. Upload your contract to TermScore today to get a clear, plain-English breakdown of your rights and risks before you commit your next line of code.