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.
Do you really need terms for a beta launch if your product is free, unfinished and only being tested by early users?
Usually, yes. The good news is your beta terms don't need to be heavy or intimidating. They just need to set clear expectations while your product is still being built.
At the pre-revenue stage, you may be inviting friends, waitlist users, pilot customers or early adopters to test an app, SaaS platform or online tool. That's exciting, but it also creates risks around bugs, downtime, feedback, personal information, confidentiality and what users think they're entitled to.
Well-drafted beta terms help you say, clearly and upfront: this is early access, things may break, access may change, and feedback can be used to improve the product.
Do I Need Beta Terms If The Product Is Free?
Yes - you should usually have beta terms even if users aren't paying you yet. A free beta can still create legal and commercial expectations.
Users may upload data, rely on your product, give you feedback, invite their team, or assume they'll keep getting access after the beta ends. If you don't set the rules early, it can be harder to manage those expectations later.
A beta testing agreement, beta participation agreement or beta user terms and conditions can help you cover:
- What the beta is: an early test version, not a finished product.
- Who can use it: invited users only, or users who meet certain eligibility criteria.
- What users can do: test features, report issues and give feedback.
- What users can't do: copy the platform, reverse engineer it, misuse data or share access without approval.
- How long access lasts: a fixed beta period, or until you decide to end or change it.
This is especially useful if your beta is public-facing. Say Maia is launching a project management app in Wellington and invites 80 waitlist users to test it free for 8 weeks. If her terms say beta access is temporary and can be withdrawn at any time, she's in a much better position when she later moves to a paid plan and closes some early accounts.
Your terms also sit alongside New Zealand laws like the Fair Trading Act 1986, which says you must not mislead users. If your website says the platform is secure, reliable or suitable for a specific use, make sure that matches reality, especially during a beta.
What Should My Beta Launch Terms Say About Bugs And Downtime?
Your beta terms should say plainly that the product is still being tested and may contain bugs, errors, interruptions and missing features.
This isn't about making excuses. It's about being honest with users at the right time. A beta product is, by nature, not finished. Your terms should match what you're actually offering.
Useful wording usually covers:
- No promise of uninterrupted access: the product may be unavailable for maintenance, updates or technical issues.
- No promise that every feature will work: some tools may be experimental, incomplete or changed without notice.
- No reliance for critical use: users shouldn't rely on the beta for safety-critical, financial-critical or business-critical decisions unless you've expressly agreed to that.
- Planned and unplanned changes: you may add, remove, suspend or change features during the beta.
- How users report issues: set out the support email, form or in-product reporting process.
For example, if your beta accounting dashboard occasionally miscalculates a forecast because a bank feed integration drops out, your terms should make it clear that users must check outputs before relying on them. That won't excuse misleading conduct, but it helps set practical boundaries around what the beta is for.
Be careful with your marketing language too. If you call your product production-ready, fully compliant or guaranteed to work, your beta disclaimer may not save you. Under the Fair Trading Act 1986, what you say on your website, in emails and during onboarding needs to line up with the limitations in your terms.
Who Owns Feedback From Beta Users?
Your terms should say that your business can use beta feedback freely to improve, change and commercialise the product.
This is one of the most commonly missed clauses in app terms and conditions for beta products in NZ. Early users often give incredibly useful suggestions. They might recommend a new workflow, describe a feature, suggest wording, upload examples or point out a product gap.
Without a clear feedback clause, a user may later say their idea was used without permission. That can be awkward, especially if the feature becomes central to your product.
A strong feedback clause should cover:
- Permission to use feedback: you can use suggestions, comments, reports and ideas without needing further approval.
- No payment for feedback: unless you've separately agreed otherwise, users won't be paid for suggestions.
- No ownership claim over your product: giving feedback doesn't give the user rights in your software, roadmap or intellectual property.
- Confidential information: users shouldn't include confidential third-party material in their feedback unless they have permission.
Let's say Tane runs a pre-revenue HR software startup. One beta user suggests a 3-step onboarding checklist. Tane's team builds a similar checklist into the paid product 3 months later. If the beta terms clearly say feedback can be used without restriction, Tane is less likely to face a messy argument about who owns that idea.
That said, feedback clauses shouldn't be used to take ownership of a user's existing intellectual property. If a user uploads their own documents, code, designs or business data, your terms should deal with that separately through digital product licence terms that allow you to use that content for providing and improving the beta.
How Should Beta Terms Handle Privacy And Data?
Your beta terms should work together with a privacy statement that explains what personal information you collect, why you collect it and how you use it.
In New Zealand, the Privacy Act 2020 applies when you collect, use, store or share personal information. Personal information can include names, email addresses, usage logs, support tickets, device identifiers, team member details and content a user uploads if it identifies someone.
For a beta launch, think carefully about what data you actually need. The Privacy Act's Information Privacy Principles expect you to collect personal information for a lawful purpose connected to your functions, and not collect more than you reasonably need.
What To Tell Beta Users
Your privacy wording should usually explain:
- what personal information you collect during sign-up, testing and support;
- why you collect it, such as account creation, product analytics, bug fixing and security monitoring;
- whether you use third-party tools for hosting, analytics, support or email;
- whether personal information may be stored or processed outside New Zealand;
- how users can ask to access or correct their personal information;
- how long you expect to keep beta data after the beta ends.
If you disclose personal information overseas, the Privacy Act 2020 has rules around cross-border disclosures. In broad terms, you need to take care that the overseas recipient is subject to comparable privacy protections, or another permitted ground applies.
What If Something Goes Wrong?
If there's a serious privacy issue during beta testing, act in order:
- Contain the issue: disable exposed links, revoke keys, pause affected features or lock down access.
- Work out what happened: record the time, systems affected, data involved and users impacted.
- Assess whether it's notifiable: under the Privacy Act 2020, a notifiable privacy breach generally needs to be reported to the Privacy Commissioner and affected individuals as soon as practicable.
- Communicate carefully: be clear, factual and avoid promising things you can't verify yet.
Good beta terms won't replace good privacy practices, but they can help you explain the testing environment, user responsibilities and what happens to data at the end of the beta.
Can I Limit My Liability During A Beta Launch?
Yes, you can usually limit your liability in beta terms, but the clause needs to be fair, clear and consistent with New Zealand law.
A liability clause is where you set boundaries around what your business is responsible for if the beta doesn't work as expected. This matters because beta products often involve bugs, downtime, data loss, inaccurate outputs or integrations that fail.
Your clause might say that, to the extent the law allows:
- the beta is provided on an as-is and as-available basis;
- you don't guarantee that the beta will be error-free, secure, uninterrupted or fit for every user's purpose;
- you aren't responsible for indirect or consequential loss, such as lost profits or lost opportunity;
- your total liability is capped, often by reference to amounts paid, which may be zero for a free beta;
- users are responsible for backing up their own data and checking outputs before relying on them.
There are limits. You can't use terms to mislead users or contract out of every legal responsibility in every situation. The Fair Trading Act 1986 can apply to claims you make about your product, and the Consumer Guarantees Act 1993 may be relevant where users are consumers. Standard form terms can also be reviewed for unfair contract terms, including in some small trade contract settings.
If your beta is used by businesses, your terms may include business-to-business limitations that are more flexible than consumer-facing terms. If your beta is open to individuals, families, students or hobby users, you need to be more careful with consumer law wording.
The safest approach is to match your liability clause to the real risk profile. A meditation app beta, a payroll tool beta and a healthtech diagnostic tool beta shouldn't all use the same liability wording.
Beta Launch Terms Checklist: What To Include
Your beta launch terms should include a clear set of clauses covering access, testing rules, feedback, data, intellectual property, platform terms and liability.
Here is a practical outline you can use when planning your document. This isn't a finished legal document. A lawyer should tailor it before you use it, because small wording choices can matter a lot once real users and real data are involved.
- Parties And Acceptance: say who the terms apply to and how users accept them, such as clicking a checkbox or creating an account.
- Beta Purpose: explain that the product is a testing version and is being provided for evaluation and feedback.
- Eligibility: set any age, location, business use, invite-only or account approval rules.
- Beta Period: state the start and end date if known, or say access continues until you end or change it.
- No Guaranteed Access: make it clear you can suspend, limit, change or withdraw access at any time.
- User Responsibilities: require lawful use, accurate account details, secure passwords and no misuse of the platform.
- Testing Restrictions: prohibit reverse engineering, copying, scraping, security testing without consent and sharing access.
- Bugs And Downtime: warn that errors, outages, data loss and incomplete features may occur.
- Feedback Rights: confirm you can use feedback without payment, ownership claims or further permission.
- Intellectual Property: say you own the software, branding, content and improvements, while users keep ownership of their own uploaded content.
- User Content Licence: get permission to host, process and use uploaded content as needed to provide and improve the beta.
- Privacy And Data: refer to your privacy statement and explain any beta-specific data practices.
- Confidentiality: if needed, stop users from sharing screenshots, unreleased features, pricing or roadmap information.
- Liability Limits: set the legal boundaries around risks, losses and disclaimers to the extent allowed by law.
- Ending Access: explain when accounts may be closed and what happens to data after the beta ends.
One more practical point: make acceptance easy to prove. A checkbox that says users agree to the website terms of use or beta terms before creating an account is usually stronger than hiding terms in a footer. Keep a record of the version each user accepted and the date they accepted it.
Key Takeaways
- Beta terms are useful even for a free, pre-revenue launch because users can still rely on your product, upload data and form expectations.
- Your terms should clearly say the product is unfinished, may contain bugs and may have downtime or changing features.
- A feedback clause helps your business use beta suggestions without later arguments about ownership or payment.
- Your privacy wording needs to reflect the Privacy Act 2020 and explain what data you collect, use, store and share during testing.
- Liability limits can help manage risk, but they need to fit your product and stay consistent with New Zealand consumer and fair trading laws.
- Templates can miss product-specific issues, especially around data, intellectual property, confidentiality and early access rules.
If you'd like help with your beta launch terms, privacy wording, software licensing clauses and feedback ownership provisions, you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.








