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.
Mia is getting ready to launch a booking app for fitness studios in Wellington. The product is working, the payment page is connected and early customers are excited, then someone asks, "Where are your terms and privacy policy?"
That question can feel like one more thing on an already long launch list. But your legal documents aren't just website admin. They explain the rules of your platform, protect your revenue, set user expectations and help you meet New Zealand laws like the Privacy Act 2020, Fair Trading Act 1986 and Consumer Guarantees Act 1993.
The good news is that this doesn't have to be complicated. You just need the right documents, written around how your website, SaaS product or app actually works.
Do You Need Website Terms And A Privacy Policy In NZ?
Yes, most websites, SaaS products and apps in New Zealand should have website terms of use, and you'll usually need a privacy policy if you collect personal information.
Your website terms set the rules for using your site, platform or app. They can cover accounts, subscriptions, acceptable use, intellectual property, user content, payment terms, liability limits and when you can suspend access.
Your privacy policy explains how your business collects, uses, stores and shares personal information. Under the Privacy Act 2020, personal information means information about an identifiable individual. That can include names, email addresses, phone numbers, location data, billing details, account activity, device identifiers and support messages.
You may also need extra documents or clauses depending on your model, such as:
- Acceptable Use Policy for user behaviour, prohibited content and misuse of your platform.
- Subscription Terms for billing, renewals, cancellations, trials and plan changes.
- Marketplace Terms if you connect buyers and sellers, providers and customers, or creators and users.
- Community Guidelines if users can post comments, reviews, photos, profiles or listings.
- Cookie Notice or tracking disclosures if you use analytics, advertising pixels or similar tools.
Templates can be a useful starting point, but they often miss the clauses that matter most for your revenue model, privacy setup and product risks. A document should be tailored before you rely on it at launch.
What Legal Documents Should Be On Your App Launch Checklist?
It depends on what your app does, but a typical launch checklist includes customer facing terms, privacy documents and any rules that sit inside the product experience.
For a standard website, SaaS platform or mobile app, start with these documents:
- Website Terms Or App Terms: explain who can use the platform, what users can and can't do, your intellectual property rights and how liability is handled.
- Privacy Policy: explain what personal information you collect, why you collect it, who you share it with and how people can access or correct it.
- Subscription Or Payment Terms: cover fees, billing cycles, failed payments, GST, refunds, cancellations and automatic renewals.
- Acceptable Use Policy: set rules against spam, hacking, scraping, harassment, unlawful content and misuse of the service.
- User Content Clauses: cover reviews, comments, uploads, listings, images, prompts, posts and other content users add.
- Support And Service Levels: explain what support is included, response times if you promise them, maintenance windows and service limits.
- Commercial Customer Terms: add business account terms if you sell to companies, agencies, clinics, schools or other organisations.
Some businesses need extra layers. For example, if your app handles health information, children's information, identity checks, payroll data or sensitive financial data, your privacy documents should be more detailed. If your product uses AI features, you may also need clauses on user inputs, generated outputs, model limitations and prohibited uses.
Keep your documents easy to find. Users should be able to access them from your website footer, signup flow, payment page and app settings. If you rely on users accepting your terms, use a clear tick box or acceptance step rather than hiding the terms somewhere they may never see.
What Should Your Website Terms And Conditions Include?
Your website terms should include the practical rules that control access, payment, content, liability and misuse of your product.
For many founders, this is where the real protection sits. If your terms are too light, you may struggle to enforce payment, remove a harmful user, protect your intellectual property or explain that your product isn't suitable for every use case.
Website Terms Fill In Outline
Use this outline as a working checklist, not a finished legal document. The wording should be tailored to your business before it's used.
- Who The Terms Apply To: say whether the terms apply to visitors, account holders, paying customers, business users or all users.
- Account Rules: set age limits if relevant, explain registration, password security and responsibility for account activity.
- Services Provided: describe what your website, SaaS or app does, and any key limits on what it doesn't do.
- Fees And Payment: state your pricing structure, billing cycle, taxes, payment method rules and failed payment process.
- Trials, Renewals And Cancellations: explain when paid access starts, how renewals work and how users can cancel.
- Acceptable Use: list prohibited behaviour, including scraping, reverse engineering, spam, unlawful content and security testing without permission.
- User Content: explain who owns uploaded content, what licence you need to host it and when you can remove it.
- Intellectual Property: make clear that your brand, software, design, code and content remain yours or your licensors'.
- Disclaimers: explain any product limitations, especially if users may rely on outputs, recommendations or data.
- Liability Limits: set sensible limits on liability where New Zealand law allows this.
- Suspension And Termination: explain when you can suspend or close an account, such as non payment or serious misuse.
- Changes To The Terms: explain how you'll notify users about updates and when changes take effect.
New Zealand consumer law still matters, even if your terms say otherwise. The Consumer Guarantees Act 1993 may apply when you supply services to consumers, and the Fair Trading Act 1986 restricts misleading conduct and unfair contract terms. For certain Fair Trading Act breaches, companies can face penalties of up to $600,000 and individuals up to $200,000, so your marketing claims and terms should line up with what your product actually does.
What Should Your Privacy Policy Checklist Cover?
Your privacy policy should clearly explain how you handle personal information across collection, use, storage, sharing, access, correction and security.
Under the Privacy Act 2020, you need to be upfront about why you're collecting personal information and what you'll do with it. Your policy should match your actual product and back end tools, not just the information visible on your website.
Privacy Policy Fill In Outline
- Who You Are: identify the business collecting the information, including your trading name and contact details.
- What You Collect: list the types of personal information you collect, such as account details, payment details, messages, usage data and device data.
- How You Collect It: cover signup forms, checkout pages, app permissions, cookies, integrations, support chats and third party tools.
- Why You Use It: explain uses such as providing the service, taking payments, verifying accounts, improving features, sending updates and meeting legal obligations.
- Who You Share It With: name categories such as payment processors, hosting providers, analytics tools, customer support platforms and professional advisers.
- Overseas Disclosure: explain if information may be stored or accessed outside New Zealand, such as by cloud providers or software tools.
- Security: describe practical safeguards, such as access controls, encryption, staff permissions and incident response processes.
- Access And Correction: tell people how to request access to, or correction of, their personal information.
- Retention: explain how long you keep information, or the criteria you use to decide.
- Privacy Breaches: explain how you'll respond if there's a privacy breach, including notification where required.
- Complaints: tell people how they can contact you about privacy concerns.
New Zealand's Privacy Act also has a notifiable privacy breach scheme. If a breach has caused, or is likely to cause, serious harm, you generally need to notify the Privacy Commissioner and affected people as soon as practicable after you become aware it's notifiable. There isn't a fixed 72 hour deadline in New Zealand, but speed and good records still matter.
If you collect sensitive information, such as health details, children's information, precise location data or identity documents, your privacy policy and security settings should be especially careful. You should also check whether your product needs privacy notices inside the app at the point of collection, not just in a footer link.
How Should You Handle Payments, Subscriptions And Refunds?
You should handle payments with clear terms that explain exactly what users pay, when they pay, how renewals work and what happens if they cancel.
This is one of the most common places where launch documents fall short. If your payment page says one thing and your terms say another, users can get confused and your business may face complaints under the Fair Trading Act 1986.
Your payment clauses should cover:
- Pricing: whether fees are monthly, annual, usage based, per seat, per booking, commission based or a single amount.
- GST: whether prices are inclusive or exclusive of GST.
- Payment Timing: when the first payment is charged and when later payments are due.
- Automatic Renewal: whether plans renew automatically and how users can stop renewal.
- Free Trials: when the trial ends, whether card details are required and when billing starts.
- Failed Payments: how many attempts you'll make and when access may be suspended.
- Plan Changes: how upgrades, downgrades and proportional charges work.
- Refunds: when refunds are available, while still recognising rights users may have under New Zealand consumer law.
Here's how this looks in practice. Say Mia's booking app charges fitness studios $49 plus GST per month after a 14 day free trial. If the signup page says "cancel anytime" but the terms say annual billing applies, that's a problem. A cleaner setup would say:
- The 14 day trial starts when the studio creates an account.
- The first $49 plus GST monthly payment is charged on day 15 unless the studio cancels before then.
- The subscription renews monthly until cancelled.
- Cancellation takes effect at the end of the current paid month.
- No refund is given for a change of mind after a month has started, unless the law requires one.
That kind of wording helps users understand the deal and gives your team a clear process to follow when someone asks to cancel.
What If Users Can Post Content, Reviews Or Listings?
If users can post content, you need clauses that let you moderate, remove and use that content without taking on unnecessary risk.
User content can be valuable. It can also create legal headaches if users upload copyright material, fake reviews, offensive comments, unsafe advice, misleading listings or personal information about someone else.
Your terms should deal with three core questions.
Who Owns The Content?
Usually, the user keeps ownership of the content they upload. Your business then gets a licence to host, display, copy, edit for formatting, promote and distribute that content as needed to run the platform.
For example, if a personal trainer uploads class photos to Mia's booking app, Mia doesn't need to own the photos. But her business does need permission to display them in the trainer's public profile, resize them for mobile and keep them visible while the trainer's listing is active.
What Can You Remove?
Your acceptable use and moderation clauses should let you remove content that's unlawful, misleading, infringing, abusive, discriminatory, spammy, harmful, or in breach of your community rules.
You should also reserve the right to suspend or terminate accounts for serious or repeated breaches. Without this, you may be stuck arguing with users about whether you have the power to remove content that damages trust in your platform.
What Promises Should Users Make?
Users should promise that they have the right to upload their content, that it doesn't infringe someone else's rights and that it won't breach the law. If your platform has reviews, you should also prohibit fake, incentivised or misleading reviews unless any incentive is clearly disclosed.
This matters under the Fair Trading Act 1986, because misleading reviews or listings can create risk for both the user and the platform, especially if your business curates, promotes or profits from that content.
How Do You Make Your Terms Enforceable Online?
You make online terms stronger by showing them clearly, getting active acceptance and keeping records of the version each user agreed to.
A link in your website footer is useful, but it's not always enough for important terms like payments, account restrictions and liability limits. If a user says they never agreed to your terms, you want a clear acceptance trail.
A practical launch process looks like this:
- Put Your Terms Where Users Make Decisions: show links near sign up, checkout, app registration and any subscription confirmation screen.
- Use An Active Acceptance Step: use wording such as "I agree to the Terms and Privacy Policy" with an unticked box or button confirmation.
- Record The Details: keep a log of the user's account ID, timestamp, IP address if appropriate and the terms version accepted.
- Version Your Documents: add an effective date and keep copies of old versions so you know what applied at the time.
- Tell Users About Material Changes: notify users about changes that affect payment, rights, restrictions, privacy practices or key product features.
- Match Your Product Flow: make sure your onboarding screens, checkout pages, help centre and terms all say the same thing.
For privacy, consent isn't always the only legal basis for handling information under the Privacy Act 2020, but transparency is still essential. If you collect information in a surprising way, such as precise location tracking or contact list access, explain it before or when you collect it.
If your business trades through a company, make sure your company name and NZBN details are consistent across your terms, invoices and public facing materials. If your brand is different from your company name, say which legal entity is operating the website or app.
Key Takeaways
- Most apps, SaaS products and online platforms need website or app terms, and a privacy policy if they collect personal information.
- Your terms should cover accounts, payments, acceptable use, user content, intellectual property, liability and suspension rights.
- Your privacy policy should match your real data flows, including analytics tools, payment processors, cloud providers and support software.
- Payment terms should be clear about trials, renewals, cancellations, refunds, GST and failed payments.
- If users post content, reviews or listings, you need moderation rights and clear promises from users about what they upload.
- Online terms are stronger when users actively accept them and you keep records of the version they agreed to.
If you'd like help with website terms, app privacy policies, subscription clauses and user content rules, you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.
Get your customer-facing terms right
What should your privacy and online terms cover?
If you collect customer data, sell online or run marketing campaigns, your public terms and privacy documents should match the real customer journey.








