contracts
SaaS Subscription Agreement in Italy: Template, Key Clauses and Local Law (2026)
A SaaS subscription agreement is the contract that gives a customer access to a hosted application on agreed commercial, service and data terms. In Italy a SaaS contract is governed by the general Civil Code rules on contracts, layered with data protection law and, for consumer customers, the Consumer Code. Two local features matter most: the specific written approval of onerous standard clauses, and the extra protections that apply when the customer is a consumer. This guide explains the local law, the clauses that matter, and a template outline. It is general information, not legal advice. ## What law governs a SaaS agreement in Italy? There is no SaaS-specific statute. The contract sits on several layers: - The Civil Code (Codice Civile, Royal Decree No. 262 of 1942) for formation, performance and the general law of obligations, including the duty of good faith in Article 1375.
- Articles 1341 and 1342 of the Civil Code on standard terms, which require specific written approval of onerous clauses.
- The GDPR (Regulation (EU) 2016/679) and the Italian Privacy Code (Legislative Decree No. 196 of 2003, as amended by Legislative Decree No. 101 of 2018), supervised by the Garante per la protezione dei dati personali.
- The Consumer Code (Legislative Decree No. 206 of 2005) where the customer is a consumer rather than a business, including rules on unfair terms and distance contracts. ## The onerous clause rule for online terms Many SaaS contracts are presented as standard online terms the vendor drafted. Under Articles 1341 and 1342 of the Civil Code, onerous clauses in such standard terms are not effective against the customer unless specifically approved in writing. The listed clauses include limitations of liability, the vendor's right to withdraw or suspend the service, tacit renewal, time bars, and arbitration or forum clauses. For a signed order form, this means a separate approval block listing those clauses by number. For a pure click-through, Italian courts have been cautious about whether a simple tick satisfies the rule, so onerous terms in a fully online B2B flow carry enforceability risk. Where it matters, pair online acceptance with a signed order form that includes the specific approval. ## Extra rules when the customer is a consumer If the SaaS is sold to consumers, the Consumer Code adds protections that cannot be waived. Terms that create a significant imbalance to the consumer's detriment can be treated as unfair and void, while the rest of the contract survives (Articles 33, 34 and 36). Distance selling rules require clear pre-contract information and, in general, a withdrawal right, although supply of digital content and services has its own conditions. Italy has also been tightening the online withdrawal rules, including a required digital withdrawal function on the interface. B2B SaaS avoids most of this, but a vendor selling to both must separate the two flows. ## Data protection Most SaaS involves processing personal data. The customer is usually the controller and the vendor the processor, which triggers the GDPR Article 28 requirement for a written processing contract. A SaaS agreement should include, or attach, a data processing agreement covering purpose and scope, security, sub-processors, breach notification, assistance with data subject rights, international transfers, and deletion on exit. The Italian Privacy Code and the Garante sit alongside the GDPR, so Italian-specific guidance should be checked for sensitive processing. ## Key clauses in a SaaS subscription agreement | Clause | What it should cover | | --- | --- | | Subscription and access | Product, users or usage metric, territory, term | | Fees and payment | Price, currency, VAT, billing cycle, late payment interest | | Service levels | Uptime, support response, service credits as the remedy | | Data protection | GDPR Article 28 processing terms, Italian Privacy Code alignment | | Intellectual property | Vendor owns the software; customer owns its data | | Confidentiality | Mutual, with carve-outs and survival | | Warranties and disclaimers | Service warranty and disclaimers to the extent allowed | | Limitation of liability | Cap and exclusion of indirect loss, with specific approval | | Term, renewal and termination | Term, tacit renewal, termination for cause | | Data export and deletion | Export format, window and deletion timeline on exit | | Governing law and disputes | Italian law, court or arbitration | | Specific approval block | Separate approval of onerous clauses under Articles 1341 and 1342 | ## A template outline you can adapt 1. Parties and definitions
- Grant of subscription and scope of use
- Fees, VAT and payment
- Service levels and support
- Acceptable use and customer responsibilities
- Data processing agreement
- Confidentiality
- Intellectual property and customer data
- Warranties and disclaimers
- Limitation of liability
- Term, renewal and termination
- Data export and deletion on exit
- Governing law and dispute resolution
- Specific approval block for onerous clauses ## Common mistakes to avoid - Relying on a pure click-through for onerous B2B terms without the Article 1341 specific approval.
- Using one flow for both business and consumer customers, ignoring the Consumer Code.
- A thin or missing data processing agreement under GDPR Article 28.
- Tacit renewal and liability caps not specifically approved.
- No clear data export and deletion process at the end of the term. ## Keeping SaaS contracts under control Beyond a single deal, the work becomes tracking: which renewals are tacit and coming up, which data terms differ by customer, where the caps sit, and which version is signed. That work is the same across every contract: draft, review for risky clauses, track the dates, keep versions straight. Teams increasingly keep drafting, per-clause risk review, version history and renewal tracking in one connected workspace rather than scattered folders. Adira is an AI contract workspace built for exactly that. Adira is India-first today, and deeper non-India jurisdiction support, including Italy, is on its roadmap, so confirm Italian law specifics with local counsel. This article is general information and not legal advice.
Frequently asked questions
- Are click-through SaaS terms enforceable in Italy?
- A click-through can form a contract, but onerous clauses in standard terms, such as liability caps, withdrawal rights, tacit renewal and arbitration, must be specifically approved in writing under Articles 1341 and 1342 of the Civil Code. Italian courts have been cautious about whether a simple online tick satisfies this, so pair online acceptance with a signed order form carrying the specific approval where those terms matter.
- Does the Consumer Code apply to SaaS in Italy?
- It applies when the customer is a consumer. The Consumer Code (Legislative Decree No. 206 of 2005) voids unfair terms that create a significant imbalance to the consumer's detriment and adds distance-selling and withdrawal protections. B2B SaaS avoids most of this, but a vendor selling to both should separate the two flows.
- Does a SaaS agreement in Italy need a data processing agreement?
- If the service processes personal data, the GDPR Article 28 requires a written processing contract between the customer as controller and the vendor as processor. The Italian Privacy Code (Legislative Decree No. 196 of 2003, as amended) and the Garante sit alongside the GDPR, so include a data processing agreement covering security, sub-processors, breach notice, transfers and deletion.
- What law governs a SaaS contract in Italy?
- The Civil Code governs formation and performance, with Articles 1341 and 1342 on standard terms. Data protection follows the GDPR and the Italian Privacy Code, and consumer sales add the Consumer Code. There is no SaaS-specific statute.
Sources
See how Adira drafts in your voice and reads contracts from your side.
Explore the showroomWorking through a contract like this? Weave is Adira’s free tool to read, mark up, and connect any contract in your browser — no account needed.
Try Weave — free