tegwick
11f2dc3a6d
Executes all remaining shared jurisdictions across both workplans: Germany/EU (deepened contract-law angle), US (deepened), UK (deepened), Argentina, India, China, Africa (South Africa + OHADA), and Asia-Pacific (Singapore, Japan, Australia) - 13 new history/ research artifacts. Highest-priority findings: - Australia's Unfair Contract Terms regime (expanded Nov 2023) covers standard-form contracts with any business under 100 employees/$10M turnover by default - the CUA is exactly such a contract, and most realistic Customers fall within this threshold. Unlike every other jurisdiction's consumer carve-out, this is not an edge case. - China requires a "foreign-related" contract even to select foreign governing law, subject to a vague public-interest override even then - confirms a dedicated China rider is needed for both the License/CUA and the Enforcement Partner Agreement, not a shared global clause. - India flatly prohibits advocate contingency fees (no exception gates, stricter than Germany) while explicitly permitting third-party litigation funding - the cleanest confirmation yet that the Litigation Funder/Local Counsel split-role model is both necessary and legal there. - Japan's Article 12 fee-splitting rule means even the split-role fallback needs jurisdiction-specific structuring - the first case where the workaround itself, not just the original mechanism, has an open compliance question. - Contingency Share ceilings vary widely where available: UK 50% (exact match), South Africa 25%, Argentina 35% (50% only with risk assumption), China 18% down to 6% on a sliding scale that shrinks as claims grow. - Recurring cross-jurisdictional pattern (Germany, EU, US via CCPA, Argentina): B2B governing-law/liability clauses are respected, but an individual/sole-proprietor Customer's consumer-protection status is the operative risk everywhere, not a one-off edge case. Updates specs/EnforcementNetworkConcept.md §8.1 with a full 12-jurisdiction findings table and three cross-cutting conclusions. Updates both V1C1 documents' Appendix A items (governing law, liability cap, data protection) with the most consequential findings. Both workplans now have only their human-gated synthesis tasks (T09-T10 / T10) remaining. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
4.7 KiB
TRSL Jurisdiction Research: India
Document status: Research artifact, Stage 0 (workplans/TREV-WP-0004-global-jurisdiction-research.md T05)
Not legal advice. Findings drawn from web research (searched 2026-07-29).
1. Limitation-of-liability clauses are generally enforceable, with statutory-violation and public-interest limits
Indian courts generally permit contractual limitation of financial exposure, but Section 28 of the Indian Contract Act voids agreements that wholly restrain a party from enforcing its rights in court — a limitation clause cannot function as a complete bar on legal recourse. Courts will not enforce limitation or indemnity clauses that attempt to exclude liability for fraud, personal injury, or statutory obligations, or that otherwise defeat legislative intent or public interest.
Direct implication: specs/TargetRevenueCommercialUseAgreement-V1C1.md §14's liability cap (not a complete bar on remedies, just a quantum cap) is the kind of clause Indian courts generally do enforce — this is a lower-friction jurisdiction for that specific clause than the UK (UCTA reasonableness test) or the US (unconscionability backstop), provided the cap is not drafted so broadly it reads as excluding a statutory obligation entirely.
2. Indemnification: no statutory cap on quantum, carve-outs from the liability cap are standard practice
Research found no statutory restriction on the quantum recoverable under an indemnity clause in Indian commercial practice, and indemnity provisions are commonly drafted to sit outside a contract's general limitation-of-liability cap (i.e., the cap applies to ordinary breach damages, not to indemnified third-party claims).
Direct implication: this is directly relevant to specs/TargetRevenueCommercialUseAgreement-V1C1.md §13, which is currently and deliberately left unwritten (Appendix A item 4, the highest-priority item in that document). If an indemnification clause is eventually drafted, Indian practice confirms the common structural choice — indemnity carved out from the general liability cap — is a defensible starting point for at least this jurisdiction, though the clause's substance (scope of indemnified claims) remains a separate, unresolved drafting question.
3. Foreign jurisdiction/governing-law clauses: respected
Indian courts recognize and respect a foreign jurisdiction/governing-law clause in an international contract. This is a comparatively clean finding relative to several other jurisdictions researched, where the answer has required more qualification (Rome I's consumer carve-out, China's expected reluctance per WP-0004 T06's task description).
4. Digital Personal Data Protection Act 2023: a "negative list" model, more permissive than GDPR by design
India's DPDPA 2023 (with 2025 Rules) uses a "negative list" approach: cross-border transfers are permitted to all countries except any the government specifically restricts by notification — and as of this research pass, no country has been so restricted. This is structurally the opposite of GDPR's adequacy-based "permitted only where a safeguard exists" approach, and is explicitly more flexible. Extraterritorial reach applies to processing connected to offering goods/services to data principals within India, similar in spirit to GDPR's own extraterritorial scope. Additional restrictions apply only to entities designated "Significant Data Fiduciaries."
Direct implication: for CUA §11, an Indian Customer is currently a low cross-border-transfer-friction case (no restricted-country list yet exists), though the Licensor should not assume this permissiveness is permanent — a future government notification could restrict transfers to a specific country with no advance-warning requirement evident in this research.
5. Summary for the WP-0004 feasibility matrix (T10)
| Question | India |
|---|---|
| Liability cap enforceable? | Generally yes, subject to Contract Act §28 (no complete bar on remedies) and statutory/public-interest limits |
| Indemnification quantum capped by statute? | No; common practice carves indemnity out of the general liability cap |
| Foreign governing-law/venue clause respected? | Yes |
| Data protection cross-border transfer friction | Low currently ("negative list" model, no restricted countries yet) but not guaranteed to stay that way |
6. Open items for T10 synthesis
- Confirm DPDPA 2025 Rules' Significant Data Fiduciary restrictions don't apply to a typical CUA Customer before relying on the "low friction" finding above for a specific deployment.
- No India-specific software-licensing/delayed-conversion precedent was found in this pass — treat the License's overall structure as untested in Indian courts specifically, same as most jurisdictions in this program.