Software Licence Contracts: Key Terms for New Zealand Businesses

Software licence contracts can look harmless, especially when a provider sends a standard set of terms and says everyone signs the same version. But this is where New Zealand businesses often get caught. A founder signs before checking who owns improvements, an operations team assumes the subscription can be cancelled on short notice, or a purchaser relies on sales promises that never make it into the written terms.

The result can be expensive. You may end up locked into a longer term than expected, exposed to broad liability, or unable to move your data when the relationship ends. Those issues matter whether you are licensing software for internal use, embedding software in your product, or allowing customers to access your platform under your own licence terms.

This guide explains the key terms in software licence contracts, what they mean in practice for New Zealand businesses, the legal issues to check before you sign, and the mistakes that most commonly cause trouble later.

Overview

A software licence contract sets the rules for how software can be used, who owns the intellectual property, what support is included, and what happens if something goes wrong. For New Zealand businesses, the commercial detail matters just as much as the legal wording, because the contract often controls pricing, renewal, risk allocation and access to business-critical data.

• what software is being licensed, and whether the scope matches your actual use case
• whether the licence is exclusive or non-exclusive, transferable or non-transferable, perpetual or fixed-term
• usage limits, including users, devices, locations, revenue caps, API calls or transaction volumes
• who owns the software, customisations, integrations, data and any improvements
• fees, renewals, price increases and termination rights
• service levels, support commitments, updates and security obligations
• warranties, liability caps, indemnities and exclusions
• privacy, confidentiality and offshore data handling
• what happens at the end of the contract, including data return, deletion and transition support

What Software Licence Contracts Means For New Zealand Businesses

A software licence contract is the document that gives one party permission to use software under stated conditions, while the owner keeps its underlying intellectual property rights.

That sounds straightforward, but there are several business models that fall under the same umbrella. A SaaS subscription, an on-premise enterprise licence, a developer SDK licence, a white-label arrangement and an end user licence for your own customers all raise different legal and commercial issues.

What the contract usually covers

Most software licence agreements deal with four core questions: what is being licensed, how it can be used, what the customer pays, and who carries the risk if the software fails or causes loss.

In practice, the contract may include:

• access rights to the software or hosted platform
• permitted users, business units and locations
• restrictions on copying, modifying, reverse engineering or sublicensing
• service levels, maintenance and update arrangements
• data use, hosting and security commitments
• payment structure, billing cycles and renewal terms
• termination rights and post-termination obligations

Why this matters for SMEs and startups

For many businesses, software is now a core operating tool rather than a back-office extra. If your CRM, POS system, payroll platform, booking software or inventory tool is licensed on poor terms, the legal risk quickly turns into a business continuity problem.

The same issue applies if you are the software provider. If you license your own product without clear terms, you may face disputes about payment, unauthorised use, IP ownership, service expectations or liability when a customer experiences downtime.

Common software licensing scenarios

New Zealand businesses usually encounter software licence contracts in one of these situations:

• buying third-party software for internal operations
• licensing a specialist platform for customer-facing services
• embedding software or code libraries in a broader product
• engaging a developer to build custom software and agreeing who owns the output
• licensing your own software to customers under subscription terms
• reselling or white-labelling another provider's software

Each scenario changes what you need to check. A customer using off-the-shelf software may focus on data access, uptime and liability. A business licensing out its own software may focus on protecting source code, limiting use, getting paid on time and stopping misuse.

How New Zealand law fits in

New Zealand contract law generally allows commercial parties to agree their own terms, but that does not mean every clause is low risk. The wording still needs to be clear, workable and consistent with the way the software will be used.

Other legal rules can also affect the arrangement. For example, the Fair Trading Act 1986 can matter if software is marketed with claims that are misleading or cannot be supported. The Privacy Act 2020 can become relevant if personal information is stored, processed or transferred through the software. If the software is supplied to consumers or in a consumer-facing context, consumer law issues may also need closer attention.

That is why software licence contracts should not be treated as a simple procurement formality. Before you accept the provider's standard terms, you should check that the agreement matches your business model and operational reality.

Legal Issues To Check Before You Sign

The key legal question before you sign is whether the contract gives you the rights you need, limits the risks you can live with, and clearly states what happens if the software or relationship fails.

1. Licence scope

The licence grant is the centre of the contract. It should tell you exactly what you can do with the software.

Check whether the licence is:

• limited to internal business use or extends to customer-facing use
• restricted to named users, a number of seats, or a group company
• limited to New Zealand or usable across multiple jurisdictions
• non-transferable, which can be a problem during a sale, restructure or group reorganisation
• fixed term or perpetual

This is where founders often get caught. A fast-growing business signs a low-cost plan based on current staff numbers, then later discovers the licence does not cover contractors, offshore support staff or a second entity in the group.

2. Intellectual property ownership

A software licence does not usually transfer ownership of the software itself. The provider normally keeps ownership, and you receive a right to use it.

The harder issue is what happens to related materials, such as:

• custom development work
• configurations and templates
• integrations with your systems
• feedback and feature requests
• derivative works or improvements

If you are paying for customisation, the contract should clearly say who owns the resulting IP and what rights each party has to use it. Do not assume payment means ownership. Before you rely on a verbal promise, make sure the ownership and licence-back wording is explicit.

3. Data rights and exit access

If the software stores operational or customer data, your ability to retrieve that information at the end of the contract can be just as important as the functionality itself.

Look for clauses covering:

• who owns the data you upload or generate
• what format it can be exported in
• whether export attracts extra fees
• how long the provider keeps data after termination
• whether data will be deleted, anonymised or retained for legal reasons
• whether transition assistance is available when moving to another system

A contract that is silent on exit can leave a business stranded, especially where the software holds customer records, transaction history, inventory data or compliance documents.

4. Privacy and security

If personal information is involved, privacy and security terms should be reviewed carefully, especially where hosting or support occurs outside New Zealand.

Questions to check include:

• what categories of personal information the software will process
• whether the provider acts only on your instructions or uses data for its own purposes
• where data is stored and who can access it
• what security standards, incident response obligations and breach notification processes apply
• whether subcontractors are used

The Privacy Act 2020 may require you to think carefully about offshore disclosure and whether the provider offers adequate protections. Even where the supplier is well known, your contract should still set expectations around confidentiality and data handling, including any privacy notice commitments.

5. Service levels and support

If the software is business critical, support and uptime should not be left to marketing material or a sales slide deck.

The agreement should state:

• target availability or uptime levels
• scheduled maintenance windows
• response and resolution times for support requests
• what counts as a critical incident
• service credits or other remedies if levels are missed
• whether support is included in the fee or charged separately

Without this detail, a supplier may promise enterprise-grade reliability while the contract gives you little recourse when the system is unavailable.

6. Fees, renewals and price changes

Many software disputes are really pricing disputes. The software works, but the customer did not understand how fees could increase or how the contract would renew.

Before you sign, check:

• whether the term auto-renews unless notice is given
• how much notice is needed to avoid renewal
• whether fees can increase during the term or only on renewal
• what usage triggers extra charges
• whether implementation, onboarding or migration fees are separate
• what happens if payment is late

These points are especially important for startups managing cash flow and scaling headcount quickly.

7. Warranties, liability and indemnities

The main risk is not just whether the software fails, but who bears the cost when it does.

Software licence contracts often include:

• limited warranties that the software will perform substantially as described
• disclaimers excluding uninterrupted or error-free operation
• caps on the provider's liability, often linked to fees paid
• exclusions for indirect or consequential loss
• indemnities for third-party IP infringement claims

These clauses can be reasonable, but they need to be proportionate. If your business would suffer major operational loss from downtime or data issues, a very low liability cap may not be commercially acceptable. If you are the provider, you may want a cap that reflects your pricing and prevents open-ended exposure.

8. Termination and suspension rights

You should know exactly how the relationship can end before you commit to it.

Review whether either party can terminate for:

• material breach
• insolvency
• non-payment
• extended outage or repeated service failure
• convenience, with notice

Also check whether the provider can suspend access before termination. Suspension rights that are too broad can create leverage against the customer even in minor billing or contractual disputes.

9. Governing law and dispute process

Cross-border software contracts often default to overseas law and forums. That can make a dispute much harder and more expensive for a New Zealand business.

If possible, check whether the agreement uses New Zealand law, or at least a dispute process that is practical for your business. Mediation and structured escalation clauses can help, but they should be realistic and not just boilerplate.

Common Mistakes With Software Licence Contracts

The most common mistake is treating software licence terms as non-negotiable boilerplate when they often contain major commercial assumptions that do not fit your business.

Relying on sales discussions instead of the contract

A provider may promise easy cancellation, unlimited usage, local data hosting or fast support. If those promises are not reflected in the written terms, you may struggle to enforce them later.

Before you sign, ask for important commitments to be written into the contract, order form or service schedule.

Ignoring who can use the software

Businesses often assume a licence covers the whole organisation. It may only cover one legal entity, a set number of authorised users or a very specific purpose.

This becomes a problem after growth, acquisition, outsourcing or internal restructuring.

Failing to plan for the end of the relationship

Founders often focus on onboarding and features, not exit. But lock-in becomes obvious only when you want to move to another platform, reduce costs or respond to poor service.

If the agreement does not address data export, migration assistance and deletion timing, your practical bargaining position may be weak at the end of the term.

Accepting a liability cap that is too low

A low cap may be acceptable for a low-cost tool used in one team. It is far less suitable for a platform that handles orders, customer records or core operations.

The right position depends on the software's role in your business, the sensitivity of the data involved and whether you have backup systems.

Overlooking customisation and integration ownership

Where software is tailored to your workflows, it is easy to assume your business owns the result. Many contracts say the supplier owns all modifications, connectors, templates and derivative material.

If you are spending money on setup or development, ownership and ongoing use rights should be negotiated early, not after the work is complete.

Missing privacy and security detail

A vague promise to keep data secure is rarely enough. If the software processes personal information or commercially sensitive data, the contract should explain what security measures exist, how incidents are handled, and what notice you will receive if something goes wrong.

Signing in the wrong entity

Sometimes a founder signs in a personal name, or the contract is entered into by one entity while another entity actually uses the software. This can create confusion around payment, access rights and liability.

Before you sign, make sure the correct New Zealand company or trading entity is named, especially if your business operates through multiple related companies.

Using your own customer licence terms without tailoring them

If you are a software provider, copying overseas licence wording or generic templates can create problems. The terms may not match your support model, pricing structure, IP ownership approach or New Zealand legal context.

Your licence terms should fit the way your software is actually sold and delivered, including subscription billing, acceptable use rules, privacy position, suspension rights and what happens on termination. In many cases, careful contract drafting at the outset avoids disputes later.

FAQs

Are software licence contracts negotiable?

Often, yes. Larger providers may resist major changes, but pricing, renewal terms, liability caps, support commitments, data export rights and privacy clauses are frequently negotiable, especially for business customers.

Who owns custom software built for my business?

Ownership depends on the contract. Payment alone does not guarantee that your business owns the code, customisations or related IP. The agreement needs to say who owns the deliverables and what licence rights apply.

Do I need a written software licence agreement if I sell SaaS?

Yes, in practical terms you usually do. Clear written terms help define customer usage rights, payment obligations, IP ownership, service limits, suspension rights and liability settings.

What should I check if the provider stores data overseas?

Check where the data is stored, whether subcontractors are involved, what security obligations apply, and how offshore access or disclosure is handled. If personal information is involved, privacy compliance should be reviewed carefully.

Can a provider automatically renew a software licence?

Yes, if the contract allows it. The key issue is whether the renewal mechanism, notice period and any price changes are clearly stated before you sign.

Key Takeaways

• Software licence contracts do more than grant access to software, they set the rules for use, payment, ownership, support and risk.
• Before you sign a contract, check the licence scope, usage limits, renewal terms, liability settings and termination rights.
• IP ownership needs careful drafting, especially where customisation, integrations or new development work are involved.
• Data rights matter from day one, including export access, deletion, retention and transition support at the end of the contract.
• Privacy, confidentiality and security terms should match the sensitivity of the information handled by the software.
• New Zealand businesses should be cautious about relying on standard terms, overseas governing law clauses or verbal promises that never make it into the agreement.
• If you are licensing out your own software, tailored customer terms can help protect your IP, manage support expectations and reduce payment and liability disputes.

If you want help with licence scope, IP ownership, liability clauses, and privacy and data terms, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.