SaaS Agreement in South Africa: Template and Key Clauses (2026)

A SaaS agreement in South Africa is the contract under which a software provider gives a customer access to a hosted application over the internet, usually for a recurring subscription. The customer does not own or install the software; it uses it as a service. The agreement covers what the service is, how much it costs, what uptime and support the customer can expect, who owns the data, and how personal information is handled. In South Africa, data protection law gives that last point real weight. This is general information, not legal advice. Technology and privacy law change, so confirm the current position before relying on any clause. ## How South African law shapes a SaaS agreement Several laws apply together. The Protection of Personal Information Act 2013, known as POPIA, governs how personal information is processed, and where the provider processes personal information for the customer it usually acts as an operator under POPIA, which calls for a written contract with security and confidentiality duties. The Electronic Communications and Transactions Act 2002 recognises electronic contracts and signatures, so a click-to-accept SaaS contract can be valid. The Consumer Protection Act 2008 can apply where the customer is a consumer or a small business within its thresholds, affecting unfair terms and cancellation. <!-- [VERIFY] POPIA operator and cross-border transfer section numbers and the CPA turnover threshold before citing exact figures --> Cross-border data flows matter, because POPIA restricts sending personal information outside South Africa unless certain conditions are met, which is common when a SaaS provider hosts data abroad. ## A clause by clause skeleton Use this as a structure to adapt, not a finished document. ``` SAAS AGREEMENT Parties: [Provider] and [Customer] Date: [date] 1. THE SERVICE What the hosted software does and the plan or tier the Customer buys. 2. ACCESS AND LICENCE A right to access and use the service for the subscription term; no ownership of the software passes. 3. FEES AND TERM Subscription fee, billing cycle, the term and how renewal and price changes work. 4. SERVICE LEVELS AND SUPPORT Uptime commitment, support response times and any service credits if targets are missed. 5. CUSTOMER DATA The Customer owns its data; the Provider may use it only to run the service. Return or deletion of data on exit. 6. DATA PROTECTION (POPIA) The Provider acts as operator, processes personal information only on instruction, keeps it secure and confidential, and helps with data subject requests and breaches. 7. SECURITY The technical and organisational measures protecting the data and service. 8. INTELLECTUAL PROPERTY The Provider owns the software and IP; the Customer owns its data and content. 9. WARRANTIES AND LIABILITY What each party promises and the agreed cap and exclusions on liability. 10. SUSPENSION AND TERMINATION When the service can be suspended or the contract ended, and the exit process for data. 11. GOVERNING LAW AND DISPUTES Governed by South African law; disputes by [arbitration / courts]. Schedule 1: Service Levels Schedule 2: Data Processing (POPIA)

- **Cross-border hosting.** POPIA restricts transferring personal information outside South Africa, so address where data is hosted and on what basis.
- **Electronic acceptance.** Click-to-accept and electronic signatures are recognised, so online sign-up can be valid.
- **Consumer protection.** The Consumer Protection Act can apply to smaller customers, affecting unfair terms and cancellation rights. ## Common mistakes to avoid - No POPIA processing terms when the service handles personal information.
- Ignoring where data is hosted and whether a cross-border transfer is allowed.
- A vague or missing service level, so uptime and support are unenforceable.
- Unclear data ownership and no exit plan to return or delete data.
- An uncapped liability clause, or a cap so low it is unreasonable. ## Keeping SaaS contracts in one place A growing software business signs the same core SaaS contract again and again, each with its own plan, price, renewal date, service level and data terms, plus order forms and amendments. When these live across email and spreadsheets, it is hard to see which customers are on which terms, whose renewal is due, and which contracts carry POPIA duties. Drafting a SaaS agreement, reviewing a data-protection or liability clause, editing a service level in plain language and holding every contract with its renewal dates in one view can live in a single AI workspace tuned to how your company contracts. Adira is built around that workspace, running on Claude, with per-seat pricing shown up front and a 7-day trial, India-first and built to work across jurisdictions. You can read more at [adiralaw.com](https://adiralaw.com). For a single deal the skeleton above is enough on its own. The point worth keeping is that a SaaS book is easier to govern when every contract, its service levels and its renewal dates stay together and current.