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.
Most New Zealand small businesses don't need a technology lawyer on retainer. You do need targeted technology-focused legal help when your website, app, SaaS product, marketplace, AI tool or digital service involves customers, revenue, data, intellectual property, contractors or material contracts.
That might sound like a lot, but the point isn't to lawyer every small product decision. It's to get the right legal foundations in place before a small issue becomes expensive to fix.
If you're launching or scaling a digital product, your legal needs usually sit across contracts, privacy, consumer law, intellectual property and employment or contractor rules. A general business lawyer may handle some of this well, but technology businesses often have details that need extra care, like user data, software ownership, platform terms, APIs, cloud providers and AI outputs.
So, do you need a technology lawyer? Sometimes. More often, you need the right legal help at the right stage.
- What Does A Technology Lawyer Actually Do In New Zealand?
- Is A Technology Lawyer Different From A Business Lawyer Or Corporate Lawyer?
- What Documents Should A Small Technology Business Get First?
- What Privacy, Data And Cyber Rules Should I Think About?
- Who Owns The Code, Designs, Data And Product IP?
- How Do Consumer Law And Online Sales Rules Affect Tech Terms?
- When Is A Template Enough, And When Should I Get Tailored Help?
- Key Takeaways
What Does A Technology Lawyer Actually Do In New Zealand?
A technology lawyer helps your business manage the legal risks that come with building, selling, licensing or using technology. For a small business, this usually means getting your contracts, privacy documents, IP position and customer-facing terms right.
Technology law isn't one separate Act of Parliament. It pulls together several areas of New Zealand law that affect digital businesses, including:
- the Privacy Act 2020, if you collect, use, store or share personal information
- the Fair Trading Act 1986, if you advertise or sell goods or services online
- the Consumer Guarantees Act 1993, if your customers may have consumer rights
- the Copyright Act 1994, if code, content, designs, databases or other creative work are involved
- the Unsolicited Electronic Messages Act 2007, if you send marketing emails or texts
- the Employment Relations Act 2000, if you hire employees or contractors to build or support your product
In practice, this can mean preparing SaaS terms, website terms, app terms, end user licence agreements, software development agreements, API terms, marketplace terms, reseller agreements, confidentiality documents, data processing terms and privacy policies.
It can also mean reviewing a customer or supplier contract before you sign it. That's especially useful where the other side wants broad indemnities, unlimited liability, ownership of your core product or strict service levels that your team can't reliably meet.
Is A Technology Lawyer Different From A Business Lawyer Or Corporate Lawyer?
Yes, but there's overlap. A business lawyer or commercial lawyer usually helps with general commercial contracts, business setup, trading terms, employment documents and shareholder arrangements, while a technology lawyer focuses more closely on digital products, software, data and online risk.
A corporate lawyer usually focuses on company setup, directors' duties, governance, shareholders agreements, fundraising documents and larger corporate transactions.
A corporate M&A lawyer is different again. They usually work on mergers, acquisitions, buying or selling businesses and due diligence. If you're looking at that type of transaction, you should get advice from an appropriate New Zealand-qualified lawyer. Some legal service providers don't act on buying or selling a business, conveyancing, leases or disputes, so check the scope before you engage anyone.
Location usually isn't the main factor. For many small businesses, the more useful question is whether the person reviewing your documents understands technology revenue models, data flows, software ownership and New Zealand consumer and privacy rules.
You may also need a New Zealand-qualified lawyer in specific situations, such as court matters, disputes, property transactions, or where legal professional privilege is central. Communications with a legal consultancy may not always be protected by legal professional privilege, so that point matters if you're dealing with sensitive contentious issues.
Do I Need One Before Launching A Website, App, SaaS Product Or AI Tool?
It depends on what you're launching and what can go wrong if the terms are unclear. A simple brochure website may only need basic website terms and a privacy policy, but a paid SaaS product, app, marketplace or AI tool usually needs more targeted documents.
If you're taking payment, setting subscription rules, collecting personal information, letting users upload content, relying on third-party platforms or promising specific results, you should get legal help before launch. It's much easier to set your position early than to rewrite customer expectations later.
Your first documents will usually cover three questions:
- what exactly are you selling, and what are you not promising?
- who owns the product, content, data, code and improvements?
- what happens if the service goes down, a customer misuses it or something goes wrong?
For AI tools, you may also need to address how prompts and outputs are used, whether users can rely on results, what human review is required, and whether your tool makes decisions that affect people. If you're using biometrics, the Biometric Processing Privacy Code 2025 may apply. It regulates biometric processing by biometric systems, including technologies used to verify, identify or categorise people.
The Privacy Act 2020 applies to New Zealand businesses that collect or hold personal information. From 1 May 2026, Information Privacy Principle 3A also affects some situations where you collect personal information indirectly from someone other than the individual. That can matter for platforms, integrations, analytics tools and AI products that receive user or customer data from another source.
Worked Example: A Wellington SaaS Startup Scaling Up
Say Brooke runs a small Wellington SaaS startup with a $29 per month self-serve product for hospitality businesses. At launch, her priorities are clear SaaS terms, a privacy policy, simple support terms and clean IP ownership from the contractor who built the first version.
Six months later, a national customer offers Brooke a $48,000 annual enterprise contract. The legal priorities change. Brooke now needs a negotiated order form, a data processing schedule, a support and service level schedule, a security and breach process, and a careful review of liability caps and indemnities. She also needs to make sure the customer gets a licence to use the platform, not ownership of the core product. Without that, one enterprise deal could accidentally limit how she sells the product to everyone else.
What Documents Should A Small Technology Business Get First?
You should start with the documents that protect your revenue, data and ownership position. The exact mix depends on whether you're selling B2C, B2B, through an app store, through a marketplace or by negotiated enterprise contracts.
For many small technology businesses, the first legal pack looks like this:
- customer terms that explain payment, renewals, refunds, acceptable use, liability limits and termination rights
- a privacy policy that explains what personal information you collect, why you collect it, who you share it with and how people can contact you
- a contractor or software development agreement that clearly deals with ownership of code, designs, documentation and confidential information
- a shareholders agreement if there's more than one founder or investor
- a confidentiality agreement for early sales conversations, product demos, partnerships or contractor discussions
You may also need more specialised terms. SaaS terms suit a hosted subscription product. An end user licence agreement suits downloadable or installed software. Marketplace terms need to deal with the relationship between you, sellers and buyers. API terms should cover permitted use, rate limits, security, suspension rights and responsibility for downstream users.
Templates can be a useful starting point, but they often miss the part that matters most: your actual product, risk profile and revenue model. A document written for a simple content website won't properly cover a paid SaaS platform with user accounts, customer data, integrations and uptime expectations.
What Privacy, Data And Cyber Rules Should I Think About?
You need to think about privacy from launch if your technology business collects or holds information about identifiable people. That includes names, email addresses, phone numbers, login details, support tickets, billing information, location data, device identifiers and some analytics data.
Under the Privacy Act 2020, you should be clear about what you collect, why you collect it, how long you keep it, who you disclose it to and whether information may be stored or accessed overseas. If you use overseas cloud providers, payment processors, CRM tools or analytics platforms, your privacy documents and customer terms should reflect that reality.
You also need a plan for privacy breaches. A notifiable privacy breach is one it's reasonable to believe has caused serious harm to affected individuals or is likely to do so. If that happens, you must notify the Privacy Commissioner and affected individuals as soon as practicable, unless an exception or permitted delay applies.
If you send marketing emails or texts with a New Zealand link, the Unsolicited Electronic Messages Act 2007 generally requires consent, accurate sender information and a functional unsubscribe facility. For organisations, civil penalties can be up to $500,000 for civil liability events.
Data terms aren't just about compliance. Enterprise customers often ask for security commitments, breach notification timeframes, audit rights, subcontractor controls and data deletion rights. If you agree to these too casually, you may create obligations your product and team can't meet.
Who Owns The Code, Designs, Data And Product IP?
You shouldn't assume your business owns the technology just because you paid for it. Ownership depends on who created the material, whether they were an employee or contractor, what the agreement says, and the type of work involved.
Under section 21 of the Copyright Act 1994, the author is generally the first copyright owner. There are important exceptions. An employer is generally the first owner of employee work created in the course of employment. Also, if you commission and pay or agree to pay for a computer program, the person commissioning it is the first owner, unless the parties agree otherwise.
That sounds helpful for software buyers, but you still want the contract to say exactly what happens. Your agreement should cover source code, object code, designs, documentation, databases, background tools, open-source components, third-party materials, improvements and licences back to the developer if needed.
Contractor classification also matters. From 21 February 2026, the Employment Relations Act 2000 contractor gateway applies and isn't retrospective. If all gateway criteria are met, the worker is treated as a contractor for Employment Relations Act purposes. If not, the usual employee-versus-contractor analysis may still be needed.
This matters for tech businesses because early product work is often done by contractors, agencies or friends helping after hours. If your paperwork is vague, you may later struggle to prove what your company owns when raising investment, selling licences or signing a serious customer.
How Do Consumer Law And Online Sales Rules Affect Tech Terms?
New Zealand consumer law can apply to digital products and online services, so your terms can't simply say that every risk sits with the customer. Your website, app screens, pricing pages, checkout process, ads, emails and social media claims all need to line up with what you actually provide.
The Fair Trading Act 1986 applies to businesses advertising or selling to New Zealand consumers online, including through websites, apps, emails, texts and social media. Your claims about price, availability, features, consumer rights, refunds, warranties and performance must not mislead. Where substantiation rules apply, you need a reasonable basis for the claim when you make it.
The Consumer Guarantees Act 1993 can also apply to consumer goods and services, including online supplies. If you're dealing business-to-business, you may be able to exclude the Consumer Guarantees Act, but only where the agreement is in writing, the goods or services are supplied and acquired in trade, all parties are in trade and agree to the exclusion, and it's fair and reasonable for the parties to be bound by it.
Unfair contract term rules also matter. They apply to standard form consumer contracts and to standard form trade contracts that are small trade contracts with an actual or expected trading relationship value of up to $250,000 including GST in any 12-month period. This can affect standard SaaS terms, online terms and supplier terms.
Practically, your key terms should be clear, prominent and easy to find. Don't bury important limits, renewal rules, refund conditions, delivery information or warranty exclusions in fine print or hard-to-find linked pages.
When Is A Template Enough, And When Should I Get Tailored Help?
A template may be enough for a very low-risk internal document or an early draft, but it's risky where the document controls revenue, customer rights, data handling, IP ownership or a major contract. The more your business depends on the document, the more it should be tailored.
A free template may not match New Zealand law, your product type or the way you actually sell. An online fixed-fee review can be useful where you already have a document and want targeted changes. A custom legal pack usually makes more sense when you're launching a paid product, handling personal information, using contractors, onboarding enterprise customers or building a marketplace or AI tool.
A traditional firm billing by the hour may be suitable for complex corporate governance, regulated technology, major transactions or matters that need a New Zealand-qualified lawyer. If you're comparing options, ask what is included, whether the scope covers privacy and consumer law as well as contract wording, who will do the work, and whether you'll receive a clear fee before work starts.
For many small businesses, the practical path is staged. Start with the launch documents you need to sell safely. Then upgrade when you add employees or contractors, collect more sensitive data, integrate with larger customers, raise funds, expand overseas or sign higher-value contracts.
Key Takeaways
- You don't need a technology lawyer for every tech decision, but you should get targeted help before customers, revenue, data, IP, contractors, AI or serious contracts are involved.
- Your core legal documents will usually include customer terms, a privacy policy, contractor or software development terms, confidentiality documents and, where needed, a shareholders agreement.
- New Zealand privacy, consumer, spam, copyright and contractor rules can all affect websites, apps, SaaS products, marketplaces and AI tools.
- Ownership of code and product IP should be written clearly, especially where contractors, agencies or commissioned software are involved.
- Templates can help with early drafting, but documents that control revenue, liability, data or ownership should be tailored to your business.
If you'd like help with your technology contracts, privacy documents, software ownership terms or online customer terms, you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.
Protect your brand
What intellectual property should you protect?
If a name, logo, design or other creative work matters to the business, check who owns it, what permissions you need and whether clearance or registration is appropriate.








