Saas Agreement

Customized Agreements

SaaS Agreement

License customer access to one identified hosted software service through coordinated subscription, user, account, usage, fee, SLA, support, data, security, backup, incident, intellectual-property, integration, risk, suspension, transition, retention, and deletion terms across seven substantive schedules.

Also called: software as a service agreement, cloud software subscription contract, b2b saas terms.

What you walk away with

A clean multi-page PDF and DOCX after you finish — not a web-form dump. Preview the document before you pay.

PDF export
DOCX export
E-sign included
No subscription

✓ Jurisdiction first (state → county)✓ State clause pack applied✓ Direct or guided path

Jurisdiction

Automatic renewal, electronic contracting, taxes, privacy, security, incidents, data transfers, consumer or sector rules, export controls, warranties, disclaimers, indemnity, liability, suspension, and deletion duties vary by governing law, parties, users, data, service, locations, and actual operations.

$14.99

One-time

Start this document

Jurisdiction details

See how this document starts in your state

Choose the state where the document will be used. The state page shows the maintained coverage level, local-rule limits, and a builder link with the canonical state code already selected.

Choose the state where this document will be used

Browse the complete jurisdiction directory

When this fits

Use this document when…

A provider selling one business cloud-software subscription to a customer
A SaaS plan with named or concurrent users, usage limits, add-ons, and measured charges
A hosted service with a selected availability commitment and support-response targets
A service processing customer data with actual security, backup, export, retention, and deletion commitments

Before you start

Information you will need

Provider, customer, service, modules, environments, subscription dates, plan, users, administrators, affiliates, quantities, governing jurisdiction, and use address
Access rights, accounts, identity and authentication, permissions, usage limits, acceptable use, restrictions, customer systems, configurations, and dependencies
Base fees, billing period, usage metrics and rates if selected, taxes, discounts, credits, invoices, disputes, automatic renewal if selected, and price changes
Availability formula if selected, maintenance, support hours, severity levels, response targets, exclusions, credit bands, fee base, cap, claim process, and reports
Data categories and processing, personal or sensitive data if selected, security responsibilities, backups, recovery, incidents, subprocessors, locations, export, retention, deletion, DPA relationship, IP, content, integrations, risk, suspension, transition, and signatures

What you receive

One customized SaaS Agreement for one identified cloud service
Schedule A subscription, service, user, access, limit, and dependency record
Schedule B fee, usage, tax, discount, credit, renewal, and price-change record
Schedule C availability, maintenance, support, exclusion, measurement, and SLA-credit record
Schedule D data processing, security, backup, incident, export, retention, and deletion record
Schedule E provider IP, customer materials and content, feedback, integration, confidentiality, and publicity record
Schedule F warranty, disclaimer, indemnity, liability, export, compliance, and third-party-service matrix
Schedule G suspension, renewal, termination, transition, export, retention, deletion, fee, and credit record
PDF and DOCX export with electronic signature capability

Document questions

Questions about this document

What is a SaaS Agreement?

How do I create a SaaS Agreement?

A provider selling one business cloud-software subscription to a customer; A SaaS plan with named or concurrent users, usage limits, add-ons, and measured charges; A hosted service with a selected availability commitment and support-response targets

What should a SaaS Agreement include?

Provider, customer, service, modules, environments, subscription dates, plan, users, administrators, affiliates, quantities, governing jurisdiction, and use address; Access rights, accounts, identity and authentication, permissions, usage limits, acceptable use, restrictions, customer systems, configurations, and dependencies; Base fees, billing period, usage metrics and rates if selected, taxes, discounts, credits, invoices, disputes, automatic renewal if selected, and price changes; Availability formula if selected, maintenance, support hours, severity levels, response targets, exclusions, credit bands, fee base, cap, claim process, and reports; Data categories and processing, personal or sensitive data if selected, security responsibilities, backups, recovery, incidents, subprocessors, locations, export, retention, deletion, DPA relationship, IP, content, integrations, risk, suspension, transition, and signatures

Special situations

The agreement covers one hosted service, not a multi-service master ordering framework.
Availability, support, security, backup, recovery, location, and deletion commitments are limited to selected actual capabilities rather than broad marketing promises.
Personal and sensitive data branches record roles, purposes, controls, subprocessors, locations, and any separate DPA relationship without claiming universal compliance.
Suspension and termination remain coordinated with service credits, fees, exports, transition, retention, backup aging, legal holds, and deletion.

Frequently asked questions

Is this a master SaaS framework?

No. It covers one identified hosted service and subscription rather than multiple future orders or unrelated services.

Can usage-based fees be included?

Yes. The conditional path records metrics, included amounts, units, rates, tiers, caps, alerts, measurement sources, corrections, and disputes.

Does it promise uninterrupted service?

No. Any selected SLA uses defined components, measurements, exclusions, maintenance, support targets, and credit remedies.

Does it guarantee perfect security or backups?

No. It records supported controls, shared responsibilities, actual backup and restore capabilities, incidents, locations, and evidence.

What happens to customer data at exit?

Schedule G coordinates export, transition, active retention, backup aging, legal holds, deletion triggers, exceptions, evidence, and completion.