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

A software license agreement in Spain is the contract by which the owner of software (the licensor) grants another party (the licensee) the right to use that software, while keeping ownership of it. The customer does not buy the software; it receives a defined, limited right to use it under conditions the licence sets. This guide explains what a Spanish software licence should contain, the law that protects software, and the user rights that Spanish law makes mandatory. It is general information, not legal advice. Confirm specifics with a Spanish-qualified lawyer. ## What is a software license agreement and when do you need one in Spain? Software is protected by copyright, so using someone else's software without permission is infringement. A licence is the permission. You need a software licence agreement whenever you: - Supply software to customers, whether installed, embedded or on-premises.

• License a tool, library or component to another business.
• Receive software and need clarity on what you may do with it. For cloud software accessed as a subscription, a SaaS agreement is usually the better fit; a classic licence suits software that is installed or delivered to the customer. ## Which law governs software licensing in Spain? Software in Spain is protected and governed mainly by: - The Intellectual Property Law. The consolidated text approved by Royal Legislative Decree 1/1996 (Real Decreto Legislativo 1/1996, the TRLPI) protects computer programs as copyright works. Its software-specific provisions (around Articles 95 to 104) implement the EU Software Directive (Directive 2009/24/EC).
• General contract law. The Civil Code (freedom of contract, Article 1255) and the Commercial Code for the contract itself.
• Data protection. If the software processes personal data, the GDPR and Spain's Organic Law 3/2018 (LOPDGDD) apply, and a data processing agreement may be needed. Because the TRLPI implements an EU directive, the core software rules are similar across the EU, but the Spanish text governs in Spain. ## User rights you cannot exclude in Spain This is the most important local point. The TRLPI gives the lawful user of software certain rights that the licence cannot take away, following the EU Software Directive: - Normal use and error correction. A lawful user may use the program for its intended purpose, including correcting errors, where necessary and unless the contract validly provides otherwise within the law's limits.
• Back-up copy. A person entitled to use the program may make a back-up copy where it is necessary for that use. This right cannot be contractually excluded.
• Decompilation for interoperability. The user may decompile parts of the program, without the rights holder's authorisation, strictly to achieve interoperability with other programs, subject to conditions. Clauses that try to ban this entirely are ineffective to that extent. A Spanish software licence can set many restrictions, but it cannot override these mandatory user rights. Drafting a blanket ban on any copying or any reverse engineering without respecting these exceptions makes those words unenforceable. ## Key clauses in a Spanish software license agreement | Clause | Why it matters in Spain | | --- | --- | | Licence grant | Define scope: users, devices, sites, territory and term. | | Permitted use | What the licensee may do with the software. | | Restrictions | What is prohibited, respecting mandatory user rights. | | Ownership and IP | Licensor keeps all IP; nothing is assigned. | | Delivery and acceptance | How and when the software is provided. | | Fees and taxes | Licence fee, model (perpetual or term) and VAT. | | Maintenance and support | Updates, patches and support, if included. | | Warranties | Performance, non-infringement and disclaimers. | | Liability and caps | Proportionate caps; fraud cannot be excluded. | | Audit | Right to verify licence compliance. | | Data protection | A DPA where personal data is processed. | | Term and termination | Breach, expiry and effect on use rights. | | Governing law and forum | Spanish law, with courts or arbitration. | ## Spain-specific points to get right - Respect the TRLPI mandatory rights. Draft restrictions so they do not purport to remove the back-up copy right or the decompilation-for-interoperability right.
• Moral rights. Under Spanish law the author of software has certain moral rights that stay with the author and are separate from the economic rights you license.
• Perpetual versus term. Be explicit. A perpetual licence still ends the right to use if the contract is terminated for breach.
• VAT. Spanish IVA usually applies to licence fees for software supplied in Spain. State whether prices include VAT.
• Language. Bilingual contracts are common; a sworn translation may be required for a Spanish court. ## A simple software license template outline for Spain 1. Parties and definitions

2. Licence grant and scope
3. Permitted use and restrictions (respecting mandatory rights)
4. Ownership and intellectual property
5. Delivery, installation and acceptance
6. Fees, payment and VAT
7. Maintenance, updates and support
8. Warranties and disclaimers
9. Intellectual property indemnity
10. Liability and caps
11. Audit rights
12. Data protection (if applicable)
13. Term and termination
14. Governing law (Spain) and dispute resolution ## Common mistakes to avoid - Writing a blanket ban on reverse engineering that ignores the interoperability exception.

• Prohibiting any back-up copy, which the TRLPI protects.
• Leaving the licence scope vague, so the number of users or sites is disputed.
• Forgetting the IP indemnity, which customers increasingly expect.
• Ignoring data protection when the software handles personal data. ## One workspace to draft, review and track your software licences A software licence is rarely signed once and forgotten. Scope changes, seats grow, renewals come due, and each new customer deal should match your approved terms. Keeping that consistent across many licensees, by hand, is where errors and missed renewals creep in. An AI contract workspace keeps it together: draft from an approved licence template, flag per-clause risk against how your company contracts, edit clauses in plain language, and track seats, renewals and obligations on a live timeline. Adira is built for this, India-first today with other jurisdictions including Spain and the EU on the roadmap, so confirm Spanish-law specifics with local counsel. The drafting, review and tracking you would otherwise do by hand can live in one workspace tuned to your business. This article is general information and not legal advice.