Software Licence Or License In The UK?

If your business develops, sells, bundles or simply uses software, you’ll deal with software licences (or licenses) sooner rather than later. The licence is the rulebook that says who can use the software, how, and on what terms. Get it right and you protect your IP, your revenue and your relationships. Get it wrong and you risk disputes, data issues and lost value.

In UK English, “licence” is the noun and “license” is the verb. In US English, “license” is used for both. Whichever spelling your customers prefer, what matters is that the agreement clearly grants permission and sets the ground rules.

In this guide, we’ll explain what a software licence is under UK law, the main licence models, the key clauses you should include, open‑source considerations, and the documents and laws you need to know. We’ll keep things practical and from a small business owner’s perspective, so you can stay protected from day one.

What Is A Software Licence (Or License) And Why Does It Matter?

A software licence is a legal permission from the intellectual property owner (usually you, the developer/vendor) to someone else (your customer or end‑user) to use your software in specific ways. It doesn’t transfer ownership of the underlying code – it grants limited rights to use it.

Under the UK Copyright, Designs and Patents Act 1988, computer programs are protected as “literary works”. That gives you exclusive rights to copy, distribute and adapt the code. A licence is how you legally allow others to do some of those things under conditions you set.

Why it matters to your business:

• Revenue protection: define the scope (number of users, devices, sites, or transactions) so usage can scale with price.
• IP control: preserve ownership of code, brand and know‑how, and set limits on reverse engineering or redistribution.
• Risk management: limit your liability, allocate responsibility for data, and set rules for support, updates and uptime.
• Clarity: avoid misunderstandings about deliverables, features and performance by putting it all in writing.

For most B2B software businesses, the right tool is a tailored Software Licence Agreement or, for hosted products, robust SaaS Terms.

Common Software Licence Models (And When To Use Them)

There isn’t one “right” licence model – the best option depends on how you deliver value and how your customers buy. Here are the models you’ll see most often in the UK market.

Perpetual Licence (On‑Premise)

The customer pays a larger, one‑off fee for a right to use a specific software version indefinitely, often with optional annual support/maintenance. Good for environments that need on‑prem control (e.g. regulated clients) but can make recurring revenue tougher unless support is mandatory.

Subscription (Term‑Based)

Customers pay monthly or annually for ongoing access. This is the default in SaaS and increasingly common even for on‑prem products. Subscriptions can be tied to users, seats, devices, features, or consumption (e.g. API calls). Easy to scale and align price with value.

End‑User Licence Agreement (EULA)

A EULA is a standard form licence presented at install or first use, typically for mass‑market or downloadable software. It sets baseline permissions and restrictions. It’s often “click‑wrap” accepted on screen. If your software is consumer‑facing or distributed at scale, an online EULA can be appropriate (often alongside EULA terms embedded in your product flow).

Enterprise Or Site Licence

A broader grant for an organisation to deploy across a location, business unit or entire enterprise, often with volume pricing and stricter audit rights. Useful for larger customers who need flexibility without counting every seat.

Concurrent Or Floating User Licence

Limits the number of simultaneous users rather than named users. Works well where many staff access software occasionally.

OEM/Embedded Licence

Allows another company to embed your software in their product. Pricing and obligations are typically bespoke, and IP ownership and branding rules are critical.

Open‑Source Licences (Inbound And Outbound)

Open‑source components in your stack are governed by their own licences (e.g. MIT, Apache 2.0, GPL). Some are permissive, others require you to disclose source code for derivative works. We cover open‑source risk later, but it’s vital to track and comply.

When To Use Which?

• SaaS or web‑delivered? Use SaaS Terms with a strong data and uptime framework.
• Installable desktop/app? Use a EULA and, if selling to organisations, a commercial licence variant for B2B sales.
• Enterprise buyers? Consider site or enterprise licences with usage audits.
• Embedding in third‑party hardware/software? Use OEM terms with clear IP, branding and update mechanics.

Key Clauses Every Software Licence Should Include

Regardless of the model, most B2B software licences cover the same core areas. Here’s what to include, in plain English.

1) The Grant Of Licence (Scope)

Spell out exactly what the customer can do:

• Type of licence (non‑exclusive, non‑transferable, revocable)
• Permitted uses (business internal use, production vs test)
• Limits (users/seats, devices, locations, transactions, feature tiers)
• Delivery (download, keys, hosted access)
• Prohibited acts (resale, sub‑licensing, reverse engineering, scraping)

Tip: link scope to pricing. If usage increases, price increases – and your audit/measurement mechanism should support that.

2) Intellectual Property And Ownership

Make clear you retain all IP in the software, documentation and updates. If you build custom features, confirm whether they’re part of your core IP or customer‑specific. Where development is bespoke, a separate Software Development Agreement with a clear IP ownership or IP Assignment clause is essential.

3) Fees, Invoicing And Price Changes

State the fee model (per seat, per site, usage‑based), billing frequency, payment terms, and what happens on late payment. If you plan to index or update prices on renewal, say how and when you’ll notify customers (e.g. 30 days before renewal).

4) Support, Maintenance And Updates

Be explicit about support hours, response/target fix times, what’s included (bug fixes, minor updates), and what’s excluded (customisation, on‑site support). If uptime is critical, include a service level (SLA) or keep it in your SaaS Terms with credits for breaches.

5) Data Protection And Security

If you’re processing personal data for customers, UK GDPR and the Data Protection Act 2018 require a written contract that covers specific points (purpose, instructions, confidentiality, security measures, sub‑processors, breach notices, deletion/return). This is typically handled in a Data Processing Agreement linked to or embedded within your licence. Also set expectations around backups, encryption, and data export on exit.

6) Warranties And Disclaimers

Common warranties include that you have the right to license the software and that it will perform substantially as described. Then limit warranties with sensible disclaimers – you won’t guarantee error‑free operation or fitness for every purpose. Balance is key: give customers confidence without over‑promising.

7) Limitation Of Liability

Under UK law, you can’t limit liability for death/personal injury due to negligence or for fraud. For commercial software, it’s standard to cap liability (e.g. fees paid in the last 12 months) and exclude indirect or consequential losses. Make sure your cap and exclusions are reasonable to remain enforceable under the Unfair Contract Terms Act 1977.

8) Audits, Measurement And Anti‑Piracy

Give yourself the right to audit usage (on reasonable notice) or to use technical measures to monitor compliance. Explain how you’ll address over‑use (true‑up fees rather than immediate termination, where appropriate).

9) Term, Renewal And Termination

Set the initial term (perpetual or fixed term), renewal mechanics (auto‑renew with notice, or opt‑in), and termination rights (for breach, insolvency, non‑payment). Include a post‑termination wind‑down: de‑install, stop using, destroy keys, export and delete data.

10) Confidentiality

Protect any non‑public information exchanged under the deal, including your source code, roadmaps and security information. Where sensitive info is shared pre‑contract, use a Non‑Disclosure Agreement.

11) Governing Law And Jurisdiction

Choose England & Wales law and courts (or arbitration) to avoid cross‑border uncertainty, unless you have strong reasons to accept another forum.

12) Acceptable Use And Website Terms

If the product is web‑based, pair your licence with clear acceptable use rules (no unlawful content, spam, scraping or load testing) and public‑facing Terms of Use that control platform behaviour for non‑contracted users.

SaaS‑Specific Issues (Hosting, Uptime, Data And Exit)

Delivering software as a service brings extra obligations and practical questions. If you run a SaaS product, make sure your terms address the following.

Hosting And Uptime

• Uptime commitment (e.g. 99.9% excluding planned maintenance) and how you measure it
• Maintenance windows and notice periods
• Credits or remedies for SLA failures (and any cap)
• Disaster recovery and RTO/RPO targets (at a high level)

Security And Sub‑Processors

State your security controls at a practical level (encryption in transit/at rest, role‑based access, logging). Identify sub‑processors (e.g. your cloud or analytics providers) and how you’ll notify customers of changes. These points often sit in your Data Processing Agreement.

Privacy Compliance

Explain what personal data you collect as a controller (e.g. account admins), and link to a transparent Privacy Policy. Where you process customer data as a processor, ensure the DPA covers UK GDPR’s mandatory clauses. If you transfer data outside the UK, include appropriate safeguards (e.g. UK IDTA or EU SCCs with UK addendum, where relevant).

Customer Data Ownership And Exit

Make it clear customers own their content and can export it in a sensible format. Provide a standard data export window and a deletion schedule after termination. This builds trust and reduces friction at renewal time.

Open‑Source And Third‑Party Components: Do’s And Don’ts

Most modern software stacks use open‑source libraries and third‑party APIs. That’s fine – but you need a handle on the licences that come with them.

• Track components: maintain a bill of materials (BOM) so you know which licences apply (MIT, Apache 2.0, GPL, LGPL, etc.).
• Comply with notices: many licences require attribution and to include the original licence text with your distributions.
• Beware copyleft: strong copyleft licences (e.g. GPL) can require disclosure of source for derivative works. Mitigate by isolating components or choosing permissive alternatives if your business model depends on closed source.
• Watch patents: some licences include patent grants; understand if you’re comfortable with their scope.
• Vet third‑party SDKs and APIs: ensure their terms permit your intended use and don’t clash with your promises to customers.

If you commission external developers, your contract should require disclosure of open‑source use, compliance with licence obligations, and assignment of new IP. A clear Software Development Agreement is your safety net here.

Buying Software For Your Business? Key Terms To Look For

If you’re on the customer side, the right licence protects your operations. Before signing, look for:

• Scope that matches your use (number of users, locations, cloud vs on‑prem)
• Clear SLAs if downtime would hurt your business
• Strong data protection obligations and a compliant Data Processing Agreement where the vendor processes your personal data
• Fair liability cap (ideally linked to your spend and risk)
• Exit rights and data export commitments
• IP indemnity if you worry about third‑party infringement claims
• Reasonable audits and usage reporting (especially with remote work)

If the vendor’s standard terms don’t fit your risk profile, negotiate. Even small changes can materially reduce risk.

How To Put Robust Software Licence Terms In Place (Step‑By‑Step)

1) Map Your Commercial Model

Decide how you’ll charge (per user, per feature, consumption), how you’ll deliver (download vs hosted), and who you’ll sell to (SMEs vs enterprise). Your licence follows the model – not the other way around.

2) Define Scope And Metrics

Choose measurable usage metrics aligned to value. For SaaS, that might be active users or monthly tracked events; for on‑prem, devices or cores. Plan for growth: allow upsizing mid‑term and true‑ups on renewal.

3) Separate Implementation From Licence

Keep your licence for ongoing rights and pair it with a statement of work or a Software Development Agreement for any setup, customisations, integrations or training. This avoids disputes about what was “included.”

4) Cover Data And Security Early

Draft your Data Processing Agreement and Privacy Policy alongside your licence so they’re consistent. Customers will ask – having these ready speeds up sales cycles.

5) Publish Or Present Terms Clearly

If you sell online, present your EULA or SaaS Terms in a click‑wrap flow (checkbox + link to terms) rather than a passive browse‑wrap. For negotiated deals, attach the full licence and any schedules to your order form.

6) Build An Update And Renewal Process

Set reminders for renewal notices and price adjustments. If you periodically update online terms, include a sensible change mechanism and notice period – and log versions per customer.

7) Don’t DIY The Legals

Templates found online rarely fit your model or UK law. It’s worth getting a tailored Software Licence Agreement drafted so it actually protects your revenue and IP.

Key UK Laws That Affect Software Licences

You don’t need to memorise legislation, but you should know the big ones that shape your obligations.

• Copyright, Designs and Patents Act 1988: protects your source code and other creative assets. Your licence is the legal permission to use that IP.
• UK GDPR and Data Protection Act 2018: govern personal data. If you process customer data, you need a compliant processor contract, security measures and transparency.
• Consumer Rights Act 2015: if you sell to consumers, digital content must be of satisfactory quality and match its description, and consumers have statutory remedies for faulty content. Be careful with warranty/limitation clauses in B2C – many won’t be enforceable.
• Unfair Contract Terms Act 1977: sets the reasonableness test for liability limitations and exclusions in B2B contracts.
• Electronic Commerce Regulations/Distance Selling rules (now under the Consumer Contracts Regulations): affect how you present online terms and cancellation rights for consumers.
• Export controls and sanctions: if you distribute encryption technologies or sell into sanctioned jurisdictions, specialist advice may be required.

It can be overwhelming to know exactly which apply to your setup – chatting to a legal expert about your specific product and risk profile is a smart move.

Common Mistakes (And How To Avoid Them)

• Vague scope: “unlimited use” sounds friendly but kills your ability to scale pricing. Define users, devices or usage.
• No data terms: skipping a DPA when you process personal data is a UK GDPR breach and a sales blocker.
• Over‑promising uptime: generous SLAs without caveats (maintenance, force majeure) create heavy liabilities.
• Copy‑pasting US terms: mismatched law, unenforceable exclusions, and missing UK consumer or data provisions.
• Ignoring open‑source: failing to comply with attribution or copyleft obligations can force unwanted code disclosure.
• Unclear IP in custom work: if you don’t clarify ownership, you risk accidentally giving away your core IP – use an explicit IP Assignment or licence for bespoke deliverables.
• No path to true‑up: without audit/measurement rights, you can’t monetise growth or police over‑use.

Do I Need Any Other Documents Besides The Licence?

Usually, yes. Your licensing framework works best alongside a small set of supporting clauses and documents:

• Order Form or Proposal: commercial details, term, pricing, modules and usage metrics.
• Implementation SOW: timeline, deliverables, acceptance testing and change control for setup work.
• Software Development Agreement: for custom builds, integrations or new modules.
• Data Processing Agreement: mandatory when you process personal data on a customer’s behalf.
• Privacy Policy: transparency as a controller for your own users/admins.
• Acceptable Use Policy: clear behaviour rules for your platform (can sit inside your Terms of Use).
• Brand/IP docs: trade mark protection for your name and logo, and clear licensing of marks if partners will use them.

Having the right pieces in place speeds up procurement reviews and reduces back‑and‑forth with larger customers.

Key Takeaways

• In the UK, a software licence is the permission that lets customers use your software without transferring ownership – get the grant and scope crystal clear.
• Pick a licence model that fits your delivery and pricing (perpetual, subscription/SaaS, enterprise/site, OEM, EULA) and link usage metrics to value.
• Cover the essentials: licence scope, IP ownership, fees, support/updates, data protection, warranties, liability caps, audits, and termination.
• If you process personal data, pair your licence with a compliant Data Processing Agreement and publish a clear Privacy Policy.
• Track and comply with open‑source and third‑party licence obligations to avoid accidental code disclosure or breach.
• Separate implementation/custom builds into a Software Development Agreement and keep IP ownership explicit (use an IP Assignment where needed).
• Don’t rely on generic templates – a tailored Software Licence Agreement or SaaS Terms will protect your revenue and reduce disputes.

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