Black Friday10% off any legal service

SaaS Terms Vs EULA: Which Does Your Product Need?

byAlex Solo9 min read

Mia has built a budgeting platform for small retailers. Customers log in through a browser, her team is about to release an iPhone app, and a few larger customers want API access.

Then launch paperwork gets confusing. Does Mia need SaaS terms, an end user licence agreement, app terms, an API agreement, or all of the above?

This is a common point of confusion for New Zealand software businesses. The good news is that the answer usually follows the way your product is delivered. Once you map how customers access your software, the contract set becomes much clearer.

Do You Need SaaS Terms Or An EULA?

It depends on whether your customer accesses hosted software online or downloads software onto their own device or system.

SaaS terms are usually the right starting point when your product is hosted by you and customers access it through the internet. Think browser apps, cloud dashboards, online subscriptions and hosted platforms. Your customer is usually buying access to a service, not a copy of the software.

An EULA, or end user licence agreement, usually fits when the user downloads or installs software. This might be a desktop app, mobile app, plugin, local agent, SDK or other code that runs on the user's device or environment. The EULA gives the user permission to use that software under certain limits.

Many products need both. For example, if your main product is a browser-based project management tool but you also offer a desktop sync app, you may need:

  • SaaS terms for the hosted platform, subscription fees, accounts, support and online service rules.
  • An EULA for the installed sync app, licence restrictions, updates and device-based use.
  • A privacy policy if you collect personal information, which most SaaS products do.

The aim isn't to collect documents for the sake of it. It's to make sure each way your customer uses the product is properly covered.

What Is The Difference Between A Software Licence And A SaaS Agreement?

The main difference is that a software licence gives permission to use software, while a SaaS agreement sets the rules for accessing an online service.

A traditional software licence often focuses on installation and copying. It might say how many users or devices are allowed, whether the customer can make backups, and what they can't do with the code.

A SaaS agreement usually deals with a wider service relationship. It should cover things like:

  • customer accounts and authorised users
  • subscription plans, billing cycles and renewals
  • acceptable use rules
  • service availability and maintenance
  • customer data and privacy
  • support levels
  • termination, suspension and data export

Say Mia charges retailers $49 per month for her hosted dashboard. Customers don't download the platform. They log in, upload sales data and use reports online. In that case, SaaS terms are the main document.

But if Mia releases a downloadable Windows app that stores encrypted transaction data on the retailer's computer and syncs with the cloud, she also needs licence terms for that installed app. The SaaS terms won't naturally cover all the device-level issues, such as local installation, updates, reverse engineering and permitted copies.

A clean contract setup usually makes your sales process easier too. Customers can see exactly what they're buying and what rules apply.

What Documents Do Browser Apps, Mobile Apps And APIs Need?

Different product channels usually need different legal documents, because each channel creates different risks and customer expectations.

Browser Apps

For a browser-based SaaS product, start with SaaS terms and conditions and a privacy policy. If you sell online to many customers on the same terms, your SaaS terms can usually work as clickwrap terms where customers tick a box or click an acceptance button before creating an account or paying.

Your browser app terms should clearly cover subscriptions, acceptable use, data handling, IP ownership, service changes and account suspension. If your customers are businesses, you can also deal with business-to-business consumer law settings, where allowed.

Mobile Apps

For a mobile app, you may need mobile app terms and conditions, an EULA, or both. App stores often provide default licence terms, but they may not deal with your pricing, subscriptions, user content, privacy settings, support, refunds or business-specific limitations.

If the app is simply another way to access your hosted SaaS platform, your SaaS terms and conditions can often remain the main contract, with extra app terms for mobile-specific issues. If the app works as standalone installed software, an EULA becomes more important.

APIs

For APIs, use API terms of use or a developer agreement. APIs raise issues that normal SaaS terms often don't cover well, such as rate limits, API keys, developer credentials, monitoring, security standards, permitted integrations and what happens if an integration overloads your system.

If enterprise customers use your API, keep the API terms consistent with your main SaaS agreement, privacy terms and security commitments.

What If You Sell To Enterprise Customers?

You usually need a more detailed contract set for enterprise customers, because larger customers often expect negotiated terms, security documents and clearer service commitments.

Your standard online SaaS terms may still work for smaller self-serve customers. For larger customers, you might use a master services agreement or SaaS agreement with order forms for each deal.

A practical enterprise contract set often includes:

  • Main SaaS agreement: the core legal terms for access, fees, IP, liability, termination and compliance.
  • Order form: the commercial details, such as products, user numbers, price, start date and subscription term.
  • Service level agreement: any uptime targets, maintenance windows, support hours and service credits.
  • Data processing terms: how personal information and customer data are handled.
  • Security schedule: security controls, access management, incident notification and audit information.
  • API terms: if the customer integrates with your platform through an API.

Here is how this can play out. Mia signs a 12-month enterprise customer paying $300 per month for API access and $900 per month for 30 staff accounts. The order form states the price, term and user limit. The SaaS agreement covers the platform. The API terms set a limit of 10,000 calls per day and allow Mia to throttle traffic if the customer's integration risks slowing the service for others.

Without those API terms, Mia may struggle to manage heavy usage without upsetting the customer or breaching her own promises.

What Should Your SaaS Terms Or EULA Include?

Your terms should cover how customers can use the product, what they pay, what you promise, what you don't promise, and what happens when the relationship ends.

Templates can be a useful starting point, but they often miss the product-specific details that matter most for software businesses. A lawyer should tailor the document before you use it, especially if you handle customer data, sell to overseas customers or have enterprise clients.

Here is a practical outline you can use to brief your legal team:

  1. Parties and product: name your business, the customer and the software or service being provided.
  2. Access or licence: explain whether the customer gets online access, an installed software licence, or both.
  3. Users and accounts: set out user limits, account security and responsibility for authorised users.
  4. Fees and payment: cover pricing, billing cycles, GST, late payment, plan changes and renewal rules.
  5. Acceptable use: ban misuse, scraping, unlawful content, security testing without consent and interference with the service.
  6. IP ownership: confirm you own the software and the customer owns or controls its own data, subject to agreed licences.
  7. Customer data and privacy: explain how data is stored, used, accessed, exported and deleted.
  8. Support and availability: set expectations for support channels, maintenance and any uptime commitments.
  9. Third-party services: cover tools such as hosting, payment processors, analytics and app stores.
  10. Liability and warranties: set sensible limits while staying within New Zealand law.
  11. Suspension and termination: state when accounts can be suspended, how cancellation works and what happens to data.
  12. Governing law: say which law applies, often New Zealand law if your business operates from New Zealand.

For an EULA, add more detail about installation, updates, device limits, copying, reverse engineering, decompiling and local security requirements.

What New Zealand Laws Should Your Product Documents Cover?

Your product documents should be built around New Zealand contract, consumer, privacy and intellectual property laws where they apply.

Under the Fair Trading Act 1986, your sales pages, pricing, feature claims and contract terms must not mislead customers. The unfair contract terms rules can also apply to standard form consumer contracts and small trade contracts. For small trade contracts, the trading relationship threshold is generally $250,000 including GST per year when the relationship starts.

The Consumer Guarantees Act 1993 can apply where goods or services are ordinarily acquired for personal, domestic or household use. If you sell to businesses, you may be able to contract out of the Consumer Guarantees Act, but only where both parties are in trade and the contracting out is fair and reasonable.

The Privacy Act 2020 matters if you collect personal information, such as names, emails, login activity, support tickets or usage analytics linked to an identifiable person. Your privacy policy and contracts should deal with collection, use, storage, overseas disclosure, security and breach response. Serious privacy breaches may need to be notified to the Privacy Commissioner and affected individuals.

For marketing emails, the Unsolicited Electronic Messages Act 2007 generally requires consent, sender identification and an unsubscribe facility.

Your IP position also matters. Copyright can protect your source code and interface materials, while trade marks for your product name or logo can be registered through IPONZ. If you trade through a company, make sure your contracting entity matches your Companies Office records, and consider using your NZBN on customer-facing documents.

Common Mistakes To Avoid

The most common mistake is using one document for every product channel, even when customers access the software in different ways.

Try to avoid these traps:

  • Using website terms for a SaaS product: basic website terms usually don't cover subscriptions, data, service access or support properly.
  • Relying only on app store terms: app store defaults may not protect your pricing model, customer data handling or business-specific limits.
  • Forgetting the API: API use can create security, traffic and integration risks that normal SaaS terms don't manage well.
  • Copying overseas terms without adapting them: US or Australian templates may not fit New Zealand consumer, privacy and contracting rules.
  • Hiding key terms after payment: customers should be able to review and accept your terms before they sign up or buy.
  • Being unclear about data on termination: say how long data export is available, when deletion happens and whether backups remain for a period.

A simple launch checklist can help:

  1. Map each product channel: browser, mobile, desktop, API, plugin or SDK.
  2. List each customer type: self-serve, business, consumer, enterprise or developer.
  3. Choose the right main document for each channel.
  4. Check your privacy policy against the data you actually collect.
  5. Make sure customers accept the terms before using or paying for the product.
  6. Keep version records, so you know which terms applied at each sign-up date.

If your product changes after launch, revisit your software licence agreement, SaaS terms and other documents. Adding AI features, API access, enterprise plans or new data uses can shift what your terms need to cover.

Key Takeaways

  • SaaS terms usually suit hosted browser-based software, while an EULA usually suits downloaded or installed software.
  • Many products need both, especially where you offer a cloud platform plus a mobile app, desktop app, plugin or SDK.
  • APIs should have their own API terms or developer agreement covering keys, limits, security and permitted integrations.
  • Enterprise customers often need an order form, service levels, data processing terms and security schedules on top of standard SaaS terms.
  • Your New Zealand documents should deal with the Fair Trading Act, Consumer Guarantees Act, Privacy Act, IP ownership and clear acceptance of terms.

If you'd like help with your SaaS terms, end user licence agreement, app terms or API terms, you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.

Drafted by Taylor, Sprintlaw's AI, and overseen by Alex Solo. How we write

Alex Solo
Alex SoloCo-Founder

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.

Need legal help?

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.