SaaS Agreement in Switzerland: Template, Key Clauses and Local Law (2026)

What a SaaS agreement is A Software as a Service (SaaS) agreement lets a customer access software hosted by a provider over the internet, for a subscription fee, instead of installing it. The customer gets a right to use the service for the term, not ownership of the software and not a perpetual licence. In Switzerland there is no single statute written specifically for SaaS. The contract is built on freedom of contract, so the wording of the agreement does most of the work. That makes a clear, complete contract more important, not less. ## The law that governs it Two bodies of law matter most. First, the Swiss Code of Obligations (Obligationenrecht, OR). A SaaS contract is usually treated as an innominate or mixed contract, borrowing features of lease, mandate and contract for work rather than fitting one named type. Because the Code gives few default rules for this kind of deal, the parties should spell out service levels, fees, liability and termination themselves. Second, the revised Federal Act on Data Protection (revFADP, also called nFADP or revDSG), which came into force on 1 September 2023 with its implementing Ordinance. Where the service processes personal data on the customer's behalf, Swiss law requires the processing to be regulated by a contract between the controller and the processor, and sets duties on sub-processors and cross-border transfers. The supervisory authority is the Federal Data Protection and Information Commissioner (FDPIC). ## Key clauses to include ### Grant of access and licence

Describe the service, the permitted users, and that this is a right to access for the term, not a sale or assignment of the software. ### Subscription term, renewal and fees Set the term, auto-renewal, notice to stop renewal, fees, payment timing and price changes. ### Service levels and support Define availability targets, planned maintenance, support response times and any service credits. ### Data protection and security Include a data processing agreement that meets the revised FADP, covering purpose, security measures, sub-processors, cross-border transfers and assistance with data subject requests. Add security commitments such as encryption in transit and at rest and access controls. ### Intellectual property Confirm the provider owns the software and the customer owns its own data. ### Warranties, liability and indemnities Set warranties, disclaimers and a liability cap. Swiss law limits how far liability for gross negligence or intent can be excluded, so draft the cap carefully. ### Data export and exit Say how the customer gets its data back in a usable format on exit, and how long the provider keeps or deletes data after termination. ### Governing law and forum Choose Swiss law and a Swiss court or arbitration seat if that suits both sides. ## Common mistakes - Copying a United States template and leaving a liability waiver that Swiss law will not fully enforce.

• Forgetting a data processing agreement that matches the revised FADP, not only the GDPR.
• Not defining what happens to customer data after the subscription ends.
• Leaving availability and support as vague promises with no measurable target. ## Draft and manage it in one workspace A SaaS contract carries renewal dates, data duties and service credits that someone has to watch for years. Adira is an AI legal workspace where a team can draft an agreement from a structured template, see each clause flagged favourable or unfavourable to its side, edit clauses in plain language and track renewal and compliance dates together. Depth for non-India jurisdictions such as Switzerland is on the roadmap, so confirm local coverage before relying on it. You can see the approach at Adira. This article is general information, not legal advice. Check the current statute text and your data protection duties with a qualified Swiss lawyer before you sign.