Startup IP Protection Agreements: 5 Crucial Steps to Avoid Loss

No applicable skill exists in this environment for a content-writing task. Proceeding directly with the regenerated blog post.

Startup IP Protection Agreements: 5 Crucial Steps to Avoid Loss

When an Indian startup hires a freelancer or agency, copyright does not automatically transfer to the company — it vests in the creator under Section 17 of the Copyright Act, 1957. A paid invoice is not an assignment. Without a written, signed, present-tense assignment agreement covering copyright, trademarks, designs, and patents, every external engagement is an open hole in your IP chain. These five steps show you exactly how to seal it — before your next investor diligence or acquisition.

Why India's Default Rules Leave Startups Exposed

Section 17 of the Copyright Act, 1957 draws a sharp line between two types of work relationships:

• Contract of service (employment): Copyright vests in the employer. Applies to salaried employees on a regular payroll.
• Contract for service (independent contracting): Copyright vests in the freelancer or contractor by default.

Most Indian startups pay freelancers on invoice against a "contract for service." Unless the contract contains an express written assignment, the developer who built your MVP, the designer who created your brand identity, or the content writer who drafted your product copy legally owns the copyright to that work — not you.

This is not an academic risk. VC firms conducting Series A and Series B diligence in FY 2026-27 now routinely demand a full IP chain-of-title review before term sheets are issued. If the chain is broken — even for a single freelancer engagement — the deal either slows, reprices, or dies.

Section 19 of the Copyright Act requires that any assignment of copyright must be in writing and signed by the assignor (the freelancer). Oral agreements, email threads, WhatsApp confirmations, and paid invoices do not satisfy this requirement. That applies whether you paid Rs. 5,000 for a logo or Rs. 50,00,000 for a full-stack product build.

Step 1: Use a Present-Tense Assignment Clause — Not a Promise to Assign

The single most common drafting mistake in freelancer IP agreements is wording the assignment as a future promise: "The contractor agrees to assign all IP to the company upon completion of the project."

Courts have held that a covenant to assign creates a contractual obligation — it does not itself transfer title. If the freelancer later disputes the obligation, moves abroad, or goes uncontactable, you hold a breach-of-contract claim, not ownership of the intellectual property. Those are not the same thing during a fundraise.

What to write instead:

> "The Contractor hereby irrevocably assigns and transfers to the Company, with full title guarantee, all copyright, design rights, database rights, and all other intellectual property rights (whether registered or unregistered) in and to the Work and all modifications thereof, throughout the world, in perpetuity, to the fullest extent permitted by law."

The word "hereby" makes the transfer operate at the moment of signing, not at some future point. The phrase "throughout the world, in perpetuity" directly addresses the geographic and temporal limitations that Section 19(5) and Section 19(6) of the Copyright Act allow parties to cap by default.

Why "full title guarantee" matters

"Full title guarantee" is a warranty that the assignor has the unencumbered right to assign and that no third-party claims exist over the work. Pair it with a financial indemnity clause so that if a third party later raises an infringement claim, the freelancer — not your startup — bears the cost of defence and settlement.

Stamp duty — the detail most teams miss

In several Indian states, an agreement that includes an assignment of intellectual property may attract stamp duty under the relevant State Stamp Act. In Maharashtra, for instance, such agreements are treated as general agreements under Schedule I and may carry duty of Rs. 500 to Rs. 100 per Rs. 1,000 of consideration, depending on structure and quantum. An unstamped instrument is inadmissible as evidence in Indian courts. For any engagement worth Rs. 2,00,000 or more, have the agreement stamped in the state where it is executed. This is a small cost that protects the document's enforceability.

Step 2: Pre-Existing IP Disclosure and the SBOM Requirement

Every freelancer walks through the door carrying a pre-existing toolkit: reusable code snippets, design frameworks, licensed stock components, proprietary methodologies, and third-party libraries. Your assignment clause covers work created under the engagement. It does not give you rights to work created before it.

You need two distinct provisions.

2a. Schedule of Pre-Existing IP

Require the freelancer to attach a disclosure schedule at the start of every engagement, listing every piece of pre-existing IP they intend to incorporate. For each item, the schedule must specify:

1. Whether it is being licensed to your company (on what terms, for how long, at what fee) or assigned outright
2. Whether any third-party licences restrict sublicensing or commercial use
3. Whether any open-source licence obligations attach

The GPL contamination risk deserves special attention. If a freelance developer incorporates code licensed under GPL v2 or GPL v3 into your proprietary codebase without disclosure, the GPL's copyleft requirement may force you to release your entire source code publicly. That is a structural defect — not a paperwork issue — and it is a deal-breaker for virtually every institutional investor. The only clean fix is a full rewrite of the affected modules, which typically takes weeks and costs multiples of what correct documentation would have cost at the start.

2b. SBOM — Software Bill of Materials

For software engagements, require the contractor to deliver a Software Bill of Materials (SBOM) as part of the final handover. An SBOM is a structured inventory of every open-source and third-party component in the codebase, along with:

• Component name and version number
• SPDX licence identifier (e.g., MIT, Apache-2.0, GPL-3.0-only)
• Repository or source URL
• Whether the component is incorporated directly or as a transitive dependency

SBOM is now a baseline expectation in software supply-chain diligence globally, and Indian startups with foreign investors or US/EU customers are increasingly required to produce one. Specify the format — SPDX 2.3 or CycloneDX 1.5 JSON — in the contract so there is no ambiguity at handover. Tools like syft, trivy, or FOSSA can generate a compliant SBOM automatically from a repository; including this as a contractual deliverable costs the contractor almost nothing and protects you substantially.

Warranty and indemnity

Add a warranty that the deliverables do not infringe any third party's intellectual property rights, that all open-source licences have been complied with, and that no GPL or similar copyleft-licensed code has been incorporated without explicit written disclosure and consent. Back the warranty with an indemnity covering defence costs, damages, and settlements.

Step 3: Confidentiality and Moral Rights — Two Provisions Teams Underweight

Confidentiality that actually works

A bare NDA is insufficient. Your IP agreement's confidentiality clause must:

• Cover all information shared during the engagement: source code, architecture documentation, business plans, customer data, financial projections, unreleased product roadmaps
• Survive termination — typically for 3–5 years post-engagement for commercial information, indefinitely for trade secrets
• Prohibit the freelancer from disclosing the existence of the engagement on LinkedIn, Behance, Dribbble, or any other platform without your prior written consent
• Restrict all use of confidential information solely to performing the engagement — no training personal AI models, no reuse in other clients' projects

The portfolio restriction matters more than founders realise. A designer who posts "case study: I built the brand for [Startup X]" on Behance before your public launch has given your competitors a roadmap. Build the restriction into the contract and specify the remedy (typically immediate takedown, with the right to seek injunctive relief without having to prove monetary damages).

Moral rights under Section 57 — you cannot delete them, but you can neutralise them

Section 57 of the Copyright Act, 1957 grants every author two non-assignable moral rights:

1. Right of paternity — the right to claim authorship of the work
2. Right of integrity — the right to object to distortion, mutilation, or modification that would be prejudicial to the author's reputation

These rights survive even after the copyright is fully assigned. You cannot contractually extinguish them. What you can do is include a non-assertion clause — the freelancer agrees not to exercise these rights against your company, its licensees, or successors:

> "The Contractor irrevocably waives, to the fullest extent permitted by applicable law, and agrees not to assert any moral rights under Section 57 of the Copyright Act, 1957 or any equivalent provisions in any jurisdiction, in relation to the Work or any adaptation thereof, and consents to the Company and its licensees modifying, adapting, combining, or publishing the Work without attribution to the Contractor."

This clause is enforceable in Indian courts and gives your company the practical freedom to rebrand, modify, or license the work without the original creator's objection years later.

Step 4: Trademarks, Designs, and Patents — Separate Clauses Are Non-Negotiable

Copyright assignment transfers exactly one thing: the copyright. Here is the gap map every startup founder needs to internalise:

Trademarks

A freelancer who designs your logo owns the artistic copyright in that logo. But nothing in a copyright assignment prevents them from filing a trademark application using that design — or prevents a third party from doing the same. Your agreement must explicitly assign all rights to apply for, obtain, and maintain trademark registrations worldwide and must prohibit the freelancer from filing any application incorporating the work.

Filing note for FY 2026-27: Trademark applications in India are filed online via the IP India portal (ipindia.gov.in). The official e-filing fee for startups and small enterprises recognised under DPIIT's Startup India scheme is Rs. 4,500 per class (versus Rs. 9,000 for others). A single-class filing for a logo mark covering software/SaaS (Class 42) will therefore cost Rs. 4,500 in official fees. Budget this at the engagement stage, not retroactively after a diligence flag.

Registered Designs

The Designs Act, 2000 protects the novel and original visual features of a product — shape, configuration, pattern, ornamentation. Registration lasts 10 years, extendable by 5. If a freelancer creates a product casing design, app icon, packaging layout, or UI component eligible for design registration, your agreement must assign the right to register under your company's name. The registered designs application fee via IP India is currently Rs. 1,000–Rs. 2,000 depending on applicant type.

Patents

Section 6 of the Patents Act, 1970 requires that the patent applicant must be the inventor or the person to whom the invention has been assigned before filing. A post-filing assignment does not cure a defective initial application in the same way. If a freelance developer, researcher, or data scientist creates a patentable invention during the engagement — an algorithm, a process, a hardware configuration — your contract must include:

1. A present-tense assignment of all inventions conceived during the engagement
2. An obligation to execute all documents the Indian Patent Office requires (Form-1 for the application, Form-6 for declaration of inventorship, as applicable)
3. Clarity on who pays prosecution and renewal fees — Indian patent prosecution can run Rs. 40,000–Rs. 1,50,000 in professional and official fees depending on complexity

Step 5: Post-Engagement Audit and Structured Hand-Over Protocol

IP leaks most often at the moment a freelancer relationship ends — not through malice, but through inattention. The developer still holds the GitHub repository. The designer holds the Figma master file. The agency has admin access to Google Analytics, Search Console, and the DNS provider.

Build a hand-over checklist directly into the contract as a schedule, triggered automatically upon project completion, contract termination, or non-renewal of a fixed-term engagement.

Minimum hand-over checklist by category

Code / Software

• [ ] Full source code repository transferred (GitHub/GitLab repository ownership change, not just access)
• [ ] All API keys, environment variables, and secrets rotated and documented
• [ ] SBOM in agreed format delivered and verified
• [ ] CI/CD pipeline documentation and deployment runbooks transferred

Design

• [ ] Editable master source files delivered (Figma, Adobe Illustrator .ai, Sketch) — not merely exported PNGs or PDFs
• [ ] Font licence confirmations and icon licence proofs provided
• [ ] All stock image/asset licence certificates or purchase receipts delivered

Content / Copy

• [ ] Original editable document files delivered (not just PDFs)
• [ ] Keyword research files, content calendars, and editorial style guides transferred

Credentials and System Access

• [ ] Admin access removed from all company platforms (AWS, GCP, Azure, Cloudflare, domain registrar, Google Workspace)
• [ ] 2FA/MFA devices unlinked from company accounts
• [ ] Third-party SaaS subscriptions transferred to company billing or cancelled

Documentation

• [ ] Architecture diagrams and technical documentation finalised and delivered
• [ ] All deliverables listed in a signed hand-over acknowledgement note confirming no further IP or access remains with the contractor

The hand-over note is a one-page document signed by both parties, confirming assets delivered, access revoked, and the freelancer's confirmation that they retain no claim over company IP or systems. File it with the original contract. It is the document your diligence lawyer will ask for first.

Worked Example: The Cost of a Missing Clause

A Bengaluru-based SaaS startup, incorporated as a private limited company, paid a freelance developer Rs. 6,00,000 (in two tranches) to build its core product over 8 months in FY 2024-25. The contract was a two-page service agreement with a scope-of-work attachment. No IP assignment clause. No SBOM requirement. No hand-over protocol.

What unfolded during Series A diligence in FY 2026-27:

1. The investor's legal team flagged the absence of a signed assignment agreement as a condition precedent to closing.
2. The freelancer — now employed full-time at a competitor — was approached for a retroactive assignment.
3. The freelancer's lawyer demanded Rs. 8,50,000 — a 42% premium over the original fee — citing the product's commercial deployment and recurring revenue.
4. An SBOM produced for the first time during diligence revealed two GPL v3-licensed components deeply integrated into the proprietary core module.
5. Replacing those components required a 6-week rewrite and a separate Rs. 1,80,000 contractor engagement.
6. Legal fees for the retroactive assignment negotiation and IP opinion letters: Rs. 2,20,000.
7. The fundraise was delayed by one full quarter.

Total unplanned cost: Rs. 12,50,000 — on a project that could have been protected correctly for the cost of a properly drafted IP agreement at the outset (typically Rs. 15,000–Rs. 40,000 in professional fees for a standard freelancer IP agreement).

The ratio is roughly 30:1. This pattern repeats across early-stage diligence cycles every year.

Common Mistakes and Pitfalls to Avoid

• Copying a US-style "work for hire" clause verbatim. Indian copyright law does not recognise "work for hire" as a transfer mechanism for independent contractors. The clause must say "assigns" — not "is a work made for hire."

• Treating the invoice as proof of ownership. An invoice is evidence of payment. It is not evidence of title. Every court hearing will look for a signed, written assignment.

• Assigning copyright but ignoring the trademark. A logo whose copyright is assigned can still be filed as a trademark by the original designer unless the agreement explicitly prohibits it and transfers that right.

• Limiting territory to India. Digital products operate globally. If your assignment says "India only," you do not own the copyright in the US, UK, or Singapore — markets your product likely serves or will serve.

• Forgetting Canva and stock site terms. Assets created inside a Canva Pro account or using licensed stock photographs are typically licensed to the designer's personal account, not assignable to a third party. Require confirmation in writing that all assets are either created from scratch, subject to an account-transferable licence, or are genuinely free of third-party restrictions.

• No clause on post-handover maintenance contributions. If you bring the freelancer back to patch bugs or add features six months later, does the same assignment apply? It should — include a clause confirming that any future work under subsequent purchase orders is governed by the same IP terms.

• Not getting the agreement notarised when the contractor is abroad. If you engage a freelancer based in the UAE, the UK, or the US, a notarised and apostilled agreement is significantly easier to enforce in a foreign jurisdiction if a dispute arises.

Key Takeaways

• Section 17, Copyright Act, 1957 defaults copyright ownership to the freelancer — not the paying company — for any "contract for service." A written, signed, present-tense assignment is the only remedy.
• A clause using "hereby assigns" transfers title at signing; a promise to assign later creates only a contractual obligation that may not survive the freelancer's disappearance or insolvency.
• Pre-existing IP disclosure and a signed SBOM are non-negotiable for software projects; undetected GPL contamination can require weeks of rewrite and derail a funding round.
• Moral rights under Section 57 cannot be extinguished by contract, but a non-assertion clause is enforceable and gives you the practical equivalent of a waiver.
• Trademark, design, and patent rights require their own assignment provisions — a copyright assignment transfers nothing in these categories, leaving significant IP value unprotected.
• A signed hand-over checklist at every engagement's close is the fastest preventive for the most common diligence failure: a former contractor still holding source files, master design files, or admin credentials.
• Budget Rs. 15,000–Rs. 40,000 for a properly drafted freelancer IP agreement the first time; retroactive repair — retroactive assignment, GPL rewrites, legal opinions — regularly costs Rs. 5,00,000 to Rs. 15,00,000 and always costs time you do not have during a fundraise.