End User Licence Agreement: What Is It And Why Do I Need One? (2026 Updated)

If you’re building or selling software in New Zealand, there’s a good chance you’ve already heard the term “EULA” (End User Licence Agreement). Sometimes it gets treated like a box-ticking exercise - the thing users scroll past and click “Accept”.

But from a legal perspective, a well-drafted EULA can be one of the most important documents in your entire product stack. It sets the ground rules for how customers can use your software, what happens if something goes wrong, and how you’ll protect your IP from day one.

This guide is updated to reflect what we’re seeing right now in the NZ market: more SaaS products, more app-based services, more subscription models, and more privacy and consumer-law scrutiny. If you’re relying on an outdated template (or you don’t have a EULA at all), it’s worth revisiting your legal foundations.

What Is An End User Licence Agreement (EULA)?

An End User Licence Agreement (EULA) is a contract between you (the software owner/licensor) and the person or business using your software (the end user/licensee).

At its core, a EULA does one key thing:

• It confirms you’re licensing the software, not selling it.

That distinction matters because software isn’t like a physical product where ownership transfers on purchase. In most cases, you want to keep ownership of the underlying intellectual property (your code, UI, content, features, databases, and brand assets) and give users a limited right to use it.

A practical way to think about it is:

• You own the software.
• Your customer has permission (a licence) to use it under certain conditions.
• If they breach those conditions, you may be able to suspend or terminate their access.

EULAs commonly appear for:

• downloadable software (desktop apps, plugins, games)
• mobile apps
• SaaS products (sometimes combined with platform terms)
• IoT products where software runs on hardware
• APIs and developer tools (often alongside API terms)

Depending on how you deliver your product, your EULA might be a standalone document or part of broader terms, like Terms of Use for a platform.

Do I Actually Need A EULA If I Have Terms And Conditions?

Sometimes. But not always.

A lot of businesses put one generic “terms and conditions” page on their website and assume that covers everything. The problem is that software has unique risks and unique IP issues - and a EULA is designed to address them directly.

Here’s the key difference in plain English:

• Website terms/terms of use usually deal with using your website or platform generally (browsing, accounts, prohibited behaviour, content rules).
• A EULA is specifically about licensing software and controlling how your software can be installed, accessed, copied, modified, shared, and used.

In practice, many SaaS businesses use a bundle of documents that work together, such as:

• platform or website Terms of Use
• a EULA (especially where software is downloaded or installed)
• subscription/payment terms (billing, renewals, upgrades, cancellation)
• a Privacy Policy (if you collect personal information)
• sometimes a service contract or Master Services Agreement for enterprise customers

If you’re unsure what you need, it usually comes down to how you deliver your product and who your customers are (consumers vs businesses). Getting the document set right early can save you a lot of painful rework later - especially when you start scaling, taking investment, or dealing with larger clients.

What Should A NZ EULA Cover?

A strong EULA is more than a copyright notice. It should be tailored to your software, your user base, and how you actually make money.

Below are the clauses we commonly see in a well-drafted New Zealand EULA, along with why they matter.

1. The Licence Grant (What Users Can And Can’t Do)

This section sets out what you’re allowing the user to do - and what’s off-limits.

A EULA often covers:

• whether the licence is personal, business, or enterprise
• whether it’s non-exclusive, non-transferable, revocable, etc.
• where the software can be used (territory restrictions, if any)
• how many devices/users are allowed
• whether sublicensing is prohibited

This is also where you spell out the big “don’ts”, like prohibiting reverse engineering, copying, selling, reselling, or trying to bypass usage limits.

2. Ownership Of Intellectual Property

Your EULA should make it crystal clear that:

• you own the software and all related intellectual property
• the user is only getting a limited right to use it
• any rights not expressly granted are reserved by you

This is particularly important if your software includes updates, proprietary features, or unique content, and you want to avoid arguments like “we paid for it, so we own it”.

If your business is also licensing code or content to third parties, you may need a separate IP Licence agreement (a EULA is usually aimed at end users rather than commercial licensing deals).

3. Updates, Patches, And Changes

Modern software changes constantly. If your EULA is silent on updates, you can end up in messy disputes about what the customer “paid for” and what they’re entitled to receive.

Your EULA can set expectations around:

• automatic updates (and whether users can opt out)
• feature changes or removals
• maintenance windows and downtime
• security patches

This is also a good place to align your EULA with your product roadmap reality - because if your legal terms promise stability and your product changes weekly, you’re setting yourself up for conflict.

4. User Accounts, Acceptable Use, And Misuse

If users access your software via accounts (common for SaaS), your EULA or related terms should cover:

• account security responsibilities
• prohibited conduct (e.g. uploading harmful content, harassment, illegal use)
• rate limits, scraping restrictions, and anti-bot rules
• what happens if a user breaches the rules

If your platform includes user-generated content or community features, “acceptable use” clauses become even more important.

5. Privacy And Data Handling (Especially If You Track Behaviour)

Most software products collect data - even if it’s just login details, billing info, or usage analytics.

In New Zealand, the Privacy Act 2020 sets rules around how you collect, store, use, and disclose personal information. Your EULA can work alongside your Privacy Policy to explain what data you collect and what you do with it.

Common examples where privacy issues pop up include:

• analytics and tracking tools (cookies, device identifiers, in-app tracking)
• crash reporting
• location services
• integrations with third-party services
• customer support logs and recordings

Privacy isn’t just about compliance - it’s also about trust. Clear terms reduce friction in enterprise deals and help you answer security questionnaires with confidence.

6. Fees, Subscriptions, And Payments (If Relevant)

Some EULAs include billing terms, while others sit alongside separate subscription terms. Either way, you want the legal documents to match how your pricing works.

For example, you may need to cover:

• free trials and what happens when they end
• renewals (monthly/annual)
• price changes
• late payments and suspension
• refund rules

If you sell to consumers (not just businesses), you should also keep the Consumer Guarantees Act 1993 and Fair Trading Act 1986 front of mind when drafting payment and refund language. You generally can’t contract out of key consumer protections in a way that’s misleading or unfair.

7. Disclaimers And Limitation Of Liability

This is the section that can protect you when something goes wrong - for example, the software causes downtime, data loss, or doesn’t integrate properly with the user’s systems.

A EULA often includes:

• disclaimers about availability and performance (e.g. “as is” / “as available” where appropriate)
• limits on the types of loss you’re responsible for (e.g. indirect or consequential loss)
• caps on liability (for example, limited to fees paid in a period)
• requirements for users to mitigate losses and back up data

These clauses need to be drafted carefully. In NZ, some limitations may not be enforceable in all situations, and consumer law can restrict your ability to exclude certain guarantees. The goal is to manage risk realistically and fairly, not to overreach.

It can also be worth aligning your EULA wording with any separate limitation of liability approach you use across your contracts, so your documents don’t contradict each other.

8. Termination And Suspension

Most software businesses need a clear right to suspend or terminate access if:

• a user breaches the agreement
• they don’t pay
• there’s suspected fraud, abuse, or security threats
• you’re required to do so by law

It’s also important to define what happens after termination, such as:

• access cut-off timelines
• whether the user can export data (and how)
• what licences end and what clauses survive (like IP and liability clauses)

9. Governing Law And Jurisdiction

If you’re a New Zealand business, you’ll often want New Zealand law to apply and disputes to be handled in New Zealand. This can be particularly important if you sell online and users could be anywhere.

That said, if you operate internationally, your approach may need to reflect where your customers are located and what your commercial leverage looks like.

How Does A EULA Protect My Business In Real Life?

A EULA isn’t just legal “paperwork” - it’s a practical tool for preventing disputes and giving you options when a customer relationship goes sideways.

Here are some common real-world situations where having the right EULA in place can make a big difference.

A Customer Misuses Your Software Or Shares Logins

Imagine you sell a per-seat subscription, but a client shares one login across ten staff. If your EULA clearly limits usage and gives you audit/suspension rights, you’re in a stronger position to enforce the rules and protect your revenue.

Someone Copies Your Product Or Tries To Reverse Engineer It

You can’t stop all bad actors, but a EULA can:

• clearly prohibit reverse engineering and copying
• support enforcement action by showing the user agreed to restrictions
• strengthen your position in negotiations if you need to send a formal demand

Your App Has A Bug And A User Threatens Legal Action

No software is perfect. If your EULA is silent on limitations, users may argue they’re entitled to broader remedies than you expected.

A well-drafted EULA helps set expectations around:

• what you’re responsible for fixing
• what the user is responsible for (like backups)
• how disputes are handled
• how liability is limited (where legally allowed)

You Need To Change Features Or Retire An Old Version

If your business evolves, your product will too. Your EULA can reserve rights to modify, update, or discontinue parts of the software - which is important if you don’t want to be locked into supporting legacy functionality forever.

You Want To Look “Enterprise Ready”

When a bigger customer is considering your product, they’ll often ask for:

• terms that clearly cover security and data responsibilities
• clear IP ownership
• enforceable limitation of liability clauses
• professional documentation that matches your business model

A tailored EULA can be part of presenting your business as mature, credible, and ready to scale.

What NZ Laws Should I Keep In Mind When Drafting A EULA?

Even though a EULA is “your” contract, you can’t write whatever you want and assume it will hold up. New Zealand law sets the boundaries of what’s enforceable - especially when your users are consumers.

Some key legal areas to keep in mind include:

Consumer Law (Fair Trading Act 1986 And Consumer Guarantees Act 1993)

If you sell software to individuals for personal use, the Consumer Guarantees Act 1993 can apply, and you may not be able to exclude certain guarantees (like acceptable quality and fitness for purpose) in the way you might for a business-to-business product.

The Fair Trading Act 1986 also matters because it prohibits misleading or deceptive conduct. That means your marketing claims, pricing representations, and what you promise in the EULA/terms all need to line up.

Privacy Act 2020

If you collect personal information, you’ll need to handle it in line with the Privacy Act 2020 - including having a clear reason for collecting it, securing it properly, and only using it in ways you’ve disclosed.

Practically, your EULA and Privacy Policy should work together so users aren’t surprised by what’s happening with their data.

Contract Law And Unfair Terms Risks

Even in business-to-business arrangements, terms that are unclear, inconsistent, or overly one-sided can create problems - including disputes about what the agreement actually means.

Clarity is your best friend here. A EULA should read in plain English and match the product experience you’re delivering.

How Do I Make My EULA Enforceable Online?

A common mistake is having a beautifully drafted EULA… and then failing to actually form a proper agreement with the user.

For online and software products, enforceability often comes down to how acceptance happens.

Use “Clickwrap” Acceptance Where Possible

Clickwrap is when the user has to actively agree (for example, ticking a box or clicking “I agree”) before creating an account, installing software, or completing checkout.

This is generally stronger than “browsewrap” terms, where you simply link to terms in the footer and assume continued use equals acceptance.

Make Sure Users Can Access The Terms

Users should be able to view the EULA easily at the point they’re agreeing. If it’s buried or hard to find, you’re inviting arguments later that they didn’t know what they were agreeing to.

Keep Records

If there’s a dispute, it helps to be able to show:

• what version of the EULA applied at the time
• when the user accepted it
• how acceptance occurred

This is especially relevant if you update your terms over time. If you’re regularly evolving your product and conditions, it may also be worth having a broader Software Licence Agreement strategy that fits your commercial model.

Key Takeaways

• An End User Licence Agreement (EULA) is the contract that sets the rules for how users can use your software, and it confirms you’re licensing the software rather than selling it.
• A tailored EULA can protect your intellectual property, control misuse (like password sharing or reverse engineering), and help you manage disputes when things go wrong.
• A good NZ EULA usually covers the licence grant, IP ownership, updates, acceptable use, privacy and data handling, payments (if relevant), limitation of liability, and termination rights.
• Your EULA should align with New Zealand legal obligations like the Privacy Act 2020, Fair Trading Act 1986, and Consumer Guarantees Act 1993, especially if you sell to consumers.
• How users accept your EULA matters - clickwrap acceptance and good version control make the agreement far easier to enforce.
• Template EULAs often miss the details that matter for your specific product, revenue model, and risk profile, so it’s worth getting it drafted properly.

If you’d like help drafting or updating a EULA (or making sure your software terms work properly alongside your privacy and subscription documents), you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.