Can an employment NDA legally claim ownership of my open-source contributions?

Can an employment NDA legally claim ownership of my open-source contributions?

Yes, if your employment agreement contains an overly broad 'Invention Assignment' clause. While many jurisdictions limit this to work related to your employer's business, poorly drafted contracts can inadvertently capture personal open-source projects created on your own time, effectively granting your employer ownership of your code.

Understanding Invention Assignment Clauses

Most employment contracts include an 'Invention Assignment' clause, which is distinct from a standard Non-Disclosure Agreement (NDA). While an NDA protects trade secrets, an assignment clause dictates who owns the intellectual property (IP) you create. If the language is not carefully scoped, it can encompass any software you write, regardless of whether it was created on a company laptop or during your weekend hours.

The Scope of 'Work-Related' Inventions

Employers often define 'Company Inventions' to include anything that relates to the employer's 'actual or anticipated business.' If you are a backend engineer for a fintech company, and you contribute to an open-source library for financial data processing, your employer may argue that your contribution falls under their ownership because it is 'related' to their business.

Key takeaway: Always check if your contract defines 'Inventions' as anything created during your employment term, rather than just those created within the scope of your specific job duties.

Action Item: Review your contract for the definition of 'Inventions' or 'Developments.' If it lacks a carve-out for personal projects, you are at risk.

Jurisdictional Protections: The California Standard

Some states provide statutory protection for employees. California Labor Code Section 2870 is the gold standard. It prevents employers from claiming ownership of inventions developed entirely on your own time, provided that:

• No company equipment, supplies, facilities, or trade secret information was used.
• The invention does not relate to the employer's business or actual/anticipated research.
• The invention does not result from work performed for the employer.

However, these protections are not universal. In states without similar statutes, the contract language is the final word. If you signed a contract that assigns 'all software created during the term of employment' to the company, you may have legally signed away your open-source rights.

How to Protect Your Open-Source Contributions

You do not have to choose between your career and your open-source contributions. You can proactively mitigate risk by following these steps:

1. Negotiate an IP Exclusion List: Before signing, provide a written list of existing open-source projects you own and wish to retain. Attach this as an 'Exhibit' to your employment contract.
2. Use Dedicated Hardware: Never push code to GitHub or other repositories from a company-issued laptop. Keep your personal development environment strictly separated.
3. Avoid Company Resources: Do not use company Slack, email, or internal documentation to solve problems for your open-source projects.
4. Get Written Consent: If you plan to start a significant new project, ask your manager or legal department for a simple email confirmation that the project is considered 'personal' and outside the scope of your employment.

Key takeaway: A 'Prior Inventions' disclosure is your best defense. If it isn't in writing, it is difficult to prove ownership later.

Action Item: Create a document listing your current active repositories and ask your HR representative to acknowledge it in writing before your start date.

The Risks of Ignoring Contractual Language

If you contribute to open-source projects while under a restrictive contract, you risk more than just losing your code. You could be liable for breach of contract, or worse, your employer could claim ownership of the entire project, potentially leading to legal disputes with the project's maintainers or the open-source foundation hosting the code.

Furthermore, if you are a maintainer of a popular project, an employer's claim could jeopardize the project's license (e.g., MIT or GPL), as the employer may not have authorized the distribution of the code under those terms. This creates a massive liability for both you and the project's community.

Action Item: If you are a major contributor to a project, ensure your employer understands that your participation is a professional development asset, not a conflict of interest.

How TermScore Can Help

Navigating complex legal language 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 overly broad IP assignment clauses and identifying potential conflicts with your personal projects. By providing clear, actionable insights, TermScore helps you negotiate better terms and protect your intellectual property before you sign on the dotted line.