Drafting SaaS terms of service for your UK startup: a practical guide

why your saas startup needs proper terms of service

Your SaaS product is live and customers are signing up. Without a clear set of terms of service you are relying on handshake promises and goodwill. That works until a payment is disputed, a user’s data is mishandled or a client expects features you never promised.

A well drafted terms of service document sets the rules of the road. It tells customers what they can and cannot do with your platform, clarifies your obligations and limits your exposure to claims. For a UK startup, it also helps you comply with consumer protection laws if you have any B2C users and with the rules that govern standard form B2B contracts.

This guide walks you through the key sections you need, in plain English. As always, it is not legal advice. When you are ready to rely on a contract, have a solicitor review your specific draft.

getting the basics right: whose terms apply

Your terms need to state clearly who is providing the service and who can accept the terms. The “who is providing” part is your company’s full legal name, registration number and registered office address. The “who can accept” part should define your customer: typically a business or an individual acting on behalf of a business. If you sell to consumers, you will need even plainer language and additional cancellation rights.

A simple start:

These terms are between ABC Tech Ltd (company number 12345678) of 123 Startup Street, London, and the customer identified during the account creation process.

what the customer gets: subscription and licence

Set out what you are selling. Is it a monthly subscription to access your platform? An annual licence? A one-time download? Most SaaS startups offer a limited, non-exclusive, non-transferable right to use the software for the customer’s internal business purposes. You are not selling the software itself, only a right to use it.

Be specific:

• describe any tiers or user seat limits
• state whether access is online only or includes any downloadable components
• note any fair use limits if you offer an “unlimited” plan

Avoid vague promises like “uninterrupted access” unless you intend to back that up with service credits or a genuine uptime guarantee.

payment terms and renewal mechanics

Customers need to know exactly what they owe and when. Spell out:

• the fee structure (monthly, annual, per user)
• payment due dates and methods
• whether fees will increase and on what notice
• what happens if payment fails

For SaaS, auto-renewal is common but must be transparent. If you are selling to consumers, the Consumer Rights Act 2015 requires that optional renewal terms are brought to their attention clearly. Even for B2B contracts, a renewal clause that surprises a customer can damage trust and lead to disputes.

Consider ending auto-renewal with a clear notice:

Your subscription will automatically renew for the same period at the end of each term unless you give us 30 days’ written notice before the renewal date.

Also explain how the customer can cancel. A customer portal is ideal; if you rely on email, confirm receipt.

data protection: building trust, not just compliance

Any SaaS startup handling customer data must address processing arrangements. Your terms of service should reference your data processing agreement (DPA), which sets out the detail required by UK GDPR. Do not bury GDPR obligations in the main terms document. Instead, make it a separate schedule or linked document that customers can review before signing up.

In your terms, include a simple statement like:

Where we process personal data on your behalf as a processor, the terms of our Data Processing Agreement apply. A copy is available at [link] and forms part of these terms.

If you process data as a controller for your own purposes (for example, to monitor usage analytics), make that clear too, and link to your privacy notice.

customer responsibilities and acceptable use

If a customer uses your platform to send spam, host illegal content or break the law, you need the right to suspend them quickly. An acceptable use policy, either embedded in the terms or as a separate document, gives you that power.

Common restrictions:

• no reverse engineering or scraping
• no use for uploading malicious code
• no activity that violates intellectual property rights of others
• no attempt to circumvent usage limits

Your terms should also state that customers are responsible for maintaining the confidentiality of their login credentials and for all activity under their account. This helps you push back if a dispute arises because a client shared passwords.

intellectual property: who owns what

Your SaaS code, brand and content are yours. Make that clear with a simple clause that reserves all rights not expressly granted. Customers often assume they own any data they input, so confirm that they do. You might also mention any licence they grant you to host and display that data solely to provide the service.

If your platform produces output or reports using the customer’s data, state who keeps ownership of that output. Some startups assign all output to the customer; others keep a licence to use aggregated, anonymised data to improve the platform. Be transparent here to avoid misunderstandings during due diligence or a dispute.

limiting your liability

This is where founders often freeze up. The key is to be reasonable and to comply with UK law. The Unfair Contract Terms Act 1977 and the Consumer Rights Act 2015 prevent you from excluding liability for death, personal injury, fraud or a fundamental breach. Beyond that, you can cap your financial exposure.

A typical cap in B2B SaaS agreements is the fees paid by the customer in the previous 12 months. Never use a nominal figure like £1 total cap unless you have taken legal advice, because a court might strike it down as unfair. Exclude indirect losses, lost profits and data loss, but double-check your insurance and commercial appetite.

term, suspension and termination

Set out how long the contract lasts (usually the subscription period) and the grounds on which either party can end it. These usually include:

• breach not remedied within a reasonable time
• insolvency or similar events
• regulatory or technical reasons that make service continuation impossible

Include a data export clause: give the customer a limited window to retrieve their data after termination. This builds goodwill and reduces the risk of a GDPR-themed complaint. State that you will delete their data after that window unless you are required to keep it by law.

changes to terms and services

You will update your software and your pricing. Reserve the right to amend the terms by giving reasonable notice – 30 days is a common starting point. For material changes that negatively affect the customer, consider offering the right to terminate without penalty during the notice period. This approach often satisfies your customer success team and reduces friction.

what a good first draft looks like

When you do not have a lawyer, start with a template designed for UK SaaS businesses. StartupDocs templates cover the essential clauses and let you edit with AI tracked changes, so you can adapt the draft to your own pricing model and risk profile. Then run it past a solicitor once you have budget. The cost of fixing a hurried DIY contract after a payment dispute is almost always higher than getting it reviewed early.

quick checklist before you publish

• Company details correct
• Licence scope clearly defined
• Subscription fees, payment terms and renewal mechanics spelled out
• Data processing agreement linked and incorporated
• Acceptable use restrictions included
• Intellectual property ownership clear
• Liability cap reasonable and compliant with UK law
• Termination, suspension and data export process covered
• Change control notice period fair
• Signed or accepted by the customer (clickwrap or electronic signature)

A well drafted terms of service won’t stop disputes from ever happening, but it gives you a clear starting point when they do. For an early stage startup, that clarity is worth far more than the modest effort of getting the paperwork right.