Software Licence Agreements in the UK

Whether you’re building your own app, licensing a platform to clients, or buying tools for your team, software licences sit at the heart of how your business uses and monetises technology.

Get them right, and you’ll protect your intellectual property, prevent scope creep, and stay on the right side of UK law. Get them wrong, and you risk unpaid use, data claims, and messy disputes over what’s included.

In this guide, we break down software licences for UK small businesses in plain English – what they are, common licensing models, the must-have clauses, key UK laws to watch, and practical steps to put robust legals in place from day one.

What Is A Software Licence (For Businesses Like Yours)?

A software licence is the legal permission you grant (or receive) to use software under certain conditions. It doesn’t transfer ownership of the code – it sets the rules for how the software can be accessed, installed, and used.

From a business perspective, your software licence is both a revenue tool and a risk control. It tells customers what they get, what they don’t, and what happens if something goes wrong. If you’re the licensee (buying or subscribing), the licence sets your rights and obligations and where you might carry risk.

In UK law, computer programs are protected as “literary works” under the Copyright, Designs and Patents Act 1988. That means copying, adapting, or distributing software without permission can infringe copyright. A clear, written licence is how you authorise use and set limits that fit your commercial model.

If you’re commercialising software you’ve built, it’s essential to capture your rights in a proper Software Licence Agreement. If your product is delivered as a hosted service, your customer relationship is usually governed by tailored SaaS Terms and a website/app Terms of Use.

Which Software Licensing Model Fits Your Business?

There isn’t a single “right” way to license software. Choose the model that aligns with how you deliver value, your cost base, and how your customers buy.

Per-User or Seat Licences

Customers pay for a set number of named or concurrent users. This can work well for B2B tools where usage scales with team size. Make sure your licence explains how new seats are added, proration and what counts as “use”.

Subscription (SaaS)

Access to your hosted software for a recurring fee (monthly/annual), usually with tiers. Your “licence” focuses on access rights, uptime commitments, support and termination for convenience or non-payment. This model typically uses SaaS Terms rather than traditional installed software licences.

Perpetual (With Maintenance)

A one-off licence fee for on-premise installation, plus an annual maintenance and support fee. Your licence must address updates, compatibility, and what happens if maintenance lapses.

Feature- or Usage-Based

Pricing and rights tied to features (e.g., “Pro”, “Enterprise”) or usage metrics (API calls, data volumes, transactions). You’ll need clear definitions and audit rights to measure usage fairly.

OEM/Embedded and Reseller

You allow another business to embed your software into their product or resell your licences. This usually needs a dedicated commercial agreement alongside the end user licence – for example, a Software Reseller Agreement for channel partners.

Open-Source Components

Many products include open-source libraries. That’s fine – but know the licence obligations (e.g., attribution, disclosure of modifications, copyleft requirements). Your own licence should also disclaim that open-source components are used under their original licences.

Key Clauses To Include In Your Software Licence

Every licence should be tailored to your product and commercial model, but the following clauses are the backbone of a solid agreement.

1) Scope Of Licence

• Licence type: non-exclusive, non-transferable, revocable or irrevocable.
• Permitted uses: internal business purposes only vs client-facing use.
• Installations/instances: on-premise copies, test/dev environments, disaster recovery.
• Territory and duration: where and for how long the licence applies.
• Restrictions: no reverse engineering, decompiling, sublicensing, or sharing logins.

2) Users, Seats And Access Control

• Named vs concurrent users; how user changes are handled.
• Technical controls to prevent unauthorised use; single sign-on or MFA requirements.
• Audit rights and usage reporting, with fair notice and confidentiality.

3) Fees, Invoices And Price Changes

• Billing cycles, invoicing, taxes (e.g., VAT), and late payment consequences.
• Automatic renewals and notice periods for termination or changes.
• Uplift mechanisms: CPI-linked increases or percentage caps per renewal.

4) Support, Maintenance And Service Levels

• Support hours and channels, response and resolution targets.
• Updates and upgrades – included or paid, impact on compatibility.
• Planned maintenance windows and downtime communication.

5) Data Protection And Security

• Who is the data controller vs processor, and what personal data is processed.
• Security measures, encryption, and breach notification commitments.
• International transfers and appropriate safeguards (e.g., UK IDTA/Standard Contractual Clauses).

If you process customer personal data on their behalf, you’ll usually need a standalone or embedded Data Processing Agreement, and your public-facing Privacy Policy should explain how you collect and use personal data.

6) Intellectual Property

• Ownership of the core software, customisations and deliverables.
• Customer content rights – licence to host, copy and use for service delivery.
• Feedback licence – rights to use customer suggestions to improve the product.

If you’re engaging contractors to help build your product, make sure IP is assigned to your business in a robust Software Development Agreement or an IP Licence with clear assignment terms. Without this, you may not actually own the code you’re licensing out.

7) Warranties And Disclaimers

• Limited warranty that the software will materially conform to documentation.
• Exclusions for issues caused by misuse, third-party systems, or unsupported environments.
• Disclaimer of implied warranties to the extent permitted by law.

8) Liability And Indemnities

• Caps on liability (often linked to fees paid in a period) with carve-outs for death/personal injury, fraud, and other non-excludable liabilities under UK law.
• Exclusions of indirect or consequential loss (e.g., lost profits, data loss).
• Indemnities for third-party IP infringement and for customer misuse in breach of the licence.

Careful drafting here is critical. If you’d like a refresher on how to structure these provisions, this plain-English guide to Limitation of Liability is a useful starting point.

9) Term, Renewal And Termination

• Initial term and renewal mechanics (automatic renewals, opt-out windows).
• Termination for breach, insolvency or non-payment – and cure periods.
• Exit steps: data export, deletion, continued access to retrieve data, accrued fees.

10) Compliance, Audits And Export Controls

• Right to verify compliance and usage, with reasonableness safeguards.
• Customer’s responsibility to comply with relevant laws using the software.
• Compliance with sanctions and export controls where relevant.

UK Laws You Need To Consider

Licensing software isn’t just a contract exercise. A handful of UK laws shape what you can promise, what you must disclose, and what you’re responsible for.

Consumer Rights Act 2015 (Digital Content)

If you sell to consumers (B2C), the Consumer Rights Act 2015 sets quality standards for “digital content” – it must be of satisfactory quality, fit for purpose and as described. You may need to provide repairs, replacements or refunds if the software is faulty or misdescribed. Some rights can’t be excluded, so your licence must be consistent with these statutory protections.

Data Protection Act 2018 And UK GDPR

If your software processes personal data, you’ll need a lawful basis for processing, appropriate security measures, and clear transparency information. When you act as a processor for business customers, UK GDPR Article 28 requires processor terms – typically via a Data Processing Agreement. For your own data collection, publish and follow a compliant Privacy Policy, and ensure cookies/SDKs are deployed lawfully with consent where required.

Copyright, Designs And Patents Act 1988

This law protects your code and other original works. Your licence should clearly reserve all rights not expressly granted, and prohibit decompilation except to the limited extent permitted by law. Where possible, implement technical controls to back up your legal protections.

Business Protection From Misleading Marketing Regulations 2008

Marketing claims about performance, compatibility or “unlimited” features need to be accurate and substantiated. Your sales pages and licence should align to avoid misrepresentation risk.

Contracts (Rights Of Third Parties) Act 1999

Decide whether third parties (e.g., affiliates) can enforce terms – and say so. Many licences exclude third-party rights to avoid unintended enforcement.

Distance Selling And Auto-Renewal Rules

For online sales, be upfront about pricing, features, and renewal terms before checkout. Hidden auto-renewals or unfair cancellation hurdles can attract regulatory scrutiny. Your renewal and price change language should be clear, prominent, and fair.

Practical Steps To Licence Software The Right Way

Here’s a straightforward roadmap to get your legal foundations in place.

1) Map Your Commercial Model And Risks

• Decide on seat vs usage vs enterprise licensing, and how you’ll scale pricing.
• List what “access” includes (environments, support tiers, uptime) and what’s out of scope.
• Identify regulated data or sectors (health, finance, children) that add compliance duties.

2) Lock Down Your IP Ownership

• Ensure employees and contractors assign IP to the company – update contracts now, not later.
• Confirm you have rights to all third-party libraries, fonts, and datasets used in the product.
• Document open-source components and comply with their licences (attribution, notices).

If there are gaps (common after rapid MVP builds), address them with a tailored Software Development Agreement or an IP Licence to bring rights into your company.

3) Draft The Right Agreement For Delivery

• On-premise or installable products usually use a traditional Software Licence Agreement (and often an end-user licence presented on installation).
• Hosted products should be covered by clear, modular SaaS Terms and a user-facing Terms of Use that link together cleanly.
• Resale or partner channels are best handled by a dedicated Software Reseller Agreement with revenue share, territory, and performance commitments.

4) Build In Privacy And Security From The Start

• Publish an accurate Privacy Policy that matches how your platform actually operates.
• Offer a customer-friendly Data Processing Agreement for B2B clients that need Article 28 terms.
• Implement technical and organisational measures (encryption, access controls, logging) and reflect these in your contracts without over-promising.

5) Calibrate Liability And Remedies

• Set realistic warranties (material conformity) and carve-outs for misuse or third-party failures.
• Use sensible liability caps, exclusions for indirect loss, and carve-outs for non-excludable liabilities.
• Offer practical service credits for SLA breaches rather than broad refund rights.

6) Make Renewal, Price Changes And Termination Clear

• Flag auto-renewals and price uplifts clearly at sign-up and in renewal notices.
• Explain what happens on exit: data export formats, deletion timelines, and offboarding support.
• Include a fair cure period for remediable breaches to reduce dispute risk.

7) Operationalise Compliance And Audits

• Implement usage tracking (e.g., per-seat enforcement) consistent with your licence.
• Prepare a sensible audit process – reasonable notice, confidentiality, and cost allocations.
• Train sales and support teams so promises match what the licence actually says.

FAQs And Common Scenarios

Can I Rely On A Click-Through Licence?

Yes, for many B2B and B2C products a click-through acceptance at sign-up or installation is valid, provided the terms are accessible and acceptance is affirmative (e.g., a tick box). Keep a record of versions and acceptance events. For enterprise deals, negotiated terms signed by both parties are still common.

What If A Client Wants Custom Features?

Keep bespoke work in a separate statement of work that sits under your master terms. Define whether code is part of your core product (you own it and license it back) or a customer-specific add-on. Your base licence should anticipate customisations to avoid disputes later.

Do I Need An EULA As Well As My Licence?

“EULA” (end user licence agreement) is just the user-facing licence for installable software. If your customers are enterprises, you may use a master licence plus order forms. If your product is in an app store, you’ll often present an EULA on install alongside the platform’s terms.

What About Using AI Within My Product?

Be transparent about AI features, training data sources, and limitations. Address ownership of outputs and any third-party content risks. Where AI processes personal data, ensure your privacy and processing notices are updated and accurate.

Mistakes To Avoid When Licensing Software

• Not securing IP first. If contractors own parts of your code, you can’t license confidently. Fix this with proper assignments before you scale.
• Over-promising uptime or remedies. Generous SLAs can backfire – calibrate to what your team can deliver consistently.
• Vague usage metrics. “Reasonable use” is not measurable. Define seats, transactions, storage limits and how you’ll measure them.
• Ignoring open-source obligations. Maintain a list of OSS components and keep notices up to date.
• Copy-pasting consumer language into B2B deals. Enterprise procurement expects negotiated liability, data protection and audit language.
• Unclear renewal or price increases. Hidden auto-renewals or sudden uplifts damage trust and may be non-compliant for consumer sales.

When To Get Legal Help

If you’re onboarding your first enterprise customer, entering a reseller/OEM arrangement, or processing sensitive personal data, it’s worth getting your documents professionally drafted and aligned with your product and risk profile. Avoid generic templates – they rarely fit how your platform actually operates.

A lawyer can also help you map the interplay between your product docs: your Software Licence or SaaS Terms, website Terms of Use, Privacy Policy and Data Processing Agreement should all line up and not contradict each other.

Key Takeaways

• A software licence is your permission slip and rulebook – it sets the scope of use, restrictions, fees, and remedies while protecting your IP.
• Choose a licensing model that matches how you deliver value (seats, usage, perpetual, SaaS) and reflect it clearly in your terms.
• Include the essentials: scope of licence, user/access controls, support/SLAs, data protection, IP ownership, warranties, and calibrated liability caps.
• UK laws matter – especially the Consumer Rights Act 2015 for B2C digital content, the Data Protection Act 2018/UK GDPR, and copyright rules under the CDPA 1988.
• Get your foundations right: secure IP ownership with developers, publish accurate privacy information, and use the right agreement for your delivery model.
• Don’t rely on templates – align your Software Licence Agreement or SaaS Terms with how your product actually works and the risks you’re willing to carry.

If you’d like help drafting or reviewing your software licence, SaaS terms or data protection documents, you can reach us on 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.