Your SaaS company is based in California. Your enterprise customer is headquartered in New York. A dispute arises over a data breach, a missed SLA, or an intellectual property claim. Which state’s laws govern the outcome? Which courts hear the case?
If your contract is silent on these questions, a court will answer them for you — and the answer may not favor your business. Governing law and jurisdiction clauses in technology contracts are among the most practically significant provisions in any agreement, yet they are routinely treated as boilerplate and accepted without careful review.
The choice of governing law affects how courts interpret your limitation of liability, indemnification obligations, and enforceability of arbitration clauses. The choice of jurisdiction determines where litigation happens and, practically speaking, how expensive and disruptive a dispute becomes. For SaaS companies and the enterprise customers they serve, both decisions deserve deliberate attention.
1. Governing Law vs. Jurisdiction: Two Distinct Concepts
These terms are frequently confused but they address different questions.
Governing law (also called “choice of law”) specifies which state’s (or country’s) legal rules apply when interpreting and enforcing the contract. If a dispute arises about whether your limitation of liability clause is enforceable, or whether your indemnification scope is reasonable, the governing law clause determines which body of case law and statutes a court applies.
Jurisdiction (also called “venue” or “forum selection”) specifies which courts have authority to hear disputes under the contract. A contract can specify that Delaware law governs (governing law) while disputes must be litigated in California courts (jurisdiction). The two choices are independent.
Most commercial contracts specify both. Some rely on arbitration clauses that supersede the jurisdiction clause for most disputes, leaving governing law as the operative choice. Understanding both provisions — and how they interact with any arbitration language in the contract — is essential before signing a technology agreement.
2. Which Governing Law Is Most Common in SaaS Contracts
SaaS companies disproportionately choose one of three governing law options: California, Delaware, or New York. Each has specific advantages and limitations.
California is the most common governing law for US-based SaaS companies, primarily because most technology companies are incorporated or headquartered there. California courts have extensive experience with technology contracts, trade secret disputes, and software licensing. However, California has some of the most aggressive consumer protection laws in the country, and its courts have at times limited liability caps and arbitration clauses that would be enforced in other states.
Delaware is favored for corporate governance matters and is the standard incorporation state for venture-backed companies. Delaware’s Court of Chancery has deep expertise in commercial disputes and a highly predictable body of case law. For B2B SaaS contracts between sophisticated commercial parties, Delaware governing law combined with Delaware court jurisdiction creates a predictable, business-friendly dispute resolution environment.
New York is preferred for financial services contracts and large enterprise agreements where sophisticated commercial parties negotiate at arm’s length. New York courts apply the plain language of commercial contracts with limited paternalistic intervention and have extensive experience with complex technology and financial services disputes.
For SaaS agreements specifically, the governing law choice affects more than just which courts apply — it determines how courts interpret ambiguous contract language, whether certain clauses are enforceable as written, and what implied duties the parties owe each other.
3. Why the Governing Law Choice Affects Contract Enforceability
Governing law is not merely a procedural preference. It determines the substantive rules that courts apply when evaluating your contract’s most important provisions.
Limitation of liability clauses are enforced differently across states. Delaware and New York generally enforce negotiated limitation of liability clauses between sophisticated commercial parties without significant intervention. California courts have a longer history of scrutinizing limitation clauses and, in some consumer-facing contexts, limiting their enforceability.
Indemnification provisions are also state-law specific. Anti-indemnity statutes exist in several states and can affect the enforceability of broad indemnification clauses in certain industries. For pure B2B SaaS contracts, these statutes rarely apply, but the specific governing law determines the case law that defines what indemnification language means and how broadly it extends.
Arbitration clauses are governed by the Federal Arbitration Act at the federal level, but state law affects the enforceability of specific arbitration terms — particularly class action waivers and limitations on arbitral discovery. California has historically been more willing to invalidate specific arbitration provisions than Delaware or New York.
Implied duties vary by jurisdiction. Every state imposes some version of the implied covenant of good faith and fair dealing on commercial contracts. The scope of that duty — and how courts apply it to SaaS performance obligations — differs meaningfully between California, New York, and Delaware.
A technology lawyer who works on SaaS contracts regularly understands these state-specific differences and can advise on which governing law choice creates the most favorable and predictable legal environment for your specific contract terms.
4. US Courts vs. Arbitration: The Forum Choice
Many commercial SaaS contracts combine a governing law clause with a mandatory arbitration provision rather than specifying court jurisdiction. Arbitration affects the litigation landscape significantly.
Advantages of arbitration for SaaS vendors: Disputes are resolved by an arbitrator with relevant technical and commercial expertise rather than a generalist judge or lay jury. Arbitration proceedings are private — financial terms and technical details do not become part of the public record. Class action waivers, which prevent customers from combining individual claims into collective actions, are more reliably enforced in arbitration than in court. Discovery is typically more limited, reducing the cost and disruption of disputes.
Advantages of court litigation for enterprise customers: Court processes allow broader discovery, which benefits the party asserting a claim. Judicial decisions create precedent that influences future dispute outcomes. Courts provide appeal rights; many arbitration clauses limit or eliminate the right to appeal an adverse award. Court judgments are easier to enforce internationally than arbitral awards in some jurisdictions.
For B2B contracts between sophisticated commercial parties where both sides have legal representation, arbitration is generally a balanced mechanism. The American Arbitration Association (AAA) Commercial Arbitration Rules and the JAMS Comprehensive Arbitration Rules are the most commonly used procedural frameworks.
If your contract includes arbitration, the governing law clause still determines the substantive rules applied in arbitration. The combination of Delaware or New York governing law with AAA arbitration seated in a specified city is a standard, commercially reasonable dispute resolution framework for enterprise SaaS contracts.
5. International Considerations for SaaS Companies
SaaS companies that sell to customers in the European Union, United Kingdom, or Canada face additional complexity. A governing law clause specifying California or New York law does not automatically override mandatory legal requirements imposed by the customer’s home jurisdiction.
The GDPR imposes requirements on data processing agreements that apply regardless of what the contract specifies as governing law. A data subject’s rights under GDPR are not waivable by contract. An EU-based customer cannot agree to a SaaS contract provision that conflicts with their legal obligations under GDPR, regardless of which US state’s law governs the agreement.
Similarly, UK post-Brexit data transfer requirements, Canadian PIPEDA and provincial privacy laws, and Australia’s Privacy Act create mandatory obligations that operate alongside whatever governing law the parties choose. The governing law clause does not displace these requirements — it governs contract interpretation for the issues those laws do not specifically address.
For cross-border SaaS relationships, the governing law clause should be drafted alongside a data processing agreement that specifically addresses the applicable privacy law requirements. For additional context on how data processing obligations interact with your main SaaS contract, our analysis of data processing agreements for SaaS companies covers these requirements in detail.
6. What Happens When There Is No Governing Law Clause
When a contract does not specify governing law, courts apply conflict-of-laws rules to determine which state’s law governs. These rules vary by jurisdiction and can produce outcomes neither party anticipated.
Most courts apply one of two approaches. The “most significant relationship” test (used by the majority of US states) applies the law of the state with the most substantial connections to the contract and the parties. The “governmental interest” analysis (used in California and a minority of states) applies the law of the state with the greatest interest in having its laws apply.
For a SaaS contract where the vendor is in California and the customer is in Texas, a dispute in California state court would likely apply California law, while the same dispute in Texas state court might apply Texas law. The applicable law can determine the outcome of a limitation of liability dispute or an enforceability question about an arbitration clause — meaning the same contract can produce different results depending on where suit is filed first.
Including a governing law clause eliminates this uncertainty. It is one of the lowest-cost provisions in any SaaS contract to include and one of the highest-cost to omit.
7. Negotiating Governing Law as a SaaS Vendor
If your SaaS company has standard terms and conditions that apply to all customers, your governing law clause should specify your preferred jurisdiction — typically the state where your company is incorporated or headquartered — and require that disputes be resolved in courts or arbitration forums in that location.
Enterprise customers will frequently push back, requesting their home state’s governing law and court system. The negotiation typically comes down to bargaining power and deal size. A startup with a new enterprise customer may accept the customer’s preferred governing law to close the deal. An established SaaS vendor with many enterprise relationships has more leverage to maintain its standard governing law provision.
When accepting a customer’s governing law as part of an enterprise contract negotiation, review how that state’s law treats the specific provisions in your agreement. A governing law change that seems minor in negotiation can have significant implications for your limitation of liability cap, your indemnification scope, and the enforceability of your arbitration clause.
This review is part of the broader enterprise contract analysis described in our Master Service Agreement guide, where governing law typically appears as a standard term that applies to all transactions under the MSA.
Frequently Asked Questions
Can we specify a governing law that neither party is based in?
Yes. Parties to a commercial contract can choose any state’s law as governing law, even if neither party is located there. Delaware is commonly chosen by companies incorporated there regardless of where they operate. Courts generally enforce governing law choices made between sophisticated commercial parties, provided the chosen state has some reasonable relationship to the transaction.
What is the difference between governing law and venue?
Governing law determines which state’s legal rules apply when interpreting the contract. Venue (or forum selection) determines which courts can hear disputes. Both provisions should appear in the contract. An agreement can specify Delaware governing law with disputes resolved in California courts — the two choices are independent.
Does governing law affect my GDPR or CCPA compliance obligations?
No. Mandatory privacy regulations like GDPR and the CCPA apply based on where your users are located and how you process their data — not based on your contract’s governing law clause. A governing law clause that specifies Texas law does not exempt you from GDPR if you process personal data of EU residents.
What happens if a dispute arises and there is no governing law clause?
Courts apply conflict-of-laws rules to determine which state’s law governs. The result depends on which court hears the case, which party files suit first, and which state has the most significant connection to the contract. This creates uncertainty that can favor the party better positioned to choose the litigation forum — typically the party that files suit first.
Is arbitration better than court litigation for SaaS disputes?
For most B2B SaaS disputes, arbitration provides faster resolution, lower costs, and greater confidentiality than court litigation. It is generally preferred by SaaS vendors because it limits class action exposure and allows the parties to select arbitrators with technical expertise. Enterprise customers sometimes prefer court litigation for the broader discovery rights and appeal options it provides. The appropriate choice depends on the specific contract and the nature of the disputes most likely to arise.
Governing Law Is Not Boilerplate
Governing law and jurisdiction clauses look like standard contract language until a dispute puts them to the test. At that point, the difference between California and Delaware law — or between court litigation and arbitration — can determine whether your limitation of liability holds, whether your indemnification clause applies as you drafted it, and how much the dispute costs to resolve.
If your SaaS agreement’s governing law clause was selected without legal review, or if you routinely accept customer governing law provisions without analyzing the implications, contact Hansen Tong at TOS Lawyer for a review of your contract’s dispute resolution framework by a technology attorney who works with SaaS companies every day.