Mobile App Terms and Conditions for New Zealand Businesses

Alex Solo
byAlex Solo11 min read

If your business has a mobile app, your terms and conditions are not just a box to tick. They set the ground rules for payments, subscriptions, acceptable use, account suspensions, refunds, intellectual property and liability when something goes wrong. Many New Zealand businesses make the same mistakes early on: they copy website terms that do not fit an app, they forget to deal with app store billing and subscription renewals, or they publish a privacy policy without matching it to how the app actually collects data.

Those gaps can create expensive disputes with users, complaints about misleading conduct, and confusion when you need to remove content, cancel access or respond to a security incident. The right mobile app terms conditions should match how your app works in practice and how your business earns money. This guide explains what mobile app terms and conditions usually cover, the key legal issues New Zealand businesses should check before they accept standard terms or publish their own, and the mistakes founders most often make before they sign or launch.

Overview

Mobile app terms and conditions are the contract between your business and the people using your app. They should explain what the app does, what users can and cannot do, how billing works, what happens if the service changes, and how privacy, liability and disputes are handled under New Zealand law.

  • Make sure the terms reflect your actual app features, payment model and user journey.
  • Check whether you need separate documents for app terms, privacy disclosures and subscription terms.
  • Deal clearly with automatic renewals, cancellations, refunds and app store payment mechanics.
  • Set out acceptable use rules, content moderation rights and account suspension powers.
  • Protect your intellectual property, including software, branding and user-generated content licences.
  • Review whether any disclaimers or limits on liability are fair and likely to be enforceable.
  • Match your privacy wording to your real data collection, storage, sharing and security practices.
  • Make sure your user sign-up flow shows users the terms and records acceptance properly.

What Mobile App Terms Conditions Means For New Zealand Businesses

For a New Zealand business, mobile app terms conditions are the main legal rules that govern how users access and use your app. They are not just legal fine print, they help you manage commercial risk at the exact points where founders usually run into trouble, such as failed payments, misuse of the platform, customer complaints and service outages.

If your app is customer-facing, your terms need to work alongside consumer law. If it is used by other businesses, the drafting may look different, especially around liability, warranties and service levels. Either way, the document should match the real commercial arrangement.

What the terms usually cover

Most app terms will deal with the core contract points between your business and the user, including:

  • who can use the app, including age, account eligibility and geographic limits
  • how accounts are created and secured
  • what the app is intended to do, and any limits on use
  • subscription fees, in-app purchases and billing cycles
  • renewals, free trials, cancellations and refunds
  • acceptable use, prohibited conduct and content standards
  • your ownership of the software, branding and content
  • any licence you need from users over uploaded content or feedback
  • what happens if the app is unavailable, changed or discontinued
  • privacy and how personal information is handled
  • liability clauses, disclaimers and indemnities
  • termination rights and dispute procedures

Why app terms are different from website terms

Founders often assume website terms can simply be pasted into an app. That is where businesses get caught. A mobile app usually raises extra issues such as device permissions, push notifications, location data, app store distribution terms, subscription management, digital content access and account-based restrictions.

For example, a retailer with an app may need to explain how loyalty rewards work, how promo codes are applied in-app, and whether stock information is live. A software business may need to deal with uptime expectations, user seats, trial conversion and data export when a subscription ends. A marketplace app may need detailed rules about listings, transactions, user reviews and who is responsible for fulfilment.

How New Zealand law affects your terms

Your terms cannot override New Zealand law just because you write a broad disclaimer. That is especially relevant if you supply services to consumers. The Consumer Guarantees Act 1993 can imply guarantees about services being carried out with reasonable care and skill, being fit for purpose in some situations, and being completed within a reasonable time if timing is not fixed.

The Fair Trading Act 1986 also matters. If your app listings, subscription offers, in-app prompts or terms give a misleading impression about price, renewals, features, data use or cancellation rights, that can create problems even if the detail appears somewhere else in the fine print.

If your app collects personal information, the Privacy Act 2020 will also shape what you need to tell users and what systems you need behind the scenes. Terms and conditions are not a substitute for proper privacy disclosures, but the documents should work together and not contradict each other.

When terms are actually binding

Terms only help if users are given a real opportunity to review them and there is a clear step showing acceptance. In practice, that often means presenting the terms during account creation, checkout, or subscription sign-up and keeping a record of assent.

A hidden link in an app footer is a weak approach if the key commercial terms are not made obvious before the user pays or signs up. If you want to rely on cancellation rules, renewal clauses or usage restrictions later, you need a clean acceptance process from the start.

The main legal issue is whether the terms actually fit the way your app operates, charges users and handles data. Before you accept the provider's standard terms, publish your own terms, or rely on a verbal promise from a developer or platform partner, check the legal detail against your product flow.

1. Business model and payment structure

Your legal terms should reflect how money moves through the app. If users pay once, subscribe monthly, buy credits, purchase through an app store, or pay a third party marketplace fee, each model raises different drafting points.

Look closely at:

  • whether prices are clearly disclosed before payment
  • when charges are taken and whether renewals are automatic
  • how free trials convert into paid plans
  • who processes payments, your business, a payment gateway, or an app store
  • what refund rights apply and whether there are any non-refundable components
  • how failed payments, chargebacks and plan downgrades are handled

If your app uses Apple or Google billing systems, your own terms need to align with the store process. You should not promise cancellation mechanics or direct refunds that are inconsistent with how the platform requires subscriptions to be managed.

2. Consumer law and fair marketing

If your users include consumers, your terms should not overreach. Broad statements such as no refunds in any circumstances, use at your own risk, or we are never responsible for service failures can be misleading or unenforceable depending on the situation.

Your app store description, sign-up screens, free trial prompts and onboarding messages all matter. If the subscription renews automatically, say so clearly before the user commits. If a feature is still in beta or depends on third party integrations, the wording should reflect that reality.

3. Privacy and app permissions

App businesses often collect more data than they realise. A mobile app may access contact details, device identifiers, location, camera, photos, notifications, health-related inputs or behavioural analytics. Your legal wording needs to match what the app actually does on the device and on your backend systems.

Check whether you have properly covered:

  • what personal information is collected
  • why it is collected and how it is used
  • whether information is shared with service providers or offshore providers
  • how users can access or correct their information
  • what optional permissions the app requests and why
  • what happens if a user withdraws a permission needed for core functions

If your app handles sensitive information or large volumes of customer data, privacy compliance should be reviewed as a separate workstream, not treated as one clause inside the terms.

4. Intellectual property ownership and licences

Your business should be clear about what it owns and what rights the user gets. Usually, users receive a limited licence to use the app, while your business keeps ownership of the software, content, branding and updates.

If users upload content, submit reviews, create profiles or send you feedback, the terms should state what licence they grant to your business and what promises they make about owning or being allowed to use that content. This is especially important for marketplace, community and creator apps.

If your app name or logo is central to the business, trade mark protection may also be worth considering. Terms help with usage rules, but they do not replace registration where brand protection matters.

5. Service levels, downtime and changes

Most apps evolve quickly. You may add features, remove features, pause maintenance, or stop supporting older devices. Your terms should give your business room to make those changes without surprising users unfairly.

It is sensible to address:

  • whether the app is provided on an as available basis, subject to legal limits
  • planned maintenance and emergency outages
  • device or operating system compatibility limits
  • your right to update, suspend or discontinue features
  • whether users will receive notice of major changes
  • what happens to stored data or credits if the service ends

These points matter before you sign a development contract too. If a developer promises uptime, support, integrations or source code access, get that in writing in the development agreement rather than assuming your customer terms will solve it.

6. Acceptable use and platform control

If users can post, upload, message, sell, review or interact with each other, your terms should give your business practical moderation tools. The main risk is that your app becomes difficult to police because the contract does not give you enough control.

Typical clauses cover prohibited behaviour such as unlawful content, harassment, spam, misuse of another person's account, scraping, reverse engineering, or attempts to interfere with the service. You also need a clear right to suspend or terminate accounts and remove content where needed.

7. Dispute handling and governing law

Your terms should say which law applies and how disputes are approached. For New Zealand businesses serving New Zealand users, New Zealand governing law is common, but the right approach depends on where your users are based and whether you are contracting with consumers or businesses.

If you serve overseas markets, a one-size-fits-all clause may not be enough. Cross-border apps can raise extra issues around local consumer laws, payment rules and privacy obligations.

Common Mistakes With Mobile App Terms Conditions

The most common mistake is publishing generic terms that do not match the actual app journey. That usually happens when a founder is moving fast, relying on copied wording, or assuming the app store settings will cover the legal basics.

Copying web terms into an app

Website terms often miss mobile-specific issues such as device permissions, app account controls, in-app purchases and push notifications. If the product is different, the terms should be different too.

Promising too much in the marketing and taking it back in the fine print

A business might advertise a free trial, instant cancellation or unlimited access, then hide exceptions deep in the legal terms. That can create Fair Trading Act risk and frustrate users.

The better approach is consistency across the app store listing, onboarding screens, payment page and legal documents.

Using broad liability exclusions that are unlikely to hold up

Founders often want the strongest possible disclaimer. The problem is that very broad exclusions can be challenged, especially where consumers are involved or where the wording conflicts with mandatory legal rights.

It is usually better to draft limitations that are realistic, tailored and aligned with the service you actually provide.

Leaving privacy wording vague

If your app asks for location, contacts, camera access or behavioural tracking, users expect a clear explanation. Vague statements about collecting information to improve services are often not enough on their own.

This is where businesses also forget to align legal wording with developer settings and consent flows. If the app requests permissions that are not explained properly, complaints often follow.

Failing to think about moderation and account suspension before trouble starts

Businesses with community, marketplace or user-content apps sometimes wait until the first abusive user, scam listing or copyright complaint appears. Then they discover their terms do not clearly let them remove content or ban accounts.

That issue is much easier to solve before you launch online than after a dispute starts.

Not capturing acceptance properly

If a user was never clearly shown the terms before subscribing or creating an account, enforcing key clauses can be harder. Keep the acceptance flow simple, visible and recorded.

Forgetting supplier and developer contracts

Your customer-facing app terms are only one part of the legal picture. If your app relies on a software developer, cloud provider, analytics platform, payment provider or white label arrangement, your upstream contracts matter too.

Founders often focus on what users agree to, but the operational risk may actually sit in a poorly negotiated supplier contract. Before you sign, check ownership of code, support commitments, service levels, security responsibilities and exit arrangements.

FAQs

Do New Zealand businesses need mobile app terms and conditions?

In most cases, yes. If users create accounts, make purchases, subscribe, upload content or rely on the app for services, terms and conditions help set the contract rules and reduce ambiguity.

Are mobile app terms the same as a privacy policy?

No. The terms govern use of the app and the commercial relationship. A privacy policy explains how personal information is collected, used, stored and disclosed. Both may be needed.

Can I copy terms from another app?

No, that is risky. The wording may not fit your product, business model or New Zealand legal context, and copying may also raise intellectual property concerns.

Do my terms need to mention the Consumer Guarantees Act?

If consumers use the app, your drafting should be consistent with consumer rights under New Zealand law. Whether the Act is mentioned expressly depends on the service and the drafting approach, but your terms should not suggest those rights disappear.

What if my app is only for business users?

The terms may allow more flexibility around risk allocation, but they still need to be clear and fair. You should also check whether your onboarding, invoicing and contracting process actually ensures you are dealing with businesses rather than consumers.

Key Takeaways

  • Mobile app terms and conditions should match how your app works, how users pay, and how your business manages access, data and content.
  • New Zealand businesses should draft app terms with consumer law, fair trading and privacy obligations in mind.
  • Website terms are rarely enough for an app, especially where subscriptions, permissions, user accounts or uploaded content are involved.
  • Clear clauses around billing, renewals, cancellations, acceptable use, intellectual property and liability can prevent avoidable disputes.
  • Your acceptance flow matters. Users should see the terms at the right time and your business should keep a record of agreement.
  • Supplier contracts, developer agreements and platform terms should also be checked before you rely on your customer-facing app terms alone.

If you want help with subscription terms, privacy compliance, developer contracts, and liability clauses, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.

Lock in the contract

Turning the information into a usable contract

Once money, deliverables or customer obligations are involved, the next step is usually a clear contract that matches how the business actually works.

Alex Solo
Alex SoloCo-Founder

Alex is Sprintlaw’s co-founder and principal lawyer. Alex previously worked at a top-tier firm as a lawyer specialising in technology and media contracts, and founded a digital agency which he sold in 2015.

Lock in the contract

Get in touch with our team

Tell us what you need and we'll come back with a fixed-fee quote - no obligation, no surprises.

Need support?

Need help with your business legals?

Speak with Sprintlaw to get practical legal support and fixed-fee options tailored to your business.