Marketplace terms and conditions, a clause-by-clause guide for Australian platforms

You have built the two-sided machine: a way for customers to find the service, and a way for providers to fill the demand. The beta is live, the first disputes have landed in your inbox, and someone has just sent you a template of marketplace terms to sign off before launch. It runs to thirty pages of dense clauses, and the template was clearly written for a different country and a different business model.

Your marketplace terms are the standard-form contract between the platform operator and everyone who uses the platform: the customers on one side, the providers on the other. They bind both sides, they displace the legal default that a platform is just a passive bulletin board, and they allocate who carries the risk when a booking falls through, a service is substandard or money goes missing. They also sit alongside a small stack of companion documents: a privacy policy, an acceptable use policy and, where you onboard providers, a contractor agreement. This guide walks through the clauses that matter, the drafting choices behind each one, and the traps that cause problems later.

The clauses that carry the weight

Who can join the platform

The terms should state who is eligible to join: minimum age, identity and verification requirements, and any licences or qualifications a provider needs. They should also set out the grounds on which the platform can suspend or terminate an account, such as low ratings, safety incidents, fraud or repeated policy breaches. The drafting choice that matters most is how much discretion you keep. A clause that lets the platform suspend accounts for any reason at its sole discretion is easy to enforce, but it reads badly to regulators and, for gig platforms, collides with the new worker protections discussed below. Three points deserve attention:

• Verification rights: reserve the right to run identity, background and licence checks, and to refuse or suspend accounts where checks fail or information turns out to be false.
• Consequences: state what suspension means in practice: access blocked, payouts withheld while an investigation runs, and whether there is any review or appeal step.
• The trap: for platforms that onboard gig workers, deactivation is no longer purely a matter of contract. The Fair Work Act 2009 (Cth) now protects employee-like workers on digital labour platforms from unfair deactivation once they have performed work through the platform on a regular basis for at least six months, and requires a Digital Labour Platform Deactivation Code dealing with valid reasons for deactivation and rights of response. Draft your termination rights with that framework in mind, not against it.

What users are allowed to do

A platform licence clause grants each user a limited, revocable, non-transferable right to use the app or site for its intended purpose. The matching acceptable use clause lists what is prohibited. For a marketplace, the prohibitions that carry real commercial weight are usually:

• Scraping and data-mining: copying listings, prices or profiles to build a competing database.
• Circumventing fees: arranging the deal off-platform after the match is made, so the commission never gets paid.
• Fake accounts and fake activity: inflating reviews, generating dummy demand or running multiple identities.
• Illegal or dangerous use: anything that breaks the law, or that creates safety risks the platform cannot control.

The drafting choice that matters is enforcement, not prohibition. A long list of prohibited conduct is worth little if the terms do not also give the platform the right to investigate, suspend and terminate for breaches, and to withhold payouts pending an inquiry.

How listings, matching and prices work

This clause explains, in plain language, how a customer finds a provider, how matches happen, and how prices are set: provider-set, platform-set, dynamic or recommended. Keep the description honest about what actually happens, because accuracy here is a legal requirement, not a UX nicety. Under s 18 of the Australian Consumer Law (ACL), which is Schedule 2 of the Competition and Consumer Act 2010 (Cth), a person must not, in trade or commerce, engage in conduct that is misleading or deceptive or is likely to mislead or deceive. A fare estimate or price range displayed in the app is conduct caught by s 18 if it is wrong. That is exactly what happened to Uber: the Federal Court found that the fare ranges Uber displayed for its UberTaxi product represented that the price a customer would pay would likely sit within the displayed range, when in fact the price was likely to be below it, in Australian Competition and Consumer Commission v Uber B.V. [2022] FCA 1466.

How fees, payouts and withholding work

For the platform this is the revenue clause; for providers it is the clause they read first. It should set out the commission or service fee, when it is charged, how payouts are calculated and timed, and the platform's rights to withhold or set off amounts for disputes, chargebacks or breaches. Two drafting choices deserve particular care:

• When the fee is earned: say whether the commission applies on booking, on completion or on payout, and what happens to the fee when a booking is cancelled at each stage of the lifecycle.
• Fee changes: if the platform can vary fees, say how much notice applies and how users are told. A power to change fees at any time without notice is a classic unfair contract term candidate, and it also destroys user trust.

The trap in this clause is overreach: broad set-off rights that let the platform dip into a provider's earnings for any debt, however unrelated, are exactly the kind of one-sided term the unfair contract terms regime targets. Keep set-off proportionate and tied to the transaction at hand.

Cancellations, refunds and what the law will not let you exclude

Spell out who can cancel, in what window, and what refund or fee applies in each case. Then check the policy against the ACL twice. First, the consumer guarantees in the ACL apply to supplies to consumers and cannot be excluded, restricted or modified by contract: s 64 of the ACL voids any term that purports to do so. The guarantee of due care and skill in s 60 applies to services supplied to consumers, so a marketplace that facilitates service provision cannot contract out of the quality standards the guarantee implies. Second, s 18 catches any mismatch between what the terms promise and what the app actually displays. In the same Uber case, consumers who selected Cancel Trip during a free-cancellation period were shown a message that they may be charged a small fee, when no fee would be charged at all. That message appeared across about 7.39 million UberX, Uber Premier and Uber Comfort trips and for around 74,559 UberPool customers. The court ordered Uber to pay penalties totalling $21 million across the fare-estimate and cancellation conduct. Nothing in Uber's written terms was misleading on its face; the contravention lived in the gap between the terms and the product.

A refund policy worth having specifies:

• Cancellation windows: free-cancellation periods, and fees for cancelling after them.
• Refund mechanics: whether refunds go back to the original payment method, in what timeframe, and who bears any platform fee.
• Quality failures: what happens when the customer says the service was not delivered or was substandard, and who investigates.

Service standards, safety and insurance

For a marketplace, the quality of the network is the product. A service standards clause sets minimum expectations for providers: punctuality, equipment, hygiene, dress and conduct. Safety obligations should be stated separately, and insurance should be made a condition of participation. Think about what the platform needs before a serious incident occurs, not after:

• Insurance requirements: public liability cover for providers, and any vehicle or professional indemnity cover relevant to the category.
• Proof and audit: the right to ask for certificates of currency and to verify cover at onboarding and periodically.
• Incident handling: an obligation on providers to report safety incidents, and a platform right to stand down or suspend a provider during an investigation.

Ratings, reviews and moderation

Ratings are the marketplace's trust engine, so the terms should explain how they are calculated, when content may be removed, and what behaviour is prohibited: defamatory or offensive reviews, fake reviews, and retaliation against customers who leave honest feedback. Reserve express rights to investigate suspicious patterns, remove inauthentic reviews and act on abuse. This clause is also a defamation control point: the platform is better positioned if its terms give it the right and obligation to take down unlawful content, and if the moderation process is documented rather than ad hoc.

Who owns the content and the brand

The terms should protect the platform's own intellectual property: the brand, the code, the listings database and the marketing content. They should also deal with user-generated content. A common drafting choice is a broad licence from users to the platform to store, display and promote the content they upload, which the platform needs in order to operate at all. If providers are allowed to use the platform's brand, such as decals, uniforms or marketing materials, define the scope of that permission and make clear it ends when the account ends. Consider registering the platform name and logo as trade marks early; an unregistered brand is much harder to enforce against copycats.

What happens to user data

A marketplace collects personal information from both sides of the platform: names, contact details, payment data, location, ratings and sometimes identity documents. The Privacy Act 1988 (Cth) applies through the Australian Privacy Principles (APPs), and the terms should reflect them. APP 3 limits collection to what is reasonably necessary for the platform's functions, and requires consent for sensitive information. APP 5 requires notification at or before the time of collection: who the platform is, what it collects and why. Note that most businesses with annual turnover of $3 million or less are exempt from the APPs, but the exemption has exceptions, and it drops away as the business grows. A data clause worth keeping:

• What is collected and why: link the privacy policy, and keep the list of purposes aligned with what the product actually does.
• Sharing with processors: payments, identity checks and analytics vendors, and what happens to data when the platform changes vendors.
• Retention and deletion: what is kept, for how long, and what happens on account closure or platform wind-down.

Where liability stops, and where it cannot

Most marketplace terms position the platform as a facilitator rather than the direct supplier of the underlying service. That framing belongs in the terms, but it must be earned: if the platform sets prices, promises outcomes, or takes control of delivery, the facilitator language will not survive scrutiny. Within that framing, the liability clause typically includes disclaimers about service outcomes, a cap on the platform's aggregate liability, and indemnities from users for breaches they cause. Two statutory limits constrain the drafting:

• Consumer guarantees: s 64 of the ACL voids terms that exclude, restrict or modify the consumer guarantees. A disclaimer that says the platform takes no responsibility for quality will not displace the guarantees where they apply.
• Unfair contract terms: under s 23 of the ACL, a term of a consumer contract or small business contract is void if it is unfair and the contract is a standard form contract. A term is unfair if it causes a significant imbalance in the parties' rights, is not reasonably necessary to protect the platform's legitimate interests, and would cause detriment if relied on; s 24 also directs attention to how transparent the term is, and presumes such terms are not reasonably necessary unless the platform proves otherwise. Since late 2023, proposing an unfair term or applying one is a contravention carrying penalties: up to the greater of $100 million, three times the benefit obtained, or 30 per cent of adjusted turnover for a body corporate, and up to $2.5 million for an individual. The small business test is broad: a contract is a small business contract if at least one party employs fewer than 100 people or has turnover under $10 million. In practice, most marketplace providers and many marketplace operators fall inside the regime.

The traps in this clause are the familiar trio: one-sided indemnities that make providers liable for everything, caps that purport to exclude liability the law will not let the platform exclude, and boilerplate that is neither plain nor prominent.

How you can change the terms

Platforms change faster than contracts, so a variation clause is inevitable. The drafting choice is how the power is exercised: a clause that lets the platform amend terms at any time, without notice, is a UCT risk and a user-trust problem. A clause that requires reasonable notice of material changes, explains how users will be told, and lets them close their accounts if they do not accept the changes, is enforceable and fair. Keep a version history and capture acceptance of updated terms where fees or rights change.

How disputes get resolved

Finally, the terms should give users a path before lawyers get involved: a clear internal complaints process with stated timeframes, an escalation step, and then a forum. State the governing law of the contract, usually the state or territory where the platform is based, and the chosen forum for disputes. For low-value disputes, consider whether the cost of court proceedings is proportionate to the amounts at stake; some platforms build a small-claims or expert-determination step into the escalation ladder.

Situational clauses worth adding

Not every marketplace needs every clause on day one, but these earn their place quickly as the model develops:

• Provider and contractor terms: include once you onboard gig workers; the contractor relationship must be documented, and it now sits alongside the Fair Work Act's employee-like worker protections, including minimum standards orders for digital platform work.
• Off-platform deal prohibitions: include where matching is high-touch and providers could realistically take the customer direct after the first booking.
• Referral and incentive programs: include once you start paying either side to grow the network, so the terms of the program are contractual rather than ad hoc.
• Regulated category compliance: include when you add alcohol delivery, health services, childcare or financial products, each of which carries its own licensing and duty-of-care obligations.
• Enterprise and SLA addendums: include when business customers ask for service levels, security terms or negotiated pricing that the standard form cannot accommodate.

How an Artificer Legal lawyer would review your marketplace terms

A lawyer reviewing these terms for you would start by mapping the clauses to the product, because the clauses only work if they describe what the app actually does. The first things we would push back on are broad unilateral variation rights, one-sided indemnities, termination at sole discretion and disproportionate set-off rights, all of which are both UCT exposure and commercially corrosive. We would insist on a refund and cancellation matrix that matches the product's actual behaviour, a fee clause that states precisely when the commission is earned, and contractor documentation that reflects how the relationship operates in practice rather than how the platform wishes it operated. The order matters too: pricing and fees first, because that is where the money and most of the regulator risk sit, then liability and termination, then the operational clauses that keep the platform running day to day.

The clause that decides whether your terms survive contact with your app

The clause that most often decides whether marketplace terms work is not any single sentence in the document: it is the alignment between what the terms say and what the product shows. Uber's written terms were not the problem in the Federal Court case that cost it $21 million in penalties. The problem was that the app displayed a cancellation message that contradicted the free-cancellation policy, and fare estimates that did not match reality. Every clause in your terms is eventually displayed somewhere in your product: the fee schedule in a checkout screen, the cancellation policy in a Cancel Trip dialogue, the refund rules in a support ticket. When the two disagree, the ACL treats the displayed message as the conduct, and the penalty falls on the platform.

The terms that work are the ones written against the product, reviewed whenever the product changes, and kept honest about what the platform controls and what it does not. Draft them that way, check them against the ACL, the Privacy Act and the Fair Work Act's gig-work protections, and have a lawyer pressure-test them before launch. The cost of a review is trivial compared with the cost of a regulator finding the gap between your terms and your app.