Software Licence Agreement: What To Include In The UK

If you build, sell, distribute or use software in your business, a clear Software Licence Agreement is one of the most important contracts you’ll put in place.

It sets the ground rules for how your software can be used, protects your intellectual property, limits your risk and helps you stay compliant with UK law.

In this guide, we’ll break down what a software licensing agreement is, when you need one, the essential clauses to include, the UK laws you’ll need to think about, and practical tips for negotiating terms with confidence.

What Is A Software Licence Agreement?

A Software Licence Agreement is a contract that governs how a customer or end user can use your software. It grants permission to use the software (a licence) while making clear that you keep ownership of the underlying intellectual property.

In practice, the agreement sets out the scope of the licence (who can use the software, for what purpose, in which territory, and for how long), pricing and payment terms, restrictions, support and maintenance, data and privacy commitments, security expectations, liability caps, and termination rights.

For many small businesses, this document appears as an End User Licence Agreement (EULA) for on-premises installs, or as part of your cloud or subscription product as SaaS Terms if you deliver software via the web.

The key idea is simple: a licence allows customers to use your software under controlled conditions, while ensuring your IP stays yours and the commercial risk is managed.

When Your Business Needs A Software Licensing Agreement

If you’re distributing software you’ve built (or software you’ve acquired the rights to), you need a Software Licence Agreement before your first user signs up. Don’t wait until launch day – being protected from day one is essential.

Scenarios where you’ll typically need a licensing agreement include:

• Selling downloadable or installed software (perpetual or term-based licences).
• Offering cloud software as a service (subscription-based access under SaaS Terms).
• Bundling your software for resale or distribution via partners (often with a Software Reseller Agreement).
• Licensing application programming interfaces (APIs) or software development kits (SDKs) to third parties.
• Delivering custom-built software to a client where you retain IP and grant them a use licence, often alongside a Software Development Agreement.

If you’re on the other side – buying software for your business – you should still care about the terms. They control your usage rights, your ability to scale seats, compliance responsibilities, refund rights for faulty digital content, and more. If the vendor’s terms are too one-sided, negotiate before you commit.

Essential Clauses To Include In Your Software Licensing Agreement

While every business is different, strong licensing terms usually cover the areas below. Avoid generic templates – your agreement should reflect your product, pricing model, customer profile, risk tolerance and regulatory environment. Getting a tailored Software Licence Agreement in place will save headaches later.

1) Licence Grant And Scope

• Type: perpetual, subscription/term, trial/demo, freemium, beta, evaluation.
• Permitted users: named users, concurrent users, affiliates, contractors, end customers (for resellers).
• Purpose: internal business use, development/test, not for production, non-commercial, or authorised commercial use.
• Territory: UK-only, EEA, worldwide.
• Transferability: assignable or non-transferable; sublicensing allowed or prohibited.

Be specific. Ambiguity around user numbers, affiliates or environments (production vs testing) is a common source of disputes.

2) Restrictions And Acceptable Use

Spell out what users must not do, for example:

• Reverse-engineer, decompile or attempt to access source code.
• Remove proprietary notices or circumvent licence controls.
• Use for unlawful, high-risk or prohibited activities.
• Benchmarking or disclosure of performance results without consent.
• Sharing logins or enabling unlicensed users to access the software.

For cloud products, pair this with an Acceptable Use Policy that can be updated as threats evolve.

3) Fees, Renewals And Price Changes

• Pricing model: seat-based, usage-based, tiered plans, or hybrid.
• Billing: when and how fees are charged, invoicing mechanics and late payment interest.
• Auto-renewal: renewal terms and notice periods. Make this clear to align with UK rules on fairness and transparency for automatic renewals.
• Price changes: how and when you can update fees (and how you’ll notify customers).

Clarity upfront reduces churn and complaints later. If you use automatic renewals, ensure your notifications and cancellation paths are fair and easy to use.

4) Delivery, Support And Service Levels

For installed software, explain delivery and any activation keys. For SaaS, outline uptime commitments, maintenance windows and incident response. Often, the detail sits in a separate Service Level Agreement that’s incorporated by reference.

• Support channels and hours (email, phone, chat).
• Response and resolution targets by severity level.
• Planned maintenance and scheduled downtime.
• Service credits and exclusions (e.g. outages caused by customer systems).

5) Data Protection And Security

If you process personal data for customers, your contract should reflect UK GDPR and the Data Protection Act 2018. Typically you’ll include or attach a Data Processing Agreement covering roles (controller/processor), processing details, security measures, subprocessor approvals, international transfers and audit rights.

Where you collect data directly from users, ensure your website and app display a compliant Privacy Policy and appropriate consent flows.

6) Intellectual Property Ownership

The agreement should clearly state that you retain all intellectual property rights in the software, except for any components specifically licensed from third parties. If you’re building custom features for a client but intend to reuse elements elsewhere, reserve your right to do so and grant the client a licence for those parts.

If your business buys or transfers IP during development, use an IP Assignment to ensure the rights land in the correct entity.

7) Open-Source Software (OSS) Notices

Most modern products incorporate some OSS. Include a schedule listing OSS components, licences and notices, and confirm you’ll comply with obligations (e.g. attribution) without inadvertently “copylefting” your proprietary code.

8) Warranties And Remedies

Provide limited warranties that the software will materially conform to documentation and be free of malicious code on delivery. Avoid blanket performance guarantees. Set out exclusive remedies like repair, replacement or re-performance within a reasonable time.

For B2C sales, remember the Consumer Rights Act 2015 has special rules for digital content (e.g. right to repair or price reduction). If you sell to both consumers and businesses, consider separate terms.

9) Liability Caps And Exclusions

Limit your total liability (for example, to 12 months’ fees) and exclude indirect losses such as lost profits, data loss or business interruption, subject to non-excludable liabilities under UK law (e.g. death or personal injury caused by negligence, or fraud). For more on getting this right, see how to structure a fair Limitation of Liability clause.

10) Term, Termination And Suspension

• Initial term and renewals; convenience termination rights if any.
• Termination for breach (with cure periods), insolvency or legal compliance reasons.
• Suspension for non-payment or security risks.
• Exit assistance, data export and secure deletion.

Make sure customers understand how they can retrieve their data at the end of the relationship, and how long you’ll hold backups before deletion.

11) Audits, Compliance And Reporting

If your pricing is seat- or usage-based, an audit clause helps you verify compliance. Build in reasonable notice, frequency and confidentiality controls. Consider privacy implications if you review user data – audits should focus on licence compliance metrics, not sensitive content.

12) Dispute Resolution And Governing Law

State English law as governing law and specify the courts of England and Wales (or arbitration, if preferred). For enterprise deals, you might include a good-faith escalation and mediation step before litigation.

13) Commercial Attachments

To keep your master licence readable, place technical and commercial specifics in schedules you can update from time to time, such as: pricing, service levels, support plans, security measures and OSS notices.

UK Laws That Apply To Software Licensing

Several UK laws and regulations shape how you draft and enforce a Software Licence Agreement. Here are the big ones to keep in mind:

Copyright, Designs and Patents Act 1988

Software is protected as a literary work under UK copyright law. You own the code you create unless the rights are assigned elsewhere (for example, to a client under contract or to your company by your employees). Your licence agreement relies on these rights to control copying, modification and distribution.

Consumer Rights Act 2015

If you sell to consumers, digital content must be of satisfactory quality, fit for purpose and as described. Consumers have statutory remedies for faulty digital content (repair, replacement or price reduction), and terms must be fair and transparent. Consider separate B2C terms and ensure your refund and support practices reflect these rights.

UK GDPR And Data Protection Act 2018

If your software processes personal data, you must comply with UK GDPR, including lawful basis, transparency, data minimisation, appropriate security and international transfer rules. Your contracts should include a proper Data Processing Agreement and align with your public-facing Privacy Policy.

Computer Misuse And Security Laws

Ensure your terms prohibit misuse and clearly set expectations around security responsibilities. If you provide admin tools or remote access for support, include controls, consents and audit trails to manage risk.

Competition And Fair Trading

Avoid unduly restrictive practices or unfair contract terms. If you use auto-renewals or price changes, present them clearly and offer simple cancellation paths. Marketing claims should be accurate and supported.

Export Controls And Sanctions

Some encryption or security products can raise export control considerations. If you sell internationally, consider compliance and include sanctions compliance clauses where relevant.

Practical Negotiation Tips And Common Pitfalls

Even if you’re a small business, you’ll often negotiate with larger customers or partners. Here’s how to protect your position without scaring off the deal.

Decide Your Non-Negotiables

Before sharing terms, be clear on your red lines: IP ownership, core usage restrictions, your liability cap structure, and security commitments you can genuinely stand behind. It’s much easier to negotiate when you know your bottom line.

Align Price And Risk

If a customer pushes for broader rights (e.g. enterprise-wide use or sublicensing) or higher liability caps, adjust pricing to reflect the extra risk and support burden. Conversely, scope-limited licences can be priced more accessibly for early-stage customers.

Separate Legal And Commercial Schedules

Keep your master legal terms stable and put pricing, usage metrics and service levels in schedules. This makes future upsells, renewals and plan adjustments smoother and keeps your agreement readable. Externalising service commitments into a dedicated Service Level Agreement is a tried-and-true approach.

Be Careful With “Unlimited” Or “Perpetual” Language

Words like “unlimited” or “perpetual” can create expectations that are hard to support. If you offer generous usage, define practical caps or fair-use triggers. If you do sell perpetual licences, pair them with separately chargeable support and maintenance so you’re not on the hook indefinitely.

Plan For Exit From Day One

Customers will ask what happens if things end. Put clear data export formats, timeframes and deletion promises in your terms, and specify any reasonable transition assistance. This reduces friction at renewal and builds trust.

Lock In The Upstream IP

If contractors or employees contribute to the codebase, ensure you own the IP. Use robust employment and contractor terms and, where needed, an IP Assignment or a tailored Software Development Agreement so the rights land in your business, not with a freelancer.

Don’t Forget The Basics

It’s easy to focus on security and SLAs and forget the fundamentals like definitions, order of precedence (master vs schedules), notices, force majeure and change control. Consistent definitions prevent many disputes.

Use The Right Document For Your Model

If you deliver cloud software, you’ll want subscription-focused SaaS Terms rather than a traditional installable EULA. If you licence content, images or training materials alongside your code, fold in a simple Copyright Licence to cover those assets too.

Get The Liability Balance Right

Overly aggressive caps or exclusions might put off enterprise buyers; over-generous liabilities can be risky for you. It’s a balancing act. A well-drafted Limitation of Liability calibrated to your price point and risk profile is key.

Document Hygiene And Version Control

Keep a clean, dated version of your terms and change logs. If you sell online, ensure customers actively accept the latest terms (for example, via a checkbox at sign-up) and that you retain acceptance records.

Related Documents That Often Sit Alongside Your Licence

• Software Licence Agreement (core legal terms for installed or on-prem software).
• SaaS Terms (for cloud/subscription products).
• Service Level Agreement (uptime, support, service credits).
• Data Processing Agreement (UK GDPR compliance between controller/processor).
• Privacy Policy (transparency for users and site/app visitors).
• Software Development Agreement (for build projects and IP ownership).

It can feel like a lot, but the right stack of documents makes sales smoother, reduces negotiation time and keeps you compliant as you grow.

Key Takeaways

• A Software Licence Agreement lets customers use your software while you retain IP ownership and control how it’s used.
• Set clear scope and guardrails: who can use the software, for what purpose, in which territory, and with what restrictions.
• Cover the essentials: fees and renewals, delivery, support and SLAs, data protection (with a Data Processing Agreement), IP ownership, warranties, and sensible liability caps.
• Align your document to your model: use subscription-focused SaaS Terms for cloud products and a tailored Software Licence Agreement for installed software.
• UK law matters: think about the Consumer Rights Act 2015 for digital content, UK GDPR for personal data, and copyright law for IP control.
• Negotiate with confidence by deciding your red lines, matching price to risk and planning for exit (data export and deletion) from day one.
• Avoid DIY templates – professionally drafted terms that fit your product and risk profile will reduce disputes and speed up sales.

If you’d like help drafting or reviewing a Software Licence Agreement or SaaS Terms tailored to your business, you can reach us on 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.