Software License Agreement in Austria: 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 Austria, 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 copyright statute, the general civil law in the Allgemeines Buergerliches Gesetzbuch (ABGB), 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 an Austria 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 Austrian counsel before you sign. ## Austria: the local law that shapes your software licence Austria protects computer programs under its Copyright Act, the Urheberrechtsgesetz (UrhG), which implements the EU directive on the legal protection of computer programs (now Directive 2009/24/EC). Three points matter for drafting. First, what is protected. Under Paragraph 40a UrhG, a computer program is protected as a work where it is the result of its author's own intellectual creation, and programs are classed among literary works. Protection covers all forms of expression, including source and object code and the development material, but not the ideas and principles behind any element of the program. So a licence protects the code, not the underlying method. Second, employee and commissioned software. Under Paragraph 40b UrhG, where an employee creates a program in the course of their duties, the employer holds an unlimited right to use it unless agreed otherwise. That rule is written for employees, not independent contractors, so for commissioned software produced by a freelancer or agency the position is governed by what the contract says. Do not assume the commissioning party automatically owns or can freely use freelance-developed code; set ownership and licence scope expressly. Third, mandatory user rights. The UrhG, following the directive, gives the lawful user certain rights that a licence cannot remove, including making a back-up copy where necessary for use, observing and studying the program to understand its ideas, and decompiling within strict limits to achieve interoperability. A clause that tries to ban these outright will not hold to that extent. ## The clauses an Austria 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 and what licence is granted.
• Fees. Licence fees, the model (perpetual fee, subscription or usage-based), maintenance and support charges, and taxes (USt/VAT).
• 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 defect liability. The warranty on the software, framed within the ABGB warranty rules (Gewaehrleistung) and what mandatory consumer 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 and AGB content control in mind.
• 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. Austrian 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 defect liability
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 - Assuming you own commissioned code. Paragraph 40b UrhG gives an employer use rights over employee-created programs, but it does not cover freelancers. For commissioned software, ownership and licence scope depend on the contract, so set them out expressly.

• 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 Austrian law is on its roadmap rather than live, so treat it as a workflow layer here and keep local counsel for the legal substance.