SaaS agreement – what should the agreement include? 12 questions to regulate
A good SaaS agreement describes more than just the right to use software. It should make it clear what the service includes, what availability and support are promised, how customer data is handled, which security requirements apply, what the parties are responsible for, and how the customer can retrieve their data when the agreement ends.
What is a SaaS agreement?
SaaS stands for Software as a Service. The customer normally gains access to a software service over the internet instead of purchasing a traditional copy of the software. The agreement is therefore a combination of commercial terms, usage rights, operations and support commitments, and rules for data and security.
There is no specific Swedish law that solely dictates exactly what a B2B SaaS agreement should look like. The concrete content of the agreement is therefore central. General contract law applies, and depending on the service, data protection regulations, copyright, cybersecurity rules, and sectoral requirements, among others, may be relevant.
12 questions a SaaS agreement should answer
- What is included in the service? Describe modules, functions, number of users, integrations, storage, implementation, and explicit limitations.
- When is the service considered delivered? If implementation or migration is included, milestones, testing, and acceptance criteria should be specified.
- What service level applies? Specify how availability is measured, what exceptions exist, and what happens in the event of recurring deviations.
- How does the support work? Define contact channels, business hours, priority levels, initial response times, and escalation.
- Who has the right to customer data? Distinguish customer data from the supplier's software, statistics, and other intellectual assets.
- How is personal data processed? Determine roles and link the correct DPA (Data Processing Agreement) when the supplier is a processor.
- What security requirements apply? Make requirements for access, MFA, logging, vulnerability management, backup, and incidents verifiable.
- Can subcontractors be used? Specify how critical subcontractors and any sub-processors are handled and how changes are communicated.
- How may the service be changed? Regulate version changes, discontinued functions, and what applies if a change significantly affects the customer's use.
- How do pricing and price adjustments work? Specify base fees, user-based fees, overusage, indexing, consulting time, and when prices may be changed.
- How is liability allocated? Define faults, remediation, any service credits, types of damages, liability caps, and relevant exclusions.
- What happens when the agreement ends? Determine export, migration support, deletion, deadlines, and costs in advance.
SLA: making the service level measurable
"High availability" is difficult to verify. A useful Service Level Agreement describes what is measured and how. The availability target needs to be combined with definitions for planned maintenance, customer-caused errors, and other exceptions.
| SLA component | Question to regulate |
|---|---|
| Availability | What percentage level applies, during which measurement period, and for which components? |
| Incident class | What distinguishes a critical P1 error from a minor fault? |
| Response time | How quickly should the supplier begin handling the incident? |
| Restoration | Are there goals for restoration and which dependencies affect them? |
| Service credit | Does a deviation result in a price reduction or credit, and is that the customer's only remedy? |
RTO and RPO are often used for restoration and data loss, but the figures should be based on the actual service and the customer's needs. Explore this in more detail in the guide on SLA, availability, RTO, and RPO.
GDPR: when is a data processing agreement needed?
If the SaaS supplier processes personal data on behalf of the customer, Article 28 of the GDPR is central. In that case, the processing must be regulated through an agreement or other binding legal act with the tasks and obligations required by the article.
Start with role distribution. The supplier is not automatically a processor just because personal data appears in the service. Read when a data processing agreement is needed and what it should contain. If sub-processors or third-country transfers are involved, those issues must also be addressed.
Separate the commercial data issue from the data protection role
The agreement should also state what the customer may export and use after the agreement ends. The commercial issue of the right to customer data is not identical to the GDPR issue of data controller responsibility and data processing.
Security: write requirements that can be verified
Adapt the security appendix based on data sensitivity and business criticality. Examples of concrete areas are identity and access management, MFA, encryption, logging, vulnerability and patch management, secure development, backup, incident communication, and continuity.
For organizations covered by the Cybersecurity Act, the supply chain is explicitly one of the areas that security measures must at least address. A supplier agreement can therefore be an important tool for setting requirements and following them up, but the agreement does not replace one's own risk management. Also read the guide on NIS2 and security requirements in supplier agreements.
Plan for exit while the relationship still works
It is often expensive to start discussing data export only when the parties want to part ways. Therefore, regulate the exit at the time of entering into the agreement.
- What export format does the customer receive?
- Are metadata, configuration, and attachments included?
- How long is export possible after termination?
- Can the customer use an API for migration?
- What migration support is included and what does extra work cost?
- When is production data, test data, and copies deleted?
- Can the supplier provide a certificate of deletion?
A good exit clause reduces lock-in and makes it easier to compare suppliers even before the purchase. Explore this area in more detail in SaaS exit and data migration – agreement checklist, which covers export formats, APIs, metadata, migration support, backup, and deletion.
Liability caps: link the level to the real risk
There is no universal percentage that fits all SaaS businesses. A reasonable liability cap depends, among other things, on contract value, data sensitivity, operational dependency, insurance, and potential consequential damages. Also check which events fall outside the cap and whether the limitation of liability interacts with service credits, confidentiality, personal data, and intellectual property.
Section 36 of the Swedish Contracts Act provides the possibility to adjust or disregard unfair contract terms, but this is no substitute for negotiating a well-thought-out risk distribution from the beginning.
Checklist before signing
- Are the scope of the service and all important exclusions documented?
- Can the SLA values be measured with data that both parties can control?
- Are support and incident channels clear?
- Have personal data roles, sub-processors, and international flows been assessed?
- Do the security requirements match the service's risk and any sector requirements of the customer?
- Are price changes and overusage predictable?
- Are the rules for changed functions clear?
- Are liability caps and exclusions consciously chosen?
- Is the customer's data actually exportable in practice?
- Are termination, suspension, and exit coordinated?

Do you need complete agreement documentation?
Mallbutiken's SaaS agreement for B2B includes a main agreement and six appendices for, among other things, service specification, SLA, DPA/GDPR, security, exit, and price. Delivered in editable Word and PDF. Price in the store: 149 SEK.
See the SaaS agreement templateCommon questions
Is a SaaS agreement the same thing as a license agreement?
Not necessarily. A SaaS agreement usually also needs to handle the ongoing service, operations, support, data, security, and exit. The license part is only one component of the relationship.
Must a B2B SaaS agreement be in writing?
There is no general formal requirement for all such agreements, but a written agreement is important to be able to demonstrate the scope of the service and risk distribution. Certain parts may simultaneously be covered by their own requirements, for example, the GDPR's requirement for binding regulation of data processing.
Can the supplier change functions during the contract period?
It depends on the agreement. Therefore, regulate the right to change, how the customer is informed, and what happens if a significant function is removed or changed.
Related guidance
Continue with the SLA guide, SaaS exit and data migration, the DPA/GDPR guide, and NIS2 and supplier security.
Sources and further reading
- Swedish Parliament: Contracts Act (1915:218)
- EUR-Lex: GDPR, especially Articles 28 and 32
- Swedish Parliament: Cybersecurity Act (2025:1506)
This guide provides general information. SaaS agreements need to be adapted to the specific service, the roles of the parties, data, risks, and any sector-specific requirements.
For SaaS and cloud services, the EU Data Act may affect contractual terms on data access, transfer and switching providers. Read our guide to the EU Data Act and cloud-service contracts to see which issues should be reviewed separately from general SaaS terms.
A SaaS agreement often covers both the ongoing service and permission to use software. If the central issue is exclusivity, intellectual property, royalties or sublicensing, compare our guide to licensing agreements and IP terms to see which provisions need separate attention.
Templates in this article
Explore the topic
Business guides – contracts, HR, AI & complianceSLAs in SaaS agreements – availability, response time, RTO, RPO, and service credits
Practical guide to SLAs for SaaS: availability, incident levels, response time, RTO/RPO, service credits, maintenance, and escalation.
Business guides – contracts, HR, AI & complianceData Processing Agreement – when is it needed and what should it include?
Determine whether a supplier is a data processor and what the data processing agreement needs to regulate. Practical examples, appendices, and chec...
Business guides – contracts, HR, AI & complianceNIS2 and supplier agreements – which cybersecurity requirements should be agreed upon?
How NIS2-affected organizations can agree on supplier security: incidents, subcontractors, access, vulnerabilities, continuity, monitoring, and exit.



