United States — Startups · corporate

Former Employer Claiming Ownership of Startup Code: What to Do in United States Startups

When a former employer sends a demand letter claiming ownership of your startup's codebase, their goal is often to freeze your fundraising or force an unearned equity settlement. In United States startup ecosystems, an employer's reach is strictly limited by federal copyright law and state employee invention statutes. Understanding where their contractual claims end and your independent ownership begins is critical to defending your venture.

What the Law Says About Code Ownership in United States Startups

In the United States startup landscape, ownership disputes over software generally hinge on two legal doctrines: the federal Copyright Act and state-level invention assignment statutes. Under federal copyright law (17 U.S.C. § 201(b)), an employer only owns software created by an employee under the 'work made for hire' doctrine if the code was developed within the actual scope of employment, applying the common-law agency standards established by the U.S. Supreme Court in Community for Creative Non-Violence v. Reid (1989). If you wrote software outside working hours, on personal devices, and without employer supervision, work-for-hire presumptions do not automatically apply.

To circumvent these baseline statutory limits, tech companies rely on Confidential Information and Invention Assignment Agreements (CIIAAs) or Proprietary Information and Inventions Agreements (PIIAs). These contracts routinely contain broad assignment clauses purporting to assign any invention conceived during your tenure. However, key startup jurisdictions severely curb these overreaching contracts. For example, California Labor Code § 2870, Delaware Code tit. 19 § 805, New York Labor Law § 203-f, and Washington RCW 49.44.140 void provisions requiring assignment of inventions developed entirely on your own time without company equipment, supplies, facilities, or trade secret information, provided the code does not directly relate to the employer's actual or demonstrably anticipated business at the time of creation.

Former employers frequently threaten claims under the federal Defend Trade Secrets Act (18 U.S.C. § 1836) or state Uniform Trade Secrets Acts (UTSA). To prevail, an ex-employer cannot simply assert that you used general software engineering skills or industry know-how; they must identify specific, protectable proprietary trade secrets or source code that you misappropriated and incorporated into your new repository.

How Overreaching IP Claims Threaten Your Startup and How Courts View Them

Corporate legal departments know that an intellectual property cloud can paralyze a nascent startup during venture capital due diligence. Threat letters often arrive right as a company announces a pre-seed or seed round, aiming to exploit the startup's lack of capital to extract licensing royalties, equity stakes, or an outright shutdown.

Courts recognize this power imbalance and enforce strict evidentiary burdens on employers. A former employer cannot seize title to independent software simply because a founder developed an idea while employed. Unless the employer can produce forensic proof that company laptops, proprietary repositories, internal APIs, or confidential specifications were utilized, broad 'trailer' clauses—which attempt to capture anything you create for months after resignation—are routinely struck down or narrowed as unlawful restraints on post-employment mobility.

What You Can Do Next to Protect Your Code and Company

Resolving an IP ownership demand requires an immediate, disciplined audit of your repository and your signed personnel agreements. You must avoid emotional email exchanges, preserve all git commit histories, and compartmentalize any disputed modules before engaging corporate litigators.

You do not have to navigate aggressive corporate demands alone. You can use Caunsel to research relevant assignment statutes, organize employment contracts and commit logs inside a secure case file, or connect with an independent startup attorney to formulate a strategic response.

Steps

• Locate and review your signed offer letter, Employee Confidential Information and Inventions Agreement (CIIAA/PIIA), employee handbook, and non-disclosure agreements from your former employer.
• Perform a forensic audit of your startup's git repository to verify commit timestamps, author email addresses, development hardware, and commit history demonstrating creation took place on personal devices and off company hours.
• Issue an internal litigation hold to preserve all personal development logs, purchase receipts for personal laptops/cloud environments, commit histories, and communications regarding your resignation.
• Segregate or refactor any code module that could arguably intersect with your prior employer's proprietary business logic or trade secrets while the ownership boundary is assessed.
• Retain corporate counsel to draft a firm response rejecting unfounded claims and highlighting statutory exemptions under applicable state invention assignment laws.

Common mistakes

• Replying directly to your former employer or HR without legal counsel, creating admissions about your moonlighting timeline or development process.
• Committing startup code from an employer-issued laptop, company Wi-Fi network, or using an enterprise GitHub account, which compromises your statutory safe harbor.
• Conceding equity, licensing rights, or signing a broad post-hoc release under pressure before a lawyer reviews the actual enforceability of the CIIAA.
• Wiping, modifying, or rewriting git histories after receiving a demand letter, which can trigger severe court sanctions for spoliation of evidence.

Questions people ask

Can my former employer claim code I wrote on nights and weekends while still employed?

Only if the code directly related to the employer's actual business or demonstrably anticipated R&D at the time, or if you used company equipment, servers, or trade secrets. In states like California (Cal. Lab. Code § 2870), New York (NY Labor Law § 203-f), and Delaware (19 Del. C. § 805), blanket assignments of independent off-hours work are void by statute.

What happens if a former employer contacts my startup's investors?

If an ex-employer sends bad-faith letters to your investors without reasonable factual or legal basis, they may expose themselves to counterclaims for intentional interference with contractual relations or prospective economic advantage. An attorney can send an immediate warning against tortious interference.

Is using general programming knowledge from my prior job considered trade secret theft?

No. Under both the federal Defend Trade Secrets Act (18 U.S.C. § 1836) and state trade secret laws, general skills, knowledge, and experience gained during employment belong to the engineer, not the former employer. They must prove you took specific proprietary code, confidential architecture, or non-public data.

General information only, last updated 2026-10-19. Caunsel is not a law firm and does not practise law. AI answers and this guide are not legal advice. Verify filings, deadlines, and statutes with a licensed lawyer in United States — Startups.