Software Escrow as a Business-Continuity Tool

Introduction : In today’s world organisations have become primary users of software applications in this digital environment to offer their services and also to have a competitive edge. This dependency also poses major risks if the vendor goes bankrupt, is acquired, fails to provide support, or any other anticipated events occur. Operational, regulatory compliance and trust of customers are all affected areas of impact that can be caused by these kinds of disruptions to organisations. 

The Software escrow is a strategic risk management mechanism which is particularly designed to address these concerns. As it ensures source code, documentation, and also critical assets of software are deposited securely with independent third parties, software escrows provide a safeguard which allow users in maintaining and supporting essential applications if the software vendor is unable to fulfil their obligations within the contract.

Legal Provisions

The Copyright Act,1957 (India)

Software escrows operate within the framework of Intellectual Property law, under Section 2(o) of the Copyright Act, 1957Computers are also considered as “literary works” and are entitled to copyright protection. Further, Section 14(b) grants rights to the copyright owner to reproduce, issue copies, adapt, and commercially exploit the computer program. 

The legal primary objective of any escrow arrangement is to balance the intellectual property rights of the developer with the need of licensees for uninterrupted access to business-critical software. The agreement of escrow ensures that ownership of source code still remains with the developer giving conditional access to the customer upon occurrence of events like insolvency, bankruptcy, or failure in providing maintenance services.

Insolvency and Bankruptcy Code, 2016 (IBC)

One of the primary reasons to establish a software escrow is to lessen the risks which can arise from insolvency or bankruptcy of a software vendor. Insolvency is a major threat to service continuity. Section 14, imposes a halt during the Corporate Insolvency Resolution Process (CIRP), Section 18 and 25, which empower insolvency professionals to take control and protect the assets of the corporate debtor specially where customers rely on the proprietary software for business operations. Therefore, Escrow agreements commonly include insolvency related triggers that allow customers to obtain access from the deposited source code when the vendor is no longer capable to perform its contractual obligations. However, bankruptcy law can sometimes complicate the enforcement of escrow arrangements by treating the source code as a part of an insolvent vendor.

The Indian Contract Act, 1872

The Indian Contract Act, 1872 Section 10 establishes the requirements for valid contracts which are free consent and consideration The software escrow agreement itself has the principal in their contractual mechanism which supports business continuity. It is entered into between the software provider, the customer and an escrow agent, Section 37 impose obligations on the parties to perform their contractual promise like on the vendor to deposit source code, modifications, and supporting documentation while requiring the escrow agent to maintain confidentiality and release the materials only on the occurrence of agreed trigger events. 

Legal Analysis

Protection of Software 

Software escrow relies upon considering the software as a protectable intellectual property asset. In Tata Consultancy Services v. State of Andhra Pradesh, (2005) 1The Apex Court mentioned that the software whether it is customised or packaged still possesses utility, value and capability to be transmitted, transferred, stored and possessed. Although this case arises in sales tax liability, the Court’s recognition of software as a commercially valuable asset supports the software escrow arrangements. The source code is deposited in escrow constitutes a protectable software asset under Section 2(o) and Section 14 of the Copyright Act,1957, which are classified as computer programs as literary works and grant rights to copyright owners.

Software Escrow and Contractual Enforceability

Software escrow agreements derive validity from the general principles of the contract law under the Section 10 of the Indian Contract Act, 1872. The significance for a  contractual certainty was emphasised in ONGC Ltd. v. Saw Pipes Ltd., (2003) 5, where the Supreme Court held that the enforcement of contractual obligations and liquidated damages where parties had mutually decided the consequences of non-performance.

Relevant Case Laws

Tata Consultancy Services v. State of Andhra Pradesh, (2005) 1 SCC 308:  The Supreme Court recognised the computer software as having commercial and proprietary value and held that software can be constituted as "goods" for legal purposes, the judgment reinforces the legal significance of the software assets and explains why access to source code can be crucial to the maintaining of business operations.

ONGC Ltd. v. Saw Pipes Ltd., (2003) 5 SCC 705:  The Supreme Court held that the enforceability of contractual obligations and liquidated damages clauses where they represent a genuine pre-estimation of loss. The case is relevant because software escrow agreements heavily rely on carefully drafted trigger events, obligations, and enforcement provisions aimed to prevent operational disruptions.

Practical Implications

The dependence of organisations on proprietary software has made software continuity a critical business concern. For sectors operating in business like banking, healthcare, telecommunications, e-commerce, and financial services, the failure of a software vendor can result in service disruptions, operational losses, regulatory non-compliance, and reputational harm. The advantage of software escrow agreements is that the organisations will have access to the source code and supporting documentation to ensure that the software is maintained if the vendor goes bankrupt or out of business or if the vendor fails to provide maintenance of obligations.

For software vendors, escrow arrangements can serve as a competitive advantage and also as a confidence-building mechanism. From a legal point of view, software escrow assists organisations in business continuity and in operational requirements. 

For legal departments and contact managers, software escrow carefully drafts for licensing and escrow agreements. But proper attention must be given to release triggers, verifications, confidentiality of obligations, and also related provisions of insolvency.

Ultimately, software escrow has evolved from a contractual safeguard to a master strategic business continuity tool.

Conclusion

The software escrow process is another valuable business continuity mechanism that allows businesses to have access to vital software assets in the event that a vendor becomes insolvent, ceases doing business or is unable to provide support services as agreed. It resolves a trust conflict between the software developer and the customer's right to access business-critical software without interruptions or disruptions.

It is based on the provisions of Section 2(0) and 14 of the Copyright Act, 1957 for protection of computer programs as literary works, Section 10, 37, 73 and 74 of the Indian Contract Act, 1872 for contractual obligations and remedies and Section of Insolvency and Bankruptcy Code, 2016 for risk arising out of insolvency of vendors.

Although software escrow will not eliminate every continuity risk, it is one of the most powerful contractual solutions that will help minimise the dependency on the vendor and safeguard the organisation's activities in the event of an unforeseen interruption.

Author: Aprajita Yadav in case of any queries please contact/write back to us via email to content@khuranaandkhurana.com or at  Khurana & Khurana, Advocates and IP Attorney