Technology Cooperation and Licensing with Chinese Partners
Technology moves in both directions. Foreign companies license software, model architectures and process know-how into Chinese joint ventures, OEMs and customers; Chinese companies license robotics, vision and battery technology out to foreign buyers. Both directions share the same failure mode: the licence describes what may be used, but says nothing about what happens to what is learned during the relationship.
That gap is where the value moves. A licence that covers the licensed code but not the improvements, the calibration data or the fine-tuned model leaves the licensor with a partner who has become a competitor using technology the licensor helped create.
Four arrangements, four risk profiles
Inbound licence. Foreign technology licensed to a Chinese entity. The licensor’s exposure is scope creep, sublicensing to affiliates, and the practical difficulty of auditing use inside a partner’s systems.
Outbound licence. Chinese technology licensed to a foreign company. The Chinese licensor faces China’s technology export control regime and, where state-owned entities or listed technologies are involved, approval requirements. The foreign licensee faces dependency risk if the licensor’s obligations are thin.
Co-development. Both sides contribute and the output is a product neither could build alone. The critical clauses are ownership of foreground IP, allocation of improvements, and what each party may do with the result outside the project.
OEM and ODM with technology transfer. Manufacturing relationships where designs, tooling and process know-how move with the order. These are licensing agreements in substance even when they are titled supply agreements.
Where the value leaks
Scope that is wider than intended. Field of use, territory, affiliates, sublicensing and the number of permitted users are the five variables that define what has actually been granted. A licence “for the Asia-Pacific region” granted to a group with a global cloud platform is a global licence in practice.
Improvements and grant-back. A clause requiring the licensee to grant back improvements sounds balanced until it is applied to everything the licensee develops in the same field. Grant-backs should be limited to improvements derived from the licensed technology, and should be non-exclusive and reciprocal.
Model weights, parameters and calibration data. These are the AI-era equivalent of source code, and they are usually not mentioned in licences drafted from software templates. Their status — background IP, licensed asset, deliverable, or trade secret — determines who may use them after termination.
Escrow and release triggers. Where the licensee’s product depends on the licensor’s software or model, escrow with defined release events is the only practical protection against the licensor’s insolvency or refusal to maintain. The triggers should be objective: insolvency, cessation of support, failure to cure a material breach within a stated period.
Technology export control. China’s Export Control Law and the dual-use regime can catch outbound transfers of listed technology, including through technical discussions and source code access. For inbound transfers, the exporter’s home jurisdiction usually governs. Either way, classification belongs in the deal timetable, not in post-closing compliance.
People. Know-how moves with engineers. Non-compete clauses are enforceable in China only within limits, and a licence that assumes the partner’s team will not be hired away is relying on a clause that may not survive scrutiny.
Termination. The default position after termination is harsh: continued use of background IP becomes infringement. Survival rights for products already in the field, for service obligations and for data return must be written into the agreement.
Ownership matrix
| Contribution | Default position | What to negotiate |
|---|---|---|
| Background IP brought by each side | Remains with the contributor | Licence scope to the project, and to the other party’s affiliates |
| Foreground IP created by one party’s staff | That party, if the contract says so | Assignment to the project company, or joint ownership with exploitation rules |
| Foreground IP created jointly | Unclear without agreement | Separate ownership of modules, or joint ownership with a licensing protocol |
| Improvements to background IP | Contributor | Non-exclusive, reciprocal grant-back limited to the licensed field |
| Data and datasets | Contributor, subject to PIPL | Use rights, storage location, cross-border terms, deletion on termination |
| Model weights and fine-tuned models | Contributor | Licence for production use, escrow, restriction on reverse engineering |
What we do
- Licence architecture: scope, field, territory, affiliates, sublicensing, exclusivity
- Background and foreground IP allocation, including improvements and grant-back
- Trade secret programme for models, parameters and calibration data
- Technology export classification and approval sequencing
- Data schedules: training data, derived datasets, cross-border transfer
- Escrow and release-trigger drafting
- Termination, survival and transition planning
- Dispute readiness: evidence of scope, access and disclosure
In-depth guides
- The Scope Clause: What a China Technology Licence Actually Grants
- Licensing AI Models and Model Weights to Chinese Partners
Related guides
Frequently asked questions
What is the difference between licensing technology into China and out of China? The architecture is similar, but the regulatory overlay is not. Inbound licences raise Chinese registration, withholding tax and data questions; outbound licences from a Chinese licensor raise China’s technology export control and may require approval for restricted technology.
Who owns the IP created during a joint development project? Whoever the contract says. Chinese law has no default rule that splits jointly developed IP evenly; absent agreement, ownership and exploitation rights are unclear and expensive to litigate.
Are model weights and parameters protected as trade secrets in China? They can be, if kept secret and subject to reasonable protective measures. Access controls, employee agreements and records of disclosure are what make the claim survive.
Can we prevent a Chinese partner from filing patents on our improvements? Only by contract — an assignment or option over improvements, a prohibition on filing without consent, and a mechanism to record the obligation.
Does exporting technology to China require Chinese government approval? It depends on the technology. Chinese controls apply to exports from China; for technology flowing in, the exporter’s own jurisdiction usually governs.
How do we handle training data used in a joint project? As a separate asset with its own schedule: permitted use, storage location, cross-border terms, and what happens to derived datasets on termination.
What happens to the licence if the relationship ends? Whatever the termination clause provides. The default is unfavourable: continued use of background IP after termination is infringement unless a survival right is granted.