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

A software license agreement is the contract by which a software owner (the licensor) grants a customer (the licensee) the right to use software on stated terms, without transferring ownership of the code. In Switzerland the licence rests on copyright law, because software is protected as a work, and it is shaped by the Code of Obligations for formation, payment and liability. This page explains the Swiss legal position, the clauses that matter, the user rights that survive the contract, and a template outline. It is general information, not legal advice. ## What law governs a software licence in Switzerland? Two main statutes: - Copyright. The Swiss Copyright Act (CopA, in German URG, SR 231.1) protects computer programs as works. The licence grants permission to use a copyright-protected work; it does not transfer the copyright unless the contract expressly assigns it. Copyright arises automatically on creation, and there is no software copyright registry in Switzerland.

• Contract law. The Code of Obligations (CO, SR 220) governs formation, payment and liability. A software licence is an innominate (unnamed) contract: Swiss courts apply general CO principles plus analogies to named types such as lease, sale or mandate depending on the deal (for example, a perpetual on-premise licence looks more like a sale, a time-limited subscription more like a lease). ## Rights the user keeps whatever the contract says The Swiss Copyright Act gives a lawful user of a program certain rights that a licence cannot fully take away: - Use and necessary copies. A person entitled to use the program may make the copies needed for that use.
• Back-up copy. A back-up copy may be made and kept.
• Interoperability. Information needed for interoperability may, in defined conditions, be obtained, including by decompilation, to make the program work with other software. A Swiss licence can impose many limits, but a blanket ban on these specific acts will not stand. Draft around them. ## Key clauses, and what to watch in each | Clause | What it should do | Watch for | |---|---|---| | Grant of licence | State scope: use, not ownership; users, sites, term | A vague grant both sides read differently | | Licence type | Perpetual or subscription, on-premise or hosted | The type affects which CO analogy applies | | Permitted and prohibited use | Define environments and copy limits | Trying to exclude back-up or interoperability rights | | Fees and payment | Price, invoicing, default interest | Forgetting the 5 percent statutory default interest | | Intellectual property | Licensor keeps ownership; licensee gets stated rights | Ambiguity over customer data and configurations | | Warranties | What the software will do, and for how long | Over-promising performance | | Support and maintenance | Whether updates are included or separate | Silence on who fixes defects | | Liability | Caps and exclusions | Art. 100 CO voids exclusions for intent or gross negligence | | Audit | Right to verify licence compliance | Audits with no notice or scope | | Term and exit | Duration, renewal, data return | No wind-down or export on exit | | Governing law | Swiss law and venue | Leaving the forum open | ## Swiss points that change the drafting - Liability line (Art. 100 CO). A clause excluding liability for unlawful intent or gross negligence is void. Cap and exclude for ordinary negligence within reason, but not beyond.
• Default interest (Art. 104 CO). If the contract sets no rate, overdue payments carry statutory default interest of 5 percent per year. Set your own rate expressly if you want a different one.
• Licence type drives the analogy. Because a software licence is unnamed, Swiss courts fill gaps by analogy. A perpetual licence for a fee is often read with sale rules in mind, a subscription with lease rules, and a bundled service with mandate rules. Spell out the terms you want so the court does not have to guess.
• Open-source components. Swiss law does not change how open-source licences operate, but a proprietary licence must be consistent with any open-source code it contains. Disclose and manage it.
• No registration, so keep records. Since copyright is unregistered, prove chain of title through assignment and contribution records. ## A short software licence outline you can adapt 1. Parties and definitions.

2. Grant of licence: scope, users, sites, term, exclusivity.
3. Licence type: perpetual or subscription, on-premise or hosted.
4. Permitted use and restrictions (respecting back-up and interoperability rights).
5. Delivery, acceptance and installation.
6. Fees, invoicing and default interest.
7. Intellectual property ownership and customer data.
8. Warranties and disclaimers.
9. Support, maintenance and updates (or a separate agreement).
10. Liability and limitation (respecting Art. 100 CO).
11. Confidentiality and security.
12. Audit rights.
13. Term, termination, and exit or data return.
14. Governing law (Switzerland) and dispute resolution.
15. Annexes: specification, support levels, fees. ## Common mistakes - Writing a prohibition that tries to override the mandatory back-up or interoperability rights.

• Excluding liability for gross negligence or intent, which Art. 100 CO makes void.
• Leaving default interest to the 5 percent statutory rate by accident.
• Confusing a licence with an assignment, so it is unclear whether copyright moved.
• Ignoring open-source components inside the licensed software. ## Keeping every licence and its obligations in one place A software business signs licences constantly, each with its own user count, renewal date, support level and audit right. The work of drafting from a standard, checking each licence against copyright and payment rules, keeping versions straight and remembering renewals and audits is the work an AI contract workspace can hold in one place: draft from your own template, flag clauses that drift from your standard, keep a live timeline of versions, and surface renewal and audit dates as alerts. If that is useful, Adira is built around that single-workspace idea. Deeper non-India jurisdiction coverage is on its roadmap; India is the deepest today. This article is general information about Swiss software and copyright practice and is not legal advice. Confirm the current statutes and take qualified Swiss advice for a specific agreement.