EULAs for New Zealand Businesses: What End User Licence Agreements Cover

EULA stands for End User License Agreement. If your business buys, downloads, resells, develops or relies on software, this document can quietly control what you are actually allowed to do with that software, and what happens when something goes wrong.

Founders often make the same mistakes. They assume a software subscription means ownership, they accept standard terms without checking licence limits, or they rely on a sales promise that never makes it into the contract. Those errors can turn into unexpected fees, data access problems, usage restrictions, or disputes about liability when a platform fails.

This guide explains what a EULA is, what a software licence agreement usually covers, and what New Zealand businesses should check before signing. It also looks at common traps, especially where software is business-critical, stores customer information, or is being rolled out across a team.

Overview

A EULA is a contract that gives the end user permission to use software under set conditions. It does not usually transfer ownership of the software itself, and the wording can heavily affect access, support, data rights, termination, warranties and liability.

For New Zealand businesses, the legal risk is often less about the label and more about the detail buried in the terms you accept before you install, subscribe or renew.

• Check whether the licence is for one user, one device, one business entity, or a wider group.
• Confirm what you can and cannot do, including copying, modifying, integrating, reselling or giving contractors access.
• Review termination rights, suspension clauses and what happens to your data when the agreement ends.
• Check liability caps, warranty exclusions and whether the supplier is avoiding responsibility for outages, errors or security issues.
• Look for privacy, confidentiality and data protection terms, especially if personal information will be processed offshore.
• Make sure important sales promises, service levels and support commitments appear in the written agreement.

What a Software Licence Agreement Covers

A software licence agreement sets the rules for use. The main point is simple: your business is usually getting permission to use software, not buying the intellectual property behind it.

What does EULA stand for?

EULA stands for End User License Agreement. You will often see it when downloading software, signing up to SaaS products, installing apps on company devices, or purchasing enterprise platforms.

Although the wording varies, a EULA is usually a form of contract between the software provider and the end user. In some cases it appears as a clickwrap agreement. In others, it sits inside a master services agreement, order form or subscription terms.

Licence scope

The licence scope tells you exactly what use is allowed. This is where founders often get caught, especially before they accept the provider's standard terms for a whole team.

Key scope issues often include:

• how many users, devices or locations are covered
• whether affiliates or related companies can use the software
• whether contractors can access the system
• whether the licence is exclusive or non-exclusive
• whether the licence can be transferred if you sell the business or restructure
• whether use is limited to internal business purposes

A startup may sign up for a platform on a single-user basis, then share logins across staff or contractors. That can breach the agreement even if no one intended to misuse the software.

Restrictions on use

Most EULAs contain restrictions. Some are standard, some are surprisingly broad.

Common restrictions include:

• no copying except for backup or permitted technical use
• no reverse engineering, decompiling or modifying the software
• no sublicensing, reselling or white-labelling without permission
• no use in prohibited industries or high-risk environments
• no removal of copyright notices or proprietary labels
• no benchmarking or publishing performance results

These clauses matter if your business plans to integrate the software into its own product, use it in a client-facing service, or rely on a developer to customise it.

Ownership and intellectual property

The provider usually keeps ownership of the software, code, branding and related intellectual property. Your business gets a limited licence only.

The agreement should also clarify ownership of:

• custom developments
• configurations and templates
• feedback and suggestions you provide
• data entered into the platform
• reports or outputs generated by the software

This becomes especially important where your business is paying for setup, customisation or integration work. Before you spend money on setup, make sure the contract says who owns what and what rights each side has to reuse it.

Fees, renewals and pricing changes

A EULA or related subscription contract often deals with payment terms. The risk is not just the subscription price, but how easily the provider can increase fees, auto-renew the term, or charge for overuse.

Look closely at:

• renewal periods and notice windows
• user-based or usage-based pricing
• setup, onboarding or migration fees
• charges for support, training or API access
• late payment consequences, including suspension

If the software is central to your operations, a suspension clause can have real commercial consequences. The effect may be immediate, especially if your team cannot access records, customer data or workflows.

Support, updates and service levels

Many business owners assume software support is included. Often, the written terms say otherwise.

The agreement may limit support to business hours, exclude custom issues, or allow the provider to change features without notice. If uptime, response times or escalation processes matter to your business, those terms should be express.

Where software downtime would disrupt customers or staff, it is worth checking:

• whether the provider gives any uptime commitment
• how maintenance windows are handled
• what support channels are available
• whether credits or remedies apply if service levels are missed
• whether updates could remove functionality you rely on

Data, privacy and security

If the software stores customer or employee information, privacy terms are not a side issue. New Zealand businesses still need to meet their own obligations under the Privacy Act 2020, even when a third-party software provider handles data.

Before you sign, confirm:

• what personal information the provider collects and processes
• where the data is stored or accessed from
• whether subcontractors or overseas hosting providers are involved
• what security measures the provider commits to
• how breaches are notified and managed
• how long data is retained after termination

A supplier's privacy policy may explain some of this, but your contract position still matters. If data handling is business-critical, the provider may need to agree to additional privacy notice or security terms.

Legal Issues To Check Before You Sign

The safest approach is to read a EULA like any other commercial contract. Before you sign a contract, the key question is not whether the software looks reputable, but whether the legal terms match how your business will actually use it.

Does the agreement reflect the sales discussion?

Verbal promises are risky. If a salesperson says the platform can do something important, support a particular integration, or meet a compliance need, that promise should appear in the written terms or attached specifications.

Many contracts include entire agreement clauses. That means the written document may override informal assurances given in demos, emails or calls. Before you rely on a verbal promise, get it recorded properly.

Who is the contracting party?

This sounds basic, but it matters. Some software providers contract through an overseas parent, a local reseller, or a regional subsidiary. You need to know exactly who is licensing the software and who is responsible if there is a problem.

For group structures, also check whether the New Zealand company signing the deal can let related entities use the software. If not, you may need the agreement to cover the wider corporate group.

What law applies, and where would disputes be dealt with?

Many software contracts are governed by overseas law. That is not always a deal-breaker, but it can make enforcement harder and negotiation more expensive.

For a New Zealand SME, foreign governing law and overseas jurisdiction clauses can create practical problems, especially where the contract value is modest but the software is important. It is worth understanding the commercial impact before you accept those terms.

How broad are the warranty exclusions?

Software agreements often exclude almost every warranty possible. The provider may say the software is supplied "as is" and may disclaim accuracy, continuous availability, fitness for purpose and non-infringement.

That wording shifts a lot of risk onto the customer. For business users, contractual exclusions can be broad, particularly where the arrangement is business-to-business. Even so, the wording should be reviewed carefully, especially if your team will rely on the software for customer delivery, financial reporting or regulated activities.

How low is the liability cap?

This is one of the most important clauses in the contract. A provider may cap its liability at a very low figure, such as the fees paid in the last month or year, even if the outage causes serious disruption to your business.

Look at:

• the amount of the cap
• whether it applies per claim or in total
• whether confidentiality, privacy breaches or IP infringement are carved out
• whether indirect or consequential loss is excluded
• whether service credits are your only remedy

If the software sits at the centre of your operations, a very low cap may not be commercially workable.

What happens on termination?

Termination rights can decide how much control you really have. Some agreements let the provider suspend or terminate access quickly for non-payment, policy breaches or suspected misuse.

You should check:

• how much notice is required for termination without cause
• whether you can terminate for repeated service failures
• what happens to prepaid fees
• how long you have to export your data
• whether the provider must assist with transition or migration

This matters before you sign because the practical pain often shows up at the end of the relationship, not the start.

Are there consumer law or fair trading issues?

Business software deals can still raise issues around marketing accuracy and contract fairness. In New Zealand, businesses should be careful about claims made to customers and claims made by suppliers to them. If a product is described in a misleading way, or key limitations are hidden, that can create risk under fair trading principles.

Where the software is on-sold, bundled into your own offering, or marketed to customers through your business, your own contracts and disclosures also need to line up with what the software can actually do.

Common Software Licence Agreement Mistakes

The most common mistake is treating a EULA as a harmless click-through form. For many SMEs, it is a key operational contract and deserves the same attention as a supply agreement or major customer contract.

Assuming payment means ownership

Paying for software does not usually mean you own the code or underlying IP. It usually means you have a limited right to use it.

This misunderstanding can surface later if you try to copy features, migrate custom elements, or keep using the software after termination. Ownership wording should be clear from the start.

Ignoring user limits

Teams grow quickly. A founder may buy a low-tier subscription, then allow staff, contractors or offshore support to use shared credentials.

That can breach the licence and trigger extra fees, audit rights or suspension. If your team structure is changing, check the user model before you accept the terms.

Not checking audit rights

Some software providers reserve the right to audit your use. That may include access to records, systems or usage data to confirm compliance with licence terms.

Audit clauses should be proportionate. You do not want an open-ended right that disrupts your business or exposes confidential information without safeguards.

Overlooking data exit terms

Businesses often focus on signing up, not moving out. That is a mistake when the platform holds customer information, contracts, project files or reporting history.

If the agreement is silent, you may have limited time to export data, or the provider may charge high extraction fees. Before you sign, understand your exit path.

Failing to address privacy and security upfront

If the software handles personal information, founders sometimes assume the provider has privacy covered. Your business still has responsibilities to customers, staff and contacts whose information you collect and use.

You should know whether the provider stores data offshore, whether subcontractors are involved, and how incidents are reported. This is especially relevant for online businesses, health-adjacent services, education providers, recruitment platforms and any business with a high volume of customer records.

Accepting one-sided variation clauses

Some EULAs let the provider change the terms at any time by posting an update. That can leave your business exposed to shifting fees, new restrictions, or reduced service commitments after you are already locked in.

For business-critical systems, try to pin down the version of terms that applies during the contract term, or at least secure notice and a right to exit if changes are material.

Relying on the supplier's template without matching your own contracts

If your business delivers services using licensed software, your own customer contracts should match reality. Do not promise unlimited uptime, ownership of third-party platforms, or features the software provider can remove.

This is where founders often get caught. The provider's EULA may contain strict exclusions, while your client agreement gives much broader promises. That gap can leave your business carrying risk that cannot be passed back upstream.

FAQs

Is a EULA legally binding in New Zealand?

Usually, yes. If the terms are properly presented and accepted, such as through a click-to-accept process or signed contract, a EULA can be legally binding. The exact enforceability depends on the wording, how acceptance occurred, and the surrounding facts.

Is a EULA the same as terms and conditions?

Not exactly. A EULA is a specific type of contract dealing with software use rights. It may sit alongside broader terms and conditions covering subscriptions, support, payments, privacy and services.

Can a software provider change the EULA after I sign?

Sometimes, if the contract allows it. The real question is how broad that right is, whether notice must be given, and whether your business can terminate if changes are significant.

Do I need a lawyer to review a software licence agreement?

Not for every low-risk tool, but it is often sensible where the software is expensive, stores sensitive data, supports customer delivery, or includes customisation, integration or long contract terms. A contract review can help spot issues before you accept the provider's standard terms.

What should I do if the EULA conflicts with what I was told in a demo?

Ask for the agreed points to be added to the contract, order form or specifications before you sign. If it is not written down, it may be difficult to enforce later.

Key Takeaways

• EULA stands for End User License Agreement, and it usually gives your business a limited right to use software rather than ownership of it.
• The most important clauses usually deal with licence scope, restrictions, renewals, data rights, termination, warranties, privacy and liability.
• Before you sign, check whether the written agreement matches the sales discussion and whether critical promises are recorded properly.
• New Zealand businesses should pay close attention to privacy obligations, offshore data handling, marketing accuracy and the practical effect of foreign law or jurisdiction clauses.
• Common mistakes include ignoring user limits, accepting low liability caps, overlooking data exit rights and treating click-through terms as low risk.
• If the software is central to your business, a legal review before you sign can save a lot of cost and disruption later.

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