SaaS Subscription Agreement in United States: Template, Key Clauses and Local Law (2026)

Is a SaaS subscription agreement binding in the United States? Yes. A SaaS subscription agreement is a binding commercial contract in the United States once there is offer, acceptance, consideration, and intent to be bound, and clickwrap or signed order forms are routinely enforced. There is no single federal SaaS statute. The agreement is a licence or access right to hosted software rather than a sale, so the customer gets a right to use the service for the subscription term and keeps nothing on the last day unless the contract says otherwise. This is general information, not legal advice. For a material SaaS deal, ask a licensed attorney in the relevant state. ## What US law applies to SaaS Contract terms are governed by the state common law you choose in the governing law clause. Whether Article 2 of the Uniform Commercial Code applies to SaaS is unsettled: because the customer does not take title to a copy, most courts treat hosted software as a service governed by common law rather than a sale of goods, though some analyses still reach for UCC analogies. Electronic acceptance is valid under the federal E-SIGN Act and state UETA. Two areas carry specific rules. On data, there is no single federal privacy law; if the service handles personal information, state comprehensive laws led by California's CCPA and CPRA, plus laws in Virginia, Colorado, Connecticut, Utah, and a growing list of other states, require contract terms with the vendor as a service provider or processor, and sector laws such as HIPAA apply to health data. On billing, automatic renewal is regulated: many states have automatic renewal laws (California's is among the strictest), and the federal Restore Online Shoppers' Confidence Act (ROSCA) governs online negative-option billing. The FTC's broader "Click-to-Cancel" negative option rule was vacated by the Eighth Circuit in July 2025, so it is not in force, but ROSCA and state auto-renewal laws still apply. ## Key clauses in a US SaaS subscription agreement ### Subscription grant and scope

State that the customer gets a non-exclusive, non-transferable right to access the service during the term, and set the usage metric (named users, seats, volume, or tier). Overuse is the most common cause of a surprise bill. ### Term, renewal, and cancellation Set the initial term, how renewal works, the notice needed to stop renewal, and how to cancel. Auto-renewal must be disclosed clearly and be cancellable, consistent with ROSCA and state auto-renewal laws. ### Fees and price increases State the fee, billing cycle, taxes, and whether renewal pricing is capped. An uncapped right to raise price at renewal is a common and avoidable trap. ### Service levels (SLA) Uptime commitments, support response times, and remedies (usually service credits) belong here or in an attached SLA. For business-critical software this matters as much as the grant. ### Data protection, security, and a DPA Cover who owns customer data (the customer should), how the vendor may use it, security measures, breach notice, and a data processing agreement where personal data is involved. Confirm whether the vendor uses customer data to train AI models and get the answer in writing. ### Intellectual property The vendor keeps all IP in the platform; the customer keeps its own data. Address ownership of any configurations or feedback. ### Warranties and disclaimers A limited performance warranty with an "as is" disclaimer beyond it is standard. Seek a real remedy if the service does not perform. ### Limitation of liability A cap tied to recent fees, with indirect and consequential damages excluded, is standard. Check carve-outs for data breach, confidentiality, and IP indemnity. ### Indemnification The vendor usually indemnifies against third-party IP infringement claims; the customer may indemnify for misuse of the service. ### Suspension and termination State the grounds for suspension (non-payment, abuse) and what happens on termination, including a data export window. The right to get your data out is critical. ### Governing law and disputes Choose one state's law and a forum, and decide court versus arbitration. ## A simple US SaaS agreement skeleton 1. Parties, effective date, and order form 2. Definitions 3. Subscription grant and restrictions 4. Customer responsibilities and acceptable use 5. Fees, billing, taxes, and auto-renewal 6. Term, renewal, and termination 7. Service levels and support 8. Customer data, privacy, and DPA 9. Security and breach notification 10. Intellectual property 11. Warranties and disclaimers 12. Limitation of liability 13. Indemnification 14. Suspension 15. Governing law and dispute resolution 16. General terms ## Points worth negotiating Negotiate a cap on renewal price increases and a clear cancellation path so auto-renewal does not lock you in. Pin down data ownership, the export window, and whether customer data trains AI models. Make the SLA remedies meaningful rather than token credits. Check the liability carve-outs, especially for data breach, since that is where SaaS risk concentrates. ## Where a single contract workspace helps SaaS contracts multiply: every order form has its own renewal date, price-increase cap, usage metric, and data term, and missing one auto-renewal can cost a year's fees. That tracking is what an AI contract workspace is built for: each agreement becomes a structured clause tree, positions are marked favourable, neutral, or unfavourable to your company, and renewal and notice dates surface automatically. Adira is one such workspace, keeping drafting, per-clause risk, version history, and renewal tracking together. Adira is India-first today; deeper United States jurisdiction coverage is on its roadmap, so for US-governed SaaS deals treat it as a drafting and tracking aid and confirm state-specific positions, especially on privacy and auto-renewal, with a US attorney. The clauses above stay the same; a workspace just makes them easier to manage.