Alex is Sprintlaw’s co-founder and principal lawyer. Alex previously worked at a top-tier firm as a lawyer specialising in technology and media contracts, and founded a digital agency which he sold in 2015.
Contents
If you’re running a small business in the UK, you’ll deal with software every day - from your CRM and accounting tools to any apps or platforms you sell to customers.
Getting the “right to use” software isn’t as simple as paying a fee. You need a proper software licence that sets out what you can do, what you can’t, and how your business is protected.
Whether you’re buying licences from a vendor or granting licences for your own software, the legal groundwork matters. In this guide, we’ll walk through how to get a software licence, what to look for in the terms, and how UK law applies so you’re protected from day one.
What Is A Software Licence (And Why Does It Matter)?
A software licence is the legal permission to use software under certain conditions. You don’t “own” the code - the copyright owner retains intellectual property rights. Instead, the licence gives you a limited right to use the software in specific ways (for example, one user vs unlimited users, internal business use only, or redistribution rights).
From a business perspective, the licence is your rulebook. It governs:
- How many users or devices can access the software
- Where it can be used (territory) and for how long (term)
- What’s prohibited (reverse engineering, resale, competing products)
- Fees, renewals, and price increases
- Support, updates, and uptime (particularly for cloud/SaaS)
- Data protection and security responsibilities
- Liability caps, warranties, and indemnities if something goes wrong
Without a clear licence, you can easily overstep the permitted use, lose access unexpectedly, or find yourself exposed to claims and costs you didn’t plan for.
How To Get A Software Licence For Your Business (Buying Or Negotiating)
If you’re acquiring licences from a vendor, take it step by step. Don’t just click “I agree” - make sure the terms actually work for your use case and risk profile.
1) Map Your Needs And Users
Start with a quick checklist:
- Number of users/seats now and for the next 12–24 months
- Internal-only use vs any customer-facing use
- Must-have features and integrations
- Data types processed (especially any personal data)
- Security or compliance standards you must meet (for example, ISO27001, UK GDPR)
This gives you the baseline to judge whether the vendor’s package and licence model (per-seat, per-site, enterprise) is suitable.
2) Choose The Right Licence Model
Common models include:
- Per-User/Seat: Priced by named users or concurrent users
- Per-Device: Licensed for installation on specific machines
- Enterprise: Organisation-wide usage under negotiated metrics
- Subscription/SaaS: Access to a hosted service under recurring terms
For cloud products, you’ll usually be signing up to platform terms (often called “SaaS Terms”). If you’re buying on-premises software, you’ll want a clear Software Licence Agreement that covers installation, updates and restrictions.
3) Review Key Clauses (Don’t Skip This)
At a minimum, check:
- Scope Of Licence: Users, territory, field of use, and restrictions
- Fees And Renewals: How pricing changes; auto-renewal, cancellation windows
- Service Levels: Uptime, support response, maintenance windows (for SaaS)
- Data Protection: Roles and responsibilities under UK GDPR; whether a Data Processing Agreement is included
- Security: Minimum safeguards, breach notification, audit rights
- IP And Warranties: What’s warranted, what’s disclaimed, who owns custom work
- Liability: Caps, exclusions, and carve-outs - align with your risk appetite
- Termination And Exit: Your rights to terminate and retrieve/export your data
If the product is a hosted solution, ask for the vendor’s SaaS Terms and ensure they align with the above.
4) Put Privacy And Security Front And Centre
If the software will process personal data, you must comply with the UK GDPR and the Data Protection Act 2018. Typically, the vendor acts as a processor and you (the customer) are the controller - so you’ll need a compliant Data Processing Agreement. You should also maintain a clear, accurate Privacy Policy that tells customers how their data is handled.
Where data is hosted outside the UK, ensure appropriate transfer safeguards are in place. Confirm how your data can be exported back to you on exit, in a usable format.
5) Negotiate The Risks That Matter
Vendors may resist edits, but it’s reasonable to negotiate where risk sits - for example, stronger warranties for IP infringement, a fairer liability cap, or tighter service levels for critical tools. If you’re unsure where to push, read up on limitation of liability clauses and speak to a lawyer about what’s market-standard for your sector and deal size.
6) Keep A Paper Trail
Record which version of the licence you agreed to and any order forms or statements of work. For bespoke configurations or integrations, consider a short Master Services Agreement or SOW to capture deliverables, acceptance testing, and milestones.
How To License Your Own Software To Customers
If you’ve built software (whether downloadable or cloud-based), you’ll need to grant customers a licence to use it. This is where your own terms do the heavy lifting to protect your IP and set sustainable commercial boundaries.
1) Decide Your Commercial Model
Pick a model that fits your product and customers:
- Per-Seat Or Tiered Subscription for SMEs
- Enterprise Licensing based on usage, revenue, or locations
- Freemium with paid add-ons
- Perpetual Licence + Maintenance (less common for new products)
For installed products, you’ll use a Software Licence Agreement. For hosted products, your terms will usually be SaaS Terms presented at sign-up or in an order form.
2) Protect Your IP From Day One
Make it crystal clear that you retain ownership of the software and any improvements. Restrict reverse engineering and unauthorised copying. Where brand is a key asset, consider filing to register a trade mark for your product name and logo.
When collaborating with contractors or early partners, use a Non-Disclosure Agreement before sharing code or roadmaps. If a third party is helping build your product, lock in IP ownership via a Software Development Agreement.
3) Build Terms That Support Scale
Think beyond your first 10 customers. Your licence should cover:
- Scope And Use: Who can use it, where, and for what purposes
- Pricing And Invoicing: Clear renewal mechanics and price increase rights
- Service Levels: Availability targets, maintenance windows, support response
- Security And Compliance: Your measures; the customer’s responsibilities
- Data: Who owns what, data access, export tools on termination
- IP And Infringement: Ownership, warranties, indemnities
- Liability: Caps that are commercially sensible and insurable
- Termination: Suspension for non-payment, material breach, insolvency
Avoid relying on generic templates - your licence is core infrastructure. Properly drafted terms reduce disputes and make enterprise sales faster because procurement teams find what they expect.
4) Bake In Privacy By Design
Explain how you handle personal data in your customer contracts, and keep your website’s Privacy Policy aligned. If you process data for customers, provide a compliant Data Processing Agreement and ensure your sub-processor list and security standards are transparent.
What UK Laws Apply To Software Licensing?
Several UK laws underpin software licensing and how you use or supply software. The key ones to be aware of are:
Copyright And IP Law
Under the Copyright, Designs and Patents Act 1988, software is protected as a literary work. Unless ownership is expressly assigned, the creator retains copyright. This is why licences exist - to permit use without transferring ownership. If you’re commissioning development work, your contract must expressly transfer IP to your business.
Contract Law And Fairness
Licences are contracts, so standard UK contract principles apply (offer, acceptance, consideration, intention). For business-to-consumer (B2C) software, the Consumer Rights Act 2015 imposes additional obligations - for example, digital content must be of satisfactory quality and as described, with specific remedies if it isn’t. Make sure any disclaimers and exclusions are fair and enforceable.
Data Protection And Privacy
If personal data is processed, the UK GDPR and Data Protection Act 2018 apply. You must have a lawful basis for processing, provide clear privacy information, and put appropriate technical and organisational measures in place. Controller–processor relationships should be documented in a Data Processing Agreement.
Consumer And Marketing Rules
If you sell to consumers, be careful with auto-renewals, cancellation rights and pricing transparency. Consumer protection law also affects your refund policy and advertising claims. Your website should carry accurate Website Terms and Conditions alongside your privacy notices.
Open Source Licences
If your product includes open-source components, comply with the specific licence conditions (for example, attribution or copyleft obligations). Keep a bill of materials and ensure you can continue to comply as you scale - investors and enterprise customers often ask for this detail.
What Should A Software Licence Agreement Include?
Every business and product is different, but strong licences tend to cover the following areas clearly and in plain English.
Scope And Permissions
- Type of licence (for example, non-exclusive, non-transferable)
- Permitted users and usage caps; restrictions on competing uses
- Territory and term (including renewal mechanics)
Fees, Billing And Changes
- Fee structure, billing frequency, late payment rights
- Indexation and process for price changes
- Discounts, trials, and promotional terms
Delivery, Support And SLAs
- Implementation timelines and acceptance criteria (if relevant)
- Service levels, maintenance windows, and support response times
- Change management and deprecation policies
Data, Security And Compliance
- Data ownership, access, and retention/deletion schedules
- Security standards, audits, and breach notification
- Controller–processor roles and a compliant DPA
IP, Warranties And Indemnities
- Who owns core IP and any customisations
- Warranties (for example, no known infringement; malware-free)
- Indemnities for IP claims, and your customer’s indemnity for misuse
Liability, Termination And Exit
- Reasonable liability caps with carve-outs where required by law
- Termination for breach, convenience (if agreed), or insolvency
- Orderly wind-down, data export and deletion at the end of the term
If you’re supplying downloadable software, your terms can be packaged as an EULA, but the core legal protections are the same. For cloud products, keep the operational detail in your SaaS Terms and attach a service description or SLA as a schedule.
Common Pitfalls (And How To Avoid Them)
Licensing is one of those areas where small oversights can cause big headaches. Here are frequent issues we see - and how to stay clear of them.
Unclear Ownership In Development Projects
If a contractor helps build your product, don’t assume you own the code. Use a tailored Software Development Agreement to assign IP to your business and define deliverables and acceptance testing.
Weak Or Missing Privacy Documentation
Collecting user data without a transparent Privacy Policy and robust DPA can put you in breach of UK GDPR. Map data flows early, minimise personal data where possible, and make sure your vendor and sub-processor terms line up.
Overly Broad Or Toothless Liability Clauses
Licence terms with unlimited liability or vague exclusions can sink a deal or expose you to disproportionate risk. Set clear, reasonable caps and carve-outs that reflect the deal size and insurance - and make sure your sales team understands why these positions matter.
Auto-Renewal Surprises
Auto-renewals with short cancellation windows catch many businesses off guard. Track renewal dates, diarise notice periods, and negotiate fair exit terms when you first sign. For consumer-facing offers, ensure your renewal notices and cancellation routes are transparent.
Open Source Compliance Gaps
Not documenting open-source use can delay funding or procurement. Keep a current inventory with licence types and attribution requirements, and build a lightweight process for updates.
Click-Wrap Without Proof
If your customers accept terms online, make sure you have a clean “click-wrap” flow and a record of acceptance. This becomes crucial if there’s a dispute about what terms apply. Your website should also carry clear Website Terms and Conditions alongside your product-specific licence.
Key Takeaways
- A software licence is the legal permission to use software under set conditions - getting this right protects your business operationally and legally.
- When buying licences, map your needs, review scope, data and security terms, and negotiate the risk points that matter, including service levels and liability.
- If you’re licensing your own software, lock in your IP ownership, choose a commercial model that scales, and put robust Software Licence Agreement or SaaS Terms in place.
- UK GDPR, the Data Protection Act 2018 and the Consumer Rights Act 2015 all impact how you structure, sell, and deliver software - align your contracts and processes accordingly.
- Document privacy properly with a Privacy Policy and a Data Processing Agreement where you process personal data.
- Avoid common pitfalls like unclear IP ownership, weak limitation of liability, and auto-renewal traps - strong, tailored contracts are your best protection.
If you’d like help drafting or negotiating your software licence, or you’re unsure which terms you need, our team can help. You can reach us at 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.
