Case Behind the Clause

How to Protect Your IP When Hiring a Freelancer in India

Published 14 September 2026 · 7 min read · Researched by Rakesh Jaiswar, LLB student, Mumbai

You paid a freelancer ₹50,000 to build your app. You have the invoice, the bank transfer, the WhatsApp messages. You do not own the code. Here's why — and the one clause that actually fixes it.

This is probably the most common IP gap in Indian startup contracts — and the most invisible. Founders only discover it when they're raising a funding round and an investor asks: "Who legally owns your product?" Or when a former contractor shows up claiming rights to the work they built for you.

What Indian copyright law actually says

Most founders assume payment transfers ownership. It doesn't — at least not for the categories of work most startups commission.

The Law — Copyright Act, 1957, Section 17 Under Section 17, the author of a work is the first owner of copyright — not the person who commissioned and paid for it. This applies to software, website code, design, written content, and most other digital work.

There is one exception: if the work was created by an employee in the course of their employment, the employer is the first owner. But a freelancer — even a long-term one, even one who works exclusively for you — is not your employee for copyright purposes. They are an independent contractor, and they retain ownership of what they create, unless they explicitly assign it to you in writing.

The Law — Copyright Act, 1957, Section 19 An assignment of copyright must be in writing and signed by the assignor (the person assigning, i.e. the freelancer) or their authorised agent. An oral agreement to assign copyright is not valid. Payment is not assignment. An invoice is not assignment. A WhatsApp "yes, you can use it" is not assignment.

Real situations where this gap causes real damage

Scenario 1 — The funding round question

A startup raises its first external round. During due diligence, the investor's lawyer asks for documentation showing the company legally owns its core product — specifically, the codebase and design assets. The founders have invoices and payment records but no signed IP assignment. The round is delayed by 6 weeks while they track down former contractors to sign retrospective assignments. Two can't be located. The investor reduces the valuation to account for the IP risk.

Scenario 2 — The contractor dispute

A founder commissions a logo and brand identity from a designer for ₹25,000. The relationship ends badly. The designer, knowing they technically own the copyright, threatens to license the same design to a competitor unless the founder pays them again. The founder has no signed assignment — so they settle, or spend more on legal fees than the original design cost to fight it.

Scenario 3 — The employee-to-contractor transition

A developer works as a full-time employee, then transitions to freelance. Work they do as an employee belongs to the company. Work done after the transition belongs to them — unless assigned. Without clear documentation of when the transition happened and what was assigned, there's a genuine dispute about who owns what.

What doesn't fix it — the common mistakes

What founders think works	Why it doesn't
Paying the invoice	Payment ≠ assignment under Section 19
"All rights reserved" on the invoice	The freelancer adding this doesn't assign it to you
WhatsApp / email "you can use it"	Must be in writing AND signed — a message isn't signed
Verbal agreement	Section 19 explicitly requires written assignment
NDA alone	Confidentiality ≠ ownership transfer
Freelance agreement without an IP clause	Many generic freelance agreements skip this entirely

What actually fixes it — the IP assignment clause

A properly drafted freelance agreement must include an explicit IP assignment clause. Here's what it needs to cover:

All work created during the engagement is assigned to the company upon creation — not just on payment
The assignment covers existing IP brought in to the project (background IP), where it's incorporated into the deliverable
Future work and modifications are also covered — not just the initial deliverable
The freelancer warrants that the work is original and doesn't infringe third-party rights
A moral rights waiver — under Indian copyright law, creators retain moral rights (right of paternity and integrity) even after assignment; this should be explicitly waived
The freelancer agrees to sign any further documentation needed to perfect the assignment (important for patents, registered designs)

What a properly drafted IP assignment clause looks like

All intellectual property rights (including copyright, design rights, and any other proprietary rights) in the Deliverables and any work product created by the Service Provider in connection with this Agreement ("Work Product") shall vest in and be owned exclusively by the Company from the moment of creation. The Service Provider hereby irrevocably assigns to the Company all present and future rights, title, and interest in the Work Product, including all copyright and related rights. To the extent permitted by law, the Service Provider waives all moral rights in the Work Product. The Service Provider shall, at the Company's reasonable request and cost, execute any further documents required to perfect the Company's ownership of the Work Product.

One thing most generic templates miss The moral rights waiver. Under Sections 57 and 57A of the Copyright Act 1957, an author retains the right to claim authorship and the right to object to distortion or modification of their work — even after assigning copyright. Without an explicit waiver, a former freelancer could still object to you modifying the logo you commissioned, or demand credit every time you use it. A verified freelance agreement will include this waiver.

What about work done before you had a proper agreement?

If you've already worked with freelancers without a proper IP assignment, the fix is a retrospective assignment — a separate document signed by the freelancer confirming that all past work is assigned to you. This is legally valid under Indian copyright law, though it requires the freelancer's cooperation. It's also exactly the document investors will ask for during due diligence if gaps are found.

The practical lesson: it's far easier to get this signed before the relationship ends than after. A departing contractor who knows you need their signature has significant negotiating leverage.

The employer exception — and why it doesn't apply

Section 17 of the Copyright Act does give employers automatic ownership of work created by employees in the course of their employment. But "employee" has a specific legal meaning here — it requires genuine employment, including PF contributions, TDS deductions under the appropriate section, and a subordinate relationship. Courts have looked at the substance of the relationship, not just the label. Calling someone a "contractor" while treating them as an employee doesn't make them an employee for copyright purposes — but the reverse is also true. If you're genuinely treating someone as a freelancer (no PF, project-based payment, no fixed hours), they are a freelancer for copyright purposes, and you need that written assignment.

Fix this before your next freelancer project

Our Freelance Service Agreement includes a verified IP assignment clause, the moral rights waiver, and the background IP provisions — drafted against the current Copyright Act, not a generic template.

View Freelance Service Agreement →

Sources: Copyright Act, 1957, Sections 17, 19, 57, 57A. This article is general legal education, not advice on your specific situation. Consult an enrolled advocate for specific legal questions about your contracts.

Researched and verified by Rakesh Jaiswar, LLB student, Mumbai — September 2026.