Digital Product Licence Terms for New Zealand Businesses

Digital product licence terms decide what your business can actually do with software, templates, online courses, digital downloads, data feeds and other digital assets. Many New Zealand businesses sign fast, assume a purchase means full ownership, or miss restrictions buried in standard terms. That is where expensive problems start, especially when a team shares logins, modifies code, resells content, or rolls a tool out to clients without the right permissions.

If you are reviewing digital product licence terms, the key questions are usually practical ones. Can you copy it, customise it, sublicence it, use it across multiple entities, or keep using it after the contract ends? This guide explains what digital product licence terms mean for New Zealand businesses, the legal issues to check before you sign, and the common mistakes that catch founders and SMEs when they accept a provider's standard terms too quickly.

Overview

Digital product licence terms set the rules for how a business may access and use a digital product. In New Zealand, those terms often sit alongside wider contract, consumer law, privacy and intellectual property issues, so the wording matters well beyond a simple tick box at checkout.

A good contract review should tell you whether the licence matches how your business actually operates now and how you expect to use the product later.

• who owns the intellectual property and what rights your business receives
• whether the licence is exclusive or non-exclusive, transferable or non-transferable
• user limits, device limits, seat limits and related entity restrictions
• whether you can modify, integrate, reverse engineer or create derivative works
• rules on resale, sublicensing, white labelling or client use
• payment structure, renewals, upgrades and price change rights
• termination rights and what happens to your access, stored data and work product after the agreement ends
• warranties, service levels, liability caps and indemnities
• privacy, security and data handling obligations if personal information is involved
• marketing claims and disclosure obligations under New Zealand fair trading rules

What Digital Product Licence Terms Means For New Zealand Businesses

Digital product licence terms are not just admin, they define the boundaries of use, risk and value in the deal.

When a business buys a digital product, it usually does not buy the underlying intellectual property. Instead, it gets permission to use the product in a specific way. That permission may be narrow or broad, temporary or ongoing, and tied to strict conditions.

For example, a design studio might pay for a premium font library, but the licence may only allow internal use on a set number of devices. A SaaS platform may permit one company entity to use the software, but not contractors, franchisees or related companies. An education business may buy course content for internal staff training, but not for resale to customers.

This distinction matters because the main risk is assuming commercial freedom where the contract only grants limited permission. Before you sign a contract, make sure the licence reflects the actual use case inside your business.

Licence terms usually deal with permission, not ownership

The provider will generally keep ownership of the software, content, code, graphics, data set or digital asset. Your business receives a licence, which is the legal right to use that asset on agreed terms.

That licence may be:

• perpetual or time-limited
• paid once or subscription-based
• exclusive or non-exclusive
• revocable or irrevocable in limited circumstances
• limited to internal business use, or broad enough to support customer-facing use

The wording matters because each of these settings affects value. A perpetual internal-use licence is very different from a short-term, non-transferable licence that disappears if you miss a renewal payment.

Digital licences often affect more than one part of the business

A single set of licence terms can touch multiple business functions. Founders often focus on price and features, but legal restrictions can flow into operations, marketing and customer delivery.

Common touchpoints include:

• sales teams using licensed materials in client proposals
• developers integrating licensed code into a product
• marketing staff republishing licensed images, audio or copy
• support teams accessing customer data through a licensed platform
• group companies sharing one account across separate entities

If the licence is drafted narrowly, ordinary business behaviour can turn into a breach. This is where founders often get caught, especially before they scale, hire contractors or offer a service to new customer segments.

New Zealand legal context still matters, even with overseas providers

Many digital products used by New Zealand businesses are supplied under overseas standard terms. Even so, your business still needs to think about New Zealand legal obligations.

For instance, if a provider makes claims about functionality, compatibility or performance, those claims may affect your rights and risk under contract and fair trading law. If the product handles personal information, your business also needs to think about Privacy Act obligations, especially around transparency, security, third party access and cross-border data use.

For some arrangements, service-style obligations may also matter. A digital product may come with support, hosting, maintenance, updates, onboarding or implementation. That means the agreement is not just a licence, it may also include service promises, limitations and exclusions that need careful review.

Legal Issues To Check Before You Sign

The best time to fix a licence problem is before you accept the provider's standard terms.

Once your team has built systems around a digital product, your bargaining power usually drops. A careful review at the start can save a messy renegotiation later, particularly when the product becomes business-critical.

Scope of use

The first issue is whether the licence actually covers your intended use. Do not rely on product pages or sales emails alone. The contract needs to say what your business can do.

Check whether the licence allows:

• internal business use only, or external customer-facing use
• use by employees, contractors, consultants and related entities
• installation on multiple devices or environments
• use in New Zealand only, or globally
• commercial use, including use in paid services or products

If you plan to embed the digital product into your own offering, white label it, or let clients access it, make sure the licence expressly permits that. A standard internal-use licence often will not.

Intellectual property ownership and derivative works

Your business should know what it owns, what the provider owns, and who owns any modifications or outputs created during use.

That point is especially important for software tools, AI-enabled products, templates, code libraries and custom configurations. Some agreements say the provider owns all improvements, customisations or feedback. Others allow you to own your specific work product but not the underlying platform.

Before you sign, check:

• whether you may adapt, customise or translate the product
• whether derivative works are allowed
• who owns configurations, user-generated content and implementation materials
• whether feedback or suggestions can be used by the provider without restriction
• whether your existing intellectual property stays yours

This matters when your team spends real money tailoring the tool to your business. You do not want to discover later that useful custom work cannot be exported or reused.

Restrictions and prohibited conduct

Most digital product licences contain a list of things you must not do. Some are expected, such as prohibitions on reverse engineering or sharing access credentials. Others are broad enough to interfere with ordinary commercial use.

Read the restrictions carefully, especially around:

• sublicensing or granting access to clients
• benchmarking or publishing performance results
• using the product with competing services
• copying, scraping, downloading or extracting data
• security testing, interoperability work or API usage

If a restriction cuts across your workflow, raise it before you sign. It is much easier to get an exception written into the written terms early than to argue about implied permission later.

Fees, renewals and pricing mechanics

Price is not just the headline subscription fee. The legal issue is how the agreement lets the supplier charge and change charges over time.

Some licence terms allow automatic renewal, unilateral fee increases, extra charges for storage, overuse fees, support tiers or paid upgrades. Others tie usage rights to prompt payment and suspend access quickly after default.

Look closely at:

• when renewals happen and how to opt out
• whether fees can increase mid-term or only on renewal
• what happens if user numbers grow
• whether implementation, migration or support fees sit outside the licence fee
• refund rights if the product does not meet key promises

For any tax treatment questions, speak with your accountant or tax adviser.

Term, termination and exit rights

Every business should know how the relationship ends and what happens next.

A supplier-friendly agreement may allow immediate termination for broad breaches, suspected misuse or convenience, while your business has limited termination rights. That can leave you exposed if the product underperforms or if your business needs to switch systems.

Check the contract for:

• fixed term versus rolling term arrangements
• termination for breach, insolvency or convenience
• cure periods to fix non-payment or technical breaches
• post-termination access to data, content and records
• obligations to delete copies or stop using embedded components

If your business depends on the product for core operations, negotiate a reasonable transition period or data export right before you sign.

Warranties, support and liability allocation

The contract should match the level of reliability your business needs.

Many standard digital product licence terms disclaim broad warranties and cap the provider's liability at a low level, sometimes only the fees paid in a short recent period. That may be acceptable for a low-cost tool, but not for software that underpins revenue, customer delivery or regulatory compliance.

Focus on:

• whether the product is promised to perform substantially as described
• response times, support windows and update commitments
• liability caps and whether they apply per claim or in aggregate
• which losses are excluded, such as indirect loss, lost profits or data loss
• indemnities for intellectual property infringement, misuse or third party claims

There is no standard answer here. The right position depends on the product's cost, importance and the damage a failure could cause.

Privacy, data use and security

If the digital product handles personal information, privacy terms need careful attention.

New Zealand businesses that collect, store or use personal information still need to comply with the Privacy Act, even when an overseas software provider processes data on their behalf. That means your business should understand where data goes, who can access it, and what the provider promises about protection and breach response.

Review:

• what categories of data the provider collects and why
• whether the provider can use your data for analytics, training or product improvement
• where data is stored and whether overseas transfers occur
• security commitments, audit rights and breach notification processes
• how data is returned or deleted on exit

If customer data is involved, your privacy notice, disclosures and internal processes may also need updating.

Common Mistakes With Digital Product Licence Terms

The most common mistake is treating a digital licence like an ordinary purchase order.

Founders often move quickly because the product seems low risk, the monthly fee looks modest, or the supplier says everyone uses the same terms. But small licence mistakes can become expensive when they affect scaling, resale or business continuity.

Assuming payment means ownership

Paying for access does not usually give your business ownership of the digital product. It gives permission to use it within the limits of the agreement.

This creates problems when a business later tries to:

• copy materials into a client deliverable
• reuse code in another product
• sell or assign the asset as part of a business sale
• move the product to a new entity after a restructure

If ownership or transfer flexibility matters, the contract needs to deal with it clearly.

Ignoring group company and contractor use

Many SMEs use contractors, offshore developers, virtual assistants or separate related entities. Standard licence terms often limit access to one legal entity and its direct employees only.

That means a perfectly normal arrangement inside your business can breach the contract. Before you sign, map who will actually use the product, not just who pays the invoice.

Missing restrictions on client work and resale

This issue often appears in agencies, consultants, education businesses and software companies. A product that works for internal use may not be licensed for client delivery, white labelling or onward sale.

If your revenue model depends on customer access, sublicensing, embedded use or resale, that must be checked early. Otherwise, your business may build an offer around rights it never had.

Accepting weak exit terms for a business-critical product

Another common mistake is focusing on onboarding and ignoring the end of the relationship. This usually surfaces only when prices rise, the provider is acquired, or your business wants to migrate.

Without clear exit terms, you may face:

• loss of access to historical records
• short deadlines to export data
• extra extraction or transition fees
• uncertainty about continued use of outputs or embedded components

That is why post-termination rights should be reviewed before you accept the provider's standard terms.

Overlooking conflicting promises in sales material

Sales demonstrations, onboarding calls and proposal documents often contain statements about functionality, uptime, compatibility or future features. The written contract may then include broad disclaimers saying the business has not relied on any outside statements.

If a feature is commercially important, get it into the agreement. Do not assume a verbal assurance will help if the contract says otherwise.

Forgetting related legal documents

Digital product licence terms rarely stand alone. Depending on the product, your business may also need aligned customer contracts, contractor agreements, privacy disclosures, acceptable use rules or intellectual property assignments.

For example, if your own service relies on a licensed platform, your customer terms should reflect any usage limits or service boundaries that sit upstream. If contractors are accessing licensed systems, their contracts should deal with confidentiality, intellectual property and proper use.

FAQs

Do digital product licence terms need to be in a signed contract?

No. They can be binding through an online click-through process, checkout acceptance, order form, account signup flow or incorporated standard terms. The real issue is whether the terms were properly presented and accepted.

Can my business share one digital licence across related companies?

Not automatically. Many licences are limited to one named legal entity. If your group structure includes multiple companies, trusts or franchisees, the contract should expressly allow that use.

Can we modify a digital product after we license it?

Only if the licence allows it. Some agreements permit configuration but prohibit code changes, derivative works or reverse engineering. Check the wording before your team starts customising anything.

What happens if the provider terminates our licence?

That depends on the contract. You may lose access immediately, need to stop all use, delete local copies, and export data within a short period. For important systems, negotiate a transition period and data return process before you sign.

Do New Zealand privacy rules matter if the software provider is overseas?

Yes. If your business collects or handles personal information, New Zealand privacy obligations can still apply. You should understand the provider's data handling, overseas storage, security protections and breach response commitments.

Key Takeaways

• Digital product licence terms usually grant limited permission to use a product, not ownership of the underlying intellectual property.
• The key legal question is whether the licence matches your actual business use, including contractor access, related entities, customer-facing use, integrations and resale plans.
• Before you sign, review scope of use, intellectual property ownership, restrictions, fees, renewals, termination rights, liability allocation and privacy terms.
• Common mistakes include assuming payment equals ownership, ignoring entity and user limits, missing resale restrictions, and accepting poor data exit rights.
• If a sales promise or feature matters to your business, get it into the written agreement rather than relying on informal statements.
• Business-critical digital products should have clear support, security, liability and transition terms that reflect the practical risk to your operations.

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