Service Agreements for New Zealand Online Course Platforms

If you run an online course platform in New Zealand, the service agreement you sign with a developer, learning management system provider, marketing agency, course creator, payment provider or support contractor can shape your revenue, your customer experience and your legal risk.

Founders often make the same mistakes: accepting the provider's standard terms without checking ownership of course content, relying on a verbal promise about response times or integrations, or missing clauses that let fees increase or services change with little notice.

A well-drafted service agreement is not just admin. It sets the practical rules for who does what, when they do it, what happens if the platform goes down, who owns the material uploaded to the system, and how customer data is handled. Before you sign, you want to know where the main risks sit, what clauses deserve negotiation, and how New Zealand law can affect what looks like a standard online contract.

Overview

A service agreement for an online course platform should match the way your business actually operates, not just the supplier's template. The strongest agreements deal clearly with platform functionality, payment terms, intellectual property, privacy, service levels and exit arrangements so you are not left arguing about assumptions later.

• Identify exactly what services are being provided, such as hosting, development, support, content production, marketing or payment processing.
• Check who owns platform code, course materials, recorded lessons, branding assets and customer data.
• Confirm service levels, response times, maintenance windows and what happens during outages.
• Review privacy and data handling terms, especially if learner information is stored offshore or accessed by third parties.
• Look closely at fees, auto-renewal clauses, minimum terms, price review rights and termination rights.
• Make sure liability limits, indemnities and warranties are fair for the level of risk involved.
• Record any important promises in writing before you accept the provider's standard terms.

What Service Agreements Cover

A service agreement should spell out the commercial deal in enough detail that both sides know what success looks like. For online course platforms, that usually means the contract needs to cover more than a basic description of services.

Scope of services

The first issue is the scope. If the agreement just says a provider will supply "platform services" or "technical support", you may have trouble enforcing expectations later.

The scope should be specific about what is included:

• platform setup and configuration
• custom development work
• hosting and storage
• user support
• content migration
• integration with payment gateways, CRMs or email systems
• analytics and reporting
• security monitoring and backups
• marketing or launch support, if relevant

This matters in founder terms. If you expect a provider to migrate 300 existing student accounts, upload 50 modules and connect your payment flow, you do not want that left as an assumption.

Service standards and timing

The agreement should set clear timing and performance standards. If the platform is central to your business, a vague promise to use "reasonable efforts" may not be enough on its own.

Useful clauses often cover:

• go-live dates and milestone deadlines
• support hours and contact methods
• response and resolution times for urgent issues
• scheduled maintenance windows
• system availability targets
• backup frequency and disaster recovery expectations
• service credits or remedies if service levels are missed

This is where founders often get caught. A provider may promise fast support in a sales call, but the actual contract can narrow support to business hours only, exclude weekends and cap the provider's obligation to a modest credit.

Fees and payment terms

Fee clauses should tell you not just what you pay now, but what you might be required to pay later. Subscription pricing, implementation fees, transaction fees and add-on charges can build up quickly.

Check whether the agreement deals with:

• one-off setup fees
• monthly or annual subscription charges
• fees per learner, course or admin user
• payment processing charges
• extra fees for custom work or additional support
• annual price increases
• suspension rights for late payment
• refund rights if service does not match what was promised

If the pricing model changes once your user base grows, you want that risk visible before you commit. It is much easier to negotiate a pricing cap before you sign than after your entire platform is built around one provider.

Intellectual property and ownership

Ownership is one of the biggest pressure points for online education businesses. The agreement should clearly separate the provider's tools and systems from your business assets.

You should know who owns:

• your course videos, lesson plans, quizzes and downloadable materials
• your trade marks, logos and brand assets
• custom code built specifically for your platform
• templates, plug-ins or software the provider brings to the project
• student reviews, comments and user-generated content
• platform analytics and reporting outputs

A common position is that you keep ownership of your pre-existing content and branding, while the supplier keeps ownership of its existing platform and tools. Custom development is where the negotiation usually sits. If you are paying for a feature to be built specifically for your business, you may want ownership, a broad licence, or at least guaranteed long-term access.

Data, privacy and security

If your platform collects learner names, emails, billing details, assessment results or progress data, privacy terms are not optional. The service agreement should align with your obligations under the Privacy Act 2020 and with the promises you make to users.

The contract should deal with:

• what personal information is collected and processed
• whether the provider acts on your instructions or uses data for its own purposes
• where data is stored
• whether subcontractors can access the data
• security standards and incident response
• how privacy breaches are handled and notified
• what happens to data when the agreement ends

If a provider stores data outside New Zealand, that is not automatically prohibited, but you should understand the arrangement and make sure your privacy notice, disclosures and contractual protections line up.

Term, renewal and exit

Your exit rights matter just as much as your start date. If the relationship stops working, you need a practical path out.

A good service agreement should explain:

• the initial term and any automatic renewal
• termination for breach
• termination for convenience
• notice periods
• what assistance is provided on exit
• how data is returned or deleted
• whether transition support is charged
• what survives termination, such as confidentiality and payment obligations

Before you spend money on setup, check whether you can actually leave without losing your content, customer records or access to your own platform materials.

Legal Issues To Check Before You Sign

The main legal question is whether the agreement allocates risk fairly for the real role the provider plays in your business. Standard terms often shift more risk to the customer than founders expect.

Consumer law style obligations and business representations

Even in a business-to-business setting, service descriptions and sales promises matter. If a provider markets a platform as suitable for a particular use, fully integrated with a system you rely on, or capable of handling a certain user volume, those representations can become legally important.

Under New Zealand's Fair Trading Act 1986, businesses must not make misleading or deceptive claims. That matters before you accept the provider's standard terms and also when your own platform signs providers or creators. If a key promise influenced your decision, it should appear in the written contract.

Service quality can also be affected by statutory guarantees in some situations, although many business contracts try to contract out where the law permits and where both parties are in trade. Whether a contracting-out clause is effective depends on the circumstances and wording, so it is worth checking rather than assuming it will always apply.

Liability caps and exclusions

Liability clauses decide who absorbs the cost when something goes wrong. This is often the most negotiated part of a service agreement for online course platforms.

Look closely at whether the provider excludes liability for:

• loss of profits or revenue
• loss of data
• service interruptions
• security incidents
• third-party integration failures
• errors in migrated content
• delays caused by subcontractors

It is common to see liability capped at the fees paid in the last 12 months. That may be acceptable for a low-cost tool, but it can be a poor fit where the provider hosts your full student database or controls core learning functionality.

Think about the real downside. If an outage blocks enrolments during a major launch or wipes assessment records, a very low cap may leave your business carrying nearly all of the commercial loss.

Indemnities and third-party claims

Indemnities transfer specific risks from one party to the other. They are not always inappropriate, but they should be targeted and clear.

For example, a provider may ask you to indemnify it for claims arising from your course content, trade mark use or marketing statements. That can be reasonable if you control the content. On the other hand, you may want the provider to indemnify you for claims tied to its software infringement, its misuse of personal information, or its breach of confidentiality.

Founders should be wary of broad indemnities that are one-sided, unlimited or disconnected from actual fault.

Intellectual property licences and restrictions

The legal risk is not just who owns the IP, but also what rights each side gets to use it. A platform provider may need a limited licence to host and display your course materials. That does not mean it should be free to reuse your content for unrelated purposes.

Check whether the agreement allows the provider to:

• copy or adapt your materials beyond what is needed to supply the service
• use your content to train tools or improve its products
• display your branding in its marketing
• restrict your access to exported content after termination

If you work with course creators or production contractors, make sure your upstream contracts also give you the rights you need. Otherwise, you can end up promising platform rights you do not actually hold.

Privacy Act and data breach responsibilities

If the provider handles learner information, the agreement should say who is responsible for privacy notices, access requests, correction requests and breach response. A generic confidentiality clause is not enough.

Before you sign, check:

• whether the provider must notify you promptly about any suspected privacy incident
• whether it must help you investigate and respond
• whether it can engage sub-processors without your consent
• whether it can move data between jurisdictions
• whether data must be deleted or returned when the contract ends

These points matter because your users will usually look to your business first if their information is mishandled.

Dispute resolution and governing law

The agreement should make disputes easier to manage, not harder. If the provider is overseas, you may find a contract governed by another country's law with disputes heard in a foreign forum.

That does not always make the deal unworkable, but it changes cost and leverage. A New Zealand business should understand whether it is practical to enforce the agreement if something goes wrong.

Common Service Agreement Mistakes

The biggest mistake is treating the service agreement like a routine click-through document when the provider is central to your business. A bad contract usually becomes a problem only after the relationship is under pressure.

Accepting vague deliverables

If the statement of work is thin, you may pay for a result that was never clearly promised. This commonly happens with custom platform builds, migration projects and integrations.

Before you sign a contract, make sure deliverables are measurable. "Course upload support" is vague. "Migration of up to 40 existing lessons, 200 student records and completion data into the live environment by 30 September" is much easier to enforce.

Relying on sales conversations

Founders often rely on a verbal promise that a feature exists, support is available on weekends, or a future update will solve a limitation. If the contract says the written terms are the entire agreement, those statements may be difficult to rely on later.

If a point matters to your buying decision, put it in writing in the agreement, order form or scope document.

Ignoring exit planning

The main risk is not always at the start. It is what happens when you want to leave.

Businesses get stuck when they discover too late that:

• content exports are limited
• student data comes out in an unusable format
• the provider charges high transition fees
• custom features do not work outside the provider's ecosystem
• termination requires long notice before renewal

Before you rely on a verbal promise about flexibility, check the actual exit mechanics.

Missing ownership gaps with contractors and educators

Online course platforms often depend on a chain of contributors, such as educators, videographers, instructional designers and software freelancers. If your contract with the platform provider assumes you own all uploaded content, but your contractor agreement does not transfer rights properly, you can create a legal mismatch.

This is where founders often get caught. One agreement says you can license content broadly, another says the creator keeps ownership and only gives limited use rights.

Overlooking privacy and marketing claims

Course businesses frequently promote secure learning environments, easy certification and strong data protection. If the service provider cannot actually support those claims, your own business may face complaints or reputational damage.

Check your agreement against the way you describe the platform to customers. Contract terms, privacy disclosures and marketing claims should line up.

Not matching the contract to the provider type

A service agreement with a hosted software provider should not look identical to an agreement with a content producer or a marketing agency. Different providers create different risks.

For example:

• a developer agreement should focus heavily on specifications, acceptance testing and IP ownership
• a hosting agreement should focus on uptime, backups, security and support
• a content creator agreement should focus on ownership, permissions, moral rights and revision process
• a payment-related service agreement should focus on compliance obligations, chargeback handling and data security

Using a generic template can leave major gaps.

FAQs

Do online course platforms in New Zealand need a written service agreement?

In practice, yes. A written agreement helps avoid disputes about scope, ownership, fees, privacy and support. It is especially important where the provider handles student data, builds custom features or hosts your course content.

Who should own the course content on a learning platform?

Your business will usually want to retain ownership of its course materials, branding and existing content. A provider may need a limited licence to host and display that material so it can supply the service, but the licence should be no broader than necessary.

Can a provider limit its liability for outages or data loss?

Often yes, at least in part, but the clause should be reviewed carefully. The key issue is whether the cap and exclusions are commercially reasonable given the provider's role and the damage an outage or data issue could cause your business.

What privacy terms should be in the agreement?

The agreement should cover data use, storage location, security measures, subcontractor access, breach notification and what happens to data on exit. If the provider stores information offshore or uses third-party processors, that should be clear.

What should I check before accepting standard online terms?

Check the scope of services, renewal mechanics, fee changes, IP ownership, service levels, privacy clauses, liability caps and termination rights. Standard terms are often written to suit the provider, not your business model.

Key Takeaways

• A service agreement for an online course platform should clearly define scope, timing, support standards, fees and performance expectations.
• Ownership of course content, custom development, branding assets and learner data should be addressed expressly, not assumed.
• Privacy, security and data handling clauses matter where the provider accesses student information or stores data offshore.
• Liability caps, exclusions and indemnities should be reviewed against the real commercial risk if the platform fails or data is lost.
• Exit terms are critical, including data return, content export, transition support and auto-renewal timing.
• Verbal sales promises should be written into the contract before you sign or before you accept the provider's standard terms.

If you want help with contract review, service scope, intellectual property ownership, privacy terms, data protection obligations, or liability clauses, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.