Source Code Escrow Legal Relevance
π 1. What Is Source Code Escrow?
A source code escrow arrangement is a tripartite setup where:
Vendor deposits source code with an escrow agent
Customer gets conditional access
Access is released only if specified trigger events occur
It protects customers from vendor failure.
π 2. Why Corporates Need It
When companies rely on:
Enterprise software
Mission-critical SaaS platforms
Custom-developed systems
they face risk if vendor:
β Goes bankrupt
β Stops support
β Terminates business
β Breaches contract
Escrow = business continuity insurance.
π 3. Legal Nature
Source code escrow involves:
| Legal Area | Role |
|---|---|
| Copyright law | Source code ownership remains with vendor |
| License law | Escrow grants conditional license upon release |
| Contract law | Trigger conditions & access rights |
| Insolvency law | Protection against vendor liquidation risk |
π 4. Typical Release Triggers
β Vendor insolvency
β Failure to provide support
β Material breach
β Discontinuation of product
β Failure to update escrow deposit
π 5. Legal Issues in Escrow Arrangements
πΉ 1. Ownership vs Access
Customer does not own code; receives limited license.
πΉ 2. Scope of Use After Release
Maintenance only? Modification? Commercial use?
πΉ 3. IP Protection
Customer must protect vendorβs trade secrets.
πΉ 4. Insolvency Complications
Escrow rights may conflict with bankruptcy proceedings.
πΉ 5. Adequacy of Deposit
Outdated or incomplete code defeats purpose.
π 6. Major Corporate Risk Areas
| Risk | Impact |
|---|---|
| Vendor shutdown | System unusable |
| No update to escrow | Code obsolete |
| IP misuse post-release | Litigation |
| Escrow terms unclear | Dispute over release |
| SaaS model without escrow | Total dependency |
π 7. Important Case Laws
β 1) Engineering Analysis Centre of Excellence v. CIT (2021, SC)
Principle: Clarified nature of software licenses.
Impact: Escrow release creates license rights, not ownership transfer.
β 2) Tata Consultancy Services v. State of Andhra Pradesh (2004, SC)
Principle: Software recognized as valuable commercial subject.
Impact: Emphasizes legal protection of software assets.
β 3) Microsoft Corp. v. Yogesh Papat (Delhi HC)
Principle: Unauthorized copying is infringement.
Impact: Escrow use beyond license scope can be infringement.
β 4) Anvar P.V. v. P.K. Basheer (2014, SC)
Principle: Electronic records must be reliable.
Impact: Escrow deposit integrity matters.
β 5) Super Cassettes v. MySpace (2016, Delhi HC)
Principle: Digital platform IP responsibilities.
Impact: Handling source code requires IP compliance.
β 6) Google India Pvt. Ltd. v. Visaka Industries (2020, SC)
Principle: Liability linked to control and knowledge.
Impact: Customer assumes responsibility when accessing code.
β 7) Ferid Allani v. Union of India (2019, Delhi HC)
Principle: Software inventions may have patent protection.
Impact: Escrow code may contain patentable elements.
π 8. Essential Escrow Clause Elements
β Clear trigger events
β Deposit update schedule
β Verification of deposit
β Scope of post-release license
β Confidentiality protections
β Escrow agent duties
β Dispute resolution mechanism
π 9. Governance Measures for Corporates
Periodic escrow verification
Ensure documentation included
Review escrow triggers
Align with business continuity plan
Legal review of post-release rights
π 10. When Escrow Disputes Arise
Serious litigation occurs when:
Vendor contests release
Code is incomplete
Use exceeds license
Insolvency administrator intervenes
π 11. Key Legal Takeaway
Source code escrow is risk mitigation, not IP transfer. It creates:
Conditional license rights activated upon defined failure events.
Its effectiveness depends entirely on clear triggers + updated deposits + well-defined post-release rights.

comments