SaaS Subscription Agreement
A modern cloud-software subscription contract covering access, uptime, data ownership, security, AI features, and the usual commercial and liability terms.
What is a SaaS Subscription Agreement?
A SaaS Subscription Agreement is a modern cloud-software subscription contract covering access, uptime, data ownership, security, AI features, and the usual commercial and liability terms.
Built for SaaS and technology companies selling access to a hosted product, and for buyers signing one, with clean terms on data ownership, service levels, security, and AI feature usage.
SaaS Subscription Agreement template, current for 2026
An explicit customer-data-ownership and no-training clause (provider can't train models on customer data without opt-in), an aggregated/de-identified usage-analytics carve-out written to current standards, an AI-features rider covering output accuracy disclaimers and human-review responsibility, an optional SLA with service credits, a DPA hook, and security-incident notice timing aligned to current breach-notice expectations.
How HDAi does this differently
Unlike a static form, HDAi runs a guided interview and assembles your SaaS Subscription Agreement as you answer. When you want it finished, a licensed Hart David Carson attorney reviews it and tailors it to your facts before you sign. The interview and the first draft are automated. The judgment belongs to an attorney.
What you’ll be asked
- Who is the SaaS provider (the company offering the software)? This is you, the vendor licensing the cloud software. We capture the legal entity name, type, and address for the title block and signature.
- Who is the customer (the subscribing company)? The organization buying the subscription. Their legal entity details drive who is bound by the agreement.
- What is the effective date of this Agreement? The date the contract's terms begin to govern the relationship. Usually the last signature date or a stated go-live date.
- What is the name of the SaaS product or platform? The branded name of the hosted software. Used throughout to identify what the customer is subscribing to.
- Briefly describe what the Service does. A one or two sentence functional description. Frames the scope of the license grant and the order-of-precedence with any Order Form or documentation.
- Which U.S. state's law governs this Agreement? Sets the governing law and the courts for disputes. Delaware and New York are common for commercial SaaS; California is common for tech vendors.
- If you selected Other, name the governing state. We use this only when the standard list doesn't cover your chosen jurisdiction.
- In which county and city will courts or arbitration sit for disputes? Fixes the exclusive venue so neither party can be dragged to an inconvenient forum.
- How should disputes be resolved? Litigation keeps disputes in court; arbitration is private, often faster, and enforceable across borders but limits appeals. This choice drives the entire Dispute Resolution section.
- What is the initial subscription term? How long the initial commitment runs. Drives the term, renewal, and early-termination mechanics.
- Should the subscription auto-renew? Auto-renewal keeps the service continuous unless someone opts out; manual renewal requires an affirmative re-sign. This affects the renewal and notice clauses.
- How many days before term end must a party give non-renewal notice? The opt-out window for auto-renewal. Only relevant if the subscription auto-renews.
- What is the subscription fee? The core recurring charge. Appears in the fees section and anchors the liability cap.
- How often is the fee billed? Sets the invoicing cadence and how the annualized fee is calculated for the liability cap.
- How should usage above the subscribed entitlements (seats, volume, API calls, AI tokens) be handled? Sets the true-up mechanic when the Customer exceeds the entitlements defined on the Order Form. Overage billing charges for the excess at a per-unit rate, a true-up reconciles at the end of a period, and hard limits block usage past the cap.
- How many days does the customer have to pay an invoice? Net payment window from invoice date. Drives the late-payment and suspension provisions.
- What monthly interest rate applies to overdue amounts? Charged on past-due balances. Keep at or below your state's usury ceiling (1.5%/month is standard).
- What is the maximum annual price increase at renewal? Caps how much you can raise the fee each renewal. Protects the customer and is a common negotiation point.
- What monthly uptime commitment will you offer? The availability guarantee (e.g., 99.9% = about 43 minutes of downtime/month). Drives the service-credit remedy.
- What is the remedy if you miss the uptime SLA? Service credits are the market-standard, capped remedy. This makes clear the SLA credit is the customer's sole remedy for downtime.
- What support level is included? Sets response-time expectations and whether support is bundled or extra.
- Where will customer data be hosted? Data-residency commitments matter for privacy compliance and regulated customers. Drives the data-handling and sub-processor terms.
- Which security certifications/frameworks will the provider maintain? Signals the security posture and gives the customer contractual assurance. Referenced in the security covenant and audit provisions.
- Within how many hours must the provider notify the customer of a security breach? The breach-notification clock. 72 hours aligns with GDPR and most state laws; tighter windows are a negotiation point.
- Which privacy laws must the parties comply with? Determines which data-protection obligations and DPA hooks appear. Select all that apply to the customer's data.
- Will a Data Processing Addendum (DPA) be incorporated? A DPA governs processor/controller obligations. Recommended whenever personal data is processed.
- Does the Service include AI or machine-learning features? Turns on the entire AI section, covering model use, training rights, output ownership, and AI-specific disclaimers. Set to No to omit it.
- Describe the AI features and how they work. Frames what the AI does and whether third-party model providers are involved. Feeds the AI transparency and disclaimer clauses.
- Does the Service rely on any third-party AI or model provider? If a third-party model provider (for example, a hosted large language model) processes Customer Data, the AI rider requires the Provider to flow down the no-training and confidentiality commitments and to give notice of a change of model provider.
- May the provider use customer data to train or improve AI models? This is the single most negotiated AI term. Most enterprise customers require No; opt-in aggregated use is a middle ground.
- Who owns AI-generated output? Clarifies IP in AI results. 'Customer owns output' is customer-favorable and market-standard for enterprise SaaS.
- Confirm the customer-data ownership position. The standard SaaS position is that the customer owns its data and the provider gets only a limited license to host and process it. Almost always 'Customer owns.'
- May the provider use anonymized usage/telemetry data for analytics and benchmarking? Lets the provider improve the product and publish aggregate benchmarks without exposing customer data. Common but worth flagging.
- How should the liability cap be measured? Caps total exposure. 12 months of fees is the market standard; a fixed dollar amount is used for smaller deals.
- If a fixed cap, what is the dollar amount? The absolute ceiling on liability. Only used when you chose a fixed cap.
- Should data-breach/security liability have a higher 'super-cap'? Many customers demand that security incidents be excluded from the standard cap or capped at a higher multiple. A common concession.
- If yes, what multiple of fees is the security super-cap? The higher ceiling for security incidents, expressed as a multiple of annual fees (for example, 3x).
- Will the provider indemnify the customer against third-party IP claims? Protects the customer if the Service infringes someone's IP. Standard in enterprise SaaS.
- Will the provider carry and evidence insurance? Cyber and general liability coverage backstops the indemnities. Enterprise customers usually require it.
- If yes, what minimum cyber/tech E&O limit is required? The minimum per-occurrence coverage for cyber and technology errors & omissions.
- For how many days after termination can the customer export its data? The post-termination window to retrieve data before deletion. 30 days is typical.
- May the provider name the customer as a reference or use its logo? Marketing rights. Customers often require prior written approval or opt out entirely.
- Will commercial specifics live on separate Order Forms? Order Forms let you add new subscriptions under one master agreement. Sets the order-of-precedence between the two.
- Who signs for the provider (name)? The individual executing on the provider's behalf. Appears in the signature block.
- What is the provider signatory's title? Confirms the signer has authority to bind the provider.
- Who signs for the customer (name)? The individual executing on the customer's behalf.
- What is the customer signatory's title? Confirms the signer has authority to bind the customer.
Frequently asked
What is a SaaS Subscription Agreement? +
Is HDAi's SaaS Subscription Agreement legally binding? +
Do I need a lawyer to use this SaaS Subscription Agreement? +
What makes this SaaS Subscription Agreement current for 2026? +
How long does the SaaS Subscription Agreement take? +
Does this SaaS Subscription Agreement work in my state? +
Related generators
IP Assignment Agreement · Data Processing Addendum (DPA) · Sales Order Form · Reseller / Referral Agreement · All 124 →