Can my employer use a confidentiality agreement to block my participation in open-source projects on personal time?

Can my employer use a confidentiality agreement to block my participation in open-source projects on personal time?

While an employer cannot strictly forbid you from coding on your own time, they can legally claim ownership of your work through broad Intellectual Property (IP) assignment clauses. If your contract defines "Inventions" to include anything created during your employment, your open-source contributions may legally belong to your employer.

Understanding IP Assignment Clauses

Most employment contracts contain an "Inventions" or "Proprietary Information" section. These clauses are designed to protect the company's core business assets, but they are often drafted with excessive breadth. If a clause states that you assign to the company all inventions "conceived or reduced to practice during the term of employment," it potentially captures every line of code you write, regardless of whether it relates to your job duties.

The Scope of "Related to Business"

Many jurisdictions, most notably California (under Labor Code Section 2870), provide statutory protections that limit an employer's reach. Under California law, an employer cannot claim ownership of an invention if:

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

Key takeaway: Even if your state has protective laws, your contract may attempt to override them. Always check if your agreement includes a "carve-out" for personal projects.

Action Item: Review your contract for the definition of "Inventions." If it lacks the four criteria listed above, you are at risk of your employer claiming your open-source work.

The Role of Confidentiality Agreements

Confidentiality agreements (NDAs) are distinct from IP assignment clauses, but they are often used in tandem to restrict open-source activity. An employer might argue that contributing to a public repository creates a "risk of disclosure" of trade secrets. If your personal project involves technologies similar to your day job, the company may claim that your contributions inevitably rely on proprietary knowledge.

Action Item:** Audit your NDA to see if it prohibits "indirect" disclosure. If it does, avoid contributing to projects that directly compete with your employer's product stack.

How to Protect Your Personal Projects

If you are a developer who values open-source participation, you must be proactive. Do not wait for a dispute to arise; address these issues before you commit code to a public repository.

1. Request a Written Carve-out: Ask your employer to sign an "IP Exclusion Agreement" that explicitly lists your personal projects as outside the scope of your employment.
2. Maintain Strict Separation: Never use a company laptop, company-licensed software, or company-hosted cloud environments for personal coding.
3. Use Personal Accounts: Ensure your GitHub or GitLab account is registered to a personal email address, not your work email.
4. Document Your Time: Keep a log of when you work on personal projects to prove they occurred outside of business hours.

Key takeaway: A verbal agreement from your manager is insufficient. You need a signed document or an email confirmation from HR to protect your intellectual property rights.

Action Item: If you are starting a new job, negotiate an "IP Carve-out" as a condition of your employment offer. Most tech-forward companies are willing to accommodate this if you are transparent.

When to Seek Legal Counsel

If your employer refuses to sign a carve-out or if you are already working on a high-value open-source project, consult an employment attorney. They can help you determine if your contract's language is "unconscionable" or "overbroad" under your state's specific laws. In some cases, a lawyer can draft a "side letter" that clarifies your rights without requiring a full contract renegotiation.

Action Item: If you are unsure about the legal weight of your contract, use TermScore to analyze your agreement. TermScore automatically flags overbroad IP assignment clauses and identifies potential conflicts with your open-source contributions, giving you the clarity needed to negotiate with confidence.