Perpetual Licences: How They Work In Australia

If you sell or buy software in Australia, you’ve probably come across “perpetual licences.” On the surface, they sound simple: pay once, use forever. In practice, the legal details, support model and contract terms make a big difference to cost, compliance and customer satisfaction.

In this guide, we’ll break down how perpetual licences operate under Australian law, how they differ from subscriptions (SaaS), the clauses to prioritise in your contract, and the documents most software businesses rely on. Our aim is to help you protect your IP, set clear expectations with customers, and scale with confidence.

What Is A Perpetual Licence (And How Is It Different To SaaS)?

A perpetual licence gives the customer a right to use software indefinitely (no fixed end date) in exchange for a one-off fee. Ownership of the software isn’t transferred - the customer receives permission to use it within the limits set out in the licence.

By contrast, Software-as-a-Service (SaaS) is usually a time-limited subscription. Customers pay recurring fees to access hosted software (often in the cloud), and their rights normally end when the subscription ends.

Common Features Of Perpetual Licences

• One-time licence fee (sometimes tiered by number of users, devices or sites).
• Optional maintenance and support, often sold as an annual add-on for updates and helpdesk.
• On-premise deployment or offline activation (though some perpetual models still phone home for validation).
• Indefinite usage right, subject to licence limits (scope, users, territory, restrictions).

Common Features Of SaaS

• Monthly or annual fees to access hosted services.
• Updates and support typically included while the subscription is active.
• Use rights are time-bound - access ends if you stop paying.
• Data hosting, uptime and security obligations are core parts of the deal.

Legally, both models grant a licence - neither transfers copyright. The big differences are duration and commercial structure. If you also offer a hosted edition, use dedicated SaaS Terms so your service levels, renewals and data handling are crystal clear.

How Perpetual Licences Work Under Australian Law

Software is protected as a “literary work” under Australia’s copyright laws. As the rights holder, you can license others to use your software without giving up ownership. A perpetual licence is simply a licence without a time limit - all the other controls (scope, user counts, territory, restrictions) still apply.

It’s A Licence, Not A Sale

Even if you ship physical media or provide a downloadable installer, a perpetual licence does not sell the copyright. The customer receives a right to use the software under agreed limits. Restrictions on copying, distribution or reverse engineering are generally enforceable (subject to permitted exceptions under Australian law).

Australian Consumer Law (ACL)

If you supply to consumers or small businesses, ensure your statements about features, performance and compatibility aren’t misleading or deceptive. This general rule is set out in section 18 of the ACL. Keep your marketing, product pages and documentation aligned with your licence terms.

Consumer guarantees can apply to digital products and services in certain scenarios (for example, goods must be of acceptable quality and fit for their intended purpose). You can describe warranties in your contract, but you can’t exclude mandatory consumer rights where they apply.

Unfair Contract Terms (UCT)

If you use a standard form contract with consumers or small businesses, the ACL’s unfair contract terms rules may apply. From late 2023, unfair contract terms are prohibited and carry significant penalties for breaches. Avoid one‑sided provisions, like broad rights to vary terms unilaterally, disproportionate liability caps or termination for convenience that only benefits the vendor.

Installation, Activation And Circumvention

Many perpetual models use activation keys, device locks or user limits. Your licence should explain how activation works, what constitutes authorised use, and consequences for tampering or bypassing technical measures. Circumventing licence controls can amount to breach of contract and may raise copyright concerns.

Updates, Maintenance And Support

Perpetual licences usually separate the core right to use (indefinitely) from ongoing maintenance (updates, patches and support). Be clear about whether updates are included, for how long, and what happens if maintenance lapses. Many vendors offer optional annual maintenance so perpetual customers remain secure and supported.

Tax And Compliance

Perpetual licence fees are often treated as taxable supplies for GST when the supplier is registered, but tax treatment depends on your specific circumstances. It’s sensible to make pricing clarity a priority (for example, whether GST is included) and to issue compliant invoices. If you’re unsure, obtain accounting or tax advice before launch.

Key Clauses To Negotiate In A Perpetual Software Licence

A clear, balanced licence reduces ambiguity, supports compliance and helps prevent disputes. Here are the clauses both vendors and customers tend to focus on.

1) Scope Of Licence

• Type: non‑exclusive or exclusive (most business software is non‑exclusive).
• Territory: Australia‑only or worldwide rights.
• Purpose: internal business use, development/testing, or redistribution (if applicable).
• Edition/Tier: what features are included, and which are add‑ons.

2) Users, Devices And Environments

• Metric: per‑user, per‑device, site or enterprise - define counting rules clearly.
• Virtualisation and cloud: how instances and containers are counted.
• Third‑party access: whether contractors, affiliates or managed service providers are covered and on what terms.

3) Delivery, Installation And Activation

• Delivery method: download, physical media, key server or licence portal.
• Activation/deactivation procedures, key management responsibilities and re‑hosting rights.
• Environment prerequisites and compatibility boundaries (supported OS versions, databases, browsers).

4) Updates, Maintenance And Support

• Definitions: what counts as an “update” versus a “new version” or “upgrade”.
• Inclusions: whether updates are included with the perpetual fee; if not, optional maintenance plans and renewal terms.
• Support: channels, response targets, severity levels and common exclusions (e.g. custom code).

5) Acceptable Use And Restrictions

• No unauthorised copying, sublicensing, renting or resale unless expressly permitted.
• No reverse engineering or circumvention of technical measures (subject to lawful exceptions).
• Security duties such as safeguarding licence keys and access credentials.

6) Warranties, Consumer Guarantees And Remedies

• Reasonable warranties (for example, the software will substantially perform as documented in supported environments).
• Acknowledgement of non‑excludable consumer guarantees where the ACL applies.
• Remedy process (patches, workarounds or limited refunds where required by law).

7) Liability And Indemnities

• Liability caps (often linked to fees paid) and exclusions for indirect or consequential loss - see how limitation of liability clauses work in Australia.
• IP indemnity from the vendor for third‑party infringement claims, and customer indemnities for misuse or breach.

8) Intellectual Property Ownership And Branding

• Reserve all IP rights in the software and documentation; the customer receives a licence only.
• Consider protecting your product name and logo with a registered trade mark.

9) Privacy, Data And Security

Privacy obligations depend on your business and the data you handle. Many small businesses under $3 million annual turnover are not “APP entities” under the Privacy Act 1988 (Cth), but some are still covered (for example, health service providers, credit reporting bodies and businesses that trade in personal information). Even when not legally required, many software businesses adopt a clear Privacy Policy and strong privacy practices to meet customer expectations, enterprise procurement standards and overseas requirements.

• Explain what personal information (if any) the software collects and how it’s used or transmitted.
• Where you process customer data on their behalf, a Data Processing Agreement can allocate roles, security controls and breach notification steps.
• State security measures and responsibilities (for example, encryption standards, access controls, update obligations).

10) Verification, Audits And Metering

• Reasonable audit rights or telemetry to verify compliance with user/device limits.
• Notice, frequency, confidentiality around findings and cost allocation.

11) Termination And Revocation

• Serious breach triggers (e.g. piracy, confidentiality breaches, non‑payment of maintenance if relevant).
• What happens on termination: uninstall obligations, key revocation and whether any paid‑up perpetual rights survive if the breach is cured.

12) Assignment, Transfers And M&A

• Whether the customer can transfer the licence during a business sale or restructure, and consent mechanics.
• Change‑of‑control clauses so both parties understand what happens in an acquisition.

13) Ordering, Invoicing And Payment

• Order forms, purchase orders and invoicing timelines.
• Maintenance renewal pricing, CPI adjustments and consequences for late payment.

Compliance, Support And Practical Tips

Perpetual models can run smoothly for years - with the right habits on both sides.

For Vendors

• Align promises with reality. Keep product pages and documentation accurate to avoid issues under section 18 (misleading or deceptive conduct).
• Offer a practical support pathway: knowledge base, ticketing and clearly defined maintenance plans.
• Decide your versioning strategy early: which fixes and features are included, which require maintenance or upgrade fees.
• Use sensible audit/telemetry that respects privacy and confidentiality requirements.
• Keep licence controls reliable so legitimate customers aren’t locked out by accident.

For Customers

• Track licence metrics (users/devices/sites) to avoid accidental overuse.
• Budget for maintenance if you’ll need security patches, compatibility updates and support.
• Clarify re‑hosting rights and transfers if you change environments or restructure the business.
• Confirm response targets for critical bugs and what counts as a supported environment.

Acceptance And Execution

Make sure you have a clear acceptance mechanism. For widely distributed installers, an in‑product click‑through to an EULA (end‑user licence agreement) is common. For negotiated B2B deals, a signed order form that references your Software Licence Agreement is typical. Electronic acceptance is generally fine in Australia - here’s a refresher on wet ink vs electronic signatures.

What Legal Documents Do You Need?

The right documents reduce risk, set expectations and keep you compliant. Most software businesses using perpetual licensing rely on some combination of the following.

• Software Licence Agreement: Your core contract granting the perpetual use right and setting scope, restrictions, warranties, liability and termination.
• EULA: A click‑wrap licence presented during install or first run - ideal when you distribute widely and need consistent terms accepted by end users.
• SaaS Terms: If you also offer a hosted edition, use separate terms for uptime, support, renewals and data handling.
• Privacy Policy: Explains what personal information you collect and how it’s handled; often expected by customers and required for many APP entities or certain industries.
• Data Processing Agreement: Allocates privacy and security obligations when you process customer data (particularly for enterprise or hybrid deployments).
• Support And Maintenance Terms: Define support scope, SLAs, version support windows and fees for annual maintenance.
• Professional Services SOW: If you provide implementation, integration or training, use a statement of work with deliverables and acceptance criteria.

If you sell through resellers or OEMs, you’ll also need aligned reseller/distribution terms and customer‑facing licence terms to avoid conflict between agreements.

Key Takeaways

• A perpetual licence grants an indefinite right to use your software, but it’s still a licence - your written terms govern how it can be used.
• Perpetual and SaaS differ mainly in billing and duration; treat them as separate offerings with a solid Software Licence Agreement and dedicated SaaS Terms where relevant.
• Keep Australian Consumer Law in mind, including misleading conduct rules and unfair contract terms - penalties can apply to one‑sided standard form contracts.
• Prioritise key clauses: scope and metrics, installation/activation, updates and support, warranties and liability, IP ownership, privacy/data, audits and termination.
• Privacy obligations depend on your business and data flows; many software vendors adopt a clear Privacy Policy and use a Data Processing Agreement when processing customer data.
• Plan your support pathway and versioning, and put simple tracking in place so both sides stay compliant over time.

If you’d like a consultation on structuring or reviewing your perpetual software licensing (or moving to a hybrid model), you can reach us at 1800 730 617 or team@sprintlaw.com.au for a free, no‑obligations chat.