Quick summary of software licence agreements
A software licence agreement is a contract where one party (the Licensor) grants to another party (the Licensee) the right to use the defined software. The clauses required depend on the nature of the software and the business model of the developer.
Key insights
- The term Software Licence Agreement can apply to both installed software as well as cloud based applications.
- Cloud based Apps are commonly referred to as SaaS Contracts because they involve the right to access and use a software application as opposed to a right to reproduce the code.
- The clauses required to be included in a SLA will depend on the nature of the software itself and the business model of the developer.
- Rarely can one licence be applied to another piece of software without substantial alteration.
- With a well drafted SLA you can both protect the intellectual property in the software and avoid costly disputes.
On this page
- Quick summary
- What clauses are common in software licence agreements?
- What are the common legal issues with SLAs?
- What is the tyranny of the perpetual licence?
- What does this mean for your software licence?
- Practical tips
- Frequently asked questions
- Key takeaways
- Our approach
- Further reading
- Links and further references
A software licence agreement (SLA) is a contract where one party (Licensor) grants to another party (Licensee) the right to use the defined software. It is often used by software developers (Developers) so that they can build and own a core application, customise it for particular clients and provide them with a licence to use the core. In many cases this licence has been the start of a substantial business enterprise.
The term Software Licence Agreement can apply to both installed software as well as cloud based applications. That said cloud based Apps are commonly referred to as "Software as a service contracts" or SaaS Contracts because they involve the right to access and use a software application as opposed to a right to reproduce the code.
The clauses required to be included in a SLA will depend on the nature of the software itself and the business model of the developer. SLAs are also commonly called "End User Licence Agreements" or EULAs (EULA). For an overview of how we help, see our software development law page.
——— Common clauses
What clauses are common in software licence agreements?
Common clauses deal with the licence fee, support, term and renewal, IP, data, indemnities, warranties and limitation of liability.
The contents of a SLA will vary according to the nature of the App that is licensed, what it is used for as well as the amount and extent of support that is required. Common clauses in SLAs include:
| Clause | What it covers |
|---|---|
| Licence fee | Licence fees vary depending on the business model which may be subscription based or, less commonly, a once off licence fee for the life of the version of the software (Perpetual Licence). |
| Master licence rights | If the Licensee can sublicense the software perhaps they also have 'master license rights' allowing them to use it to create and subsequently sublicence bespoke versions – almost anything is possible. |
| Free trials | Commonly software providers are offering free trials of the software to prospective Licensees. Care must be taken to ensure the terms of these free trials are express. Commonly the agreement will detail what happens to data which is entered into the trial version of the software. It may or may not be retained when moving to a paid version. |
| Support | Rights to access various types of support and the rights to access it and how it is paid for. |
| Term and termination | The Licence would need to include provisions which detail when the software licence comes into effect (Commencement Date) and the circumstances which give rise to it ending. |
| Renewal | If the software is licensed for a period of time (Term) then it is usual to include provisions surrounding renewal of a further term including provisions for automatic renewal. |
| Intellectual property | Intellectual property (IP) clauses are usually substantial and significant in SLAs. They may protect and grant rights to both the Licensor and the Licensee. Clauses relating to IP may set out the conditions upon which the software can be copied, grant the Licensor rights to use the Licensee's user generated content for example. |
| Reverse engineering | It's usual for Developers to attempt to contractually protect the IP in the software by including clauses to prohibit reverse engineering. These need to be carefully drafted to ensure that they are enforceable. |
| Transaction Out of Data | The circumstances where data is transportable (or exportable) from an App and the assistance that the Licensor must provide to the Licensee are usual considerations to include in a SLA. |
| Confidential Information | The nature of the software may give rise to an obligation of confidence that either the Licensor or the Licensee may wish to protect. If this is the case then clauses will need to be included that address the contractual obligation of confidence. |
| Indemnity | The Licensor may want to be indemnified against certain losses caused by the Licensee's use of the software. Non-payment is a usual one as is misuse of the software in a way that it was not intended or in a way that causes loss to the Licensor. Because each Software Application is different, the indemnities should be tailored to the needs of the Licensor. For example, an indemnity may be drafted that requires a Licensee to pay the Licensor's losses if the software is used in contravention of spam laws. Such an indemnity would only apply if the software included features allowing the Licensee to send emails. |
| Warranties | The Licensor would usually warrant the software is free from material defects and is fit for purpose. These are of course required under the Australian Consumer Law. Again the specific warranties that could be included will depend on the nature of the software that is licensed. |
| Limitation of liability | It would be unusual for a SLA not to include a limitation of liability clause. A SLA may (or may not be) a consumer contract for the purposes of section 23(3) of Schedule 2 of the Competition and Consumer Act 2010 (Cth) so the way that the Developer's liability applies may change. |
| Data sovereignty | With more and more personal information data being stored, collected or distributed by software, the provisions of the entity's privacy policy are almost always imported into the licence. |
| Legislative compliance | Regardless of what the software does we live in a highly regulated economy. The terms of a SLA must be compliant with various pieces of legislation that cannot be avoided. |
In short, the specific clauses that could be included will depend on the nature of the software that is licensed.
Licensing your software? Dundas Lawyers drafts software licence agreements and advises on enforcing their terms. Call 07 3221 0013 or submit an enquiry online.
——— Legal issues
What are the common legal issues with SLAs?
Common problems are pressure to assign the IP rather than license it, and generic or US templates that do not fit the software.
Every SLA is (or should be) as different as the software that is licensed. Common problems faced by Developers at the early stage of commercialisation of their Software is that they are pressured by an initial client to assign the IP in their software as opposed to licensing it to them.
It's common for early adopters of software to receive generic templates that clearly don't apply because of the nature of the software licensed. Rarely can one licence be applied to another piece of software without substantial alteration. In most cases it takes longer to 'fix' an agreement like this than it does to draft one from scratch.
Worse still, in trying to cut corners, Developers may elect to rely on SLAs developed by US software companies which are typically incompatible with the Australian Law. Most people don't appreciate the effort that is required to draft a solid SLA and that despite it appearing on the internet the copyright in it belongs to someone else!
In short, rarely can one licence be applied to another piece of software without substantial alteration.
——— Perpetual licences
What is the tyranny of the perpetual licence?
It arises where clients have a perpetual licence for software that the Developer no longer wants to support because of the passage of time.
In recent years one issue facing Developers has been the "tyranny of the perpetual licence". The Developer's clients have 'purchased' a perpetual licence for the software, but the Developer no longer wants to support it because of the passage of time.
Upgrading those on perpetual licences using old technology needs to be considered carefully to avoid complaints and potential breach of contracts. Issues such as how long the Developer has to maintain backwards compatibility and interoperability with old operating systems are issues that need careful consideration.
If you want to avoid common problems like these, you should engage a specialist technology lawyer to draft your SLA.
——— Takeaways
What does this mean for your software licence?
A well drafted SLA can protect the intellectual property in the software and avoid costly disputes.
Legal disputes over software licences are common. With a well drafted SLA you can both protect the intellectual property in the software and avoid costly disputes where the terms of the agreement are uncertain or have been breached.
——— Practical tips
Practical tips for software licence agreements
Tailor the licence
Every SLA is (or should be) as different as the software that is licensed, so generic templates rarely apply without substantial alteration.
Think before assigning your IP
Developers are often pressured by an initial client to assign the IP in their software as opposed to licensing it to them.
Avoid US templates
SLAs developed by US software companies are typically incompatible with the Australian Law, and the copyright in them belongs to someone else.
Plan for perpetual licences
Consider how long the Developer has to maintain backwards compatibility and interoperability with old operating systems.
See also our article on end user licence agreements.
Frequently asked questions about software licence agreements
What is a software licence agreement?
A software licence agreement is a contract where one party (the Licensor) grants to another party (the Licensee) the right to use the defined software. It can apply to both installed software and cloud based applications.
Is a software licence agreement the same as an EULA?
SLAs are also commonly called End User Licence Agreements or EULAs. Cloud based Apps are commonly referred to as Software as a service contracts or SaaS Contracts.
What is a perpetual licence?
A perpetual licence is a once off licence fee for the life of the version of the software. Licence fees may instead be subscription based, which is more common.
Can I use a template software licence agreement?
Rarely can one licence be applied to another piece of software without substantial alteration. SLAs developed by US software companies are typically incompatible with the Australian Law, and the copyright in a template on the internet belongs to someone else.
Can a software licence agreement prohibit reverse engineering?
It is usual for Developers to attempt to contractually protect the IP in the software by including clauses to prohibit reverse engineering. These need to be carefully drafted to ensure that they are enforceable.
Does the Australian Consumer Law apply to a software licence agreement?
A SLA may (or may not be) a consumer contract for the purposes of section 23(3) of Schedule 2 of the Competition and Consumer Act 2010 (Cth), so the way that the Developer's liability applies may change.
Key takeaways on software licence agreements
- A software licence agreement is a contract where the Licensor grants to the Licensee the right to use the defined software.
- Common clauses include the licence fee, support, term and termination, renewal, IP, indemnities, warranties and limitation of liability.
- The specific clauses will depend on the nature of the software that is licensed.
- Upgrading those on perpetual licences using old technology needs to be considered carefully to avoid complaints and potential breach of contracts.
- With a well drafted SLA you can both protect the intellectual property in the software and avoid costly disputes.
Need a software licence agreement? Call Dundas Lawyers on 07 3221 0013 or submit an enquiry online.
Our approach to software licence agreements
Dundas Lawyers drafts software licence agreements and advises on enforcing their terms. We look at the nature of the software, the business model of the developer and how the IP in the software is protected.
Further reading
For further reading on software licensing, see the following articles written by the team at Dundas Lawyers.
- End user licences – what an end user licence agreement covers. See: What are end user licence agreements?
- SaaS agreements – the key issues in a SaaS agreement. See: What should a SaaS agreement cover?
- Implied licences – when a licence to use software is implied. See: Do I have an implied licence for software?
- Support agreements – what a software support agreement should include. See: What should a software support agreement include?
- Development agreements – the common clauses and problems in software development agreements. See: What is a software development agreement?
Further information about software licence agreements
If you need assistance drafting a Software Licence Agreement or enforcing its terms, please telephone me for an obligation free and confidential discussion.

Malcolm Burrows B.Bus.,MBA.,LL.B.,LL.M.,MQLS.
Legal Practice Director
T: +61 7 3221 0013 (preferred)
M: +61 419 726 535
E: mburrows@dundaslawyers.com.au

Disclaimer
This article contains general commentary only. You should not rely on the commentary as legal advice. Specific legal advice should be obtained to ascertain how the law applies to your particular circumstances.







