Rules and ethics
Part of Landing page software rules and ethics: a UK review guide
Six things to read in a landing page software contract before signing
Review landing page software contracts across parties, service scope, charges, acceptance, IP, data, security, change, liability and a tested exit.
Landing page software commercial contracts should describe the service actually bought and how the customer can leave it. A product name or checkout receipt is not a complete contract record.
Method: Contract areas were included where an official source supports the underlying buyer control and omission could block service, data or asset recovery.
Research date: 6 September 2026.
Scope: Purchases by organisations operating in England, with consumer-only rules labelled and UK data requirements kept separate.
Inclusions: Parties, service and edition, charges, acceptance, IP, data, security, support, change, liability, termination and exit.
Exclusions: Supplier rankings, model terms, prices, tax advice, negotiated outcomes and enforceability opinions.
Ranking: Non-ranked. The entries are concurrent review areas.
Conflicts: No supplier funded this article and no contract was tested or recommended.
This is general information. Named UK commercial, data-protection, security, IP, finance and tax reviewers must assess the proposed agreement and facts.
What to take away
- A product name or checkout receipt is not a complete contract record.
- Tie the order to an exact edition, domain, user unit, territory and permitted use.
- Map data purposes before assigning controller or processor labels.
- Read liability, termination, export and continuity terms together.
- Approval should stop if required assets or personal data cannot be recovered.
1. Legal party, service and edition
Record the supplier and customer legal names, registration details where relevant, ordering entity, incorporated terms and precedence. The Companies House service can provide filed company information, but the register does not prove product ownership, authority to contract or service quality. Tie the order to an exact edition, domain, user or workspace unit, territory and permitted use.
2. Price, VAT, currency, unit and term
Write the quoted currency, VAT status, billing unit, quantity, period, minimum term, usage cap, renewal and increase mechanism. Do not fill gaps with a typical price. For consumer invitations to purchase, the CMA's price-transparency guidance, updated 7 January 2026, addresses mandatory charges and total-price presentation. Its consumer scope should not be presented as a universal business-contract rule.
3. Service, acceptance, support and change
Describe page publishing, hosting, forms, integrations, support and any excluded work. Define objective acceptance evidence and the response when it fails. Version service levels, maintenance, deprecation and unilateral-change terms. GOV.UK guidance on fair contracts for customers concerns consumer terms; it is a useful warning against hidden or one-sided wording, not an enforceability opinion for a business agreement.
4. IP and permitted asset use
Allocate ownership and licences for templates, copy, code, fonts, images, domains and generated output. State territory, term, sublicensing, editing and post-termination use. The Intellectual Property Office explains that a copyright licence is a contractual agreement setting what a user can do with a work. Counsel must test the actual chain of rights.
5. Data roles, security and incidents
Map purposes before assigning controller or processor labels, as the ICO says Article 28 requires a binding arrangement when a controller uses a processor; its contracts guidance is marked under DUAA review.
Cover instructions, sub-processors, transfers, assistance, audit. Handle return and deletion. NCSC SaaS security guidance shows customer configuration responsibility, so specify incident notice and recovery evidence rather than a general security label.
6. Liability, termination, export and continuity
Read exclusions, caps, indemnities, suspension, termination events and governing law together. List every asset and dataset to export, its format, timing, cost, deletion evidence and restore test. Preserve a manual publishing or lead-capture fallback. Approval should stop if a required domain, page asset, suppression record or personal-data export cannot be recovered on terms the named decision owner accepts.
Before you act
- Record supplier and customer legal names and registration details.
- Write the quoted currency, VAT status, billing unit and minimum term.
- Define objective acceptance evidence and the response when it fails.
- Allocate ownership and licences for templates, copy, code and images.
- List every asset and dataset to export, with format and timing.
- Preserve a manual publishing or lead-capture fallback.
Common questions
What should a landing page software contract describe?
It should describe the service actually bought and how the customer can leave it. A product name or checkout receipt is not a complete contract record. The article covers parties, service and edition, charges, acceptance, IP, data, security, support, change, liability, termination and exit.
Does the Companies House register prove product ownership or service quality?
No. The register can provide filed company information, but it does not prove product ownership, authority to contract or service quality. The article says to record legal names, registration details where relevant, ordering entity, incorporated terms and precedence, then tie the order to an exact edition, domain, user or workspace unit, territory and permitted use.
What should be specified for incident notice and recovery?
Specify incident notice and recovery evidence rather than accepting a general security label. Cover instructions, sub-processors, transfers, assistance, audit, return and deletion. The ICO says Article 28 requires a binding arrangement when a controller uses a processor, and its contracts guidance is marked under DUAA review.
