Foreign companies frequently sign a vendor or employment contract that was written by their home-country lawyers, assume it protects their IP everywhere they operate, and never have it checked against Indian law. Three gaps show up over and over.
Jurisdiction clauses that don't actually apply
A contract governed entirely by, say, English or US law, with no Indian jurisdiction or enforceability clause, can be far harder to act on if something goes wrong with a team or vendor actually operating inside India. If your engineers, your vendor's office, and the work itself all sit in India, your contract needs enforceable Indian jurisdiction language alongside your home-country governing law — not instead of it, but as well as it.
Non-compete clauses that are weaker than they look
Section 27 of the Indian Contract Act generally renders post-employment non-compete restrictions unenforceable in India — a contract clause that would hold up cleanly in the US or UK often will not hold the same way here. Companies that rely on a broad non-compete as their main IP-protection mechanism are relying on a clause that a court is likely to strike down. The reliable protections are different: strong NDAs, IP assignment clauses that take effect during employment (not after), and access controls that limit exposure in the first place rather than trying to punish it after the fact.
IP assignment gaps between employees and contractors
Work created by a direct employee within the scope of employment is generally assigned to the employer by default. Work created by a contractor is a much greyer area under Indian copyright law unless the contract explicitly assigns IP rights — and a lot of vendor agreements are written loosely enough that this assignment is implied rather than stated. If your vendor relationship runs through subcontracted or freelance labor rather than direct employees, that ambiguity is a real gap, not a formality.
What actually protects you
- Explicit IP assignment language, effective from the start of work, not on exit.
- NDAs paired with real access controls — role-based repo access, no shared credentials, audit logs — rather than trust alone.
- A no-subcontracting clause, so you know exactly who has access to your code and IP at every point.
- Indian jurisdiction and enforceability language alongside your home-country contract terms.
We've written about the practical side of this in more depth in how to protect intellectual property with offshore developers. The short version: a contract template that works in your home market is a starting point, not a finished product, once real work is happening on Indian soil. Getting a local review before you sign — not after a dispute — is the difference between a clause that's enforceable and one that's decorative.
