Software License Agreement in Sweden: 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 Sweden the licence rests on copyright law, because software is protected as a literary work, and it is shaped by general contract law and, where the software is supplied for a fee, by rules on payment and defects. This page explains the Swedish legal position, the clauses that matter most, 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 Sweden? Three layers: - Copyright. The Swedish Copyright Act (Lag (1960:729) om upphovsrätt till litterära och konstnärliga verk) protects computer programs as literary works. The licence is permission to use something the licensor owns under copyright; it does not transfer the copyright unless the contract expressly assigns it. Swedish copyright law is read in line with the EU Software Directive.

• Contract law. The Contracts Act (Avtalslagen, SFS 1915:218) governs formation and validity, and section 36 lets a court adjust an unreasonable term.
• Supply and payment rules. For paid software there are rules on defects and remedies (by analogy to the Sale of Goods Act, Köplagen, SFS 1990:931, for deliveries of goods, and general contract principles for pure licences) and, for late payment between businesses, the Interest Act (Räntelag, SFS 1975:635). ## Rights the user keeps whatever the contract says Because Swedish copyright law implements the EU Software Directive, a lawful user of a program keeps certain rights that cannot be fully contracted away: - Back-up copy. A person who has the right to use the program may make a back-up copy necessary for that use.
• Observing and testing. A lawful user may study how the program works to understand the ideas behind it, while using it normally.
• Decompilation for interoperability. In defined, narrow circumstances a user may decompile to achieve interoperability with other programs. This right cannot be excluded by contract. A Swedish software licence can restrict a great deal, but a blanket ban on these specific acts will not stand. Draft around them rather than against them. ## Key clauses, and what to watch in each | Clause | What it should do | Watch for | |---|---|---| | Grant of licence | State scope: use, not ownership; named users or sites; term | A vague grant that both sides read differently | | Permitted and prohibited use | Define environments, copies, modification limits | Trying to exclude the back-up or interoperability rights | | Fees and payment | Price, invoicing, and interest on late payment | Forgetting the statutory default interest baseline | | Intellectual property | Licensor keeps ownership; licensee gets stated rights only | Ambiguity over customer configurations and data | | 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, within reason | Section 36 can adjust a grossly one-sided cap | | Audit | Right to verify licence compliance | Audits with no notice or scope limit | | Term and termination | Duration, renewal, exit and data return | No wind-down or data export on exit | | Governing law | Swedish law and venue | Leaving the forum open | ## Swedish points that change the drafting - Late-payment interest. For commercial payments the Interest Act (Räntelag 1975:635) sets a default interest rate, pegged to the Riksbank reference rate plus a margin, if the parties do not agree otherwise. The underlying EU Late Payment Directive shapes this. Set the rate expressly or the statutory default applies.
• No registration needed. Copyright arises automatically on creation; there is no software copyright registry in Sweden. Ownership and chain of title are proved by records and contracts, so keep assignment and contribution paperwork tidy.
• Open-source components. Swedish law does not change how open-source licences work, but a proprietary licence must be consistent with the terms of any open-source code it contains. Disclose and manage this.
• Unreasonable terms. Section 36 of the Contracts Act allows a court to set aside or adjust a term that is unreasonable, which is most often argued against one-sided liability caps or automatic price increases. ## A short software licence outline you can adapt 1. Parties and definitions.

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

• Leaving the payment-interest position to the statutory default by accident.
• Confusing a licence with an assignment, so it is unclear whether copyright moved.
• Ignoring open-source components inside the licensed software.
• Using a US-style licence unchanged, when Swedish copyright and contract rules differ. ## 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 Swedish software and copyright practice and is not legal advice. Confirm the current statutes and take qualified Swedish advice for a specific agreement.