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

A software license agreement is the contract by which the owner of software (the licensor) grants another party (the licensee) the right to use that software on defined terms, while keeping ownership. It is not a sale. The licensee gets a bundle of permissions, such as to install, run and copy within limits, and everything the licence does not grant stays with the licensor. The contract turns on the scope of that grant, the price model, the warranties, and what happens on termination. In Portugal, software is protected as a special category of copyright work, and the licence sits on top of that protection. The contract is built from the software copyright statute, the general law of obligations in the Civil Code, and, where the software processes personal data or is sold to consumers, data protection and consumer law. This guide sets out the local law that actually bites, the clauses a Portugal software licence should contain, and a section-by-section skeleton you can adapt. It is general information, not legal advice; confirm the detail with qualified Portuguese counsel before you sign. ## Portugal: the local law that shapes your software licence Portugal protects computer programs through a dedicated statute, Decree-Law 252/94, which transposed the EU directive on the legal protection of computer programs (now Directive 2009/24/EC). Rather than amend the general Copyright Code, the legislature gathered the rules for software into this separate law. Three points matter for drafting. First, what is protected. A program with a creative character is protected like a literary work, and its preparatory design material is treated the same way. Protection covers the program's expression in source and object code, but not the ideas, principles, logic, algorithms or programming languages behind it. So a licence protects the code, not the underlying method. Second, commissioned and employee software. Under Decree-Law 252/94, where a program is created on commission or in the course of employment, the recipient (the employer or the client who commissioned it) is presumed to hold the rights, unless the contract says otherwise or the purpose of the contract indicates otherwise. This default has been applied by the Portuguese courts. Because it is only a presumption, say expressly in the contract who owns commissioned code, rather than relying on the default. Third, mandatory user rights. The directive and Decree-Law 252/94 give the lawful user certain rights that a licence cannot remove, including making a back-up copy where necessary, observing and studying the program to understand its ideas, and decompiling it within strict limits to achieve interoperability. A clause that tries to ban these outright will not hold. ## The clauses a Portugal software licence should contain The core clauses are: - Grant and scope. What is licensed, for how many users or machines, in what territory, and whether the licence is exclusive or non-exclusive, perpetual or term, and transferable or not.

• Permitted use and restrictions. What the licensee may and may not do, bearing in mind the mandatory user rights that cannot be excluded.
• Ownership and IP. A clear statement that the licensor keeps all intellectual property, and, for commissioned work, who owns the result (do not rely on the statutory presumption alone).
• Fees. Licence fees, the model (perpetual fee, subscription or usage-based), maintenance and support charges, and taxes (VAT/IVA).
• Delivery, installation and acceptance. How the software is delivered, any acceptance testing, and when the licence takes effect.
• Maintenance, support and updates. What is included, service levels, and whether new versions are covered.
• Warranties and disclaimers. The warranty on the software, and disclaimers framed within what mandatory consumer and good faith rules allow.
• IP infringement indemnity. Protection for the licensee if the software is alleged to infringe a third party's rights.
• Liability. Caps and exclusions, with carve-outs for what cannot be limited.
• Data protection. Where the software processes personal data, a cross-reference to a GDPR Article 28 data processing agreement.
• Term and termination. Duration, termination for cause and insolvency, and the effect on the licence.
• Post-termination. Whether use must stop, copies be deleted, and any data be returned.
• Governing law and disputes. Portuguese law, the competent court or arbitration, and the contract language. ## A software licence agreement skeleton you can adapt Use this running order as a drafting checklist. It is a skeleton, not a finished contract, and it is not legal advice. 1. Parties and definitions

2. Grant of licence: scope, users, territory, exclusivity and term
3. Permitted use and restrictions (respecting mandatory user rights)
4. Ownership and intellectual property (and commissioned code)
5. Fees, payment model and taxes
6. Delivery, installation and acceptance
7. Maintenance, support and updates
8. Warranties and disclaimers
9. IP infringement indemnity
10. Limitation of liability
11. Data protection (cross-reference to a DPA where relevant)
12. Confidentiality
13. Term and termination
14. Consequences of termination (cessation of use, deletion)
15. Governing law, jurisdiction or arbitration, and language
16. Boilerplate (assignment, force majeure, notices, entire agreement) ## Common mistakes to avoid - Relying on the ownership presumption for commissioned code. Decree-Law 252/94 presumes the client holds rights in commissioned software, but it is only a presumption. State ownership expressly so there is no argument later.

• Banning mandatory user rights. A licence cannot remove the lawful user's right to a back-up copy, to study the program, or to decompile within limits for interoperability. A blanket ban is unenforceable.
• Confusing a licence with a sale. The licensee gets permissions, not ownership. Everything not granted stays with the licensor. Say so clearly.
• A thin IP indemnity. For a licensee, infringement risk sits with the code it did not write. Make sure the indemnity actually covers it.
• Ignoring data protection. If the software processes personal data, a GDPR Article 28 data processing agreement is needed alongside the licence. ## Keeping the agreement alive after signing The work does not stop at signature. A software licence carries renewal and maintenance dates, version and support entitlements, user or seat counts to track, and termination triggers that stop the right to use. Most disputes come not from a badly drafted clause but from a maintenance renewal that lapsed unnoticed, a seat count that crept over the licence, or a commissioned-code ownership question nobody wrote down. That is the case for keeping drafting, review, version history and obligation tracking in one place rather than spread across inboxes, a shared drive and a spreadsheet. Adira is one such AI workspace: you draft from your own templates, see each clause flagged as favourable, neutral or unfavourable to you, edit clauses in plain English, and keep a live timeline of every renewal, maintenance window and obligation, built on Anthropic's Claude. Adira is India-first today; deeper support for Portuguese law is on its roadmap rather than live, so treat it as a workflow layer here and keep local counsel for the legal substance.