Ask a lawyer:
What are the typical terms for a software escrow agreement?

mwakili.com

Introduction

A software escrow agreement is a legally binding contract involving three parties: the software developer (licensor), the end user (licensee), and a neutral third-party escrow agent. This agreement ensures that the software’s source code and other relevant assets are securely stored with the escrow agent. The primary purpose of a software escrow agreement is to protect the licensee in case the licensor fails to maintain or support the software, goes out of business, or breaches the terms of the software license agreement.

In Kenya, software escrow agreements are becoming increasingly relevant as businesses rely more on proprietary software solutions. This document will explore the typical terms of a software escrow agreement, the legal framework governing such agreements in Kenya, and relevant case laws that provide context and precedent.

Introduction
Key Terms of a Software Escrow Agreement
1. Deposit of Source Code
2. Verification of Deposited Materials
3. Release Conditions
4. Maintenance and Updates
5. Confidentiality
6. Dispute Resolution
7. Termination
Legal Framework in Kenya
Relevant Case Laws
Conclusion
TLDR

1. Key Terms of a Software Escrow Agreement

1.1 Deposit of Source Code

The core of a software escrow agreement is the deposit of the software’s source code and other relevant materials with the escrow agent. This deposit typically includes:

Source Code: The human-readable version of the software.
Documentation: Technical documentation that explains how the software works and how it can be maintained.
Build Instructions: Instructions on how to compile the source code into executable software.
Third-Party Software: Any third-party software or libraries required to run the software.

The deposit ensures that the licensee has access to the necessary materials to maintain and support the software if the licensor fails to do so.

1.2 Verification of Deposited Materials

Verification is a critical component of a software escrow agreement. It involves the escrow agent or a third-party expert verifying that the deposited materials are complete, accurate, and functional. Verification can include:

Technical Verification: Ensuring that the source code can be compiled into executable software.
Operational Verification: Testing the software to ensure it functions as intended.
Documentation Verification: Reviewing the documentation to ensure it is complete and accurate.

Verification provides assurance to the licensee that the deposited materials are usable in the event of a release condition.

1.3 Release Conditions

Release conditions specify the circumstances under which the escrow agent will release the deposited materials to the licensee. Common release conditions include:

Bankruptcy: If the licensor files for bankruptcy or becomes insolvent.
Breach of Contract: If the licensor breaches the terms of the software license agreement, such as failing to provide support or updates.
Failure to Maintain: If the licensor fails to maintain or support the software as agreed.

The release conditions are designed to protect the licensee’s investment in the software and ensure continuity of operations.

1.4 Maintenance and Updates

The software escrow agreement should specify the licensor’s obligations regarding maintenance and updates of the deposited materials. This can include:

Regular Updates: The licensor must regularly update the deposited materials to reflect the latest version of the software.
Bug Fixes: The licensor must deposit any bug fixes or patches.
Enhancements: The licensor must deposit any enhancements or new features added to the software.

These provisions ensure that the deposited materials remain current and usable.

1.5 Confidentiality

Confidentiality is a crucial aspect of a software escrow agreement. The agreement should include provisions to protect the confidentiality of the deposited materials. This can include:

Non-Disclosure: The escrow agent and any third parties involved in verification must sign non-disclosure agreements.
Access Control: Strict access controls to ensure that only authorized individuals can access the deposited materials.
Data Security: Measures to protect the deposited materials from unauthorized access, theft, or loss.

Confidentiality provisions protect the licensor’s intellectual property and trade secrets.

1.6 Dispute Resolution

Dispute resolution provisions outline the process for resolving any disputes that may arise under the software escrow agreement. This can include:

Arbitration: A provision for binding arbitration to resolve disputes.
Mediation: A provision for mediation before resorting to arbitration or litigation.
Jurisdiction: Specifying the jurisdiction and venue for any legal proceedings.

Dispute resolution provisions provide a clear process for resolving conflicts and can help avoid costly litigation.

1.7 Termination

Termination provisions outline the circumstances under which the software escrow agreement can be terminated. This can include:

Mutual Agreement: The agreement can be terminated by mutual consent of all parties.
Breach: The agreement can be terminated if one party breaches its terms.
Expiration: The agreement can be terminated upon the expiration of the software license agreement.

Termination provisions provide clarity on how the agreement can be ended and the obligations of each party upon termination.

2. Legal Framework in Kenya

In Kenya, software escrow agreements are governed by general contract law principles as outlined in the Law of Contract Act (Cap 23). The key elements of a valid contract under Kenyan law include offer, acceptance, consideration, and the intention to create legal relations.

Relevant Statutes

Law of Contract Act (Cap 23): This Act provides the general principles of contract law in Kenya, including the formation, performance, and enforcement of contracts.
Intellectual Property Act: This Act governs the protection of intellectual property rights in Kenya, including software copyrights.
Data Protection Act: This Act provides for the protection of personal data and may be relevant in the context of software escrow agreements that involve the storage of personal data.

Key Provisions

Offer and Acceptance: The software escrow agreement must involve a clear offer by one party and acceptance by the other.
Consideration: There must be something of value exchanged between the parties, such as the licensee’s payment for the software and the licensor’s provision of the software and support.
Intention to Create Legal Relations: The parties must intend for the agreement to be legally binding.

3. Relevant Case Laws

Case Law 1: Kenya Commercial Bank Ltd v. Specialized Engineering Co. Ltd [1982] KLR 485

Parties: Kenya Commercial Bank Ltd (Plaintiff) and Specialized Engineering Co. Ltd (Defendant)
Outcome: The court held that for a contract to be valid, there must be a clear offer and acceptance, consideration, and the intention to create legal relations.
Relevance: This case underscores the importance of the fundamental elements of a contract, which are also applicable to software escrow agreements.

Case Law 2: National Bank of Kenya Ltd v. Pipeplastic Samkolit (K) Ltd & Another [2001] eKLR

Parties: National Bank of Kenya Ltd (Plaintiff) and Pipeplastic Samkolit (K) Ltd & Another (Defendants)
Outcome: The court emphasized the importance of clear and unambiguous terms in a contract.
Relevance: This case highlights the need for clear and precise terms in a software escrow agreement to avoid disputes and ensure enforceability.

Case Law 3: Kenya Shell Limited v. Kobil Petroleum Limited [2006] eKLR

Parties: Kenya Shell Limited (Plaintiff) and Kobil Petroleum Limited (Defendant)
Outcome: The court held that confidentiality agreements are enforceable and that breach of confidentiality can result in damages.
Relevance: This case is relevant to the confidentiality provisions in a software escrow agreement, emphasizing the importance of protecting the licensor’s intellectual property.

Conclusion

A software escrow agreement is a critical tool for protecting the interests of both the licensor and the licensee in a software licensing arrangement. The typical terms of a software escrow agreement include the deposit of source code, verification of deposited materials, release conditions, maintenance and updates, confidentiality, dispute resolution, and termination. In Kenya, these agreements are governed by general contract law principles and relevant statutes such as the Law of Contract Act and the Intellectual Property Act.

By understanding the key terms and legal framework of software escrow agreements, parties can ensure that their interests are protected and that the software remains accessible and maintainable in the event of unforeseen circumstances.

TLDR

A software escrow agreement in Kenya involves the deposit of software source code and related materials with a neutral third-party escrow agent. Key terms include deposit, verification, release conditions, maintenance, confidentiality, dispute resolution, and termination. These agreements are governed by general contract law principles and relevant statutes such as the Law of Contract Act and the Intellectual Property Act. Relevant case laws emphasize the importance of clear terms, confidentiality, and the fundamental elements of a valid contract.

Sources