Code written for you is not automatically yours. In a German employment relationship, §69b UrhG gives the employer the economic rights to software created by employees in the course of their duties. That rule does not extend to code written by a vendor's engineers in India. There, the rights reach the German client only through a contractual chain: from the engineer to the Indian employer, and from that employer to the client. Each link follows different rules, and Indian copyright law contains default provisions that can quietly limit an assignment if the contract is silent. This guide explains the chain and lists the clauses that close it.
Why the rights chain carries real value
Software is the asset DACH technology companies are valued on, and it is increasingly built across borders. EY's Startup-Barometer counted EUR 8.4 billion in venture capital raised by German startups in 2025 across 716 financing rounds, and ownership of the core code is a standard item in investor due diligence on rounds like these. Bitkom expects the German software market to grow 9.9 percent to EUR 58.1 billion in 2026.
Where value is created, risk follows. In its 2025 economic protection study, Bitkom put the damage to the German economy from data theft, industrial espionage and sabotage at a record EUR 289.2 billion, with 87 percent of companies affected within twelve months. On the delivery side, NASSCOM estimates that Indian engineering, research and development services generated USD 63 billion in revenue in FY26. Contracts that route that work to German clients need a rights chain that holds up in both legal systems.
The German side: Nutzungsrechte, not ownership
Computer programs are protected under §69a UrhG. Under German law, copyright itself cannot be transferred during the author's lifetime (§29 Abs. 1 UrhG). What can be granted are rights of use (Nutzungsrechte) under §31 UrhG, either exclusive or non-exclusive, and limited or unlimited in time, territory and content. When a contract does not list the types of use specifically, §31 Abs. 5 UrhG applies the purpose-of-transfer principle (Zweckübertragungslehre): the scope of rights is determined by the purpose of the contract, which tends to be narrower than the client expects. A German contract should therefore enumerate the types of use explicitly, including modification, further development, combination with other software, sublicensing and transfer to third parties such as acquirers.
The Indian side: assignment rules with default limits
Under Section 17 proviso (c) of the Indian Copyright Act 1957, the employer is the first owner of copyright in a work made in the course of employment under a contract of service, in the absence of an agreement to the contrary. A properly structured Indian vendor therefore holds the rights in its employees' code. Passing them on is governed by Section 19:
| Provision | Rule | Contract consequence |
|---|---|---|
| Section 19(1) | An assignment is valid only in writing, signed by the assignor or an authorised agent | No implied or email-only assignments |
| Section 19(4) | If the assignee does not exercise the rights within one year, the assignment is deemed to lapse unless otherwise specified | State expressly that non-exercise does not lead to lapse |
| Section 19(5) | If the period is not stated, the assignment is deemed to be for five years | State the period, typically the full term of copyright |
| Section 19(6) | If the territory is not specified, it is presumed to extend within India | State worldwide territory |
A German-law contract that grants exclusive, unlimited Nutzungsrechte but says nothing on duration, territory or lapse may create uncertainty if the assignment is later tested under Indian law. The pragmatic answer is to draft so that the clause works under both systems.
Choosing German law and a German place of jurisdiction for the client contract is common and sensible. It does not, however, replace checking whether the assignment is also effective where the rights arise and may have to be enforced. For larger engagements, a brief review of the clause by Indian counsel is worthwhile.
The rights chain in practice
- Engineer to vendor. Employment contracts of the vendor's engineers should confirm that work created in the course of employment belongs to the employer. If the vendor uses freelancers or subcontractors, written assignments from them are required, because Section 17 (c) covers employment, not service contracts.
- Vendor to client. The client contract grants or assigns the rights, with explicit duration, territory, types of use and exclusion of lapse.
- Evidence. The vendor should be able to show, on request, that the chain is closed for every person who contributed code.
Points that are often missing
Timing of the transfer
Many vendor templates transfer rights only on full payment. That is understandable commercially, but it leaves the client without rights to work already delivered during a dispute. A balanced pattern: rights to accepted and paid increments pass immediately, a non-exclusive right to use pending work applies until payment.
Pre-existing materials
Vendors bring libraries, templates and internal tools. These should be identified and licensed (non-exclusive, perpetual, sufficient for the client's use and further development), not transferred. Without such a list, disputes about what belongs to whom arise at the end of the engagement.
Open source
Open source components remain under their licences. The contract should require a list of components with licences (for example as a software bill of materials) and prohibit components whose licence terms conflict with the client's distribution model without prior consent.
AI-assisted code
Whether and to what extent code generated with AI assistants is protected by copyright is not settled. Contracts increasingly require disclosure of AI tools used, compliance with the client's policy on such tools, and warranties that the output does not knowingly reproduce third-party code under incompatible licences.
Moral rights
Both legal systems recognise author's personal rights that cannot be fully transferred. Contracts typically include an agreement not to assert attribution and integrity rights to the extent legally permissible, so that modification and anonymous use remain possible.
Repository ownership as a practical safeguard
Legal rights are only useful if the client can access the code. Work in repositories owned by the client from day one, with the vendor's engineers as invited members. This removes the need for escrow arrangements in most cases and makes handover a matter of revoking access.
Clause checklist
- Exclusive Nutzungsrechte, unlimited in time, territory and content, with enumerated types of use
- Express worldwide territory, term of copyright, exclusion of lapse for non-exercise
- Written confirmation of the vendor's rights chain, including subcontractors
- Transfer timing linked to acceptance and payment of increments
- List and licence for pre-existing materials
- Open source list and approval procedure
- AI tool disclosure and policy compliance
- Non-assertion of moral rights where permissible
- Code in client-owned repositories
Payments to foreign vendors that include rights components can also raise withholding tax questions under §50a EStG. Clarify this with your tax adviser before the first invoice.
This article is general information and does not constitute legal or tax advice for your specific situation.
A rights chain is easiest to defend when the code never leaves your control in the first place. That is why niogod™ pods work in client-owned repositories, so that the code base and its history sit with you from the first commit, as outlined on the compliance page. If offshore development is on your roadmap, reviewing the rights clauses before signature costs far less than repairing the chain in the middle of a funding round.
Talk to niogod™
Planning engineering capacity in DACH? Book a 30-minute consultation with the niogod™ team.
Book consultation