Alex is a co-founder of Sprintlaw. 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.
Priya is launching a project management web app for New Zealand consultants. The landing page is ready, Stripe is connected, and the first paid users are waiting - but there's one awkward gap. What rules will apply when someone creates an account, uploads client files, misses a subscription payment or blames the app for lost work?
That's where your web app terms and conditions come in. They set the ground rules between your business and your users from day one.
This doesn't have to be complicated, but it does need to be clear. A web app has risks that a simple brochure website does not, especially if users can log in, pay, upload content, invite team members or rely on your software for business decisions.
- Do I Need Web App Terms And Conditions In NZ?
- How Should I Handle Accounts, Subscriptions And Payments?
- What If Users Upload Content Or Invite Team Members?
- Can I Limit Liability In My Software Terms?
- How Do Privacy And Acceptable Use Rules Fit In?
- How Do I Make Sure Users Actually Accept The Terms?
- Key Takeaways
Do I Need Web App Terms And Conditions In NZ?
Yes, if users can create accounts, access software, pay for subscriptions or interact with your platform, you should have web app terms in place before signups open.
Your terms are the contract between your business and each user. They explain what users can do, what they can't do, what they're paying for, and what happens if something goes wrong.
For a web app, terms and conditions, app terms of use, SaaS terms and software terms usually point to the same core document. The name matters less than whether the document actually fits how your product works.
Your terms are especially important if your app includes:
- user accounts or team workspaces
- subscription plans, trials or auto-renewals
- user-generated content, files, comments or messages
- integrations with other software
- business-critical tools such as reporting, workflow or financial dashboards
- different user roles, such as admins, invited users and guests
New Zealand contract law generally allows online terms to form a binding agreement, but the user needs a fair chance to see and accept them. A hidden footer link is much weaker than a clear checkbox or signup button that says the user agrees to your terms.
If you're searching for a web app terms lawyer in NZ, you're probably past the point where a generic website template is enough. Templates can be useful for spotting common clauses, but they often miss the details that make your app different.
What Should My Web App Terms Cover?
Your web app terms should cover the full user journey, from account creation through to cancellation, data handling and suspension.
A good way to draft them is to walk through what a user actually does inside your app. Where do they sign up? What do they pay? What can they upload? What could go wrong? Your terms should answer those questions in plain English.
A Launch-Ready Clause Outline
Here is a practical outline you can use to brief your legal team. It isn't a finished legal document, and it should be tailored before you use it.
- Parties: identify your company name, NZBN if you have one, trading name and the user who accepts the terms.
- Acceptance: explain how users agree, such as creating an account, clicking a checkbox or using the web app.
- Accounts: set rules for account security, accurate information, authorised users and admin permissions.
- Plans And Subscriptions: describe subscription terms, fees, billing cycles, renewals, upgrades, downgrades, failed payments and cancellation.
- User Content: explain who owns uploaded content and what licence your business needs to host, process and display it.
- Acceptable Use: ban misuse such as scraping, reverse engineering, illegal content, spam and security testing without permission.
- Availability And Support: explain planned maintenance, outages, support channels and any service standards you're prepared to promise.
- Third-Party Tools: deal with payment processors, integrations, AI tools, cloud providers and external links.
- Intellectual Property: protect your software, branding, content, trade marks and documentation.
- Privacy: link the terms to your privacy policy and explain how personal information is handled under the Privacy Act 2020.
- Liability: set sensible limits on liability where the law allows, while respecting New Zealand consumer law.
- Termination: explain when either side can end the account and what happens to data afterwards.
Your terms should also match your company structure. If you have incorporated through the Companies Office, the contracting party should usually be the company, not you personally as the founder.
How Should I Handle Accounts, Subscriptions And Payments?
You should make your account and payment rules clear at signup, especially if users are entering card details or moving onto a paid plan after a free trial.
Subscription disputes often come from unclear expectations. A user thought the trial would end automatically. Your product charged monthly until cancellation. Someone downgraded halfway through a billing cycle and expected a refund. Your terms can reduce these arguments by setting the rules upfront.
Your subscription clauses should cover:
- whether fees are monthly, annual or usage-based
- whether prices include or exclude GST
- when payment is taken and what happens if it fails
- whether subscriptions renew automatically
- how a user cancels and when cancellation takes effect
- whether refunds, credits or pro-rated adjustments are offered
- what happens to access if an invoice is overdue
Say Priya offers a 14-day free trial, then charges $49 plus GST per month unless the user cancels. Her signup page should say that clearly, not just bury it in the terms. The terms can then explain that cancellation takes effect at the end of the current monthly billing period, and that the user keeps access until then.
You also need to be careful with marketing claims. Under the Fair Trading Act 1986, your pricing, free trial wording, feature descriptions and cancellation process must not mislead users. If a plan says it includes unlimited projects, you shouldn't quietly apply a hidden project limit unless that limit is made very clear.
What If Users Upload Content Or Invite Team Members?
If users can upload content or invite others into a workspace, your terms need to explain ownership, permissions and responsibility.
Most web apps shouldn't claim ownership of user content. Instead, you usually need a limited licence to store, process, back up, display and transmit that content so the app can work.
For example, if a customer uploads PDFs into your workflow app, you don't own those PDFs. But you do need permission to host them, generate previews, let the customer's team access them and include them in backups.
Your terms should say that users are responsible for making sure they have the right to upload and share content through the app. This matters where users upload client data, staff information, copyright material, confidential documents or images of other people.
If your app has team accounts, think carefully about the role of the workspace owner or admin. Your terms should deal with:
- who can add or remove users
- whether invited users are bound by the same terms
- who controls billing for the workspace
- what happens if an admin leaves the customer's organisation
- whether your business can rely on instructions from an admin
You should also protect your own intellectual property. Your source code, interface designs, documentation, branding and trade marks belong to your business or its licensors. If your app name is important to your growth plan, consider whether to apply for a trade mark through IPONZ so you have stronger brand protection in New Zealand.
Can I Limit Liability In My Software Terms?
Yes, you can usually limit liability in your software terms, but there are limits, especially where the Consumer Guarantees Act 1993 or Fair Trading Act 1986 applies.
Liability clauses are there to keep risk proportionate. If a customer pays $29 a month, you usually don't want your business exposed to unlimited losses because they relied on your app in a high-risk way.
A common approach is to cap liability by reference to fees paid over a set period. For example, your terms might cap your liability to the fees the customer paid in the previous 12 months, except for things that can't legally be limited.
You also need to think about what types of loss are excluded. Many software terms exclude indirect loss, loss of profits, loss of revenue, loss of data, business interruption and loss caused by third-party services. The wording needs to fit your product and be reasonable for your user base.
New Zealand consumer law still matters. The Consumer Guarantees Act 1993 gives consumers certain guarantees that you generally can't contract out of. For business users, you may be able to contract out of the Consumer Guarantees Act and parts of the Fair Trading Act if the agreement is in trade and the clause is fair and reasonable.
Your terms shouldn't promise more than you can deliver. Avoid absolute statements such as 100% uptime, error-free software or guaranteed results unless you're genuinely prepared to stand behind them. It's usually safer to explain that the app is provided on the basis described in your plan, subject to maintenance, outages and reasonable limitations.
How Do Privacy And Acceptable Use Rules Fit In?
Your terms should work alongside your privacy policy, not replace it.
Under the Privacy Act 2020, if your web app collects personal information, you need to tell people what you collect, why you collect it, who you share it with and how they can access or correct it. Your privacy policy usually handles this in detail, while your terms should point users to it and explain that use of the app involves data collection and processing.
Personal information can include names, email addresses, IP addresses, usage data, payment details, profile information and content that identifies someone. If your users upload their own customers' personal information, you should be clear about whether you're acting as a service provider, what security measures you use, and how deletion or export requests are handled.
Acceptable use rules are just as important. They give you a clear basis to suspend or terminate accounts if someone misuses the platform.
Your acceptable use section might ban users from:
- using the app for unlawful, harmful or misleading activity
- uploading malware, spam or content that infringes someone else's rights
- trying to bypass security or access another user's account
- scraping, copying or reverse engineering the software
- overloading the platform or interfering with other users
- using the app in a way that breaches privacy, confidentiality or employment obligations
If you use AI features, analytics tools or overseas cloud providers, your privacy and terms should say so in a way your users can understand. For some products, especially healthtech, fintech, education or HR software, getting tailored advice is worth it because the data risk is higher.
How Do I Make Sure Users Actually Accept The Terms?
You should make acceptance clear, recorded and hard to miss.
The best terms in the world won't help much if you can't show that the user agreed to them. For web apps, this usually means using a clickwrap flow, where the user must tick a box or click a button confirming they agree to the terms and privacy policy.
A stronger signup flow usually includes:
- a visible link to the current terms before the user creates an account
- a checkbox that isn't pre-ticked
- button wording that makes acceptance clear, such as creating an account or starting a paid plan
- a record of the date, time, user ID and version of terms accepted
- a process for notifying users when terms change
You should also keep version control. Save each version of your terms with the date it went live. If a question comes up six months later, you'll want to know which version applied when the user signed up or paid.
For paid plans, show key subscription terms at checkout, not only inside the legal document. Users should see the price, billing frequency, renewal terms and cancellation process before they pay.
If your app serves both consumers and businesses, think about whether you need different wording for each group. A business-only SaaS product can take a different approach to risk allocation than an app sold to everyday consumers, especially where Consumer Guarantees Act protections are involved.
Key Takeaways
- Your web app terms are the contract between your business and your users, so they should be ready before signups or payments open.
- Account rules, subscription terms, acceptable use, user content and termination clauses should match how your app actually works.
- New Zealand laws such as the Fair Trading Act 1986, Consumer Guarantees Act 1993 and Privacy Act 2020 can affect what your terms can say.
- Liability caps can help manage risk, but they need to be drafted carefully and can't override non-excludable consumer protections.
- A clear clickwrap signup flow and good version records make it much easier to show that users accepted your terms.
- Templates often miss product-specific details, so your terms should be tailored before you launch.
If you'd like help with your web app terms, subscription clauses, privacy policy or acceptable use rules, you can reach us at 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.







