Can an employment NDA legally prohibit me from contributing to open source projects on my own time?

Can an employment NDA legally prohibit me from contributing to open source projects on my own time?

An employment NDA cannot legally prevent you from contributing to open source projects, provided you do not disclose proprietary company information. However, the real threat to your side projects is not the NDA itself, but the 'Invention Assignment' clause often bundled within your employment contract, which may grant your employer ownership of your code.

The Critical Distinction: NDAs vs. PIIAs

Many employees conflate Non-Disclosure Agreements (NDAs) with Proprietary Information and Inventions Assignment Agreements (PIIAs). Understanding the difference is vital for protecting your intellectual property.

Non-Disclosure Agreements (NDAs)

An NDA is designed to protect trade secrets. It prohibits you from sharing confidential data, internal roadmaps, or proprietary algorithms. Contributing to open source is perfectly legal under an NDA as long as you are not leaking your employer's private code or internal documentation.

Invention Assignment Agreements (PIIAs)

This is where most developers face legal jeopardy. A PIIA typically states that any work you create during your employment, or using company resources, belongs to the employer. If your contract is poorly drafted, it could claim ownership of any software you write, regardless of whether it relates to your job.

Key takeaway: An NDA restricts what you say, but an Invention Assignment Agreement restricts what you own. Always check your PIIA for language that claims ownership of 'all inventions' created during your term of employment.

Red Flags in Your Employment Contract

When reviewing your contract, look for these specific clauses that could jeopardize your open source contributions:

• Broad Scope: Language that claims ownership of any work created 'during the term of employment' without limiting it to company business.
• Resource Usage: Clauses that claim ownership of anything created using 'any company equipment, supplies, or facilities.'
• Non-Compete Overlap: Clauses that prohibit you from working on projects that 'compete' with the company, which can be interpreted very broadly by aggressive legal teams.

Jurisdictional Protections

Your location significantly impacts how enforceable these clauses are. Some states have enacted specific protections for employees:

Action Item: Check your state's labor laws. If you live in a state with strong employee protection statutes, your employer's contract may contain clauses that are legally unenforceable, but still intimidating.

How to Safely Contribute to Open Source

To minimize risk, follow this standard protocol for maintaining personal projects while employed:

1. Use Personal Hardware: Never use your work laptop, company-provided cloud accounts, or office Wi-Fi for personal coding.
2. Maintain Strict Separation: Work on your projects outside of your designated work hours.
3. Avoid Company Business: Ensure your project is not related to your employer's current or anticipated business interests.
4. Request a Carve-out: If you have a significant side project, ask your employer to sign a written acknowledgment that the project is excluded from your invention assignment.

The Role of Contract Analysis

Navigating the nuances of employment law is complex, and standard contracts are often written to favor the employer. TermScore uses advanced AI to scan your employment agreements, identifying overly broad assignment clauses and potential conflicts with your open source activities. By highlighting these risks before you sign, TermScore empowers you to negotiate better terms and protect your intellectual property from the start.