Terms for a no-code product built on another platform

A product built on someone else's platform is a product whose availability, data location, pricing and future are partly decided by a company its customers have never heard of, and the terms have to say so without frightening the customer off. They have to be honest about the dependency, exclude what the platform controls from the supplier's commitments, put the platform in the subprocessor list, settle what the supplier owns in what it built, pass down the platform's rules, and provide for the day the platform changes its terms or closes. I draft those terms for a fixed fee of £995, delivered in five working days.

Who this is for

Businesses in England and Wales selling a product built on no-code, low-code, workflow or database platforms, or on another company's application as an add-on, who need customer terms that fit the product they can deliver.

What matters in terms for a product built on another platform

What the customer is told about the platform

The terms should disclose that the product is built on and operates through a named third-party platform, that the supplier does not control it, and that the product depends on the platform's continued availability and terms; a customer that discovers the dependency when the platform fails has a misrepresentation argument, and a customer told at the outset has a contract. The description should be accurate under section 3 of the Misrepresentation Act 1967, which limits exclusions of liability for pre-contract statements to what is reasonable.

Availability and the platform's outages

Any availability commitment should exclude downtime caused by the platform and by the other third-party services the product uses, and the terms should say that the supplier passes on the platform's published availability rather than guaranteeing its own, with the supplier's obligation limited to reasonable care and skill under section 13 of the Supply of Goods and Services Act 1982 in operating what it controls. Service credits, if offered, should not be payable for platform outages the supplier cannot influence.

Data location, the platform as subprocessor and security

Customer data lives on the platform's infrastructure, often outside the UK, so the platform is a subprocessor that must be listed under the processor terms Article 28 of the UK GDPR requires, with its location and the transfer mechanism under Article 46 stated, and the supplier's security commitments under Article 32 limited to what it controls and supplemented by the platform's certifications. A supplier that promises data residency it cannot deliver has promised the platform's roadmap.

Intellectual property in what was built

The supplier owns the configuration, logic, workflows, interface and content it created on the platform, to the extent the platform's terms allow, under the Copyright, Designs and Patents Act 1988, and licenses the customer to use the product; the platform owns the platform. The terms should say what the supplier owns and licenses, that the customer receives no rights in the platform beyond those needed to use the product, and, where the customer could in theory export the build to its own platform account, whether that is permitted.

The platform's terms flowing down

The platform's terms will require the supplier to impose obligations on its customers: acceptable use, no reverse engineering, compliance with the platform's policies, and sometimes the platform's right to suspend, and the terms should flow those down so that the supplier is not in breach of the platform contract because of a customer's conduct. Where the platform's terms permit the platform to access data for support or to change features, the customer terms should say so.

Platform changes, closure and liability in proportion

The terms should allow the supplier to change the product where the platform changes, to migrate to another platform on notice with data preserved, and to terminate on notice with a refund of prepaid fees if the platform ends or changes its terms so that the product cannot continue, and should cap liability at the fees paid with the dependency-related losses excluded, tested under section 11 of the Unfair Contract Terms Act 1977 for business customers and within the Consumer Rights Act 2015 for consumers. English law applies and third-party rights are excluded under the Contracts (Rights of Third Parties) Act 1999, with the platform neither a party nor a beneficiary.

What it costs

SaaS terms of service, £995. Your standard customer-facing terms. Five working days.

Buying online forms the engagement on payment. The scope is what the saas and technology contracts page describes, you accept the Terms of Service at checkout, and I email you within four working hours to get started. If you would rather ask something first, email me.

What you get

• A bespoke contract drafted for how your product is sold, delivered and supported
• Service levels you can meet, with remedies that are proportionate rather than aspirational
• A liability position that is defensible and will survive enterprise procurement
• IP and data provisions that fit together rather than contradicting each other
• A commercial note on where you will get pushback and what is worth conceding
• One round of amendments

What is not included

• Negotiating individual enterprise deals, which I quote separately
• Advice on the law of jurisdictions outside England and Wales
• Technical security certification or audit
• Regulatory advice for regulated sectors such as financial services or health

Questions I am often asked

Do we have to tell customers which platform we are built on?

The terms disclose the dependency and the platform's role as subprocessor, which requires naming it in the subprocessor list at least. Customers who ask where their data is will find out anyway, and the terms are better read first.

The platform doubled its prices. Can we pass that on mid-term?

Only if the terms allow price changes on notice with a right to cancel, which the terms provide for business customers, or at renewal. A consumer's price can change only at renewal with notice and a right to cancel first.

If the platform shuts down, do we owe customers anything?

A refund of prepaid fees for the unexpired period, and the terms say so, with the supplier's liability for the customer's wider losses excluded. Migration to another platform on notice is the alternative the terms also provide for.

Related guidance and services

• SaaS and technology contracts, £995, the service this page describes
• Contract review, £495
• Data protection agreements and privacy terms, £795
• Terms for a Shopify app or plugin
• SaaS terms of service for a B2B product

This page is general guidance for businesses in England and Wales, not advice on your own circumstances. Last reviewed: September 2026. Email geoffrey@caesar.co.uk.