Every company that tries to extend development team remotely to India in 2026 faces a compliance landscape that changed more in the last eight months than it did in the previous three decades. India's four consolidated labour codes became law in November 2025. The final central rules were notified in May 2026. IP assignment requirements got stricter. The Digital Personal Data Protection Act is on a rolling enforcement schedule.
If your contract with an Indian IT staff augmentation services provider was drafted before November 2025, it is probably outdated. And an outdated contract in a changed regulatory environment is not just a paperwork problem. It is an IP ownership gap, a payroll compliance risk, and a potential data protection liability sitting inside your vendor relationship.
This guide covers the three areas that matter most for foreign companies using staff augmentation services in India: intellectual property, the new labour codes, and the contract clauses that hold it all together.
#RECENT EVENTS: India's labour code implementation is ongoing. State-level rules are at varying stages of notification as of mid-2026. Verify current status through your legal counsel or the Ministry of Labour and Employment (labour.gov.in) before acting on anything in this article.
What Changed with the Four Labour Codes
India consolidated 29 central labour laws into four codes between 2019 and 2020. Those codes became effective on November 21, 2025. The central rules under all four codes were notified on May 8, 2026.
The four codes are the Code on Wages 2019, the Industrial Relations Code 2020, the Code on Social Security 2020, and the Occupational Safety, Health and Working Conditions Code 2020.
For companies that hire dedicated developers through Indian vendors, three changes matter most.
The 50% Wages Rule
Basic wages (or basic plus dearness allowance) must now be at least 50% of an employee's total compensation. This changes how Indian IT companies structure CTC (cost to company). If your vendor has not restructured their payroll, their PF and gratuity contributions may be calculated on the wrong base. That is the vendor's compliance burden, not yours directly, but vendor non-compliance creates instability.
An engineer whose employer is in a wage dispute is not an engineer focused on your sprint.
Fixed-Term Employee Protections
The new codes give fixed-term employees the same benefits as permanent staff, including pro-rata gratuity regardless of tenure length. This matters because many it staff augmentation companies in India historically classified augmented engineers on fixed-term contracts with reduced benefits. That gap is now closed by statute.
Appointment Letters Are Mandatory
The OSH Code requires every employer to issue a written appointment letter. If your vendor's engineers do not have formal appointment letters, the vendor has a compliance gap. Ask.
IP Ownership: What Indian Law Actually Says
This is the area where most foreign buyers get it wrong, and where the cost of getting it wrong is highest.
The Default Rule for Employees vs. Contractors
Under Section 17 of the Indian Copyright Act 1957, an employer owns the copyright of works created by an employee during the course of employment. That default is clear. But augmented engineers are typically not your employees. They are employees of the vendor, or in some cases classified as independent contractors by the vendor.
When the developer is the vendor's employee, copyright vests with the vendor by default. Not with you. For the IP to reach your company, the vendor must explicitly assign it. A service agreement that says "work product belongs to the client" is a start but may not survive scrutiny without a proper deed of assignment.
Why a Written Assignment Is Not Optional
Indian law requires IP assignment to be in writing. Verbal agreements or implied terms do not transfer copyright. Furthermore, under the Indian Stamp Act, an unstamped deed of assignment may be inadmissible in Indian courts. If your vendor is assigning IP through a clause in a master services agreement without proper stamp duty, that assignment could be challenged.
The practical fix is a standalone IP assignment deed executed per engagement or per developer, stamped according to the applicable state's stamp schedule. Your vendor should handle this. If they do not know what this means, that is a red flag.
Independent Contractors Retain Everything
If your vendor uses independent contractors (freelancers subcontracted to your project), those contractors retain all IP by default under Indian law. The vendor needs an explicit written assignment from the contractor before they can assign anything to you. Ask your vendor whether any of the engineers on your project are subcontracted, and if so, whether the contractor-to-vendor IP assignment is in place.
Data Protection: The DPDP Act
The Digital Personal Data Protection Act, 2023 (DPDP Act) rules were notified in November 2025, with full enforcement rolling out through 2027. If augmented developers handle any personal data from your users or customers, a Data Processing Agreement (DPA) between your company and the vendor is a regulatory requirement. Penalties go up to 250 crore rupees per breach.
Even if your current project does not involve personal data today, scope creep can introduce it. Cover the DPA in the master agreement upfront.
What Your Contract Should Say
A compliant staff augmentation contract with an Indian vendor in 2026 needs to address five areas that many older agreements miss.
IP Assignment Chain
Your agreement should trace IP from the individual developer to the vendor to your company. If the vendor uses subcontractors, there must be a developer-to-vendor assignment before the vendor-to-client assignment means anything. Each link in that chain must be in writing and properly stamped.
Confidentiality with Dual Jurisdiction
NDAs that reference only US or UK law are not enforceable in Indian courts without an Indian arbitration clause. Your NDA should reference the Indian Contract Act 1872 alongside your home jurisdiction. Specify Indian arbitration as the dispute resolution mechanism for any India-side breach.
Non-Compete Limitations
Section 27 of the Indian Contract Act makes most non-compete clauses unenforceable. Post-employment restraints on an engineer's ability to work for competitors are generally void under Indian law. Non-solicitation and confidentiality clauses are enforceable. Structure your protections around what Indian law supports, not what your US template says.
Labour Code Compliance Warranties
Your contract should require the vendor to warrant compliance with the four labour codes, including the 50% wages rule, appointment letter issuance, and social security contributions. This protects you from vendor instability and gives you a contractual remedy if the vendor cuts corners on statutory obligations.
Data Processing Agreement
If any engineer on the engagement touches personal data, a DPA compliant with the DPDP Act must be in place before access is granted. Specify data categories, processing purposes, retention periods, and breach notification timelines.
What This Looks Like in Practice
A US SaaS company engaged an IT staff augmentation company in India for three backend engineers. The initial MSA had a generic "all work product belongs to client" clause and a US-only governing law provision. Six months in, one engineer left the vendor. The replacement was a subcontractor. No one updated the IP chain. The company later discovered that six months of code written by the subcontractor had no valid assignment to the vendor, and therefore no valid assignment to them. Legal remediation took four months and cost more than the entire augmentation engagement. #SOURCES
This is not unusual. It is the default outcome when contracts are not structured for Indian law.
How to Vet an Indian Vendor for Compliance
If you are evaluating it staff augmentation companies for India-based engagements, five questions separate compliant vendors from the rest. Have they restructured payroll under the new codes? Can they show a sample IP assignment deed? Are any engineers subcontracted, and is the IP chain documented? What is their DPDP Act readiness? What is their stamp duty process on IP assignments?
Vendors who treat these questions as routine have done the work. Vendors who hesitate are telling you something.
Do Not Wait for a Dispute to Fix the Contract
India's compliance landscape for staff augmentation moved faster in 2025 and 2026 than most foreign buyers expected. The labour codes, the DPDP Act, and tighter IP assignment standards are not future risks. They are current requirements.
If you already have an Indian vendor, audit the contract against the five areas above. If you are evaluating new providers, put compliance vetting ahead of rate comparison.
Book a discovery call with a provider that understands the new framework and can walk you through the IP chain, the labour code warranties, and the DPA structure before the first engineer starts. That upfront work is cheaper than the alternative.
Book a Free Consultation
Frequently Asked Questions
1. Do India's new labour codes apply to staff augmentation vendors?
Yes. The four labour codes are effective nationwide as of November 21, 2025, with central rules notified May 8, 2026. Any vendor employing engineers in India must comply, including it staff augmentation companies serving foreign clients. #RECENT EVENTS: State-level rules are still being notified. Confirm your vendor's state-specific compliance status.
2. Who owns the IP when I hire dedicated developers through an Indian vendor?
By default, the vendor does, not you. Under Section 17 of the Indian Copyright Act, the employer (the vendor) owns works created by their employees. You only own the IP if there is an explicit, written assignment from the vendor to you.
3. What is the 50% wages rule and why should I care?
Basic wages must be at least 50% of total compensation. This increases the vendor's PF and gratuity costs. If the vendor has not restructured payroll, they may be non-compliant, which creates financial instability that can disrupt your engagement.
4. Is a standard US NDA enforceable against an Indian developer?
Not easily. A US-only NDA lacks enforceability in Indian courts without an Indian arbitration clause. Best practice is a dual-jurisdiction NDA referencing both the Indian Contract Act and your home jurisdiction.
5. Can I include a non-compete clause for augmented engineers in India?
Non-competes are largely unenforceable under Section 27 of the Indian Contract Act. Use non-solicitation and confidentiality clauses instead, which Indian courts do enforce.
6. What is the DPDP Act and how does it affect staff augmentation?
The Digital Personal Data Protection Act 2023 regulates how personal data is processed in India. If augmented engineers handle your users' data, you need a Data Processing Agreement with the vendor. Penalties can reach 250 crore rupees per breach. #RECENT EVENTS: Full enforcement is rolling out through 2027.
7. Does the vendor need to provide appointment letters to augmented engineers?
Yes. The OSH Code 2020 mandates written appointment letters for all employees. This is the vendor's obligation, but you should confirm compliance as part of vendor vetting.
8. What happens if the vendor uses subcontractors on my project?
IP risk increases. Subcontractors retain all IP unless they have explicitly assigned it to the vendor in writing. Without that link, the vendor cannot validly assign IP to you. Ask your vendor to disclose and document any subcontractor arrangements.
9. How do I verify that my vendor's IP assignment is legally valid in India?
Check three things: the assignment is in writing, it is executed as a standalone deed or clearly worded clause, and it is stamped per the applicable state's stamp duty schedule. Unstamped deeds may be inadmissible in Indian courts.
10. Should I audit my existing Indian vendor contract for the new codes?
Yes. Any contract drafted before November 2025 predates the labour codes' effective date and likely does not include the required warranties around the 50% wages rule, social security contributions, or DPDP Act compliance. Audit now. Do not wait for a dispute.
