Arbitration of Cloud and SaaS Service Agreements

1. Introduction

Cloud-computing and Software-as-a-Service (SaaS) agreements have become central to modern commercial relationships. Instead of purchasing and installing software locally, the customer obtains continuing access to software, infrastructure, storage, platforms, applications, databases, analytics and related services through the internet.

A SaaS/cloud agreement commonly involves:

• subscription and recurring fees;
• service-level agreements (SLAs);
• uptime and availability commitments;
• data hosting and migration;
• cybersecurity obligations;
• data protection and privacy;
• intellectual-property rights;
• software updates and upgrades;
• technical support;
• service suspension;
• termination and exit assistance;
• data portability;
• business continuity and disaster recovery;
• limitation of liability; and
• an arbitration clause.

Disputes can therefore be technically complex and legally multi-layered. A dispute may simultaneously concern contract law, technology, data protection, intellectual property, cybersecurity, confidentiality and damages.

Arbitration is particularly suitable because parties can appoint arbitrators with technological expertise, maintain confidentiality, conduct proceedings remotely and select a neutral seat.

2. Nature of Cloud and SaaS Agreements

A cloud/SaaS arrangement normally differs from a traditional software licence.

Traditional software licence

The customer ordinarily receives a copy of software and installs it on its own infrastructure.

SaaS

The customer generally receives a contractual right to access functionality operated by the provider. The software, infrastructure and often the underlying databases remain controlled by the provider.

For example:

Customer subscribes to an enterprise accounting platform for five years. The provider promises 99.9% uptime, data security, technical support and daily backups. The customer pays an annual subscription. A dispute later arises because the platform suffers repeated outages and the customer loses business data.

The arbitration may have to determine:

1. whether the SLA was breached;
2. whether downtime was contractually excused;
3. whether the provider's cybersecurity measures were adequate;
4. whether consequential losses are recoverable;
5. whether contractual liability caps apply;
6. whether the customer's own conduct contributed to the loss; and
7. whether termination was lawful.

3. Why Arbitration Is Important in Cloud and SaaS Disputes

Arbitration offers several advantages.

A. Technical expertise

A cloud dispute may require understanding of:

• cloud architecture;
• APIs;
• databases;
• encryption;
• cybersecurity;
• uptime calculations;
• backup architecture;
• disaster recovery;
• latency;
• data migration;
• source-code functionality; and
• service monitoring.

The parties can appoint arbitrators with appropriate technological or commercial expertise.

B. Confidentiality

Cloud disputes may involve:

• source code;
• security architecture;
• customer databases;
• trade secrets;
• vulnerability reports;
• business information; and
• confidential algorithms.

Confidential arbitration can therefore be commercially attractive.

C. International enforcement

Cloud providers and customers frequently operate in different jurisdictions. Arbitration allows the parties to select a neutral seat and potentially benefit from the New York Convention framework for enforcement.

D. Procedural flexibility

Arbitration can accommodate:

• electronic evidence;
• expert reports;
• remote hearings;
• technical demonstrations;
• forensic evidence;
• document-production protocols; and
• expedited proceedings.

4. Formation of the Arbitration Agreement

This is often the first major problem in SaaS disputes.

Cloud contracts may be formed through:

• master service agreements;
• order forms;
• online terms;
• clickwrap agreements;
• browsewrap terms;
• incorporation by reference;
• electronic acceptance;
• procurement portals; or
• successive versions of online terms.

The tribunal or court must determine whether a valid arbitration agreement actually exists.

Under Indian law, Section 7 of the Arbitration and Conciliation Act, 1996 requires an arbitration agreement and permits recognition of agreements in electronic or other legally acceptable forms.

5. Case Law on Electronic and Technology-Related Arbitration Agreements

Case 1 — Trimex International FZE Ltd. v. Vedanta Aluminium Ltd.

(2010) 3 SCC 1

The Supreme Court recognised that an arbitration agreement can be established through exchange of communications, including electronic communications, where the intention to arbitrate can sufficiently be established.

Relevance to SaaS

Cloud agreements are frequently negotiated through:

• emails;
• electronic order forms;
• purchase orders;
• online acceptance;
• master agreements; and
• digital correspondence.

Therefore, the absence of a traditional wet-ink document does not necessarily prevent arbitration.

Principle

The essential question is whether the communications demonstrate a sufficiently clear consensus to arbitrate.

This is particularly important where:

Master Agreement → online Order Form → SLA → Data Processing Agreement → incorporated SaaS Terms

are spread across several documents.

6. Shakti Bhog Foods Ltd. v. Kola Shipping Ltd.

(2015) 9 SCC 166

The Supreme Court considered whether an arbitration agreement could be inferred from correspondence and contractual documents.

The Court emphasised that an arbitration agreement must demonstrate the parties' intention to submit disputes to arbitration.

SaaS significance

A cloud provider may argue:

"The arbitration clause was contained in the online Terms of Service."

The customer may respond:

"The signed Master Services Agreement does not contain that clause."

The tribunal/court must then determine whether the online terms were properly incorporated.

This makes contract hierarchy clauses extremely important.

7. Govind Rubber Ltd. v. Louis Dreyfus Commodities Asia Pvt. Ltd.

(2015) 13 SCC 477

The Supreme Court examined whether arbitration could be established through contractual correspondence.

The decision is important for demonstrating that courts look at the substance of communications and contractual intention, rather than merely insisting upon a particular physical form.

Application to SaaS

A SaaS relationship may evolve through:

1. initial proposal;
2. master agreement;
3. online registration;
4. purchase order;
5. renewal;
6. updated terms; and
7. subsequent emails.

The arbitration clause must be examined within that entire contractual framework.

8. M.R. Engineers & Contractors Pvt. Ltd. v. Som Datt Builders Ltd.

(2009) 7 SCC 696

The Supreme Court considered incorporation of arbitration clauses by reference.

The Court distinguished between:

• general incorporation of another document; and
• specific incorporation of an arbitration clause.

Importance for cloud agreements

Cloud contracts frequently contain language such as:

"Customer agrees to the Provider's standard terms."

or:

"This Agreement incorporates the Provider's online Service Terms."

Merely incorporating another document may not always be sufficient to incorporate its arbitration clause.

The contractual language must be sufficiently clear.

Practical lesson

A SaaS agreement should expressly state:

"The arbitration clause contained in the Cloud Services Terms is expressly incorporated into and forms part of this Agreement."

This greatly reduces jurisdictional disputes.

9. Arena Mobile Pvt. Ltd. v. Microsoft Corporation (India) Pvt. Ltd.

Delhi High Court, 9 August 2017

This is particularly relevant to technology-sector contracting.

The dispute concerned a Microsoft Priority Reseller Agreement containing an arbitration clause providing that disputes arising out of or in connection with the agreement would be referred to arbitration in India. The Delhi High Court dealt with the appointment of an arbitrator under Section 11 of the Arbitration and Conciliation Act.

Significance

The case demonstrates that technology-company commercial agreements can contain enforceable arbitration mechanisms and that disputes concerning technology distribution relationships can appropriately be brought within arbitration.

SaaS analogy

The same principle is relevant to:

• cloud reseller agreements;
• SaaS distribution agreements;
• Microsoft/AWS/Google-type enterprise relationships;
• software implementation contracts; and
• technology-partner agreements.

10. Ya Mon Expeditions, LLC v. YATCO, LLC

Eleventh Circuit, 2026

This recent case is particularly interesting because it involved a SaaS agreement.

YATCO operated an online platform and sought to compel arbitration under its SaaS agreement. The agreement provided for binding arbitration for claims arising from the agreement, the parties' relationship and use of the services. The dispute also involved non-signatories and arguments based on agency and equitable estoppel.

Importance

The case illustrates one of the most important issues in cloud arbitration:

Who is actually bound by the SaaS arbitration clause?

Potential parties may include:

• the subscribing company;
• parent companies;
• subsidiaries;
• employees;
• contractors;
• brokers;
• implementation partners;
• resellers; and
• platform users.

The case therefore demonstrates why SaaS agreements should carefully define:

• "Customer";
• "Affiliate";
• "User";
• "Provider";
• "Authorized User"; and
• third-party beneficiaries.

11. Tejon v. Zeus Networks, LLC

Eleventh Circuit, 2026

This case concerned an online streaming platform and the enforceability of an arbitration clause contained in online Terms of Service. The court examined the circumstances under which a user could be considered to have assented to terms that contained an arbitration provision.

SaaS relevance

This issue is directly applicable to consumer and enterprise SaaS platforms.

There is a major difference between:

Clickwrap

The user must affirmatively click:

"I agree to the Terms."

and:

Browsewrap

The website merely states:

"By using this website, you agree to our Terms."

The second arrangement creates substantially greater evidentiary problems.

Drafting lesson

For SaaS providers, the safest approach is:

1. display the relevant terms;
2. provide an accessible hyperlink;
3. require affirmative acceptance;
4. preserve acceptance records;
5. identify the version of the terms;
6. retain timestamp and account information; and
7. preserve the arbitration clause applicable at acceptance.

12. Coinbase, Inc. v. Suski

602 U.S. 143 (2024)

The U.S. Supreme Court addressed competing contractual provisions concerning arbitration and forum selection.

Importance to SaaS

Cloud customers often accept multiple contractual documents over time:

• Master Services Agreement;
• SaaS Terms;
• Order Form;
• Data Processing Agreement;
• Privacy Policy;
• acceptable-use policy;
• renewal terms.

These documents may contain inconsistent dispute-resolution provisions.

For example:

MSA → ICC arbitration

but:

later online Terms → court litigation.

The question becomes:

Which agreement controls?

Coinbase v. Suski demonstrates the importance of determining which contractual document governs and whether the parties agreed to delegate arbitrability.

13. Scope of the Arbitration Clause

A cloud arbitration clause should ideally cover disputes:

"arising out of or relating to this Agreement, the Services, the Platform, Customer Data, Service Levels, security, privacy, subscription fees, suspension, termination, intellectual property, implementation, support and any use of the Services."

This is preferable to a narrow clause covering only:

"disputes arising under this Agreement."

Why?

Because SaaS disputes frequently involve claims described as:

• negligence;
• cybersecurity breach;
• confidentiality breach;
• data misuse;
• IP infringement;
• statutory violations;
• misrepresentation; or
• unjust enrichment.

A broad arbitration clause reduces arguments that a particular claim falls outside arbitration.

14. Kompetenz-Kompetenz

The doctrine of kompetenz-kompetenz allows an arbitral tribunal to determine questions concerning its own jurisdiction.

Under Indian law, Section 16 of the Arbitration and Conciliation Act, 1996 embodies this principle.

A cloud provider may argue:

"The customer agreed to arbitrate."

The customer may respond:

"I never accepted those online terms."

The tribunal may need to determine:

1. whether the contract exists;
2. whether the arbitration clause exists;
3. whether it was incorporated;
4. whether the clause covers the dispute; and
5. whether the particular party is bound.

15. Delegation of Arbitrability

Some SaaS agreements expressly provide that the arbitrator shall determine:

• scope;
• interpretation;
• validity;
• enforceability;
• arbitrability; and
• formation disputes.

This is particularly common in online platform agreements.

However, the drafting must be clear because courts may retain authority over fundamental questions such as whether any arbitration agreement was formed at all.

16. Service-Level Agreement Disputes

SLA disputes are among the most common cloud arbitration claims.

An SLA may promise:

• 99.9% availability;
• response times;
• resolution times;
• backup frequency;
• recovery time objective (RTO);
• recovery point objective (RPO);
• cybersecurity standards;
• maintenance windows;
• support availability.

Suppose the contract promises:

99.9% monthly uptime.

The provider experiences four hours of downtime.

The tribunal must determine:

• what counts as downtime;
• whether scheduled maintenance is excluded;
• whether force majeure applies;
• whether network failures are excluded;
• whether customer-caused downtime is excluded;
• how uptime is calculated; and
• what remedy is available.

17. Service Credits versus Damages

A SaaS agreement may provide:

"Customer's sole remedy for downtime is service credits."

This creates an important arbitration issue.

The customer may claim:

₹50 crore in business losses.

The provider may argue:

"The contract limits the remedy to service credits."

The tribunal must interpret:

• exclusive-remedy clauses;
• limitation-of-liability provisions;
• exclusion of consequential damages; and
• service-credit provisions.

The interaction between these provisions should be expressly addressed in the contract.

18. Data Loss Disputes

Cloud arbitration frequently involves allegations of:

• deletion of customer data;
• corrupted databases;
• failed backups;
• ransomware;
• unauthorized access;
• migration failures;
• accidental deletion;
• inadequate disaster recovery.

A tribunal may have to determine:

Provider's obligations

Was the provider required to:

• maintain backups?
• encrypt data?
• maintain redundancy?
• notify the customer?
• preserve logs?
• restore data within a specified period?

Customer's obligations

Did the customer:

• maintain its own backups?
• properly configure access controls?
• use the platform according to the acceptable-use policy?
• protect administrator credentials?

19. Cybersecurity Disputes

A cybersecurity incident may give rise to multiple claims.

For example:

Hacker obtains access to a SaaS database containing customer information.

The customer may claim:

• contractual breach;
• negligence;
• confidentiality breach;
• failure to comply with security standards;
• failure to notify;
• indemnification;
• regulatory losses.

The provider may argue:

• sophisticated third-party attack;
• force majeure;
• customer credential compromise;
• contractual limitation of liability;
• compliance with industry standards.

Arbitration is useful because expert evidence can address the technical cause of the breach.

20. Data Protection and Privacy

Cloud agreements frequently contain a separate Data Processing Agreement (DPA).

The arbitration tribunal may have to interpret:

• controller/processor responsibilities;
• data breach obligations;
• subprocessor provisions;
• cross-border transfers;
• data retention;
• deletion obligations;
• audit rights.

The arbitration clause should therefore expressly state whether disputes under the DPA are included.

21. Intellectual Property Disputes

SaaS relationships may involve:

• source code;
• APIs;
• trademarks;
• databases;
• algorithms;
• software modifications;
• custom integrations;
• customer-generated content.

A dispute may arise when a customer claims:

"The provider used our proprietary data to train another system."

Or:

"The provider's software infringes our intellectual-property rights."

The arbitration agreement should specify the extent to which IP disputes are arbitrable under the applicable law.

22. Software Updates and Modification Disputes

SaaS providers frequently reserve the right to:

• update;
• modify;
• replace;
• discontinue;
• improve; or
• materially alter

their services.

A dispute arises when an update removes an important functionality.

The customer may argue:

"The provider materially breached the contract."

The provider may respond:

"The agreement permits modifications."

The tribunal must interpret the contractual change-management provisions.

23. Service Suspension and Termination

Cloud providers may suspend accounts because of:

• non-payment;
• security threats;
• prohibited usage;
• regulatory requirements;
• suspected fraud;
• breach of acceptable-use policies.

A dispute may arise over whether suspension was justified.

The tribunal should examine:

1. contractual suspension rights;
2. notice requirements;
3. cure periods;
4. emergency suspension provisions;
5. data-access rights;
6. termination rights; and
7. post-termination assistance.

24. Exit and Data-Portability Disputes

Termination does not necessarily end the provider's obligations.

The customer may require:

• data export;
• migration assistance;
• database conversion;
• API access;
• deletion certificates;
• continued access for a transition period.

An arbitration clause should cover disputes occurring after termination, because otherwise the provider may argue that the arbitration clause no longer applies.

A useful clause should expressly cover:

"disputes arising during or after termination, including data return, migration, deletion, transition services and post-termination obligations."

25. Limitation of Liability

This is one of the most important contractual issues.

A SaaS agreement may say:

"Provider's aggregate liability shall not exceed fees paid during the preceding 12 months."

But exceptions may apply to:

• fraud;
• wilful misconduct;
• confidentiality;
• IP infringement;
• data protection;
• cybersecurity;
• indemnification.

The tribunal must determine whether the particular claim falls within an exception.

26. Consequential Damages

Customers often claim:

• lost profits;
• lost business;
• reputational damage;
• loss of customers;
• business interruption.

Providers frequently exclude such losses.

A tribunal therefore needs to distinguish:

Direct damages

Loss directly caused by the breach.

Consequential damages

Secondary or indirect commercial losses.

This distinction can dramatically affect the amount of an award.

27. Evidence in Cloud Arbitration

Cloud disputes generate enormous quantities of electronic evidence.

Relevant evidence may include:

• server logs;
• access logs;
• API logs;
• security alerts;
• database records;
• source-code repositories;
• incident-response reports;
• emails;
• Slack/Teams messages;
• system monitoring reports;
• uptime dashboards;
• audit trails;
• cloud configuration records.

The tribunal may need to determine:

Who created the record, when was it created, whether it was altered, and whether the record accurately reflects the underlying event?

28. Expert Evidence

Expert evidence is often essential.

A tribunal may appoint or hear experts concerning:

• cloud architecture;
• cybersecurity;
• software functionality;
• SLA calculations;
• data loss;
• forensic investigation;
• damages;
• software valuation.

The tribunal should preferably establish an early procedural timetable for expert evidence.

29. Confidentiality and Source Code

One of the biggest advantages of arbitration is the ability to protect confidential technical material.

For example, the customer may allege:

"The SaaS platform failed because the provider's algorithm was defective."

The provider may need to disclose source code.

A tribunal can use:

• confidentiality rings;
• restricted document access;
• redaction;
• expert-only inspection;
• secure electronic data rooms.

This is especially important where source code constitutes a trade secret.

30. Interim Measures

Cloud disputes frequently require urgent relief.

Examples include orders preventing:

• deletion of customer data;
• destruction of logs;
• suspension of essential services;
• disclosure of confidential information;
• misuse of source code;
• destruction of evidence.

Under the Indian Arbitration and Conciliation Act, Section 9 permits court-ordered interim measures, while Section 17 gives the arbitral tribunal powers concerning interim measures.

For a business dependent entirely upon a SaaS platform, delay can itself cause catastrophic commercial loss.

31. Choice of Seat

The contract should distinguish between:

• seat of arbitration; and
• venue/place of hearing.

For an Indian enterprise and foreign SaaS provider, parties might choose:

• New Delhi;
• Mumbai;
• Singapore;
• London; or
• another neutral seat.

The seat determines the procedural law and supervisory jurisdiction of courts.

32. Governing Law

A cloud agreement should ideally identify separately:

Contract law

For example:

"This Agreement shall be governed by Indian law."

Arbitration law/seat

For example:

"The seat of arbitration shall be New Delhi."

Institutional rules

For example:

"The arbitration shall be administered under the rules of [chosen institution]."

This avoids unnecessary disputes.

33. Institutional versus Ad Hoc Arbitration

For large international cloud contracts, institutional arbitration may be preferable because it provides:

• established procedural rules;
• institutional administration;
• emergency-arbitrator mechanisms where available;
• appointment mechanisms;
• case-management procedures;
• internationally familiar processes.

For smaller SaaS disputes, parties may prefer ad hoc arbitration because of potentially lower administrative costs.

34. Multi-Contract SaaS Relationships

A major problem arises when several documents contain different dispute clauses.

Example:

The tribunal may have to determine whether all documents form one contractual framework.

This is why SaaS agreements should contain a clear order-of-precedence clause.

For example:

MSA → DPA → Order Form → SLA → Online Terms

or whatever hierarchy the parties actually intend.

35. Non-Signatory Issues

Cloud ecosystems often involve numerous entities:

Provider → Parent Company → Cloud Infrastructure Provider → Subprocessor → Reseller → Customer → Affiliate → End User

A dispute may raise the question:

Can a non-signatory participate in or be bound by the arbitration?

Potential doctrines include:

• agency;
• assignment;
• assumption;
• alter ego;
• third-party beneficiary;
• estoppel; and
• group-of-companies doctrine, where applicable.

The recent Ya Mon Expeditions v. YATCO decision illustrates how SaaS disputes can raise precisely these non-signatory questions.

36. Indian Position on Non-Signatories

The Supreme Court's jurisprudence has evolved considerably concerning non-signatories.

The group-of-companies doctrine was comprehensively considered by the Supreme Court in:

Cox and Kings Ltd. v. SAP India Pvt. Ltd.

2023 INSC 1051

The Supreme Court clarified the doctrinal basis for binding non-signatories and emphasised that mere corporate affiliation is not, by itself, sufficient.

SaaS application

Suppose:

Indian subsidiary signs the SaaS agreement, but the foreign parent company operates the cloud platform.

Whether the parent can be joined to arbitration cannot simply be answered:

"They belong to the same corporate group."

The factual and contractual relationship must be examined.

37. Arbitrability of Statutory and Regulatory Claims

A cloud dispute may overlap with:

• data-protection law;
• competition law;
• consumer law;
• intellectual-property law;
• cybersecurity regulations;
• telecommunications regulation.

The existence of a contractual arbitration clause does not automatically mean every statutory claim is arbitrable.

Indian courts apply the principles governing arbitrability, including those discussed in:

Vidya Drolia v. Durga Trading Corporation

(2021) 2 SCC 1

The Supreme Court identified the framework for determining which disputes can properly be submitted to arbitration.

38. Competition Law Issues

Suppose a dominant cloud provider requires customers to purchase additional services as a condition of access.

The customer alleges:

"This is an abuse of dominant position."

The dispute may involve both:

• contractual arbitration; and
• competition-law jurisdiction.

The tribunal must carefully determine which issues are contractually arbitrable and whether any statutory forum has exclusive jurisdiction.

39. Cybersecurity Indemnification

A sophisticated cloud agreement should specify whether the provider indemnifies the customer for:

• third-party claims;
• regulatory penalties;
• data-breach costs;
• forensic expenses;
• notification costs;
• credit-monitoring expenses;
• restoration costs.

The arbitration tribunal may have to distinguish between:

contractual indemnity

and

ordinary contractual damages.

This distinction can affect both the liability cap and recoverability.

40. Damages in Cloud Arbitration

Damages may be calculated using:

A. Cost of replacement service

What would it cost to migrate to another provider?

B. Cost of restoration

What did it cost to recover lost data?

C. Lost profits

What profits were lost because of downtime?

D. Service credits

What credits are contractually owed?

E. Migration expenses

What did the customer spend moving away from the provider?

F. Diminution in value

Did the provider's breach reduce the value of a technology investment?

Technical experts are often necessary to establish causation.

41. Force Majeure

Cloud providers commonly rely on force majeure for:

• internet outages;
• natural disasters;
• cyberattacks;
• geopolitical events;
• infrastructure failures;
• government restrictions.

But the tribunal must examine the actual wording.

A provider may not necessarily escape liability merely by characterising every infrastructure problem as "force majeure."

The key questions are:

1. Was the event covered?
2. Was it beyond reasonable control?
3. Could it reasonably have been prevented?
4. Did the provider mitigate its effects?
5. Were backup systems available?

42. SLA Measurement Disputes

A technically sophisticated arbitration clause should specify the source of measurement.

For example:

"Availability shall be measured using Provider's monitoring system."

This can create evidentiary problems if the provider's monitoring system is itself disputed.

A better arrangement may require:

• independent monitoring;
• mutually agreed monitoring tools;
• audit access;
• preservation of logs.

43. AI and Automated Cloud Services

Modern SaaS platforms increasingly use AI.

Disputes may concern:

• inaccurate AI output;
• model downtime;
• hallucinations;
• training-data misuse;
• algorithmic errors;
• intellectual property;
• confidential information entering training datasets.

An arbitration clause should therefore be broad enough to encompass disputes concerning AI-enabled functionality incorporated into the SaaS platform.

44. Recent Development: Online Acceptance and Delegation

Recent U.S. technology-platform cases demonstrate increasing judicial attention to:

• hyperlink-based terms;
• arbitration clauses;
• delegation provisions;
• formation disputes;
• versioned online agreements.

For example, the 2026 Tejon decision involved online subscription registration where the arbitration clause was contained in linked Terms of Service, illustrating how the precise user-interface design can become legally important.

This is directly relevant to SaaS providers using online onboarding.

45. Recommended Arbitration Clause for Cloud/SaaS Agreements

A well-designed clause should address:

1. broad scope;
2. seat;
3. governing law;
4. institution/rules;
5. number of arbitrators;
6. language;
7. confidentiality;
8. emergency/interim relief;
9. technical experts;
10. electronic evidence;
11. remote hearings;
12. source-code confidentiality;
13. data protection;
14. post-termination disputes;
15. non-signatories; and
16. consolidation/joinder, where appropriate.

46. Model Structure

A commercially robust clause could be structured as follows:

"Any dispute, controversy or claim arising out of or relating to this Agreement, the Services, the Platform, any Order Form, SLA, Data Processing Agreement, Customer Data, security obligations, confidentiality, intellectual property, fees, suspension, termination, migration, data return or any use of the Services, including any question concerning the existence, validity, interpretation, performance, breach or termination of this Agreement, shall be finally resolved by arbitration."

The clause should then separately specify:

• institution;
• rules;
• seat;
• governing law;
• tribunal composition;
• language;
• confidentiality;
• emergency relief; and
• technical evidence procedures.

47. Key Case-Law Principles — Consolidated

48. Major Legal Issues for an Arbitral Tribunal

A cloud/SaaS arbitration will typically proceed through the following questions:

Stage 1 — Jurisdiction

Was there a valid arbitration agreement?

↓

Stage 2 — Parties

Who is bound by it?

↓

Stage 3 — Scope

Does the dispute fall within the clause?

↓

Stage 4 — Applicable law

Which substantive and procedural laws apply?

↓

Stage 5 — Contract interpretation

What did the SaaS provider promise?

↓

Stage 6 — Technical breach

Did the service actually fail to meet the contractual specifications?

↓

Stage 7 — Causation

Did that failure cause the customer's loss?

↓

Stage 8 — Contractual limitations

Are liability caps, exclusions or service-credit provisions applicable?

↓

Stage 9 — Damages

What amount is legally and contractually recoverable?

↓

Stage 10 — Relief

Should the tribunal award damages, specific performance, data restoration, injunctions or other relief?

49. Conclusion

Arbitration of cloud and SaaS agreements is increasingly a specialised form of technology-contract arbitration. The dispute is rarely limited to a simple question of whether a service was delivered. It can involve contract formation, electronic acceptance, SLA performance, cybersecurity, data protection, intellectual property, non-signatories, expert evidence, limitation of liability and sophisticated damages calculations.

The most important legal lesson is that the arbitration clause must be designed with the architecture of the cloud relationship in mind. It should cover not merely the master agreement but also SLAs, order forms, data-processing agreements, online terms, implementation arrangements, renewals, suspension, termination and post-termination data migration.

The Indian authorities such as Trimex, Shakti Bhog Foods, Govind Rubber, M.R. Engineers, Vidya Drolia and Cox & Kings, together with technology-specific decisions such as Arena Mobile v. Microsoft and recent SaaS/platform decisions such as Ya Mon Expeditions v. YATCO, demonstrate that the critical questions are increasingly electronic consent, incorporation, scope, arbitrability and the identification of the parties bound by the arbitration agreement.