Do I Need A Software Licence Agreement? (2026 Updated)

Building software is exciting - whether you’re launching a SaaS platform, selling a desktop app, licensing an API, or distributing software to enterprise customers.

But once your product is out in the world, a very practical question comes up fast: who’s allowed to use it, how can they use it, and what happens if something goes wrong?

That’s what a software licence agreement is for. And because software products, subscription models, and data expectations keep evolving, it’s worth making sure your approach is current - this guide has been updated for today’s New Zealand tech and compliance environment.

Below, we’ll walk through when you need a software licence agreement, what it should cover, how it differs from other common software documents, and how to get set up properly so you’re protected from day one.

What Is A Software Licence Agreement (And Why Does It Matter)?

A software licence agreement is a contract that sets the rules for how someone can use your software.

In plain terms, it answers:

• What you’re giving the user (permission to use the software - not ownership of it)
• How they can use it (permitted uses and restrictions)
• How long they can use it for (subscription term, perpetual licence, trial period)
• What happens if they breach the terms (termination, suspension, remedies)
• Who’s responsible if something breaks (warranties and liability limits)

This matters because software is usually protected by copyright, and your business model often relies on licensing rather than “selling” the product outright. If your terms are unclear (or missing), you can end up in messy disputes about scope, payment, access, and responsibility.

It’s also one of the simplest ways to reduce risk as you scale. Imagine you sign a major customer, they roll your software out company-wide, and then you realise the “deal” doesn’t actually say how many users they’re paying for or whether they can copy it to multiple environments. A well-drafted licence agreement avoids that kind of ambiguity.

Licence Vs Ownership (A Common Confusion)

Most customers assume that if they “pay for software”, they own it. But in many software businesses (especially SaaS), they’re buying:

• a subscription or licence to access your platform, and/or
• a limited right to install and use your software, subject to rules.

Your agreement should make this crystal clear. If you don’t clearly state that the software is licensed (not sold), you can create avoidable arguments later about what the customer can do with your product.

Do You Actually Need A Software Licence Agreement?

If you’re offering software to anyone outside your business (customers, users, beta testers, resellers, enterprise clients), you’ll usually be much safer with a software licence agreement in place.

Here are common situations where a software licence agreement is either essential or strongly recommended.

1. You’re Selling Software (Even If It’s A One-Off Sale)

If you sell software as a downloadable product, desktop program, plugin, or embedded system, you’re giving customers ongoing ability to use something valuable. Your agreement helps you control:

• how many devices it can be installed on
• whether it can be copied, shared, or resold
• whether updates are included
• what support (if any) you provide

2. You Run A SaaS Platform

SaaS businesses often use platform terms rather than a classic “licence agreement”, but the concept is similar: you’re licensing access to your software and setting rules around acceptable use, subscriptions, downtime, support, and suspension.

Depending on your model, you might use a combination of documents such as SaaS Terms plus privacy and data processing terms.

3. You Licence Software To Businesses (B2B / Enterprise)

If your customers are businesses (especially larger organisations), they’ll expect clear legal terms around:

• user limits and usage environments
• service levels and support
• security and data handling
• audit rights and compliance
• indemnities and liability caps

This is where a tailored agreement becomes particularly important, because enterprise customers often have procurement requirements and risk policies you’ll need to meet (or negotiate).

4. You Provide An API Or Developer Access

If you’re exposing functionality via an API, you’re still licensing your software and your platform access - and you’ll want rules around usage limits, rate limiting, permitted purposes, and restrictions on reverse engineering.

In that case, an API Agreement is often the right tool, sometimes alongside broader platform terms.

5. You’re Allowing Others To Distribute Or Resell Your Software

If you have distributors, resellers, or partners who on-sell your software, your licensing terms need to cover who can sub-licence, how branding works, what your reseller can promise to end customers, and what happens when the relationship ends.

Without those guardrails, you can lose control of pricing, customer expectations, and even your IP.

What Should A Software Licence Agreement Include?

There’s no one-size-fits-all software licence agreement. The right terms depend on your product (SaaS vs installed software), customer type (consumer vs business), and your risk profile.

That said, most software licence agreements in New Zealand should consider the following core sections.

Licence Grant: What Rights Are You Giving?

This is the heart of the agreement. It usually covers:

• whether the licence is exclusive or non-exclusive (most are non-exclusive)
• whether it’s transferable or non-transferable
• territory (NZ only or global)
• who can use it (named users, seats, organisation-wide use)
• what environment it can be used in (production, testing, internal only)

Restrictions: What Can’t The User Do?

Restrictions protect your IP and business model. Typical restrictions include:

• no reverse engineering or decompiling (subject to any mandatory legal rights)
• no copying except permitted backups
• no sharing access credentials
• no resale or sublicensing without permission
• no use to build a competing product

These clauses are also where you can deal with misuse, including misuse that increases your operational costs (for example, excessive API calls or scraping behaviour).

Fees, Renewals, And Payment Terms

Your agreement should make it easy to understand:

• the licence fee (one-off, monthly, annual)
• when payment is due
• what happens if payment isn’t made (late fees, suspension, termination)
• whether fees increase at renewal
• tax treatment (for example, GST)

This is one of the most common sources of disputes, so clarity here is a big win.

IP Ownership (And What Happens To Feedback)

Your licence agreement should confirm you retain ownership of your:

• software and source code
• documentation and user interfaces
• updates and improvements (unless separately agreed)

If customers provide feedback or feature requests, you’ll also want terms covering whether you can use that feedback to improve your product without owing them anything.

Support, Updates, And Service Levels

Many software businesses promise support informally (for example, “we’ll fix bugs quickly”). If it’s not documented, expectations can blow out.

You should consider covering:

• what support channels are available (email, help desk, phone)
• support hours (business hours vs 24/7)
• response time targets
• whether updates are included and how they’re delivered
• planned maintenance windows

Sometimes this sits in a separate Service Level Agreement, especially for B2B and enterprise customers.

Warranties And Disclaimers (What Are You Promising?)

Most software is provided “as-is” to some degree - but you need to be careful here, because your ability to disclaim warranties depends on who you’re selling to and how you sell.

If you sell to consumers in New Zealand, the Consumer Guarantees Act 1993 can apply and give customers automatic rights around acceptable quality and fitness for purpose.

If you sell to businesses, you may be able to contract out of the Consumer Guarantees Act in some circumstances (but it needs to be done properly and usually must be in writing).

Your agreement should also align with the Fair Trading Act 1986 - meaning you shouldn’t make misleading claims about what your software can do (including marketing claims, feature lists, and “guarantees” on your website).

Limitation Of Liability (A Big One For Software)

This is where you manage what you’re on the hook for if something goes wrong - for example, an outage, data loss, or integration failure.

A well-drafted limitation of liability clause might cover:

• types of loss excluded (like indirect or consequential loss)
• a liability cap (for example, fees paid in the last 12 months)
• carve-outs (situations where the cap doesn’t apply, like intentional wrongdoing)

Liability is one of those areas where templates can do more harm than good. If you want a deeper background on the concept, limitation of liability is worth understanding before you lock in your approach.

Termination, Suspension, And What Happens After

Your agreement should set clear rules for:

• when you can terminate (non-payment, breach, misuse, insolvency)
• when a customer can terminate (end of term, breach, convenience)
• what happens to access on termination (immediate cut-off vs grace period)
• data return/export timeframes (especially for SaaS)
• ongoing obligations (confidentiality, IP protection, unpaid fees)

This is especially important if your software supports a business-critical function. Your customers will want certainty, and you’ll want a clean offboarding process that reduces disputes.

How Is A Software Licence Agreement Different From Other Software Terms?

Software legal documents often overlap, and it’s easy to end up with a patchwork of terms that don’t match (for example, website terms say one thing, a customer contract says another, and your invoice says nothing at all).

Here’s a simple way to think about the common documents.

Software Licence Agreement Vs Terms Of Use

Terms of use usually cover how people use your platform or website, including acceptable use rules and account obligations. They can include a licence grant too, but they’re often broader and more “site-wide”.

If you run a platform, you might rely on Terms of Use that include licensing language, rather than a standalone “software licence agreement”.

The key is making sure the document still properly addresses licensing, IP, liability, termination, and payment (if applicable).

Software Licence Agreement Vs EULA

An end user licence agreement (EULA) is a type of software licence agreement commonly used for installed software and apps. It’s usually clicked-to-accept during installation or account setup.

If your product is a downloadable app or installed software, an EULA can be the right format.

Software Licence Agreement Vs A Services Agreement

If you’re doing custom software development, implementation, configuration, or ongoing managed services, you may also need a services contract to cover deliverables, timelines, change requests, and acceptance testing.

In that case, a Service Agreement often sits alongside your licence terms (or includes them).

Software Licence Agreement Vs Privacy Policy

If your software collects personal information (customer data, user profiles, payment details, analytics identifiers), you will also need privacy documentation. A licence agreement controls software use; privacy terms explain how data is collected, stored, used, and disclosed.

In New Zealand, your privacy obligations are governed by the Privacy Act 2020. As a starting point, having a clear Privacy Policy is often a key part of building trust and complying with the law.

What NZ Laws Should You Keep In Mind When Licensing Software?

Even though software licensing is “contract-based”, your contract doesn’t exist in a vacuum. Some New Zealand laws will shape what you can (and can’t) do in your terms, and what customers can expect.

Fair Trading Act 1986

The Fair Trading Act is about misleading or deceptive conduct and false representations.

For software businesses, the risk often shows up in:

• feature claims (especially “coming soon” features)
• performance claims (speed, security, uptime)
• pricing representations (what’s included, whether add-ons are required)
• comparative claims (“best”, “number one”, “guaranteed”)

Your licence agreement won’t fix misleading advertising, but consistent, accurate terms can reduce confusion and help demonstrate your true offering.

Consumer Guarantees Act 1993

If you provide software to consumers, the Consumer Guarantees Act can impose non-excludable guarantees, such as acceptable quality and fitness for purpose.

This affects how you write disclaimers, refund provisions, and “no warranty” clauses. If you sell primarily B2B, you may be able to contract out - but it needs to be done properly and in a way that fits your sales process.

Privacy Act 2020 (Especially For SaaS)

If your product processes personal information, privacy compliance is a day-one issue. You should think about:

• what personal information you collect and why
• where you store it (NZ or offshore hosting)
• who you share it with (vendors, subprocessors)
• what security steps you take
• what happens if there’s a data breach

If you’re working with business customers who are sensitive about data handling (health, finance, education), you may also need stronger contractual data clauses, not just a public-facing privacy policy.

Copyright And IP Protection

Software is generally protected by copyright in New Zealand. A licence agreement is how you commercialise that copyright - and how you stop customers from treating your software like something they can copy, modify, or distribute freely.

It also helps protect the value of your business. If you ever want to raise capital or sell, investors and buyers will look closely at whether your IP is properly controlled through enforceable contracts.

Key Takeaways

• A software licence agreement sets the rules for how customers and users can use your software, and helps protect your IP, revenue model, and risk exposure.
• If you sell software, run a SaaS platform, provide an API, or licence software to businesses, having clear written licence terms is strongly recommended (and often expected).
• Most software licence agreements should cover the licence grant, restrictions, fees, IP ownership, support expectations, warranties/disclaimers, limitation of liability, and termination/offboarding.
• Your software terms should be consistent with key NZ laws like the Fair Trading Act 1986, Consumer Guarantees Act 1993 (where applicable), and the Privacy Act 2020 if you handle personal information.
• Different models often need different documents (for example, a EULA for installed software, SaaS terms for subscription platforms, or an API agreement for developer access).
• Avoid relying on generic templates - licensing, liability, and consumer/privacy obligations are highly context-specific, and mistakes can be expensive later.

If you’d like help putting the right software licence agreement in place (or reviewing what you’re currently using), you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.