SaaS Agreement (Subscription Agreement)

What is a SaaS agreement?

A SaaS agreement, also called a subscription agreement, is the contract you accept when you pay for software that runs in the cloud. You do not buy the software. You pay for the right to use it for a set period, such as a month or a year.

"SaaS agreement" is a general name, not one document. In practice it is a bundle. A typical bundle has these parts:

• A main agreement, called a master service agreement in sales-led deals or terms of service on self-serve plans.
• An order form or online checkout with your price, seats and term.
• A data processing agreement (DPA) for personal data.
• Online policies, such as the acceptable use policy, service level agreement, security measures and product-specific terms.

Atlassian's agreement shows this clearly. It defines "Agreement" as the customer agreement "as well as the Product-Specific Terms, the DPA and the Policies" (section 21). HubSpot defines its Agreement as its general terms "and all materials referred or linked to in here" (HubSpot Customer Terms).

What it looks like in a vendor's terms

A typical clause reads like this:

This Agreement consists of these Terms, each Order Form, the Data Processing Addendum and the Policies linked below. We may modify the Policies from time to time. Fees for each Subscription Term are set out in the Order Form, and subscriptions renew automatically unless either party gives notice.

• "Consists of": your contract is every listed document, not only the one you signed.
• "Policies linked below": some parts live on web pages. This is incorporation by reference.
• "We may modify the Policies": the vendor can change some parts without your signature.
• "Renew automatically": an auto-renewal clause.

A real change we caught

Venpo flagged a change in which Snyk dropped its 5% renewal cap and added an AI training exception. One update touched two different parts of the bundle: what you pay at renewal and what happens to your data.

Why it matters to you

Each part of the bundle can change in a different way. Knowing which parts are fixed and which can move tells you where to look.

• Fixed parts. Your order form and any signed amendments stay as signed unless both sides agree to change them. Salesforce's MSA ranks the order form first in a conflict (section 12.3), and it incorporates the DPA as posted on the effective date (section 2.2).
• Parts that move. Online policies and documentation often apply "as updated." Salesforce defines its Documentation that way (section 1). Atlassian can modify its agreement, policies, product terms and DPA, with commercially reasonable efforts to post changes 30 days ahead (section 20.9).
• Whole-agreement changes. HubSpot says it "may modify any part or all of the Agreement," and gives customers 30 days after notice to object (section 12.1).
• Limits on change. Some vendors promise a floor. Salesforce warrants it will not materially decrease the overall security of the services during a term (section 8.2).

For you, this affects money (renewal price, overages, refunds), data (DPA, AI training, subprocessors) and your promises to your own customers.

What to check

• Make a list of every document in the bundle. Save a dated copy of each one when you sign.
• For each document, note whether it is fixed or can change, and how much notice you get.
• Check the order of precedence clause so you know which document wins in a conflict.
• Write your key commercial terms, such as a renewal cap and seat flexibility, into the order form.
• Note the renewal date and the notice deadline to cancel.
• Check your right to object to changes, and whether you get a refund if you leave because of one.

How Venpo helps

A SaaS agreement is only as stable as its online parts. Venpo monitors each vendor's public terms, DPA, subprocessor list and policies, and emails you a plain-English alert that says what changed and why it matters. The Fine Print Scan answers four questions per vendor: AI training, data retention, sale or ads use, and price increases.