SaaS Agreement in Austria: Template, Key Clauses and Local Law (2026)

What a SaaS agreement in Austria is A SaaS (software as a service) agreement in Austria is a contract under which a provider gives a customer access to hosted software over the internet for a fee, usually by subscription, rather than selling or licensing a copy to install. Austrian law has no single SaaS statute. The contract is governed by general civil and contract law in the Allgemeines Buergerliches Gesetzbuch (ABGB), shaped by its subject matter, which is a continuing service plus a right to use. Because it is a continuing-use service rather than a one-off sale, Austrian commentators treat SaaS as close to a rental or lease-type contract (Bestandvertrag) combined with service elements, which matters for warranty and availability. This page sets out the law and the clauses. It is general information, not legal advice. ## The law that governs it in Austria - General contract and warranty law in the ABGB. Statutory warranty (Gewaehrleistung) under sections 922 and following applies to defects; for a continuing service the provider must keep the service in conformity for the supply period.

• Limits on liability clauses. Liability caps and exclusions between businesses are judged mainly under section 879 paragraph 3 ABGB (a clause that grossly disadvantages one party can be void) and section 864a ABGB (surprising or unusual terms in standard-form contracts do not become part of the contract). Caps are generally respected between businesses when they are transparent and proportionate, but you cannot exclude liability for intent or gross negligence, or for personal injury.
• Consumer rules are stricter. If the customer is a consumer, the Verbrauchergewaehrleistungsgesetz (VGG), in force since 1 January 2022, implements the EU Digital Content Directive (2019/770). It covers digital services such as cloud software, requires the provider to supply the updates needed for conformity for the whole contract term, places the burden of proof on the provider during the supply period, and extends the proof presumption to one year. Austrian law also restricts severability clauses in consumer contracts, so business-to-business terms should not be reused for consumers.
• Data protection. Where the service processes personal data, the GDPR applies and a data processing agreement meeting Article 28 GDPR is mandatory. The Austrian Data Protection Act (Datenschutzgesetz, DSG) supplements it, and the EU Data Act now adds rules on data access and switching for cloud services. ## Key clauses to include ### The service and its performance
• A clear description of the service and scope of use (users, environments, usage limits).
• Service levels: an availability or uptime target, support response times, and what happens when they are missed (service credits).
• Maintenance windows and the provider update and upgrade rights. ### Commercial terms
• Fees, billing cycle, and price-change mechanics.
• Term, renewal, and notice to terminate.
• Suspension rights for non-payment or misuse. ### Risk allocation
• Warranties limited to conformity with the documentation, drafted with the ABGB limits in mind.
• A liability cap and exclusions that keep the carve-outs Austrian law requires (intent, gross negligence, personal injury).
• Indemnities, for example for third-party intellectual property claims. ### Data and security
• A GDPR Article 28 data processing agreement as an annex: subject matter, duration, purpose, data types, security measures, subprocessors, and deletion or return on exit.
• Confidentiality and security commitments.
• Where data is hosted and any data-residency promises. ### Exit
• Data export format and a deletion timeline after termination.
• Assistance with migration to another provider. ## A simple clause skeleton 1. Definitions and the service.

2. Grant of access and acceptable use.
3. Service levels and support.
4. Fees and payment.
5. Term, renewal, suspension, and termination.
6. Warranties and their limits.
7. Liability cap and carve-outs.
8. Intellectual property and indemnities.
9. Data protection annex (Article 28 GDPR) and security.
10. Confidentiality.
11. Exit, data export, and deletion.
12. Governing law and disputes (Austrian law, a named venue such as Vienna). ## Common mistakes to avoid - Using a US-style unlimited liability exclusion that falls foul of section 879 ABGB.

• Hiding an important term in standard conditions, where section 864a ABGB can strike it out as surprising.
• Treating a consumer SaaS contract like a business one and ignoring the VGG update and proof rules.
• Forgetting the Article 28 data processing agreement, or leaving exit and deletion undefined. ## Drafting and managing an Austrian SaaS contract in one workspace A SaaS contract is rarely signed once and forgotten. You renew it, renegotiate the service levels, update the data terms when the law changes, and track renewal and deletion dates. That is far easier when drafting, review, tracking, and governance sit in one place. Adira is an AI legal workspace where you can draft the agreement, see each clause flagged as favourable, neutral, or unfavourable to you, edit clauses in plain English, and track renewal dates and obligations across your whole contract portfolio. Adira is deepest on Indian law today; Austria-specific depth, including the VGG and DSG points above, is on the roadmap, so pair it with Austrian counsel for the local-law detail.