Software License Agreement in South Africa: Template, Key Clauses and Local Law (2026)

A software license agreement in South Africa grants a customer the right to use software on set terms while the developer keeps ownership. Software is licensed, not sold. The licence defines what the customer may do (install, run, number of users), what it may not do (copy, modify, redistribute, reverse engineer beyond what the law permits), and who owns the code and any changes. South Africa has no single software statute. The agreement rests on copyright law, the common law of contract, and consumer and electronic transactions law. This guide explains that framework, lists the clauses a software licence should contain, and gives a skeleton you can adapt. It is general information, not legal advice. Confirm the current position with a qualified South African lawyer before you sign. ## The law that governs software licensing in South Africa - Copyright Act 98 of 1978. A computer program is a separate category of work with its own protection under the Act. Copyright gives the owner exclusive rights to reproduce and adapt the program, so a licence is what makes the customer's use lawful. The Act permits a lawful user to make a back-up copy for use where the original is lost or damaged. Note that amendments to South African copyright law have been under consideration, so confirm the current text.

• Common law of contract. The licence is a contract, governed by ordinary principles and freedom of contract, tested against public policy.
• Consumer Protection Act 68 of 2008 (CPA). Where software is supplied to a consumer, the CPA implies quality standards and regulates unfair terms and the presentation of limitation and indemnity clauses. Pure business deals above the regulated threshold fall outside the CPA.
• Electronic Communications and Transactions Act 25 of 2002 (ECTA). It validates click-through and electronically signed licences. ## Key clauses in a South African software license agreement ### 1. Licence grant and scope State what is licensed, the permitted use, whether the licence is exclusive or non-exclusive, perpetual or subscription, and any user, device, or site limits. ### 2. Restrictions List prohibited acts (copying beyond the licence, sublicensing, reverse engineering), while allowing for the back-up copy the Copyright Act permits a lawful user. ### 3. Intellectual property ownership Confirm the developer owns the software and all IP, and set who owns configurations or customisations. ### 4. Open source and third party components Disclose open source components and their terms, and allocate compliance responsibility. ### 5. Delivery, installation and acceptance Cover delivery, installation duties, and acceptance where relevant. ### 6. Support, maintenance and updates State the support and updates included, response targets, and whether maintenance is separate. ### 7. Warranties and the CPA Give performance warranties and, where the CPA applies, remember you cannot contract out of its implied quality standards. ### 8. Limitation of liability Cap liability and exclude indirect loss, drafted within the CPA where it applies, which requires limitation terms to be clear and conspicuous. ### 9. Fees and audit Set licence fees, payment terms, and any right to audit usage against the licensed scope. ### 10. Source code escrow For business-critical software, consider an escrow arrangement releasing source code on defined trigger events. ### 11. Term, termination and effect Set term, termination grounds, and post-termination duties, including ceasing use and deleting copies. ## A simple clause skeleton 1. Parties and definitions

2. Licence grant and scope
3. Restrictions on use
4. Intellectual property ownership
5. Open source and third party components
6. Delivery, installation and acceptance
7. Support, maintenance and updates
8. Fees, payment and audit
9. Warranties and CPA position
10. Limitation of liability
11. Source code escrow (if applicable)
12. Confidentiality
13. Term and termination
14. Governing law and disputes ## One workspace to draft, review and track the agreement A software licence does not end at signature. Renewal and notice dates fall due, user counts and support terms change, and each variation has to be applied without breaking the licence grant or the liability position. Across email and folders, the current version is easy to lose. Adira is an AI legal operating system that keeps drafting, review, clause-level editing, version history, and key-date tracking in one workspace, so the current licence, its scope, and its key dates all live in one place. Indian corporate law is deepest today, and wider non-India jurisdiction depth, including South Africa, is on the roadmap, so treat this page as general guidance and verify South African specifics locally. You can see the product at Adira. ## Frequently asked questions