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

A SaaS subscription agreement is the contract under which a customer pays a recurring fee to access software that the provider hosts and runs, rather than software installed on the customer's own machines. The customer never takes a copy to keep; it gets a right to use the service for the term. That single fact drives the whole contract: there is no perpetual licence, so the terms turn on availability, support, data, security and what happens when the subscription ends. In Austria there is no SaaS statute. The contract is built from the general civil law in the Allgemeines Buergerliches Gesetzbuch (ABGB), the e-commerce rules in the E-Commerce-Gesetz (ECG), consumer law where the customer is a consumer, and data protection law because the provider almost always processes the customer's personal data. This guide sets out the local law that actually bites, the clauses an Austria SaaS agreement 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 SaaS agreement A SaaS contract sits within freedom of contract under the ABGB, so the parties set most of their own terms. Three bodies of law constrain that freedom. First, e-commerce. SaaS is an information society service, so the E-Commerce-Gesetz (ECG), which transposes the EU E-Commerce Directive 2000/31/EC, applies. It sets information duties the provider owes before and at contracting and rules on how an online contract is concluded. Second, consumer protection. If the customer is a consumer, the Konsumentenschutzgesetz (KSchG) and the Fern- und Auswaertsgeschaefte-Gesetz (FAGG) on distance contracts add mandatory information duties and, in many cases, a right of withdrawal, none of which can be excluded. Most business SaaS is business to business, but confirm which side of the line you are on, because it changes the drafting. Third, data protection. Because the provider hosts and processes customer data, the EU General Data Protection Regulation (GDPR) and Austria's Datenschutzgesetz (DSG) require a written data processing agreement with the content in Article 28 GDPR, overseen by the national authority, the Datenschutzbehoerde (DSB). Attach that DPA to the subscription agreement. ### Auto-renewal and standard terms SaaS contracts usually auto-renew. Where the terms are pre-drafted standard business terms (AGB), the ABGB controls them: a clause that is grossly disadvantageous and surprising can be struck under the Paragraph 879(3) content control, and an unusual clause the other side need not expect may not become part of the contract at all under Paragraph 864a. A silent auto-renewal with a long notice window and a steep uplift is exactly the kind of term those rules target, especially against a consumer. Make renewal, price changes and notice periods transparent. ## The clauses an Austria SaaS agreement should contain The core clauses are: - Subscription and access. What the service is, the right to access it for the term, the users or seats covered, and any usage limits.

• Fees, billing and renewal. Subscription fees, billing cycle, taxes (USt/VAT), price change mechanics, auto-renewal, and the notice needed to stop renewal.
• Service levels (SLA). Uptime commitment, measurement, planned maintenance, support response times, and the remedy for a miss (usually service credits).
• Customer data and security. Ownership of customer data stays with the customer; the provider gets a limited licence to host and process it; security measures; breach notification. Cross-reference the DPA.
• Data protection. A GDPR Article 28 data processing agreement covering subprocessors, international transfers, assistance and deletion on exit.
• Acceptable use. What the customer may not do, and the provider's rights if the service is misused.
• Intellectual property. The provider keeps all IP in the software; the customer gets only the subscription right, not a copy or a perpetual licence.
• Warranties and defect liability. The service warranty, framed within the ABGB warranty rules and what mandatory consumer rules allow.
• Liability. Caps and exclusions, with carve-outs for what cannot be limited and with AGB content control in mind.
• Term, suspension and termination. Duration, suspension for non-payment or misuse, termination for cause and insolvency.
• Exit and data return. Export of customer data in a usable format, and deletion after a defined window.
• Governing law and disputes. Austrian law, the competent court or arbitration, and the contract language. ## A SaaS subscription 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. The subscription: grant of access, users and scope
3. Provider obligations and service levels
4. Customer obligations and acceptable use
5. Fees, billing, taxes, price changes and renewal
6. Customer data, security and confidentiality
7. Data protection (cross-reference to the DPA)
8. Intellectual property
9. Warranties and defect liability
10. Limitation of liability
11. Term, suspension and termination
12. Exit, data export and deletion
13. Governing law, jurisdiction or arbitration, and language
14. Boilerplate (assignment, subprocessing, force majeure, notices, entire agreement) ## Common mistakes to avoid - Drafting SaaS like a software licence. There is no copy to license perpetually. The value is access, uptime and data, so the SLA and data clauses carry the weight.

• A hidden auto-renewal. In standard terms, a surprising or grossly disadvantageous renewal clause can be struck or may never become part of the contract. Make it transparent.
• A thin data clause. Hosting customer data makes you a processor. GDPR Article 28 content is mandatory, not optional.
• No exit path for data. If the contract does not say how the customer gets its data out and when yours deletes it, exit becomes a dispute. Specify format and timing.
• Assuming business rules apply to a consumer. The KSchG and FAGG distance-selling rules are mandatory. Check who your customer is before relying on a B2B exclusion. ## Keeping the agreement alive after signing The work does not stop at signature. A SaaS agreement carries a renewal date, price-change windows, service-level reports, subprocessor updates and data-deletion deadlines, each with its own version and its own trigger. Most disputes come not from a badly drafted clause but from a renewal that auto-extended unnoticed, an SLA credit never claimed, or a data deletion that nobody tracked. 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, price change 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.