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

A SaaS subscription agreement lets a customer use software hosted by the supplier for a recurring fee. Poland has no SaaS statute, so the contract rests on the Civil Code, but if any customers are consumers the digital-services rules add real obligations, and data protection law applies whenever personal data is involved. This guide covers the law, the key clauses and a working skeleton. It is general information, not legal advice; confirm a live deal with a Polish lawyer. ## What law governs a SaaS agreement in Poland? SaaS is a service, not a sale of goods, so it rests on the Polish Civil Code (Kodeks cywilny) of 23 April 1964, under the freedom of contract in Article 353(1). Where the service is not a named contract, Article 750 applies the mandate rules (Articles 734 and following) by analogy. Two extra layers matter: - Consumer digital services. If you sell to consumers, the Act of 30 May 2014 on Consumer Rights, as amended to transpose the EU Digital Content Directive (2019/770) from 1 January 2023, governs the supply of digital content and digital services, including conformity, updates and remedies for non-conformity. Since 2021, some of these protections also reach individual entrepreneurs (sole traders) for contracts that are not of a professional character for them.

• Data protection. The GDPR and the Polish Act of 10 May 2018 on Personal Data Protection apply where personal data is processed, overseen by the President of the Personal Data Protection Office (UODO). The supplier is usually a processor, so an Article 28 data processing agreement is required. ## Key clauses in a Polish SaaS agreement - Subscription and licence: the right to access and use the service, seat or user limits, and that no software copy is delivered.
• Service levels: uptime target, support response, maintenance windows and service credits.
• Fees, renewal and price changes: charges, billing cycle, auto-renewal with a clear notice window, and how prices may change; be careful with one-sided change rights toward consumers and sole traders.
• Data protection and security: the Article 28 data processing agreement, security measures, sub-processors, and transfer safeguards such as standard contractual clauses.
• Data portability and exit: export format and a return or deletion window.
• Intellectual property: the supplier keeps the IP; the customer gets a limited licence; customer data stays the customer's.
• Warranties and liability: service warranties and caps, remembering that liability for intentional harm cannot be excluded in advance (Article 473 of the Civil Code).
• Term and termination: duration, renewal, termination for cause and consequences for data.
• Contractual penalties: if used, remember they secure non-monetary obligations only, and a court can reduce an excessive one.
• Governing law and forum: Polish law and a chosen court or arbitration. ## A simple drafting skeleton 1. Parties and date

2. Definitions
3. Grant of access and scope of use
4. Service levels and support
5. Customer responsibilities and acceptable use
6. Fees, billing, renewal and price changes
7. Data protection and the linked DPA
8. Security and sub-processors
9. Confidentiality
10. Intellectual property and customer data
11. Warranties
12. Limitation of liability (Article 473 limit respected)
13. Term, suspension and termination
14. Data export and deletion on exit
15. Governing law (Polish) and dispute resolution
16. Signatures ## Common mistakes - Treating SaaS as a licence of delivered software rather than a hosted service, which changes the warranty and data terms.

• Ignoring the consumer digital-services rules when any customers are consumers or sole traders.
• Skipping the Article 28 data processing agreement or an international transfer safeguard.
• Trying to exclude liability for intentional harm, which Article 473 forbids.
• Using an auto-renewal with no clear notice window, which is weak against consumers. ## Keeping a subscription contract portfolio under control If you sell the same service to many customers, the hard part is not the master template. It is tracking which renewal is due, which custom SLA applies, and whether a liability or renewal clause holds up. That work (drafting from a tuned template, flagging risky clauses, tracking renewals and keeping versions straight) is what an AI contract workspace can hold in one place. Adira is built for this, with per-clause risk review and plain-English clause editing; it is India-first today with other jurisdictions on its roadmap, so verify local depth before relying on it for Polish law. More at Adira. The law above stands on its own. ## Bottom line A Polish SaaS agreement is freely negotiated under the Civil Code, but the consumer digital-services rules apply when you sell to consumers or sole traders, and the GDPR and the Act of 10 May 2018 govern personal data. Add a proper Article 28 data processing agreement, keep exit and renewal terms clear, respect the Article 473 limit on excluding liability, and get Polish advice before signing a real deal.