Business Software Licensing Duties in New Zealand

Software is woven into almost every New Zealand business, but many founders still treat licences like a box-ticking exercise. That is where problems start. Common mistakes include assuming a one-off purchase means unlimited use, letting contractors install tools under personal accounts, and signing supplier terms without checking who owns customisations, data rights, or renewal obligations. Those issues can become expensive quickly, especially when your team grows, your software stack changes, or an audit lands on your desk.

Business software licensing affects more than IT. It can shape your contract risk, privacy obligations, customer promises, intellectual property position, and day-to-day operating costs. If you are buying software, developing it, reselling it, or using it to deliver services, you need to know what your licence actually allows and what it prohibits.

This guide explains what business software licensing means in New Zealand, when it usually becomes a legal issue, and the practical steps to take before you sign a contract or spend money on setup.

Overview

Business software licensing sets the rules for how your business can access, install, modify, share, and commercialise software. The fine print matters because a licence can limit user numbers, locations, integrations, data use, resale rights, custom development, and even how long you can keep using the platform.

For New Zealand businesses, the main job is to match the licence terms to the way the business actually operates. That means checking your internal use, customer use, contractor access, privacy settings, and exit rights before you commit.

• Identify whether you are a buyer, user, developer, reseller, or all three
• Check who can use the software, on what devices, and in what locations
• Review fees, auto-renewals, audit rights, and any penalties for overuse
• Confirm who owns custom code, integrations, data outputs, and improvements
• Assess privacy, data hosting, security, and confidentiality obligations
• Make sure customer contracts and customer terms line up with your software rights and limits
• Keep records of licences, seats, purchase terms, and authorised users
• Plan what happens if the vendor changes terms, increases price, or shuts the service

What Business Software Licensing Means For New Zealand Businesses

Business software licensing is a legal permission, not ownership of the software itself. In most cases, your business is paying for the right to use software on certain terms, not buying the underlying intellectual property.

That point catches businesses out because software can feel like any other business asset. You pay for it, your staff rely on it, and you may build your processes around it. But the licence agreement controls the scope of that use, and if your business goes outside that scope, you may be in breach even if you paid on time.

Licensing is usually a contract issue and an IP issue at the same time

The contract side covers pricing, duration, service levels, termination rights, liability caps, support, and renewal terms. The intellectual property side covers copyright, restrictions on copying or modifying the software, ownership of derivatives, and whether you can let others access it.

For example, a SaaS platform may let your employees log in but prohibit you from giving direct access to clients unless you have a reseller or white-label arrangement. A developer tool may permit internal business use but ban commercial redistribution. A design platform may allow use of templates but restrict trade mark use or transfer of account assets.

Licences come in different forms

The legal risks depend heavily on the type of software and the business model. Common examples include:

• Software as a service subscriptions
• Desktop or device-based licence agreements
• Enterprise software agreements with negotiated terms
• Open source software licences
• White-label or reseller software arrangements
• Custom software development agreements
• API access and integration licences

Each of these raises different questions. Open source software, for instance, may be free to use but still carry obligations around attribution, code disclosure, or licence compatibility. A custom build may involve arguments about whether your business owns the source code, receives only a limited licence, or has rights to future updates.

Your obligations often extend beyond the software contract itself

A software licence can affect how you market your services, what you promise customers, and how you handle personal information. If your software stores customer data, the Privacy Act 2020 may come into play. If your sales materials overstate what your software-enabled service can do, the Fair Trading Act 1986 may become relevant. If you sell technology solutions to customers, your own customer terms need to reflect the limits in the software you rely on.

This is where founders often get caught. They sign one vendor agreement, then make much broader promises to their customers without checking that the two documents align.

Software licensing also matters during setup and growth

When founders start a business in New Zealand, they often focus on registration, business structure, company setup, banking, and branding first. That makes sense, but software contracts deserve attention early too, especially if your business model depends on online delivery, ecommerce, customer portals, scheduling systems, or proprietary technology.

Before you launch online, ask whether the software stack you are using is licensed for commercial use, whether your contractors are using properly authorised accounts, and whether your trade mark, privacy policy, and customer contract settings match the tools you have chosen. Those are not separate issues. They often intersect.

When This Issue Comes Up

Business software licensing usually becomes a real problem at moments of change. The contract may sit quietly in the background until your business expands, pivots, signs a major customer, or gets into a dispute with a vendor or developer.

When you buy software for internal operations

The first common trigger is ordinary business use. You subscribe to accounting, HR, CRM, project management, or cybersecurity software and assume the standard terms are non-negotiable or low risk. Sometimes that is true. Sometimes the real issue is not negotiation, but understanding limits around users, affiliates, contractors, offshore access, and data storage.

If your team grows quickly, you can breach seat limits without meaning to. If a contractor signs up in their own name, your business may have no clear rights to the account or stored data when the relationship ends.

When you engage a developer or software agency

Custom software projects create some of the biggest licensing disputes. A founder pays for an app, website, plugin, or internal tool and assumes that payment means full ownership. The contract may say something quite different.

Key questions include:

• Who owns the source code and documentation
• Whether pre-existing code libraries remain the developer's property
• Whether your business gets an exclusive or non-exclusive licence
• Who can maintain the software later
• Whether the developer can reuse parts of the build for other clients

These points matter before you sign a contract, not after a relationship breaks down.

When you sell software-enabled services

Many SMEs are not pure software companies, but they rely on software to deliver what they sell. Think of logistics businesses using route software, agencies using reporting tools, healthcare providers using booking systems, or retailers using ecommerce platforms and plug-ins.

If your customer-facing service depends on third-party software, your customer agreements should not promise more than your upstream licence allows. That applies to uptime promises, feature commitments, data portability, and support obligations.

When you resell, distribute, or white-label software

If your business wants to package software for clients, you need express rights to do that. A standard business user licence is usually not enough. You may need a reseller agreement, distribution terms, or a white-label arrangement that covers branding, support responsibility, payment flows, and customer ownership.

This point is especially important for IT consultants, managed service providers, digital agencies, and ecommerce operators bundling apps or platforms into their offer.

When your software handles personal information

If the software collects, stores, or processes personal information, legal obligations go beyond the licence fee. You may need to review:

• What personal information is collected
• Where the data is hosted
• Who the vendor can share it with
• What security standards apply
• How long data is retained after termination
• What your privacy policy says to customers and staff

If an overseas vendor hosts data outside New Zealand, that can raise extra privacy questions. The contract and your internal privacy practices should line up.

When a vendor changes terms or prices

Another common flashpoint is renewal. Many software providers reserve wide rights to update terms, increase pricing, remove features, or discontinue support. Businesses only notice when the invoice changes or an important feature disappears.

If the software is mission-critical, this is not a minor issue. It can affect service delivery, customer commitments, budgeting, and business continuity.

Practical Steps And Common Mistakes

The best way to manage business software licensing is to treat it like a commercial risk review, not just a procurement task. A short check before you sign can prevent much larger disputes later.

Map how the software will actually be used

Start with your real-world use case. Do not rely on the vendor's product summary alone. Ask who will use the tool, whether clients will access it, whether contractors need logins, whether it will connect with other systems, and whether it forms part of the service you sell.

A useful internal checklist includes:

• Number of employees, contractors, and related entities needing access
• Whether use is internal only or customer-facing
• Whether any use occurs offshore
• Whether the software stores confidential or personal information
• Whether the software is core to delivery or replaceable

Read the licence scope closely

The main risk is using software in a way the licence does not permit. Check clauses dealing with user limits, subsidiaries, transfer rights, sublicensing, reverse engineering, modification, and integration.

Look carefully at any terms that prohibit commercial use, service bureau use, public-facing access, or redistribution. Those restrictions can be easy to miss in standard online terms.

Confirm ownership of customisations and outputs

If your business is paying for development, integrations, workflows, templates, or automations, clarify ownership in writing. The contract should spell out whether your business owns the custom work, receives a licence to use it, or shares rights with the supplier.

Also think about outputs. If software generates reports, designs, code, AI-assisted content, or customer-facing materials, check whether the terms say anything about ownership or permitted commercial use.

Check privacy and data handling terms

Software contracts often say a lot about what happens to data, but businesses skip those clauses because they feel technical. They are not just technical. They affect your legal obligations to customers, staff, and business partners.

Review points such as:

• Data location and cross-border hosting
• Security commitments and incident notification
• Backup and recovery arrangements
• Rights to retrieve data on exit
• Deletion timing after termination
• Use of subcontractors and third-party processors

If the software supports your website or online store, make sure your privacy policy and customer-facing notices reflect how the platform actually handles information.

Align your downstream contracts

If you deliver services using third-party software, your own contracts should reflect that reality. This does not mean copying the vendor terms into your customer agreement. It means setting realistic boundaries around availability, support, third-party dependencies, and data access.

For example, if a platform can suspend service for maintenance or security reasons, avoid promising uninterrupted availability to your clients unless you can genuinely stand behind it. If your licence limits use to certain features, do not advertise or contract for functionality you do not control.

Plan your exit before you commit

Every business should know how it would leave a software platform before it becomes dependent on it. Exit planning is part legal and part operational.

Check:

• How the contract can be terminated
• Whether notice periods apply
• Whether fees are refundable
• How data export works
• Whether there is migration support
• Whether access stops immediately or after a transition period

This is especially important before you spend money on setup, integrations, and staff training.

Keep proper records

A surprising number of licence disputes come down to poor recordkeeping. Businesses lose track of who accepted terms, which version applies, how many seats were purchased, or whether an account was opened in the business name.

Keep a simple register of software used across the business, including licences, renewals, user counts, billing contacts, and linked supplier terms. That helps with audits, budgeting, and business sales or investment due diligence.

Common mistakes to avoid

Several recurring errors cause trouble for startups and SMEs:

• Assuming payment means ownership of software or source code
• Using personal or contractor accounts for business-critical tools
• Ignoring automatic renewal clauses and price variation rights
• Allowing customers to access software without clear permission in the licence
• Failing to match customer promises with vendor limitations
• Overlooking privacy and confidentiality terms
• Using open source components without checking licence conditions
• Not protecting your own brand, trade mark, and business data when adopting a platform

These mistakes are common because software contracts often look operational rather than legal. In reality, they sit right at the centre of how many modern businesses run.

FAQs

Do I own software just because my business paid for it?

Usually no. Payment generally gives your business a licence to use the software on agreed terms. Ownership of the software and underlying intellectual property usually stays with the vendor or developer unless the contract clearly says otherwise.

Can my contractors use the same business software accounts as employees?

Only if the licence allows it. Some licences permit contractor access, while others limit use to employees only. It is safer to check the terms and keep accounts in the business name so access and data stay under your control.

What if I want to resell or white-label software to my clients?

A standard user licence is often not enough. You usually need a separate reseller, distribution, or white-label agreement that gives explicit rights to package, brand, or provide the software to customers.

Are privacy obligations relevant if the software is hosted overseas?

Yes. If personal information is involved, overseas hosting can raise extra privacy questions about access, storage, security, and disclosure. Your contract terms, privacy policy, and internal processes should all be consistent.

What should I check before signing a custom software development agreement?

Focus on ownership of code, licence rights, use of pre-existing materials, payment milestones, acceptance testing, support, maintenance, confidentiality, and what happens if the project ends early. Those points are much easier to settle before work begins.

Key Takeaways

• Business software licensing is about legal permission to use software, not automatic ownership of it.
• The most important question is whether the licence matches how your business actually operates, including staff, contractors, customers, integrations, and growth plans.
• Custom development work should clearly state who owns source code, customisations, and related intellectual property.
• Software terms can affect privacy compliance, customer contracts, marketing claims, confidentiality, and operational continuity.
• Auto-renewals, pricing changes, audit rights, and exit terms deserve close attention before you sign.
• Good recordkeeping and aligned contracts can prevent many common licensing disputes.

If your business is dealing with business software licensing and wants help with software contracts, custom development terms, privacy compliance, and intellectual property ownership, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.