Terms

Terms & conditions.

The terms on which we provide our websites, hosting, domains and email, SEO, digital marketing, social media, apps, hubs and portals, and the support that goes with them.

Download these Terms as a PDF

Contents

Key terms at a glance

A plain summary to help you find your way. It is not part of the Agreement: the numbered clauses, the Schedules and your Proposal are what count.

  • Your Proposal comes first. It sets your specifics: prices, term, hosting, Users, hours, service levels, ownership and any liability figures. Where it says nothing, these Terms give the default. (clause 4)
  • Prices. As in your Proposal, plus VAT. Extra work is £75 + VAT an hour unless your Proposal says otherwise, and is always agreed with you first. A setup fee is a fixed price, with setup hours as the expected total time, including your requests, revisions, meetings and data; extra time is agreed with you first. (clauses 7 and 10)
  • Paying. Plan fees by Direct Debit (GoCardless), monthly in advance; setup fees invoiced on signing; Website Fees in the stages your Proposal sets. A missing purchase order never delays payment, and you may not deduct anything except a disputed part of an invoice. (clauses 3.3 and 10)
  • Hours. Unused setup hours end when setup ends. Time Bundles must be used within 6 months of purchase unless your Proposal or our Rate Card says otherwise. Hours have no cash value, and setup fees and Time Bundles are refunded only as clause 7.6 says. (clause 7)
  • How long. Every Plan has a minimum term of 12 months from the Start Date unless your Proposal says otherwise. After that, or where your Proposal makes a Plan rolling, it can be ended on 30 days’ notice (at least 90 days from us for a System). At least 2 months before a Fixed Term ends, we send a renewal offer: you can end the Agreement when the term ends, or do nothing and continue monthly at the new price (within the clause 11.2 limit unless you accept more in writing). Automatic renewal applies only if your Proposal says so, and you can opt out up to 30 days before the term ends. (clause 12)
  • Leaving early. You can end a minimum term or Fixed Term early. If you do, or we end the Agreement for your breach, you pay the monthly fees up to the next Review Point (or the end of the term), less third-party costs we no longer pay, plus VAT, unless your Proposal says otherwise. There is no charge at a Review Point, for our material breach, or for the other reasons clause 12.7 lists. (clause 12.7)
  • Price review. Fees are fixed for any Fixed Term unless your Proposal says otherwise. On rolling Plans we may review them once a year, by no more than the higher of CPI or 3%, and never more than 5%, with 30 days’ notice. (clause 11)
  • Faults are free, Changes use hours. We fix Faults in our work free while a Plan with hosting, care or support runs, or for 90 days after Acceptance for one-off work. Anything new or different is a Change, quoted or taken from your hours first. (clauses 7 and 8)
  • Approvals. Nothing is published, and no website goes live on your domain, without your go-ahead. A website proof not answered within 10 Working Days, and 5 more after our reminder, may be treated as approved. (clauses B1.4 and B4.10)
  • Late payment. If an undisputed bill is 14 days overdue we may pause new work. We suspend a Service only if it is still unpaid 14 days after a written notice sent once it is 14 days overdue (30 days for Systems with a Security Pack or a Fixed Term of 12 months or more). Suspension never deletes your data or blocks your export. Restoring a suspended website, hosting or social scheduling may cost £100 + VAT, but not for Systems. Statutory interest and recovery costs apply. (clause 10)
  • What you own. Websites: what we made just for you is yours once the Website Fee is paid (a website on a System passes with the System; a free one with another Plan, once that Plan has been paid for 12 months). Apps and software: where your Proposal sets an Ownership Date, the work made for you, its code and a permanent licence to the shared Think Mad parts it uses are yours from that date (or earlier, as clause B5.13(f) says). Until then, and where no Ownership Date is set (as with our Team App range), you use the System under licence. Your data is always yours to take. (clauses 14, B1.8 and B5.13)
  • Your data and accounts. Always yours. Domains, Google Business Profiles, and ad, social and app store accounts are in your name wherever possible, and never held back for payment. (clause 15)
  • Hosting. Most websites use Shared Hosting with GURU Cloud; hubs and Team App Plans use Platform Hosting, which we arrange and look after, separate from our main website server; larger projects can have Dedicated Hosting in a UK data centre, or Client Hosting on your own cloud account (such as AWS) or servers. We are happy to host wherever suits you, and agree the provider and location with you; the data your website or System holds stays in the UK unless we both agree otherwise. Your Proposal says which, and your Proposal or Security Pack names the provider. We never promise uninterrupted service. (module B2)
  • Support. 9:00 to 17:30 on Working Days. Where your Proposal includes weekend critical cover, we are also available from 8:00 to 20:00 on Saturdays, Sundays and bank holidays for Critical issues such as a website or System being down; we respond as quickly as we can, without a committed response time. No 24/7 support unless your Proposal says so. We still tell you about security incidents within the times in Schedule 3, including at weekends. (Schedule 1)
  • No guarantees of results. We promise the work, not rankings, traffic, leads, sales or revenue. (clause 5)
  • AI and contractors. We use AI tools, such as Claude, with our people steering and checking the work. Your personal data only goes into AI tools listed as Sub-processors, and other confidential data only into AI tools named in your Security Pack or Sub-processor list, on business terms that stop the provider training on it. We tell you before any contractor starts on your project. (clauses 19 and 20)
  • Data protection. Schedule 3 is our data processing agreement. (clause 16)
  • Liability. For all claims in each Contract Year, each of us is limited to the greater of that year’s fees or £5,000, with a separate higher limit for security incidents, data breaches, confidentiality and our IP indemnity (by default the greater of twice that year’s fees or £25,000), unless your Proposal sets other figures. Lost profits are excluded except as clause 21.3 says, and claims must be brought within 2 years. (clause 21)
  • Hiring each other’s people. A fee of 20% of the first year’s pay or fees agreed for the new role applies if either of us hires someone from the other’s team who worked on your Services, during the Agreement or for 12 months after. (clause 26.3)
  • Problems. Talk to your usual contact or Luke Hilditch first: luke@thinkmad.co.uk, 0151 316 0110. (clause 25)

Which parts apply to you

If you buy The parts that apply
A website build Part A, B1, B3 (if we register your domain), B6, Schedule 1 (targets in paragraph 4), Schedule 2, Section A, Schedules 3 and 4
Hosting or website care Part A, B2, B3 (for domains, email and SSL), B6, Schedule 1 (targets in paragraph 4), Schedule 2, Section A (and Section B for Dedicated or Client Hosting), Schedules 3 and 4
SEO, marketing, ads or social media Part A, B4, B6, Schedule 1 (targets in paragraph 4), Schedule 2, Section A, Schedules 3 and 4
An app, hub, portal or Team App Plan Part A, B2, B5, B6 and Schedules 1 to 5
You are a consumer, not a business Also Schedule 6

If you buy more than one Service, every matching row applies.

Part A: General terms

1. About these Terms

1.1 These Terms and Conditions (the “Terms”) set out how Think Mad Ltd (“Think Mad”, “we”, “us”, “our”) provides its Services to the business named in your Proposal (“you”, “your”).

1.2 Part A applies to every Service. Each Part B module applies where your Proposal includes that Service. Schedules 1 to 5 apply to the Services each paragraph names, and Schedule 6 applies to consumers.

1.3 We work with businesses, and you confirm you are contracting for your business. If you are in fact a consumer, Schedule 6 applies and your statutory rights take priority.

1.4 Headings, the “Key terms at a glance” summary and the “Which parts apply to you” table do not affect meaning. “Including” means including without limitation. “In writing” includes email, unless a clause requires a signature. Where a clause speaks of both of us together (such as “we both”, “we agree” or “we choose together”), it means you and Think Mad; otherwise “we” means Think Mad.

2. Words with special meanings

2.1 In these Terms:

  • “Acceptance” has the meaning in clause 9.3.
  • “Agreement” means your Proposal, these Terms (including the Schedules) and any Security Pack your Proposal names.
  • “Blocking Fault” means a Fault that stops a Deliverable working as your Proposal or an agreed written specification describes, or that puts Client Data at risk.
  • “Care Plan” means a Plan under which we look after a website, as described in clause B6.3.
  • “Change” means anything new or different from what the Proposal or an agreed specification describes, including changes to something you have already approved.
  • “Client Data” means all data that you, your Users or your Client Group give us, or that the Services create or store for you, including personal data, price lists and pricing data, customer lists, quotes and content you supply or your Users enter, but not our own business records about you, and not the code, designs or other Deliverables we create, which clause 14 deals with.
  • “Client Group” means you and your subsidiaries and holding companies, and their other subsidiaries, as defined in section 1159 of the Companies Act 2006.
  • “Client Materials” means content, images, logos, fonts, data, brand assets and other materials supplied to us by you or on your behalf.
  • “Client-Specific Work” means the code, designs, content, configuration and other work we create only for you, but not Platform Components or Third-Party Components.
  • “Confidential Information” means information about the business, customers, suppliers, systems or affairs of one of us (or, for you, your Client Group) that the other receives or sees in connection with the Agreement and that is marked confidential or that a reasonable person would see as confidential, including Client Data, price lists and pricing data, the Source Code of Platform Components, methods and security information.
  • “Contract Year” means each 12-month period starting on the Start Date or an anniversary of it.
  • “Data Protection Law” means the UK GDPR, the Data Protection Act 2018 and the Privacy and Electronic Communications (EC Directive) Regulations 2003 (“PECR”), as amended (including by the Data (Use and Access) Act 2025), any regulations made under them, and any other law on personal data that applies to the Services.
  • “Deliverable” means anything we deliver under the Agreement, such as a website, System, design, content or report.
  • “Fault” means a reproducible error in work we created that stops it working as your Proposal or an agreed written specification describes (after Acceptance, as accepted under clause 9). These are not Faults, and work on them is a Change: (a) something that works as described but not as you now want, including its design, wording, layout, speed or ease of use; (b) anything your Proposal or specification does not describe; (c) a problem caused by a change made by you, your Users or another supplier (other than our contractors), by Client Data or Client Materials that do not follow the format your Proposal or an agreed specification describes, or by use not allowed by the Agreement or Schedule 5; (d) a defect in a Third-Party Component itself, although we apply any fix its supplier releases where your Plan includes updates; (e) a change after Acceptance in a law, standard, model form, third-party platform you use (such as Google, Meta, Microsoft, Apple or a payment provider you chose), browser, device or operating system; and (f) websites, code or systems we did not create, unless your Proposal says we take responsibility for them. A problem caused by an update we apply, or by our own hosting and service suppliers, is treated as a Fault, which we fix or work around as far as we can.
  • “Fixed Term” means the term of set length for a Plan: 12 months from the Start Date unless your Proposal states another period or says the Plan is rolling, including any renewal term.
  • “Hosting Tier” means Shared Hosting, Platform Hosting, Dedicated Hosting or Client Hosting, as described in clause B2.2.
  • “Hourly Rate” means £75 + VAT an hour, or the rate in your Proposal. It changes only under clause 11.
  • “Information Commission” means the UK data protection regulator, which took over from the Information Commissioner on 30 September 2026 and is still known as the ICO, and any successor.
  • “Named contact”, “decision-maker” and any group, legal or finance contact mean the people your Proposal names for those roles, or replacements either of us gives in writing. If your Proposal names no decision-maker, your named contact is also your decision-maker.
  • “Ownership Date” has the meaning in clause B5.13.
  • “Plan” means any Service paid monthly or at another regular interval.
  • “Platform Components” means code, modules, libraries, templates, designs, tools, methods and know-how that we owned or developed before or apart from your project, and general improvements to them made during your project that contain nothing specific to you, your Client Data or your Confidential Information. Work is not a Platform Component just because we later use something similar for another client.
  • “Proposal” means the proposal, quote or order form you accept under clause 3, as varied under clause 4.9.
  • “Rate Card” means our price list published at thinkmad.co.uk or sent to you, as it stands when you agree to buy.
  • “Review Point” means a point in a Fixed Term at which your Proposal lets either of us end the Agreement (for example a review at month 6).
  • “Security Incident” means any actual or reasonably suspected unauthorised access to, or loss, alteration, disclosure or destruction of, Client Data or a System we manage, including malware, a compromised administrator account or exposure of price lists. Unsuccessful attempts that compromise nothing, such as blocked scans or failed sign-ins, are not Security Incidents.
  • “Security Pack” means our security and data pack describing how we protect a System and Client Data, identified by version and date.
  • “Services” means the services described in your Proposal.
  • “Source Code” means complete, buildable source code, with the database structure, build and deployment scripts and instructions good enough for a competent developer to build, deploy and run the software without our help, but not passwords or other secrets.
  • “Start Date” means the date you sign or accept your Proposal, unless it states another date.
  • “Sub-processor” means any third party, including a contractor, that processes personal data on our behalf for the Services.
  • “Support Hours” means 9:00 to 17:30 on Working Days, unless your Proposal states otherwise.
  • “System” means an app, hub, CRM, portal, platform or other software application we build, configure, host or manage for you, including the Team App range, systems built on the Think Mad Hub and any integration that forms part of one. A website, or a link between a website or marketing tool and another service, is not a System, but a website that runs on a System, sharing its hosting or database, is treated as part of that System.
  • “Third-Party Components” means software, open-source code, themes, plugins, fonts, stock images and other materials owned by someone other than you or us.
  • “Time Bundle” means a block of prepaid hours. Where your Proposal sets Time Bundle prices, they change only under clause 11; where it sets none, the price is the one in our Rate Card when you agree to buy.
  • “Users” means people who sign in to a System. “Staff Users” are people in your business, staff of Client Group companies, and anyone using the System to run their own business internally. “Customer Users” are people at your customers or other organisations you invite to use the System’s customer features.
  • “Website Fee” means the price your Proposal gives for a website or, where the website is included in a setup fee, that setup fee.
  • “Working Day” means Monday to Friday, excluding bank and public holidays in England, and “Working Hour” means an hour within Support Hours.

3. How the Agreement is made

3.1 Your Proposal sets out the Services, the price and anything specific to you, and names the version of these Terms that applies, which we give you, or link to, before you accept. It is valid for 30 days unless it says otherwise.

3.2 The Agreement is made when you sign your Proposal or accept it in writing or, if sooner, when after receiving it you pay any invoice or deposit for it, ask us in writing to start, or use the Services. For a System, a Fixed Term or a Proposal that names a Security Pack, we may ask for a signature from someone authorised to sign for you, and need not start until we have it. Whoever signs or accepts confirms they are authorised to do so for the business named in the Proposal.

3.3 Only the Agreement applies. Terms in or referred to in your purchase order, supplier portal, onboarding form or any other document you send us or ask us to accept do not apply, whether they arrive before or after the Agreement is made, and even if we sign, accept, register on or act on that document, unless it is a variation signed under clause 4.9. We quote your purchase order number on invoices, but a missing or late purchase order never delays payment of a sum that is due.

3.4 Free prototypes. We may offer a free prototype or demo before you buy. It carries no obligation on either side, and we decide its scope. It stays ours: until you buy, you may look at it and share it inside your business to make your decision, but not copy it, use it live, or give it or our proposal (before you accept it) to anyone else to build from. It should not hold your real personal data unless we agree in writing; sample data we create for it is ours as controller (clause 16.3) and never goes into your live System. If you sign up, we may switch the prototype on as your System, removing any sample data first. Otherwise we may delete it 60 days after we show it to you, and we delete any of your data in it when you ask.

4. How the documents fit together

4.1 If parts of the Agreement conflict, this order applies: (a) a variation made under clause 4.9; (b) Schedule 3, on data protection matters, except where your Proposal gives you more protection; (c) your Proposal; (d) the other Schedules; (e) the Part B module for that Service; (f) Part A; (g) the Security Pack. The Security Pack may add to the measures in Schedule 2 but never reduces them. A Proposal that says it prevails over these Terms prevails over the parts ranked below it in this clause, not over (a) or (b).

4.2 Your Proposal completes these Terms. These Terms set the framework, and your Proposal sets the specifics, such as prices, term, hosting, Users, service levels, ownership, liability figures and named contacts. A statement in your Proposal changes these Terms only where it says so expressly or deals specifically with the same point, without needing to name the clause. Descriptions and sales statements in a Proposal never change a limit or exclusion in clause 21 unless the Proposal says so expressly. Where your Proposal is silent, the default in these Terms applies.

4.3 Your Proposal can add to the protection in Schedules 2 and 3, but cannot take away anything Article 28 of the UK GDPR requires.

4.4 Aims and examples. Anything in a Proposal described as an aim, target, estimate, example, illustration or suggestion is not a promise, unless the Proposal or these Terms attach a remedy to it (such as the availability exit in Schedule 1).

4.5 Security Pack. The Security Pack named in your Proposal (where it names no version, the version we sent you before you signed) forms part of the Agreement and describes how we meet Schedule 2 for you. We may issue a new version as tools and suppliers change, and send it, with the changes marked, to your named contact and any group contact in your Proposal. It replaces the earlier version 30 days after we send it, unless within that time you tell us in writing, with reasons, that it reduces the protection given by any measure in the earlier version; that measure then stays as it was until we agree a change under clause 4.9. We answer your security questionnaires honestly and to the best of our knowledge at the time, but those answers are not promises unless they are repeated in the Security Pack or your Proposal. If we learn that an answer has become materially untrue, we tell you within 10 Working Days.

4.6 Entire agreement. The Agreement is everything we have agreed about the Services. It replaces all earlier proposals, drafts, brochures, website pages, demonstrations, prototypes, emails and discussions. Neither of us has relied on, or has any remedy for, any statement or promise not in the Agreement, including the “Key terms at a glance” summary. Nothing in this clause limits liability for fraud or fraudulent misrepresentation.

4.7 Changes to these Terms. New versions of these Terms apply to new Proposals and renewals. For rolling Plans, we may move you to a new version on at least 30 days’ written notice, with a marked-up copy (or, for a full rewrite, a plain summary of the changes); if it materially disadvantages you, you may end the affected Service without penalty before it takes effect. During a Fixed Term, the version you agreed stays in place, except for changes required by law, Sub-processor changes under Schedule 3, and changes that do not disadvantage you, each on 30 days’ notice with a marked-up copy. If you tell us within that time, with reasons, that such a change does disadvantage you, it does not apply to you during the Fixed Term. Any other change needs a variation under clause 4.9.

4.8 Earlier versions. A Proposal agreed under an earlier version stays under it until it renews or we move it under clause 4.7. A Plan that was rolling under an earlier version stays rolling if we move it under clause 4.7; the 12-month term in clause 12.2 applies to it only if you agree a new Proposal. A Proposal issued under version 2.1 but signed on or after 9 November 2026 applies these Terms instead if it names them. Where a Proposal that applies these Terms refers to a clause of version 2.1, read its clause 1 as clauses 1 to 4 of these Terms; 2 as 1.2 and Part B; 3 as 3.1, 10.1 and 10.2; 4 as 10; 5 as 9 and B1; 6 as 7 and B1.3; 7 as 14, B1.8, B4.11 and B5.13; 8 as B3; 9 as B2 and Schedules 1 and 2; 10 as 5.3 and B4; 11 as B4.8 to B4.11; 12 as 5.4, 10.2 and B5.15; 13 as 6 and 21.9; 14 as 16 and Schedule 3; 15 as 17; 16 as 12; 17 as B1.7; 18 as 10.7 and 13; 19 as 21; 20 as 11 and 4.7; 21 as 23; 22 as 25; 23 as 26; 24 as 27; and Annex A as Schedule 3.

4.9 Variations. Except where these Terms allow a change by notice (clauses 4.5, 4.7, 11, 12.5, 12.6, B2.9, B5.7 and B5.15, and Schedule 3, paragraph 7), a change to the terms of the Agreement (including prices, term, liability figures, ownership, and data protection or security commitments) is valid only if it is in a document that refers to the Agreement and is signed, including electronically, by an authorised signatory of each of us. No conduct, course of dealing or informal message changes the Agreement. Approving a Change under clause 7.5, a proof, content or a test checklist by email is an instruction under the Agreement and does not change its terms.

5. Our promises to you

5.1 We provide the Services with reasonable care and skill, in line with good industry practice (the care and skill a competent supplier of similar services would use) and your Proposal, using suitably experienced people.

5.2 Dates. We work to the dates in your Proposal. If a date is going to move, we tell you as soon as we know, with the reason in writing. If something we need from you arrives late, dates move by the same amount (or as clause B1.6 says for long pauses), and we tell you straight away if anything else is affected.

5.3 No guarantee of results. Search engines, AI tools, ad platforms and social networks are run by others whose rules change without notice, so we cannot promise any ranking, AI answer, traffic, leads, sales, revenue, return on ad spend or reach, and rankings can fall as well as rise. Forecasts are aims, and any revenue goal in a Proposal is your goal, which we support. What we promise is the work: done with care, within the platforms’ published rules, reported honestly, with a clear word from us if something is not working.

5.4 Third-party platforms. We are not responsible for changes, outages or decisions made by platforms such as Google, Meta, LinkedIn, Microsoft or Apple, but we remain responsible for our own work and the suppliers we choose (clause 20 and Schedule 3). You are not bound by our suppliers’ terms unless you sign them, except our hosting provider’s acceptable use rules under clause B2.4.

6. Your part

6.1 You will: (a) give us the information, content, access, approvals and decisions we need, in good time; (b) name a contact and a decision-maker; (c) keep your own logins secure, use two-step sign-in where offered, and tell us promptly if an account may be compromised; (d) tell us before you or another supplier changes anything we manage; and (e) check what we send for approval, especially facts, prices, offers and technical claims.

6.2 Client Materials. You confirm that Client Materials are yours or properly licensed for our use, accurate and lawful, and do not infringe anyone’s rights. If you ask us to use someone else’s material (for example a supplier’s images), please confirm by email that you have permission. We may refuse or remove material we reasonably believe is unlawful, infringing or offensive.

6.3 Advertising rules and regulated sectors. You are responsible for your marketing claims being true and backed by evidence, and for following the UK Code of Non-broadcast Advertising and Direct & Promotional Marketing (the CAP Code) and your sector’s rules. If you are in a regulated sector (for example financial services, health, aesthetics, audiology, legal, gambling or alcohol), or your content makes technical or standards claims (for example BS 7671, BS 5839 or BS EN 54), tell us and approve that content before we publish it. Financial promotions must be approved, where the law requires, by an FCA-authorised firm that has the FCA’s permission to approve financial promotions. We flag claims we think need evidence.

6.4 You are responsible for content you supply or approve. We are responsible for our own mistakes, such as publishing something you did not approve, or an error you could not reasonably have spotted.

7. Setup, hours, Time Bundles and changes

7.1 Setup fees. A setup fee is a fixed price for the setup work your Proposal describes. It includes the number of specialist hours your Proposal states (the “setup hours”). Unless your Proposal says they are an allowance only for what depends on you, the setup hours are the expected total time for the setup work, including your requests and revisions, meetings and workshops, preparing, correcting and re-importing your data, and rework caused by information that arrives late, changes or is incomplete. If changes, extra requests or rework you ask for would take the total beyond the setup hours, we tell you first and agree any extra time with you at the Hourly Rate. Our people plan and steer the work, AI tools help (clause 19), and our people check it for integrity, quality and security before delivery. If the total runs over only because our own work on what your Proposal describes took longer than we planned, that is our cost, not yours. We record setup time against named tasks and tell you when about 80% of the setup hours are used, with a short note of where the time has gone. Setup ends on Acceptance of the last setup Deliverable or, if setup is held up for more than 60 days (or the period in your Proposal) waiting for something we need from you, not counting time spent waiting for your group’s approval under clause B5.3 or B5.4, on the date we tell you in writing that it has ended. Unused setup hours then expire, and any remaining setup work is scheduled from your included hours or quoted. Setup fees are not refundable once work has started, except as clause 7.6 says.

7.2 Beyond the allowance. Changes, and requests beyond the setup hours or your included hours, are charged at the Hourly Rate or taken from a Time Bundle, and only after you have approved the time in writing. We never go over an approved amount without your written approval.

7.3 Included hours. Where your Plan includes hours: (a) they go on the work you choose; (b) time is recorded in 15-minute units against a named task, with a running total in your System, your monthly report or on request, and we keep these records for 2 years; (c) we tell you at 80% and never go over without your written approval; (d) unused hours carry over only as your Proposal says; (e) hours have no cash value and are not refunded; (f) unless your Proposal says otherwise, hours are used in this order: any carried over, then the current month’s included hours, then Time Bundles; and (g) meetings you cancel with less than one Working Day’s notice are logged as used, up to the time booked.

7.4 Time Bundles are paid in advance and must be used within the period stated in your Proposal or our Rate Card (6 months from purchase unless stated); unused hours then expire. Time Bundles bought before 9 November 2026 with no stated expiry may be used until 9 May 2027. A Time Bundle buys hours of work, including meetings, reviews and revisions, not a guaranteed finished result. If the hours run out first, we pause and tell you straight away. Unused Time Bundle hours are refunded only as clause 7.6 says.

7.5 Changes. Your named contact or decision-maker may ask for a Change in writing. Within 3 Working Days we estimate the hours, cost, timing and any effect on security, data or hosting, or say when to expect an estimate for a large Change. Where a Change needs more than an hour to scope, we tell you first and the scoping time uses your hours. We start once you approve in writing. A Change adding a new flow of personal data, a new supplier or a new link to another system needs your decision-maker’s written approval.

7.6 Refunds of setup fees and prepaid hours. Setup fees and Time Bundles are not refundable, except that if you end the Agreement under clause 13.1 because of our material breach, under the availability exit in Schedule 1, or under clause 23.4, we refund the part of the setup fee for setup work not yet accepted and the price of any unused Time Bundle hours. If your group refuses approval, clause B5.3 applies instead.

8. Faults and warranty

8.1 One simple rule: Faults are free, Changes use hours.

8.2 We fix Faults in our work free of charge: (a) for a website or System while you have an active Plan that includes its hosting, care or support, for as long as that Plan runs; and (b) for one-off work with no such Plan, for 90 days after Acceptance. After that, fixes are Changes.

8.3 When accepted, each System will work materially as described in your Proposal and any agreed specification. This is not a promise that a System is fit for any purpose that your Proposal or specification does not describe.

8.4 Please report a Fault with enough detail to reproduce it; we respond under Schedule 1. If we think a report is not a Fault, we tell you why before charging any time, and the first 30 minutes spent looking into each report are free. If you disagree, we still do the work if you ask, recording the time. It is charged only if you agree it was a Change or, if we have not agreed within 20 Working Days, an expert decides it was; either of us may refer that question under clause 25.4.

8.5 These promises replace terms implied by law about quality and fitness for purpose, as far as the law allows. We do not promise that a website or System will be free of every error, but we will fix Faults as this clause says. This clause does not apply if you are a consumer (Schedule 6).

9. Approvals and Acceptance

9.1 Website proofs are approved under clause B1.4, and marketing and social content under clause B4.10.

9.2 For each Deliverable that needs testing (each System release or phase, and each finished website), we send a short test checklist. You have 10 Working Days, or the period in your Proposal, to test it and report any Blocking Fault with enough detail to reproduce it. After we fix a Blocking Fault, you re-test it within 5 Working Days. Only the fixed item is re-tested, and if you report nothing in that time it counts as fixed.

9.3 A Deliverable is accepted (“Acceptance”) when the first of these happens: (a) there are no open Blocking Faults after testing; (b) the testing period in clause 9.2, which starts when we make the Deliverable available and send you the checklist, ends without a Blocking Fault being reported; or (c) you start using it for real business, other than beta or pilot use agreed in the test checklist or your Proposal (for example named customers testing a portal).

9.4 Other Faults do not hold up Acceptance; they go on a fix list and we fix them free. Requests to change what is described are Changes.

9.5 If a Deliverable fails re-testing because of Blocking Faults twice, you may: (a) give us a further period to fix them; (b) accept it with a fix list and a fair reduction in the setup fee, agreed between us or, failing agreement within 10 Working Days, decided by an expert to whom either of us may refer it under clause 25.4; or (c) if it is a System and it still has a Blocking Fault 20 Working Days after the second failed re-test, end the Agreement under clause 13.1 as if for our material breach.

10. Paying us

10.1 Prices are as set in your Proposal, plus VAT at the current rate. We issue VAT invoices for our fees.

10.2 Third-party costs (such as paid placements, ad spend, licences, premium plugins, stock assets, fonts, app store fees, domain fees, usage charges and cloud bills under Client Hosting) are agreed with you before they are incurred. You pay them directly, or we charge them at the price in your Proposal or our Rate Card (ad spend and cloud bills at cost, plus any card, currency or payment fees). Where we pay a third party for you, we may ask you to pay us first.

10.3 Direct Debit. Plan fees are collected monthly in advance by Direct Debit through GoCardless from the Start Date, unless your Proposal says otherwise. We, or GoCardless for us, give advance notice of each collection, as the Direct Debit Guarantee requires, and you are protected by the Guarantee. Each monthly fee is due on its collection date (the Start Date for the first month), whether or not a Direct Debit collects; a failed collection may be presented again and stays due from the original date.

10.4 Invoices and stages. Setup fees are invoiced on signing and, unless your Proposal says otherwise, collected by Direct Debit with your first monthly fee or paid within 14 days. We may wait to start setup work until the setup fee is paid or your purchase order is issued. Website Fees are paid in the stages your Proposal states, for example a deposit to start and the balance on Acceptance; the final stage is due on Acceptance under clause 9.3, whether or not you have yet given the go-ahead to go live. Where a website is included in a setup fee, it is paid as this clause says for setup fees. Other invoices, including invoices against a purchase order where your Proposal allows them instead of Direct Debit, are payable within 14 days unless the invoice or your Proposal states otherwise.

10.5 Disputed invoices. If you think part of an invoice is wrong, tell us in writing within 10 Working Days of receiving it, saying which part and why, and pay the rest on time. While we try to settle an amount disputed in good faith, we will not suspend anything over it, and we both aim to settle it within 14 days; if we cannot, clause 25 applies. Any part later agreed or decided to be due carries interest under clause 10.6 from its original due date. Apart from withholding a disputed part under this clause, you may not withhold, deduct or set off any amount from what you owe us, unless we have agreed in writing, or a court has decided, that we owe it to you.

10.6 Late payment. We may charge statutory interest and compensation under the Late Payment of Commercial Debts (Interest) Act 1998 (which does not apply to consumers) on any sum not paid when due, and you also pay our reasonable costs of recovering overdue sums so far as that compensation does not cover them. A sum is undisputed unless you have disputed it in good faith under clause 10.5 and the dispute is not yet settled or decided.

10.7 Pausing work and suspension for non-payment. If an undisputed sum is 14 days overdue, we may pause new work, Changes and the use of included hours and Time Bundles after telling your named contact (and any finance contact). A pause never affects hosting, access, security work, Faults with Critical priority or your data, and paused hours are added to the next month once you have paid. We may suspend a Service only if an undisputed sum is at least 14 days overdue (30 days for a System that is covered by a Security Pack or is on a Fixed Term of 12 months or more), we have then given written notice that we will suspend it, and the sum is still unpaid 14 days after that notice. Before we limit access for Customer Users, we give a further 7 days’ notice to your decision-maker and any group contact. We suspend only what is needed, your data export stays available, and we restore the Service within one Working Day of payment. Cancelling your Direct Debit mandate without agreeing another way to pay counts as non-payment of the next collection.

10.8 Your data is never at risk. Suspension never means deleting your data, and returning your data, domains and accounts never depends on payment (clause 15).

10.9 Reactivation fee. For websites, hosting and social scheduling only, restoring a suspended Service may carry a reactivation fee of £100 + VAT for the work of restoring it. There is no reactivation fee for Systems, or for a website or hosting provided with a System.

10.10 Chargebacks. If a chargeback or payment reversal proves unjustified, the amount stays payable and clause 10.7 applies to it.

11. Price review

11.1 Fees for a Fixed Term, including the Hourly Rate and any Time Bundle prices in your Proposal, are fixed for that Fixed Term, unless your Proposal says otherwise.

11.2 For rolling Plans, we may review fees, the Hourly Rate and Time Bundle prices once a year. Any increase will be no more than the higher of the annual Consumer Prices Index (CPI) rate most recently published by the Office for National Statistics before our notice and 3%, and never more than 5%. If CPI stops being published, a comparable official index applies.

11.3 We give at least 30 days’ written notice by email, showing the new amount in pounds and pence, which then applies from the date in the notice.

11.4 Renewal prices. A renewal offer may set a new price for the next term, for example to reflect how the Services are actually used. If it raises the monthly fee for the same Services by more than the limit in clause 11.2, our offer says so clearly, and that price applies only if you accept it in writing (clauses 12.5 and 12.6). A renewal for the same Services carries no new setup fee.

12. How long the Agreement lasts, and renewal

12.1 The Agreement starts on the Start Date and continues until ended under these Terms.

12.2 Term of every Plan. Every Plan runs for a Fixed Term of 12 months from the Start Date unless your Proposal states a different term or says the Plan is rolling (annual services renew under clause 12.8). A Plan is rolling where your Proposal says so, and once its Fixed Term has ended and it continues monthly under clause 12.5(c). Once any minimum term has passed, either of us may end a rolling Plan on 30 days’ written notice, except that we give at least 90 days’ notice to end a rolling Plan for a System.

12.3 Minimum terms (periods during which a rolling Plan cannot be ended on notice) apply to a rolling Plan only where your Proposal states one, after which the Plan rolls monthly. If you end the Plan during a minimum term, clause 12.7 applies.

12.4 Fixed Terms and Review Points. A Fixed Term runs for the period in your Proposal. At a Review Point, either of us may end the Agreement as your Proposal describes, and no fees are payable for any period after it ends.

12.5 Renewal offer. At least 2 months before a Fixed Term ends, we send you a renewal offer with the new price and term. You may: (a) accept a new Fixed Term in writing; (b) end the Agreement when the Fixed Term ends, by telling us in writing before then; or (c) do nothing, and the Agreement continues monthly at the new price (or, where that raises the monthly fee for the same Services by more than the limit in clause 11.2 and you have not accepted it in writing, at the existing price increased by no more than that limit), which either of us may end on 30 days’ written notice (at least 90 days’ notice from us for a System, as clause 12.2 says). If our offer is late, the existing price continues until 2 months after you receive it, and the choices above apply from then; either of us may still end the Agreement on notice under clause 12.2 once the Fixed Term has ended.

12.6 Automatic renewal. Where your Proposal says the Agreement renews automatically (as our Team App Plans usually do), it renews for a further Fixed Term of the same length at the price in our renewal reminder, unless you opt out. We send the reminder in writing at least 2 months before the Fixed Term ends, with the renewal price, the term and how to opt out. You may opt out by written notice up to 30 days before the Fixed Term ends, and the Agreement then ends with the Fixed Term. If our reminder is late, the renewal date moves to 2 months after you receive it, the existing price continues until then, and you may opt out at any time up to 30 days before that date. If the renewal price raises the monthly fee for the same Services by more than the limit in clause 11.2 and you have not accepted it in writing under clause 11.4, there is no automatic renewal and clause 12.5(c) applies.

12.7 Ending a term early. You may end a Fixed Term or minimum term early at any time by written notice; we may do so only as these Terms or your Proposal allow. If you end it early, or we end the Agreement under clause 13.1(a) because of your breach, you pay an early exit charge: the monthly fees that would have been payable from the end date to the next Review Point (or, if there is none, to the end of the Fixed Term or minimum term), less any third-party costs we no longer have to pay (such as hosting or licences for your System), plus VAT, unless your Proposal sets a different charge. It is due 14 days after the end date. There is no early exit charge when you end the Agreement at a Review Point or under clause 4.7, 13.1, 13.2, 23.4 or B5.3.

12.8 Annual services. Standalone annual services, such as domains, renew each year unless you cancel in writing at least 14 days before the renewal date.

12.9 Notices to end must be in writing under clause 26.4, not by phone or in person.

13. Ending the Agreement and what happens next

13.1 Either of us may end the Agreement, or the affected Service, straight away by written notice if the other: (a) commits a material breach, or repeated breaches of the same obligation that together amount to a material breach, and does not put it right within 30 days of being asked in writing (10 Working Days for a breach of clause 16, 17 or 18 or Schedule 2 or 3); or (b) becomes insolvent, enters administration or liquidation, has a receiver appointed, makes an arrangement with its creditors, stops trading or cannot pay its debts (so far as the law allows; for example, section 233B of the Insolvency Act 1986 may stop us ending a supply to you for this reason). Failing to pay an undisputed sum within 30 days of a written notice from us that refers to this clause is a material breach. A breach can be put right if its practical effect can be put right in the time allowed: a missed record, report or notice is put right by completing it, and a late security update by applying it.

13.2 You may also end the Agreement, or the affected Service, without any early exit charge: (a) under the availability exit in Schedule 1; (b) after objecting to a Sub-processor under Schedule 3 where we cannot offer an alternative; (c) where a change under clause 4.7 materially disadvantages you; (d) under clause 26.1 or 26.2; (e) under clause 18.2; or (f) under clause B5.7.

13.3 What you pay. On ending, you pay for Services provided up to the end date, any agreed third-party costs we cannot cancel, and any amount under clause 12.7 where it applies. If you end under clause 13.1 because of our breach or insolvency, or under clause 13.2, you pay nothing for any later period, and we refund Plan fees paid in advance for it; setup fees and Time Bundles follow clause 7.6.

13.4 What happens next. We return your data and help you move under Schedule 4; ownership follows clause 14 and clauses B1.8, B4.11 and B5.13; each of us returns or deletes the other’s Confidential Information, except anything the other may keep and use under clause 14.3, B5.13 or B5.14, subject to Schedule 4 and any legal duty to keep it; and access to our own tools, such as our scheduling dashboard, ends after any continued-service period.

13.5 Clauses 7.6, 10 (for sums due), 12.7, 13.3, 13.4, 14 to 17, 18 and Schedule 2 (until your Client Data is deleted), 20.1, 21, 22.2, 24, 25 and 26, clauses B1.8, B4.11, B5.13 and B5.14, and Schedules 3 and 4 continue after the Agreement ends, with any other clause that by its nature should.

14. Who owns what

14.1 Your materials and data. Client Materials and Client Data stay yours. You give us a non-exclusive, royalty-free licence to use them only to provide the Services and carry out Schedule 4.

14.2 Deliverables. Ownership of Deliverables is set out in clauses B1.8 (websites), B4.11 (marketing content) and B5.13 (Systems). Until ownership passes, you have a non-exclusive licence to use each Deliverable for your business while the Agreement continues.

14.3 Platform Components stay ours. Where they form part of a Deliverable you own, we grant you a permanent, royalty-free, non-exclusive licence to use, copy and change them, and to have another developer maintain them for you, as part of that Deliverable and only for the internal business of you and your Client Group companies. We cannot withdraw this licence, and it continues after the Agreement ends. It passes only to a Client Group company or to someone who takes over your business, or the part of it that uses the Deliverable. You may not sell, license, rent or share the Platform Components, or any Deliverable containing them, outside your Client Group, offer them as a product or service to others, or sell or license outside your Client Group a product built from them that competes with ours. Anyone who works on them for you must first agree in writing to keep them confidential and use them only for your Deliverable. Your Users may use the Deliverable as normal.

14.4 Our reuse. We may keep using Platform Components and our general know-how for other clients, but never your Client Data, prices, branding, Confidential Information or Client-Specific Work.

14.5 Third-Party Components keep their own licences. At handover of a System we list its main Platform Components and its open-source and other Third-Party Components, with their licences. We will not use a component whose licence would force your own code to be published (for example the AGPL in server code) without your written agreement.

14.6 AI-assisted work is owned on the same basis as other Deliverables, and we transfer whatever rights exist in it. UK law on copyright in purely AI-generated material is under review, and AI tools can produce similar output for others, so we cannot promise every AI-assisted element is protected by copyright or unique to you. We do not deliver a logo or core brand mark generated by AI alone.

14.7 Portfolio and credit. Unless you ask us in writing not to, we may say we work with you, show work we made for you in our portfolio and, for websites, include a small “Website by Think Mad” credit in your footer. Where your Proposal is marked confidential, we do none of these without your prior written consent. We only show a System, its screens or any Client Data with your written consent, and we never show your prices or anything confidential.

14.8 Making ownership work. We confirm that we have, or will have by the time it is due, every right needed to assign and license what this clause and clauses B1.8, B4.11 and B5.13 promise. Our people and contractors assign their rights in their work to us and waive in writing their moral rights in Client-Specific Work. We will sign any document you reasonably need to record or register an assignment, at our cost.

15. Your data, accounts and domains are always yours

15.1 Returning your data never depends on payment of any sum. Whatever happens, including a dispute or an unpaid invoice, we return your Client Data under Schedule 4.

15.2 Accounts in your name. Domains, Google Business Profiles, Google Analytics, Tag Manager and Search Console, ad accounts, social media accounts and pages, app store developer accounts, cloud accounts under Client Hosting, and email and marketing tool accounts we set up for you are registered in your business’s name wherever the platform allows, with us as a manager or user. If a platform makes us create something in our name, we transfer it to you as soon as practical, and in any case when you ask.

15.3 We never hold any of these back for payment. When your named contact or decision-maker asks in writing, and we have confirmed the request with them by phone or another channel we already use with them, we hand back control and remove our access within these times: 7 Working Days for a Google Business Profile (Google makes a newly added owner wait 7 days before primary ownership can pass to them, and we follow any longer wait it sets), 2 Working Days for a domain transfer under clause B3.3, and otherwise 5 Working Days.

16. Data protection

16.1 Each of us will comply with Data Protection Law.

16.2 Where we process personal data for you, including prospect research under clause B4.15, you are the controller, we are your processor, and Schedule 3 applies.

16.3 We are the controller of our own business data about you and your staff (such as contacts and billing), of sample data we create for demos and prototypes, and of our own marketing data, as our privacy notice at https://thinkmad.co.uk/privacy/ explains. You or your staff can complain to us about how we use personal data through the route in that notice, and we acknowledge complaints within 30 days.

16.4 If we both sign your own data processing agreement as a variation under clause 4.9 in place of Schedule 3, clause 21 applies to all liability under or in connection with it, including any indemnity in it, unless that variation names clause 21 and states the figures that replace those in it.

16.5 We may record calls for training and record-keeping under our legitimate interests. We tell you before recording starts and share recordings only where the law requires.

16.6 Please send personal data and price lists through the System or another secure route we agree, not by ordinary email.

17. Confidentiality

17.1 Each of us will keep the other’s Confidential Information confidential and use it only for the Agreement, including any licence it gives (such as under clauses 14.3, B5.13 and B5.14).

17.2 Each of us may share it with our staff, contractors, auditors, insurers, professional advisers and regulators, and you may also share it with your Client Group companies, in each case where they need to know it and are bound by duties at least as strict. Each of us is responsible for those it shares with.

17.3 This clause does not cover information that is public (other than through a breach of this clause), already known to the receiver, developed independently, or received lawfully from someone else. If the law requires disclosure, the party required to disclose tells the other first, where it lawfully can.

17.4 These duties last during the Agreement and for 5 years after it ends. For trade secrets, our Source Code and Platform Components, personal data and Client Data, including your price lists and customer data, they have no end date.

17.5 Neither of us puts the other’s Confidential Information into an AI tool except as clause 19 allows (for us) or as the owner agrees in writing. Each of us tells the other promptly on becoming aware of any unauthorised use or disclosure of the other’s Confidential Information.

18. Security

18.1 We protect Client Data and Systems with the baseline measures in Schedule 2, Section A, and the enhanced measures in Schedule 2, Section B wherever clause B5.5, your Proposal or your Security Pack says they apply.

18.2 Certifications. Our current certifications, if any, and their dates are in the Security Pack. We send you each new certificate when issued and tell you if one lapses. Your Proposal may set a target date for Cyber Essentials, Cyber Essentials Plus or another certification. If it does and we miss one by more than 60 days, you may end the Agreement without any early exit charge by written notice given within 60 days after that.

18.3 We tell you about Security Incidents under Schedule 3, paragraph 9.

18.4 Independent testing. You may commission an independent security test of your System, at your cost, on 10 Working Days’ notice and under rules we agree to protect our other clients and any shared platform. We fix free of charge any finding rated high or critical by the tester and, acting reasonably, by us, and any finding that shows your System falls short of Schedule 2 or your Security Pack, where it lies in work, settings or Third-Party Components we are responsible for: critical and high findings within 14 days, others within 60 days, or by another date we agree where a fix needs a larger Change. If we do not agree a rating, either of us may refer it under clause 25.4. Other recommendations, such as further hardening or new features, are Changes, and we give you a plan and estimate for them. This does not cover changes made by you or another supplier.

18.5 Security suspension. We may suspend a User, a feature or a Service straight away where reasonably needed to stop a Security Incident, unlawful use or harm to other clients. We limit this to what is needed, tell you as soon as we can, and restore the Service once the risk has passed.

18.6 No disabling code. We will not put into any Deliverable any code or setting designed to stop it working, limit access to it or delete data, such as a time lock or kill switch, and we use no technical means to stop or restrict a Service except under clause 10.7, 18.5, B5.7 or B5.9, or when the Agreement or that Service ends (your data stays available under Schedule 4). Removing our licence keys or tool access when a Service ends is not a restriction under this clause.

19. How we use AI

19.1 We use AI tools, including Claude from Anthropic, to support research, drafting, design, analysis and software development. Our people steer the work, check it before it is delivered, and stay responsible for it as if it were made without AI.

19.2 We only put Client Data into AI tools that we use under business or commercial terms which do not allow the provider to train its models on what we put in or get out, and which limit how long the provider keeps it. We never use a personal or consumer AI account for your work. This applies equally to AI features built into other tools we use, such as design, SEO, writing and social scheduling tools, and to AI assistants connected to your systems or accounts. The Security Pack, or our Sub-processor list, names each AI tool, what we use it for, what data it can see, where it processes data and how long the provider keeps it.

19.3 Your personal data only goes into AI tools listed as Sub-processors under Schedule 3, and your other Confidential Information, such as price lists, only into AI tools listed in your Security Pack or our Sub-processor list; where your Proposal requires your written approval of Sub-processors, only into AI tools you have approved for your personal data, price lists and customer data. Connecting an AI assistant to a System, website, mailbox, CRM or account that holds your personal data counts as putting that data into the AI tool. We ask before adding a new use of AI involving your data. Coding assistants listed in the Security Pack or our Sub-processor list may work on your System’s code and test data, but not your live data or price lists, and are not connected to your live databases, unless you approve otherwise in writing. We do not knowingly put special category data, passwords or payment card details into an AI tool, and we set up our AI tools and connections to keep them out; if any gets in by mistake, we treat it as a Security Incident and have it deleted from the tool where the provider allows.

19.4 A person reviews AI-assisted work before it reaches you, including checking key figures and facts against the sources we used. We flag technical, legal and standards claims for you to check, as clause 6.3 says, and you approve anything we publish for you.

19.5 You may ask us to make a specific Deliverable without AI. We will respect that, telling you first if it affects timescales or hours. Any extra time is a Change.

19.6 We never let AI or other automated means alone make a decision that has a legal or similarly significant effect on a person (Articles 22A to 22D of the UK GDPR).

19.7 AI features inside your System (such as an assistant, chatbot or automated scoring) are switched on only with your agreement, tell Users when they are dealing with AI, and use providers listed as Sub-processors. Where Users are in the EU, they also follow Article 50 of the EU AI Act.

19.8 AI tools that read public web pages for prospect research cannot change data in your System. A person reviews what they find before it is saved.

20. Contractors and subcontractors

20.1 We may use contractors and subcontractors to support our work, and we remain fully responsible for their work as if it were our own.

20.2 Before a contractor starts work on your project, we tell you in writing who they are, what they will do, where they are based and their relevant credentials (such as qualifications, experience, vetting or certifications). The notice never includes passwords or other login details.

20.3 A contractor who will access your personal data, or a system holding it, is a Sub-processor, and one who will access your other systems or Client Data is treated the same way for notice and objection. We give you at least 10 Working Days’ notice before their access starts (or the period in your Proposal), and you may object on reasonable data protection grounds under Schedule 3, paragraph 7. If we need urgent cover, for example for illness or a Fault with Critical priority, we may give shorter notice, as soon as we can, with access limited to that need, and you keep the same right to object. Where your Proposal requires your written authorisation, urgent cover comes only from a named pool of contractors you have approved in advance in your Security Pack, or from a contractor your named contact approves by email before access starts.

20.4 Every contractor is bound in writing, before they start, by confidentiality, data protection and security terms at least as protective as these Terms, and assigns to us in writing all intellectual property in the work they do on your project. They get only the access they need, through their own named logins with two-step sign-in, and lose that access within one Working Day of their work ending. They use only the AI tools allowed under clause 19, keep no copies of your data after their work ends, and may not pass any of the work to anyone else without our written agreement and the notice in clause 20.2. A contractor based outside the UK who will see your personal data is also a transfer under Schedule 3, paragraph 8. Screening under clause 24.2 applies to contractors with administrator access as it does to our staff.

20.5 For small jobs where a contractor has no access to your systems, Client Data or personal data (for example a freelance illustrator working from files we supply), a lighter notice is enough: an email naming them and their role before they start. Whatever the job, we tell you who is working on your project whenever you ask.

21. Liability

21.1 Each of us is responsible for our own breaches and will take reasonable steps to limit any loss.

21.2 No limit applies to liability for: (a) death or personal injury caused by negligence; (b) fraud or fraudulent misrepresentation; (c) anything else that cannot lawfully be limited or excluded; (d) your duty to pay fees, charges and other sums due under the Agreement, including any early exit charge under clause 12.7; (e) your use, copying, disclosure or licensing of Platform Components, or of code deposited under clause B5.14, outside what clauses 14.3 and B5.14 allow; or (f) our deliberate abandonment, without lawful reason, of all or substantially all of the Services, continuing for 10 Working Days after your written notice that refers to this clause. Item (f) does not include a pause or suspension we make in good faith under clause 10.7 or 18.5, or a genuine dispute about what the Agreement requires.

21.3 Subject to clause 21.2, neither of us is liable for loss of profit, revenue, business, contracts, goodwill or anticipated savings (whether direct or indirect), or for indirect or consequential loss. This does not affect: (a) sums payable to us, including any early exit charge or, where you end a Fixed Term or minimum term in breach and clause 12.7 does not apply, the fees for the rest of it less costs we save; (b) costs made recoverable by clause 21.7; or (c) your loss of profit or revenue resulting directly from a disclosure of your price lists, pricing data or customer data caused by our breach of clause 16, 17 or 18 or Schedule 2 or 3, which is recoverable within the higher limit in clause 21.5.

21.4 General limit. Subject to clauses 21.2 and 21.5, the total liability of each of us for all claims arising from events in each Contract Year, whether in contract, tort (including negligence), breach of statutory duty or otherwise, is limited to the greater of:

  1. the total fees paid and payable under the Agreement for that Contract Year (for a Fixed Term, the fees for the whole Contract Year as set in your Proposal, even if the Agreement ends earlier; for rolling Plans, the fees paid and payable in the 12 months before the first event giving rise to a claim in that Contract Year); or

  2. £5,000,

unless your Proposal states different figures, which replace only the amount in (a) or (b). This is one limit for all claims together in each Contract Year, not a limit for each claim. All claims arising from the same event, a series of connected events or a continuing breach count as arising in the Contract Year of the first of them, however each claim is put. In this clause, “fees” means our fees under the Agreement excluding VAT, ad spend and third-party costs recharged to you.

21.5 Higher limit for security incidents, data breaches, confidentiality and our IP indemnity. For all claims arising from a Security Incident, a personal data breach or a disclosure of Confidential Information, however put (including under clause 5.1 or in negligence), and for the indemnity in clause 21.8, the total liability of each of us for all such claims arising from events in each Contract Year is limited to the figure in your Proposal or, if none is set, the greater of twice the fees in clause 21.4(a) or £25,000. These claims fall only within this higher limit, not the general limit, and the same loss cannot be recovered twice.

21.6 Lost or damaged data. If Client Data is lost or damaged because of our breach, we restore it, at our cost and as quickly as we reasonably can, from the most recent backup we should have held under Schedule 2 or your Proposal. You may also recover the reasonable cost of recreating anything that cannot be restored. Both are within the limits in this clause (the higher limit, where clause 21.5 applies).

21.7 Data incident costs. So far as caused by our breach, these are direct losses recoverable within the higher limit: reasonable costs of restoring data, investigating a Security Incident, and notifying affected people and the Information Commission. Neither of us is liable to the other for any fine or penalty imposed on the other by a regulator or court, except where the law does not allow this to be excluded. This does not affect either party’s own liability to a regulator.

21.8 Our IP indemnity. We will defend you against any third-party claim that a Deliverable infringes their copyright, database right, design right, registered trade mark or rights in confidential information in the UK, and pay the damages and reasonable costs finally awarded, or agreed in a settlement that we (and, where needed, our insurers) approve, together with our own defence costs, within the higher limit. This does not cover claims arising from Client Materials; material generated from prompts, examples or instructions you supplied; Third-Party Components (except where we chose them and did not have, or did not keep to, the licence needed for the use we made of them); changes not made by us or our contractors; combinations with things we did not supply; use outside the Agreement; or use after we have offered a non-infringing replacement under this clause. You must tell us promptly, let us and our insurers control the defence and settlement, give reasonable help at our cost, and make no admission. If a claim is made or likely, we may change the Deliverable so it no longer infringes but works the same way, get you the right to keep using it, or, if neither is reasonably possible, remove it and refund the fees paid for it, less one thirty-sixth of those fees for each month you have used it. This is your only remedy for third-party IP claims about Deliverables.

21.9 Your indemnity. On the same conditions as clause 21.8, with our roles reversed (so you control the defence and settlement, and we give reasonable help at your cost), you will defend us against any third-party claim arising from Client Materials or content you supplied or approved infringing rights or being unlawful, or from marketing sent on your instructions to contacts you supplied in breach of Data Protection Law, except to the extent caused by our breach. This is subject to the general limit in clause 21.4 or, for marketing to contacts you supplied, the higher limit in clause 21.5.

21.10 Any service credits your Proposal adds count towards these limits, are your only financial remedy for the failure they relate to, and are never more than 10% of the monthly fee for the affected Service in any month. Statutory interest and fees owed to us do not count towards these limits.

21.11 Time limit. A claim is barred unless court proceedings for it are issued within 2 years of the date the claiming party became aware, or should reasonably have become aware, of the facts giving rise to it. Time stops running while a dispute is being discussed or mediated under clause 25.2 or 25.3, and for 30 days after that ends. For a claim under the indemnity in clause 21.8 or 21.9, time runs from when the third party first makes its claim in writing. This clause does not apply to claims for fees or other sums payable under the Agreement (including under clauses 12.7 and 26.3).

21.12 Our prices reflect these limits. If you need higher limits, ask us before you accept your Proposal: we will quote once we have confirmed that our insurance supports them, and your Proposal records the limits that apply.

22. Insurance

22.1 During the Agreement we will keep, with insurers authorised to provide insurance in the UK: (a) professional indemnity insurance of at least £500,000 for each claim; (b) cyber and data insurance of at least £50,000 in total for each policy year, renewed while we provide Services; (c) public liability insurance of at least £2,000,000 for each claim; and (d) employers’ liability insurance as the law requires. Your Proposal may set higher figures. Our insurance does not increase or reduce our liability under clause 21.

22.2 We will keep the professional indemnity insurance in clause 22.1(a), or buy run-off cover giving the same protection, for at least 6 years after the Agreement ends. We send certificates on request, and tell you within 10 Working Days if any policy in clause 22.1 is cancelled, not renewed, or reduced below those figures.

23. Events outside our control

23.1 Neither of us is liable for a delay or failure caused by an event beyond its reasonable control, such as a widespread power or internet failure, fire, flood, epidemic, war, a cyber operation carried out by or for a state, or government action.

23.2 These do not count: (a) a failure to carry out the security, backup and continuity measures in Schedule 2, your Security Pack or your Proposal (but the time reasonably needed to restore a Service using those measures after an event that is otherwise outside our control is excused); (b) a cyber-attack, unless those measures, properly applied, could not have prevented it; (c) a failure by our own contractors or suppliers, unless it was itself beyond their reasonable control (including their insolvency or a widespread outage of their service) and could not reasonably have been worked around using those measures; and (d) shortages or strikes among our own people.

23.3 Such an event does not excuse payment for Services provided, or our duties to restore from backup, notify Security Incidents and return your data.

23.4 The affected party tells the other promptly and works to reduce the impact. If the event lasts more than 30 days, either of us may end the affected Service by written notice without penalty, and we refund Plan fees paid in advance for Services not provided (setup fees and Time Bundles follow clause 7.6).

24. Doing business properly

24.1 Each of us will comply with the Bribery Act 2010, the Modern Slavery Act 2015, the Criminal Finances Act 2017 (including not facilitating tax evasion) and UK sanctions law. Neither of us will commit fraud, including fraud intended to benefit the other. Each of us keeps procedures to prevent these things that are proportionate to its size and risks, tells the other promptly of any breach connected with the Agreement, and helps with reasonable checks. A breach of the first two sentences of this clause is a material breach that cannot be put right, so the other may end the Agreement under clause 13.1 straight away. A breach of the rest of this clause is a material breach if it is not put right within 30 days of written notice.

24.2 Our people are bound by written confidentiality duties, trained in data protection and security for their role, and screened appropriately for their role, as described in the Security Pack.

25. Resolving problems

25.1 If something goes wrong, we would always rather sort it out quickly. Please tell your usual contact at Think Mad, or Luke Hilditch (luke@thinkmad.co.uk).

25.2 If it is not resolved, either of us may give written notice of a dispute, and a director or senior manager from each side (Luke Hilditch for us) will talk within 14 days to try to settle it in good faith.

25.3 If that does not settle it within 14 days, either of us may, within the following 14 days, refer it to mediation under the CEDR Model Mediation Procedure, or with another mediator we agree, sharing the mediator’s fees equally.

25.4 A technical question (such as whether something is a Fault or a Change, or the rating of a test finding) may go to an independent expert, acting as an expert and not an arbitrator, if we both agree or where these Terms let either of us refer it. If we have not agreed on the expert within 5 Working Days, either of us may ask CEDR to nominate one. The expert’s written decision is final and binding on that question, except in the case of fraud or obvious error, and the expert decides who pays their fees (equally, if the expert does not say).

25.5 Where mediation has been asked for under clause 25.3, court proceedings may start only if it has not settled the dispute within 30 days of referral or the other party will not take part. This does not stop either of us from bringing a claim within the small claims limit, going to court at any time to recover sums that are due and not disputed under clause 10.5, seeking urgent court relief, or issuing proceedings to stop a claim running out of time (and then pausing them while this clause is followed).

26. General

26.1 Transfer. You may transfer the Agreement to a Client Group company by written notice, staying responsible for sums due before the transfer and, for the rest of the current Fixed Term, for any sums that company does not pay. Otherwise neither of us may transfer it without the other’s written consent, not to be unreasonably withheld, except that we may transfer it by written notice to a successor taking over all or most of our business. If you reasonably object to that successor on security, data protection or competition grounds within 30 days, you may end the affected Services without penalty.

26.2 Change of control, conflicts and key people. We tell you within 30 days if control of Think Mad changes. If the new controller or its group competes with you or your Client Group, or you have other reasonable concerns about it, you may end the Agreement without any early exit charge on 30 days’ written notice given within 60 days of being told. Unless your Proposal gives you exclusivity, we may work for other businesses in your sector, but we keep your Confidential Information and Client Data away from that work, and we tell you if we take on a direct competitor of yours for a System. We tell you if the named lead in your Proposal changes.

26.3 Non-solicitation. During the Agreement and for 12 months after it ends, neither of us will employ or engage, directly or through another business, anyone from the other’s team (including contractors) who was materially involved in the Services in the previous 12 months, without written agreement. This does not apply to someone who answers a general public advertisement, or stop either of us continuing to use a freelancer who worked for it before the Services began. If either of us breaks this clause, it will pay the other a fee equal to 20% of the annual salary or fees first agreed with that person for their new role, as a fair estimate of the cost of recruiting and training a replacement.

26.4 Notices. Notices must be in writing and sent by email: to you, to the named contact in your Proposal; to us, to projects@thinkmad.co.uk for the attention of Luke Hilditch. A notice to end the Agreement, or about a breach, dispute or Security Incident, should also be copied to the other’s decision-maker and any legal or group contact named in the Proposal and, for us, to luke@thinkmad.co.uk, but a missing copy never makes a notice invalid. A notice may also be delivered by hand or sent by recorded post to the other’s registered office, and is received on delivery or, if posted, at 9:00 on the second Working Day after posting. An email notice is received when sent within Support Hours on a Working Day, and otherwise at 9:00 on the next Working Day, unless the sender is told it was not delivered. A notice ending the Agreement at a Review Point counts as received on the day it is sent if it is emailed by 23:59 on the last day for notice.

26.5 Reselling. You may not resell or sub-license the Services, except to your Users and to Client Group companies named in your Proposal.

26.6 Other points. If any part of these Terms is unenforceable, it is changed to the minimum extent needed, or removed, and the rest continues. A delay in using a right is not a waiver of it, and a waiver is valid only in writing and only for the occasion it covers. You may recover, as if they were your own, losses suffered by Client Group companies named in your Proposal because of our breach, within the limits in clause 21 and without double recovery, and they may enforce clause 14.3 under the Contracts (Rights of Third Parties) Act 1999. Otherwise, nobody else has rights under that Act to enforce any term of the Agreement, and we may vary or end the Agreement without anyone else’s consent. We are independent contractors, not partners. The Agreement may be signed electronically and in counterparts.

26.7 Law. The Agreement, and any dispute or claim (including a non-contractual one) arising out of or in connection with it, are governed by the law of England and Wales, and its courts have exclusive jurisdiction, except that consumers may bring proceedings in their local courts.

27. How to contact us

Our details are at the top of these Terms. For anything about these Terms, contact Luke Hilditch: luke@thinkmad.co.uk, 0151 316 0110.

Part B: Service modules

B1. Websites

B1.1 What we build. We design and build your website as your Proposal describes, on the platform it states (usually WordPress, set up so you can update your own pages).

B1.2 Your content. Please send content and materials when we ask. Until they arrive we may use clearly marked placeholder text and stock images.

B1.3 Revisions. Your Proposal includes a set number of revision rounds (typically two for each page template), plus reasonable minor edits within the agreed design. Anything more is a Change.

B1.4 Proofs and going live. We send proofs and clearly ask for approval. If we have not heard back within 10 Working Days, we send a reminder giving the date by which we will treat the proof as approved. If we still have not heard back within 5 Working Days of that reminder, we may treat that proof as approved so the build can move on. Your website only goes live on your domain with your clear go-ahead, and prices, offers, regulated content, technical or standards claims, and statements about named people always need your clear yes.

B1.5 Testing. Clause 9 applies to the finished build, with a checklist covering things like forms, redirects, tracking and cookie consent.

B1.6 Pauses. If the project waits on you for more than 30 days, we may schedule it around other work and invoice for work done to date (not the next stage), then restart with a new date when you are ready.

B1.7 Ending a build early. If you cancel after work has begun, you pay for work done to date, valued at the Hourly Rate for time recorded or by the stages completed in your Proposal, and third-party costs already committed, up to the Proposal price. We keep what you have paid to that extent and refund anything above it. We return your Client Materials and Client Data whatever happens, and hand over designs and files for work you have paid for. This clause does not apply to a website included in a setup fee or that runs on a System; clauses 7.1 and 7.6 apply to those instead.

B1.8 Ownership. Except as the rest of this clause says, once the Website Fee is paid in full, we assign to you, with full title guarantee, all intellectual property in the website’s Client-Specific Work, such as designs, layouts, content we wrote and custom code. Going live does not by itself transfer ownership while a balance remains. Platform Components are licensed under clause 14.3; themes, premium plugins, fonts and stock assets are Third-Party Components. Where a website runs on a System, it passes with the System under clause B5.13, unless your Proposal says otherwise. If we design a website at no extra cost alongside another Plan, it becomes yours once that Plan has been paid for 12 months, unless your Proposal says otherwise; if the Plan ends sooner, we give you your content and media, and you may buy the website’s design and build at the price in your Proposal or our Rate Card.

B1.9 Premium plugins and themes may run under our agency licences while we look after your site. If you move away, we remove our licence keys, and you will need your own licences for updates and security fixes. We give you a list of what is used.

B1.10 Fonts. We use open-licence fonts by default and can host them on your site. A commercial font is licensed in your name, or bought for you and recharged.

B1.11 Accessibility. Where your Proposal says so, we aim for WCAG 2.2 level AA in the parts we design and build, checked with tools and by hand. We cannot guarantee full conformance, because later content and third-party tools also affect it. A formal audit is an extra. Your own legal accessibility duties (such as under the Equality Act 2010) stay yours.

B1.12 Cookies and privacy. You are responsible for your cookie consent tool and privacy notice, which we can set up under your Proposal. Tags we add respect your consent tool: advertising, tracking and analytics tags wait for consent, unless your Proposal says that analytics may run under the statistical purposes exception in PECR, which applies only where they are used solely to improve your website, the data is not shared with anyone for their own purposes (so not most advertising-linked Google Analytics setups), and visitors are clearly told and can easily object for free. Please tell us before anyone else adds tags.

B1.13 Browsers and speed. Unless your Proposal says otherwise, we support the current and previous major versions of Chrome, Edge, Firefox and Safari on desktop and mobile; small visual differences are normal. We aim for fast pages and strong Google speed test scores, but scores are aims, not promises.

B2. Hosting

B2.1 Your Proposal states the Hosting Tier for each website and System. We are happy to host wherever suits you: on our hosting, with a provider or data centre you prefer (for example AWS, Microsoft Azure or Google Cloud), or on your own servers. We agree the provider and location with you before we set it up, taking account of your preferences and any policies your group has, and record them in your Proposal or Security Pack. The data your website or System holds stays in the UK unless we both agree another location in writing, with the safeguards in Schedule 3, paragraph 8. Any difference in cost is agreed with you first.

B2.2 The four tiers.

  • Shared Hosting. For most websites, shared cloud hosting provided by GURU (GURU Cloud, guru.co.uk), which we manage for you as a reseller.
  • Platform Hosting. For hubs, Team App Plans and other Systems on our platform: hosting we arrange and look after for our hubs and apps, with a provider named in your Proposal or Security Pack, separate from the server most of our websites use, with each client’s hub or app kept separate from other clients’ (as your Security Pack describes) and behind Cloudflare where your Proposal or Security Pack says so, the data it holds stored in UK data centres unless your Proposal says otherwise, and each client’s data kept separate. Where a project needs more, we move it to Dedicated Hosting or Client Hosting. Your Proposal or Security Pack names the provider and server and says how backups work.
  • Dedicated Hosting. For larger projects, a server used only for your Systems (either a physical server, or a virtual server whose operating system, storage and database are not shared with any other client), with a dedicated IP address where useful, in a UK data centre or a UK region of a major cloud provider such as Amazon Web Services (AWS), Microsoft Azure or Google Cloud, managed by Think Mad, with the enhanced security in Schedule 2, Section B. Your Proposal or Security Pack names the provider and data centre and says whether the server is physical or virtual.
  • Client Hosting. We install and manage your System on infrastructure owned by you or your group: either your own cloud account (for example AWS, Microsoft Azure or Google Cloud) in a UK region, or your own servers, in your premises or your data centre. The enhanced security in Schedule 2, Section B applies to the parts we manage.

B2.3 Shared Hosting is included with a marketing Plan where your Proposal says so. Otherwise, hosting and support are provided as a Plan at the price in your Proposal or our Rate Card, including the support time stated there.

B2.4 Shared Hosting: what to expect.

  • Availability. Where your Plan includes monitoring, we monitor your website and act quickly if it goes down. GURU’s published service targets are GURU’s, not our promise, and we do not promise uninterrupted service.
  • Backups. Your Plan or Proposal states how often we back up, where, for how long, and how we restore. Where it does not, we rely on GURU’s automatic backups, which GURU does not guarantee to us, so please keep your own copy of your content. We give you a full copy of your website files and database on request.
  • Fair use. Shared Hosting is for a normal business website. GURU’s acceptable use rules apply to it, and we send you a copy on request; in short, no unlawful, infringing or offensive material, no spam or bulk email, and no use that overloads the server. Marketing email goes through an email service provider, never the web server.
  • Updates and malware. Updates are our job only where your Care Plan includes them. If your site runs software that its maker no longer supports, such as an old PHP version, we tell you within 30 days of finding it and propose a plan to move it, under your Care Plan or as a Change you approve. If no plan is agreed within 30 days, we may move the site to a separate hosting account to protect other sites, and we are not responsible for a Security Incident caused by that software unless updating it was our job. If your site is hacked, we may suspend it under clause 18.5 while we fix it. Clean-up is free if it came from something we were responsible for, such as a missed update under your Care Plan; otherwise it is charged at the Hourly Rate, and we tell you the expected cost first where we can.

B2.5 Platform Hosting: what to expect. Where your Plan includes monitoring, we monitor your System and report availability under Schedule 1. Updates follow Schedule 2, Section A, and where clause B5.5 applies, your System also has the measures in Schedule 2, Section B, paragraphs 3 to 9.

B2.6 Dedicated Hosting: what to expect. Your data, including backups, is stored in the UK unless your Proposal says otherwise. We manage the server, its security, monitoring and backups under Schedule 2, Section B, and availability and support follow Schedule 1. If your use ever needs a bigger server, we show you the figures and agree any extra cost in writing first. IP addresses belong to the hosting provider and stay with the server when you leave. A dedicated IP address helps with things like allowlisting, but does not by itself make a site more secure or rank better.

B2.7 Client Hosting: who does what. You (or your group) own the account or servers and keep control of the owner and billing logins. We work through named administrator accounts with two-step sign-in, which your IT team can review or remove at any time, with our actions logged where the provider allows. We are responsible for the setup, configuration, updates, monitoring, backups and security we manage inside the account, as your Proposal describes. You are responsible for the provider’s terms, account settings we do not manage, and changes made by your team or other suppliers. On your own servers, you are also responsible for the hardware, power, network, firewall, physical security and operating system updates, unless your Proposal says we manage them, and for giving us secure remote access; downtime caused by those things does not count against our availability aim or exit (Schedule 1, paragraphs 7 and 8). If our access is reduced so we cannot do that work, the related service levels pause until it is restored. Who pays the provider’s bills, and any change to our fee, is set in your Proposal or agreed in writing before the move.

B2.8 Maintenance and the end of hosting. Planned maintenance follows Schedule 1. When hosting ends, Schedule 4 applies, and we never charge a release fee.

B2.9 Changing provider. We may change our hosting provider or plan, keeping your service at least as good. Where the hosting holds personal data for you, for example website form entries, orders or user accounts, a change of provider follows the Sub-processor process in Schedule 3, paragraph 7, whatever the Hosting Tier.

B3. Domains and email

B3.1 Your domains are yours. Unless your Proposal says otherwise, we register domains with you as the legal registrant (owner), and we manage renewals and DNS as your agent.

B3.2 Renewals are invoiced each year at the price in your Proposal or our Rate Card, shown on your invoice. We remind you before each one and aim never to miss one, but are not responsible if a domain lapses because its renewal invoice was not paid after our reminder.

B3.3 No release or transfer fees, ever. Once we have confirmed a request under clause 15.3, we provide your domain’s transfer code or, for a .uk domain, change its tag to your new registrar, within 2 Working Days, free, and never hold it back for payment.

B3.4 If a domain you want is not available, we suggest a close alternative and always ask before registering it.

B3.5 DNS. We will not change your DNS records without telling you, except for urgent security work. If your domain is managed elsewhere, we send you the exact records to change.

B3.6 Email. Business email is provided as your Proposal says, ideally through Microsoft 365 or Google Workspace in your own account, with mailbox sizes and fair use as stated. Mailboxes must not be used for bulk or marketing email. You are responsible for mailbox passwords and two-step sign-in. Archiving and legal hold are not included unless stated. When you leave, we help you export your mailboxes.

B3.7 Where your Proposal includes it, we set up SPF, DKIM and DMARC email authentication on domains we manage.

B3.8 SSL. Standard certificates are included with our hosting and set to renew automatically, and where we monitor your site we act if one fails to renew. A paid certificate is a third-party cost and may need your help to validate.

B4. SEO, digital marketing, advertising and social media

B4.1 Scope. Your Proposal sets out the work, which may include search and keyword research, on-page optimisation, structured data, content, rank and AI visibility tracking, reporting, link research, Google Business Profile management, paid advertising, social media, email marketing, influencer work and prospect research. Clause 5.3 applies: we promise the work, not the results.

B4.2 Keywords. If you have not given us target keywords or focus areas within 21 Working Days of our asking, we may choose a set we reasonably think suits your business and location, and tell you.

B4.3 Links and paid placements. We tell you which opportunities are paid, what they cost and who receives the money, and you approve and pay for each one. We only arrange a paid placement where the host site agrees to label it clearly as advertising (for example “Advertisement feature” or “#ad”) where you or we control the content, or as sponsored where you only paid for it to appear, and to mark its link rel=“sponsored”; we check it once it is live and ask the host to fix or remove it if not. We never use link networks, link farms, automated link schemes or undisclosed paid links. We keep a log of every link we arrange and give you a copy whenever you ask and when our work ends. If a search engine acts against your site because of a link we placed in breach of this clause, we help remove or disavow it free.

B4.4 Reviews. We never write, buy or post fake reviews, reward positive reviews, hide genuine negative ones, or “gate” reviews by asking only happy customers. If we help you ask for reviews, we ask all your customers or a fair sample, and any incentive is disclosed and never depends on a positive review. For Google reviews we offer no incentive at all, because Google does not allow them. Testimonials you give us must be genuine, current and used with permission. If a website or System we build shows reviews, you are the publisher and responsible for your review policy.

B4.5 Influencer and creator content. Where included, our briefs require a clear label such as “#ad” at the start (“sponsored” or “spon” is not enough), we never ask anyone to review a product they have not used, and you will not ask anyone to hide the relationship.

B4.6 Paid advertising. Ad accounts are in your name, with us added to manage them. You pay the platforms directly for ad spend; our management fee is separate. If we pay a platform for you, we recharge it under clause 10.2. We set campaigns so monthly spend stays within the budget you approve, allowing for the platforms’ own daily variation. Platforms can reject ads or restrict accounts; we follow their published policies, and you are responsible for the truth of claims in your ads and landing pages. When we stop working together, you keep the accounts, campaigns, audiences and history, and we remove our access.

B4.7 Google Business Profile. Your Business Profile is free and belongs to you. You stay the owner and we are a manager. Our fee for managing it is separate and shown on your invoice. We reply to reviews only with your written agreement. If you ask, we hand back full control and remove our access under clause 15.3, whether or not any invoice is outstanding.

B4.8 Social media accounts. Your accounts, pages, followers and ad accounts are yours. Any we set up are in your business’s name with you as owner from day one. We use role access wherever the platform offers it (otherwise we agree in writing how we sign in, and keep the password in our password manager), and at least one of your people keeps admin rights.

B4.9 Social media management. The number of profiles, channels and posts is set in your Proposal. Our scheduling dashboard, unified inbox and other tools (our own, or licensed to us) are available while your Plan is active, unless they are part of your System, so please export anything you want to keep before it ends; published content stays on your accounts. We reply to comments and messages only where your Plan includes it, in Support Hours, and pass complaints, legal matters, safeguarding issues and press enquiries straight to you. We are not liable for platform changes, outages, restrictions, removals or suspensions unless our breach caused them.

B4.10 Approving content. Social posts, adverts, emails and other marketing are never published without your approval, which can be a standing written approval of a content plan or of routine posts, and we keep a record of each approval. Adverts, prices, offers and regulated content always need your clear yes. Unapproved items are held and move to the next month once; items still unapproved after that lapse. Your monthly fee is payable whether or not you approve content in time, and the time we spent preparing held items counts as used.

B4.11 Who owns marketing content. Content we create for you, such as posts, graphics, copy and emails, becomes yours once the month or work it relates to is paid for, subject to clauses B4.13 and 14.6.

B4.12 Email and SMS marketing. You are the controller and instigate the messages. PECR can apply to both of us where we send them, so we only send to lists that meet this clause. You confirm that everyone on your lists has agreed to hear from you or the soft opt-in applies, and that you have checked for sole traders and partnerships, who may count as individuals (clause B4.15(h)). Every message carries your identity and a working unsubscribe (one-click for email, which large email providers require). We never use bought or rented lists, we apply your suppression lists, and we send through a proper email service provider from your own domain, authenticated where clause B3.7 applies. You are responsible for the lawfulness of lists you supply; we are responsible for running the controls we have agreed to run.

B4.13 Stock images. We choose stock licences that let you keep using the work we created for you after our work ends, and we tell you if a use needs your own licence (such as large print runs or merchandise). We never use stock images in logos or trade marks, and we give you a list of the stock assets used, with sources, on request and when our work ends.

B4.14 User content and AI images. Before we repost a customer’s photo, video or post, you confirm you have the creator’s permission and the consent of anyone identifiable in it. We never use AI to create images that misrepresent your products, results, premises or staff, and we label AI-generated people where viewers could otherwise be misled. For content aimed at people in the EU, we label deepfake images, audio and video as AI-generated in every case.

B4.15 Prospect research (lead generation support). Where your Proposal includes prospect research, this clause and Schedule 3 apply.

  1. We act as your processor. You are the controller and decide how the research is used. Your written instructions (the agreed sources, criteria and controls) are recorded in the impact assessment under paragraph (c), and we follow them. Each record is assigned to the people you name.

  2. We use only information in the public domain, such as company websites, Companies House, public business profiles and public social media viewed by a person, and registers and directories whose terms allow it, read one target at a time, and we may check and complete your own contact records from those sources. We do not crawl or bulk-copy directories or websites, never use bought lists, and never use tools that automate LinkedIn connections or messages. Any LinkedIn work is done by a person through your own Page and admin role, and is limited to reviewing, by hand, people who engage publicly with your own posts and Page, finding which roles exist at a company, and recording a link to a public profile; we do not copy content from LinkedIn profiles into your System.

  3. Before any research or outreach, we help you complete a legitimate interests assessment and a short data protection impact assessment for you (or your group) to approve, using your hours unless your Proposal includes it. Research and outreach start only once you (or your group) have approved them in writing. You can keep prospect research switched off.

  4. We research companies first. Named prospects are added only when someone is ready to approach them, and are contacted with the notice in paragraph (e), or deleted, within 28 days unless your Proposal states otherwise. Records about sole traders and partnerships (other than limited liability partnerships and partnerships in Scotland) identify individuals from the start, so they count as named prospects as soon as they are recorded. Scores use business criteria you agree, and a person decides who to contact.

  5. Every record shows its source and the date it was collected. Each person is given, in your name, the privacy information Article 14 of the UK GDPR requires, at the latest in the first message to them and in any case within 1 month of their details being recorded: including who you are, that the lawful basis is legitimate interests and what those interests are, where their details came from, who they are shared with (including us and our Sub-processors), how long they are kept, and their rights, with the right to object to direct marketing at any time stated clearly and separately, and the right to complain to you and to the Information Commission. The first message can give the key points and link to your full privacy notice. You approve the wording before any outreach starts.

  6. Your opt-out lists are loaded into a suppression list before any outreach, and anyone who opts out later is never added again. Opt-outs are applied across every Client Group company named in your Proposal.

  7. Before any sales calls, numbers are screened against the Telephone Preference Service and Corporate Telephone Preference Service (TPS and CTPS), by you or, if your Proposal says so, by us under our own subscription, refreshed at least every 28 days. Calls show a number the person can call back, and anyone who objects is added to the suppression list straight away.

  8. Sole traders, and partnerships other than limited liability partnerships and partnerships in Scotland, count as individuals under PECR. They receive marketing email or texts only with consent, or under the soft opt-in, which never applies to people who have not bought from you or asked about buying. If you are a registered charity, the charity soft opt-in in PECR may also apply to supporters who gave their details while showing interest in your charitable purposes. Marketing emails to companies and other corporate bodies always say who they are from and give a simple, free way to opt out.

  9. Research for you is used only for you. We never reuse it, or anything learned about the people in it, for another client or for our own marketing or prospecting, and we keep it only in your System or another place your Proposal names, apart from short-lived working copies in AI tools listed as Sub-processors, deleted under Schedule 3, paragraph 12.

  10. We record only business contact details: name, job title, work email, work phone, business address and links to public business profiles. We never record personal email addresses, personal or home phone numbers, home addresses, photographs, anything about a person’s private life, or special category data.

  11. A person checks each named prospect against its source before they are approached. Unless your Proposal sets another period, a named prospect who has not replied or become a customer within 6 months of first contact is deleted, keeping only what the suppression list needs.

B5. Apps, hubs, portals and software

B5.1 Scope. Your Proposal (and any agreed specification) describes the System, its phases, Users, roles, storage, integrations, Hosting Tier and support. Systems are web-based, need an internet connection and do not work offline unless your Proposal says so. A System does not replace professional sign-off, scheme approval or regulatory submissions: for example, forms based on industry model forms follow the version you approve, and you remain responsible for their content and sign-off. If your System is likely to be used by children, tell us before we start; the extra design and assessment work is a Change.

B5.2 Group companies. For any Service, your Proposal may name Client Group companies that may use it. You are responsible for them as if they were you, and their staff who sign in to a System count as Staff Users. Any other business needs its own Proposal.

B5.3 Group approval. Your Proposal may make the Agreement subject to your group approving our hosting or security. If, within the period your Proposal states (45 days from the Start Date unless stated otherwise), your group confirms in writing that it will not approve them, giving reasons that relate to our hosting, security or data protection, we have 14 Working Days (or the period in your Proposal) to resolve those reasons, for example by agreeing to move to Client Hosting. The reasons count as resolved if we make a written offer that meets them and your group does not explain in writing, within those 14 Working Days, why it does not. If by the end of the approval period your group has neither approved nor refused in writing, either of us may extend it once by up to 30 days by written notice. If there is still no written approval at the end of that period (or any extension), your group is treated as having refused, and the 14 Working Days above start then, to resolve any concerns it has raised. If the reasons are not resolved, either of us may end the Agreement by written notice. Fees paid or due before that notice remain payable and are not refunded, nothing further is owed by either of us, and we return your data and then delete it under Schedules 3 and 4.

B5.4 Data before approval. Your Proposal may say which data goes into a System before your group approves it (for example test data and limited staff details). We keep all other Client Data out until you or your group approve it in writing.

B5.5 Systems that hold your customers’ data. A System that Customer Users sign in to, or that holds price lists or personal data beyond your staff’s names, work contact details and roles, always has the measures in Schedule 2, Section B, paragraphs 3 to 9, whatever its Hosting Tier. It does not run on Shared Hosting unless your Proposal says so and explains how those measures are met.

B5.6 Users and roles are as your Proposal states. One person per login, never shared. View-only and extra Users are priced as your Proposal says. Our own support access is logged and you can remove it; if you do, the targets in Schedule 1 and our duty to fix Faults pause until access is restored.

B5.7 Fair use and storage. “Unlimited” means fair use within the storage, email, request and other limits in your Proposal. Unless your Proposal says otherwise, a System includes 10GB of storage for documents and uploads. If use goes well beyond those limits, or a bigger server is needed, we show you the figures and propose the extra cost in writing. If we cannot agree within 30 days, we may limit use to the stated limits (for example, pausing new uploads above your storage) after 14 days’ further notice, or either of us may end the affected Service without any early exit charge.

B5.8 Your Users and customers. Your System is your service to your staff and customers. You are responsible for: the terms and privacy notice your Users agree to, in place before go-live (we can provide template portal terms and privacy wording, using your hours); deciding who has access, and removing leavers or asking us to (we do it within one Working Day); first-line help for your customers; and the accuracy of data your Users enter. Quotes and sales made through your System are on your own terms of sale, and we are not a party to them; your terms of sale should let you correct obvious price errors, and we tell you about any we notice. Help we give your customers uses your hours. We may redirect your Customer Users’ requests to you, and the targets in Schedule 1 apply to requests from your named contacts and administrators.

B5.9 Acceptable use. Schedule 5 applies to all Users, and you make it part of your terms with them. We may suspend a single User account that breaches Schedule 5 or threatens security, and tell you promptly.

B5.10 Acceptance follows clause 9. Where clause B5.5 applies, our own security testing under Schedule 2, Section B is part of the checklist before Customer Users can sign in.

B5.11 Releases. We test changes before release, back up before each release where Schedule 2, Section B applies, and use a separate test environment where your Proposal includes one. We give at least 2 Working Days’ notice of a release that changes how Users or data are handled; others may go out at any time.

B5.12 Browsers and devices. As clause B1.13, plus the iOS and Android versions still receiving security updates from Apple and Google, unless your Proposal says otherwise.

B5.13 Ownership.

  1. From day one, your Client Data, Client Materials and domain are yours.

  2. The Ownership Date is the date your Proposal states, or the date on which a condition your Proposal sets for ownership is met (for example, “once the first 12 months are paid” means the day after the first 12 months end, once the fees for them have been paid in full). If your Proposal states none, there is no Ownership Date: you use the System under licence for as long as the Agreement continues, and when it ends you receive your data and exit pack under Schedule 4, but not the code.

  3. On the Ownership Date we assign to you, with full title guarantee, all intellectual property in the Client-Specific Work in your System, and within 10 Working Days give you its complete Source Code, including the Platform Components it uses and, where their licences allow, its Third-Party Components, together with its setup documentation. Passwords and other secrets needed to run the System are handed over separately and securely on request, and in any case under Schedule 4, paragraph 7 when the Agreement ends. Your licence to the Platform Components under clause 14.3 applies from then.

  4. Owning your System in full means you own the Client-Specific Work outright and hold a permanent licence to the Platform Components in it, which together let you use, copy, change and have anyone maintain the whole System without us, for your own business.

  5. Before the Ownership Date, you and your Users have a non-exclusive licence to use the System for your business during the Agreement and any continued-service period. If the Agreement ends before the Ownership Date, that licence ends then and the code does not pass to you, unless your Proposal says otherwise or paragraph (f) or clause B5.14 applies. You still receive your data and exit pack under Schedule 4.

  6. If, before the Ownership Date, you end the Agreement under clause 13.1 because of our material breach or insolvency, we stop trading, or we end the Agreement at a Review Point or on notice under clause 12.2, the Ownership Date is brought forward to the end date, once you have paid the fees due up to then. If you end it under clause 13.2, you may bring the Ownership Date forward by paying, within 30 days of the end date, the monthly fees that would have been due up to the Ownership Date. Otherwise, this paragraph does not apply when the Agreement ends at a Review Point or under clause B5.3, or where your Proposal states no Ownership Date.

  7. Systems on our platform. The Team App range, and other Systems your Proposal describes as running on our platform, are provided under licence for the term, with no Ownership Date unless your Proposal states one. Your content, forms, settings and Client Data are included in your exit pack in a format you can use elsewhere.

B5.14 Code deposit and escrow. Where your Proposal includes a code deposit, from go-live until the Ownership Date we place the current Source Code and build notes for your System (without passwords or other secrets) in a private repository you control, at least monthly, and tell you each time we update it. You may use it only if: (a) any event in clause 13.1(b) happens to us, or we stop trading; (b) we fail to fix or work around a Fault with Critical priority within 10 Working Days of your written notice (or the time in your Proposal); or (c) we stop providing the Services for 10 Working Days or more in breach of the Agreement, other than a suspension under clause 10.7 or 18.5. If we dispute (b) or (c) in good faith, either of us may refer it to an expert under clause 25.4, who should decide within 10 Working Days, and the code may be used only if the expert finds the event has happened. You may then use, copy and change that code, and have another developer maintain it, to keep your System running for your own business, with its Platform Components licensed under clause 14.3. Once a year you may have a developer check, at your cost, that the deposit builds. If the Agreement ends before the Ownership Date with no release event, and clause B5.13(f) does not apply, you delete the deposited code within 10 Working Days and confirm this in writing. Formal escrow with an escrow provider is available at your cost.

B5.15 Third-party services. Some features rely on other companies’ services, such as maps, payments, SMS, accounting links or AI, which your Proposal lists. Usage charges are paid by you directly or recharged under clause 10.2. If a provider raises its prices, we give you at least 30 days’ written notice (or as much notice as the provider gives us, if that is less) and the new cost applies from then. If you do not want to pay it, you may switch that feature off, or move it to your own account with that provider, without penalty. If a provider changes or withdraws something your System relies on, we tell you, explain the options and agree any work first. Card payments go through a provider you approve, and we never hold card details.

B5.16 Your own systems. Where your System links to your own systems (such as accounting software), you are responsible for those systems and for their suppliers’ help, access and costs. No link is added without your decision-maker’s approval under clause 7.5.

B5.17 App stores. Store-listed apps are published in your business’s name from your own Apple and Google developer accounts, which need a D-U-N-S number for your business. You pay the stores’ fees and accept their terms, and we are added to your accounts to build, test and submit releases. We draft store listings and privacy details for you to approve. Stores can delay or refuse a release; we fix any issue from our work but cannot control their decisions. Store rule changes after launch that need app changes are Changes unless your Proposal includes them. Apps that let people create an account also let them delete it in the app and, for Google Play, through a web link.

B5.18 Online safety. If your System lets users post content or message each other, and you decide who can use it, you are normally the provider under the Online Safety Act 2023 and responsible for the risk assessments, reporting tools and moderation it requires, unless an exemption applies (for example tools used only internally by your business). For Systems on our platform where we control access, your Proposal confirms who is the provider. We build the safety features we agree, under your Proposal or at the Hourly Rate.

B5.19 Accessibility. Where your Proposal says so, we aim for WCAG 2.2 level AA in the parts we build, on the same basis as clause B1.11.

B6. Support and changes

B6.1 What support covers. Fixing Faults (free, as clause 8 says), quick “how do I” questions, and the help your Plan or Proposal includes. Changes use your hours or are quoted first (clause 7).

B6.2 How to ask. Through your System’s support area where it has one, by email to projects@thinkmad.co.uk, or on 0151 316 0110 in Support Hours. Response targets are in Schedule 1.

B6.3 Website Care Plans. A Care Plan is a Plan under which we look after your website. Your Plan or Proposal states what it includes, such as updates, monitoring, backups, small changes and support time. Unused support time does not roll over unless it says so. If you have hosting only, updates are your responsibility unless your Proposal says otherwise.

B6.4 Updates. We apply the updates we are responsible for, at the times in Schedule 2, Section A, paragraph 5 and your Care Plan. If an update risks breaking something, we may hold it back briefly while we test, and tell you.

B6.5 Training and calls. Go-live training is as your Proposal states. Demo and review calls are on request; those your Plan or Proposal includes do not use your hours, and others do, as does later training.

Schedule 1: Service levels and support

  1. How this works. Your Proposal sets your support targets, availability aim and any exit threshold. Where it is silent, these defaults apply.

  2. Support Hours are as defined in clause 2.1. Outside them, we provide only the weekend critical cover in paragraph 6A where your Proposal includes it, and no overnight or 24/7 support unless your Proposal says so; the times for telling you about a Security Incident in Schedule 3, paragraph 9 still run in clock hours.

  3. Default targets for Systems on Dedicated or Client Hosting, and any System whose Proposal applies this paragraph.

Priority For example First response Target to fix or work around
Critical System or website down; Staff Users cannot sign in; wrong prices showing to customers; suspected Security Incident 1 Working Hour Worked on continuously in Support Hours, with updates every 2 Working Hours
High A key function broken for some Users 4 Working Hours 2 Working Days
Normal A Fault with a workaround, or a question Next Working Day 10 Working Days; Changes scheduled in your hours
  1. Default targets for everything else (including Systems on Platform Hosting, websites, hosting, marketing and social media).
Priority For example First response Target to fix or work around
Critical System or website down; no Staff User can sign in; suspected hack or Security Incident 4 Working Hours Worked on in Support Hours until fixed or worked around, with updates at least daily
Normal Anything else Next Working Day 10 Working Days for Faults; Changes scheduled in your hours

On Shared Hosting, some fixes depend on GURU.

  1. What the targets mean. A first response means a person has acknowledged your request, set its priority and started work. Fix targets are aims, and the first step may be a workaround. You suggest a priority, and we agree it with you or explain any change.

  2. Out of hours. Where your Plan includes monitoring, automatic alerts reach our team. Where your Proposal offers an out-of-hours response, we use reasonable endeavours to respond to Critical alerts outside Support Hours; this is not a committed response time unless your Proposal states one. Otherwise, we pick them up at the start of the next Support Hours.

6A. Weekend critical cover. Where your Proposal includes it, we are available from 8:00 to 20:00 on Saturdays, Sundays and bank holidays for Critical issues only: for example your website, System or portal is down, staff cannot sign in, wrong prices are showing, or you suspect a hack or breach. You contact us by phone on the number in your Proposal or that we give you at kick-off, and through the hub where your System has one. We aim to respond and start work as quickly as we can, but we do not commit to a response or fix time, and these hours are not Support Hours for paragraphs 3, 4 and 8. Weekend work on a Fault, or on anything we are responsible for, is included. Weekend work on anything caused by you, your Users or a third party we do not manage uses your included hours or is charged at the Hourly Rate, and we tell you before we start if it will.

  1. Availability aim. For Systems on Dedicated or Client Hosting, our availability aim is the figure in your Proposal, or 99.5% each calendar month if none is stated. For Systems on Platform Hosting, where your Plan includes monitoring, we monitor and report availability, and there is no aim or exit threshold unless your Proposal sets one. Your Proposal or Security Pack states how often our monitoring checks. A System is unavailable when it cannot be reached, Users cannot sign in, or a key function fails for all Users. Not counted: planned maintenance under paragraph 9; emergency security work to protect you, which we tell you about; causes on your side or from your Users or other suppliers; third-party services you chose; provider account outages under Client Hosting; and events under clause 23. Where we monitor availability, we report it monthly. Websites on Shared Hosting have no availability figure; where your Plan includes monitoring, we monitor them and act quickly.

  2. Availability exit. If availability is below the exit threshold in your Proposal (or, for Systems on Dedicated or Client Hosting where your Proposal sets none, below 99%) in 2 calendar months running, you may end the Agreement or the affected Service on 30 days’ written notice, without any early exit charge, given within 30 days after the end of the second month. For this paragraph only, unless your Proposal includes an out-of-hours response with a committed response time, time when the System is unavailable outside Support Hours counts only from the start of the next Support Hours; every minute still counts towards the aim we report. Within 10 Working Days after the end of the first month below the threshold, we send you a written plan to fix the cause.

  3. Planned maintenance and releases. We give at least 2 Working Days’ notice of planned maintenance on Systems on Platform, Dedicated or Client Hosting, and do it outside 8:00 to 18:00 on weekdays, unless your Proposal sets other maintenance windows. Releases expected to cause less than 10 minutes’ interruption may take place at any time, and need notice only if they change how Users or data are handled (clause B5.11). On Shared Hosting, GURU may carry out its own maintenance, and we pass on any notice we receive.

  4. Service credits. None, unless your Proposal adds them.

  5. Reporting. For Systems and Plans with included hours, each month we report on availability (where we monitor it), support requests and hours used.

Schedule 2: Security

Section A: Baseline measures for every Service

  1. Named logins. Our people use their own named logins to access your systems. Where a platform needs a shared or service account (for example the account our website tools connect through), only named staff can use it, its use is logged where the platform allows, and its password is kept in our password manager.

  2. Two-step sign-in. Our administrator access to Systems, and to servers and cloud accounts we manage under Platform, Dedicated or Client Hosting, uses two-step sign-in.

  3. Least privilege. Our people and contractors get only the access they need. For Systems, and for servers and cloud accounts we manage, we review who has access at least every 3 months and keep a record of each review. We remove access when it is no longer needed (for contractors, within one Working Day of their work ending, as clause 20.4 says), and on the day someone leaves our team, including their accounts, keys and tokens, and we change any shared secret they knew.

  4. Passwords. We keep login details secure and never send passwords by ordinary email or chat. Where a platform allows, you give us access by role-based invitation rather than a shared password.

  5. Updates. For Systems, and for the servers and hosting accounts that run them under Platform, Dedicated or Client Hosting, we apply security updates that the maker rates as critical or high risk within 14 days of their release (sooner if the weakness is being actively exploited), and other security updates within 30 days, as far as the hosting provider lets us; the software that runs your System is a version its maker still supports with security updates. For websites, updates are applied as your Care Plan states, and unsupported software is dealt with under clause B2.4.

  6. Encryption in transit. Websites and Systems we host use HTTPS (TLS), and we provide secure routes for Client Data to reach us (clause 16.6).

  7. Secure development. We develop with the OWASP Top 10 in mind. A person reviews changes before release. We keep secrets out of code, keep dependencies updated and checked for known weaknesses, and develop with test data wherever possible. AI coding assistants are used under clause 19.

  8. Logging. Systems log sign-ins, administrator actions (including ours) and key data changes, with the time and the account used. Your Proposal says what you can see.

  9. Separation. Each client’s website has its own database, and new client websites get their own hosting account. Each System keeps your Client Data separate from other clients’ data, with its own database or with separation checked on every request, and where Customer Users see their own data, we test that one customer cannot see another’s. Our own business systems, such as email and file storage, hold Client Data only where needed for the Services, with access limited to the people working for you.

  10. Users. We remove a User from a System within one Working Day of your request.

  11. Incidents. We keep an incident response process and notify you under Schedule 3, paragraph 9.

  12. People and concerns. Our people are covered by clause 24.2. Anyone can report a security concern to projects@thinkmad.co.uk, and we look into it promptly.

Section B: Enhanced measures (paragraphs 1 to 9 for Dedicated and Client Hosting and wherever your Proposal or Security Pack says they apply; paragraphs 3 to 9 for every other System under clause B5.5)

  1. A server used only for your Systems in a UK data centre or UK cloud region (physical or virtual, as clause B2.2 describes) or, under Client Hosting, your own UK cloud account or servers, with the provider named in your Security Pack, and Client Data, including backups, stored in the UK.

  2. Cloudflare, or the equivalent named in your Security Pack, in front as a web application firewall and to filter attacks.

  3. Two-step sign-in for all Staff Users; server-side checks of the User’s role on every page and action; and Customer User sign-in by invitation only, with password rules, lockout and single-use reset links.

  4. Daily backups, encrypted and held off the server in the UK for 30 days, under separate login details so that someone who takes control of the server cannot change or delete them. A full restore is tested before Customer Users can sign in (or before go-live, for a System without Customer Users) and every 6 months after, and we keep a record of each test. A backup is taken before every release.

  5. An audit log you can see, covering sign-ins, price changes, approvals and exports, kept for at least 12 months and included in the off-server backups, with automatic monitoring alerting our team.

  6. Before Customer Users can sign in (or before go-live, for a System without Customer Users), our team tests the System against the OWASP Top 10 and the OWASP Application Security Verification Standard (ASVS) Level 1 requirements that apply to it, in the version named in your Security Pack, recording each as met, not met or not applicable, with scanning and manual tests of sign-in, roles and data separation, including one customer trying to reach another’s data. We fix every high and critical finding before launch, and medium findings within 30 days or a time we agree with you. We send you a summary report and test again after major changes. This is our own testing, not an independent penetration test.

  7. Your data and backups are encrypted at rest. Our aim is to restore the System from backup within one Working Day of a serious failure, or the time in your Proposal; this is an aim, not a promise. Data entered since the last backup (up to 24 hours) could be lost in a serious failure. Other measures are as described in your Security Pack.

  8. Your setup documented (server, accounts, domain records and recovery steps) with a copy for your IT contact, and more than one of our people able to support your System.

  9. Security updates for the System, its server and the software on it: those the maker rates critical or high risk within 14 days of release, and sooner if the weakness is being actively exploited; all others within 30 days of release; with a backup before each one.

Section C: Certifications, and what we do not claim

  1. Our current certifications, if any, and their dates are in the Security Pack; clause 18.2 covers targets.

  2. Unless your Proposal or Security Pack says otherwise, we do not hold ISO 27001 certification, we hold only the Cyber Essentials certificates named in the Security Pack, and our own testing is not an independent penetration test. Data centre certifications are the provider’s own. Systems do not work offline, and we do not promise uninterrupted service. Where something is a target rather than a guarantee, we say so.

Section D: The Security Pack

  1. Your Security Pack sets out how we meet this Schedule for you, including providers, locations, Sub-processors, AI tools, backup and recovery details and our policies. Clause 4.5 governs updates to it.

  2. Unless your Proposal says otherwise, we answer your group’s security questions free until Customer Users can first sign in (or until go-live, for a System without Customer Users), up to 8 hours including one call with your IT team, and one security questionnaire a year after that. Further questions use your hours or are charged at the Hourly Rate.

Schedule 3: Data Processing Agreement

  1. Roles. This Schedule applies where we process personal data for you. You are the controller and we are your processor. Terms such as “personal data”, “processing” and “personal data breach” have their UK GDPR meanings. This Schedule reflects Article 28 of the UK GDPR. If a Client Group company is subject to the EU GDPR, this Schedule applies to its personal data as if references to the UK GDPR included the EU GDPR.

  2. Particulars. Subject matter: providing the Services. Duration: the Agreement, plus the time needed to carry out Schedule 4. Your Proposal or Security Pack may add detail.

Service Nature and purpose People Types of personal data
Websites and hosting Building, hosting and maintaining websites; forms; analytics Visitors, enquirers Contact details, enquiry content, IP addresses, analytics and cookie identifiers; special category data (such as health information in a clinic’s enquiry form) only where your Proposal says so
Marketing, social, email and ads Creating and scheduling content; social inboxes; email; ad audiences; reporting Customers, prospects, subscribers, followers Contact details, social handles and messages, engagement and analytics data
Systems Building, hosting and supporting Systems; data import; reporting Staff Users, Customer Users, customer contacts, prospects, enquirers Business contact details, sign-in and audit data, lists, quotes, orders, notes, enquiries, marketing engagement; special category data only where your Proposal says so, after an impact assessment
Prospect research Researching businesses from public sources; scoring; preparing outreach (clause B4.15) Prospects, including sole traders and partners Names, job titles, business contact details, public profile links, source and date
  1. Instructions and our own purposes. We process personal data only on your documented instructions (the Agreement and your written instructions), including on transfers outside the UK, unless the law requires otherwise, in which case we tell you first unless the law forbids it. We tell you straight away if we think an instruction breaks Data Protection Law. We do not use your personal data or other Client Data for our own purposes, including our own marketing or prospecting, benchmarking, product improvement or training AI models. We may use anonymous technical measurements, such as server load and error rates, to run and improve the Services.

  2. Requests from public authorities. If a court, regulator, police force or other public authority asks us for your personal data, we tell you straight away unless the law forbids it, disclose only what the law requires, and ask the authority to come to you first where we lawfully can.

  3. Confidentiality. Everyone we allow to process personal data is under a written duty of confidentiality.

  4. Security. Our measures under Article 32 of the UK GDPR are those in Schedule 2 and your Security Pack.

  5. Sub-processors.

7.1 You give general written authorisation for the Sub-processors in the list attached to your Proposal or Security Pack, or sent to you, with a version number and date. The list says what each Sub-processor does, what personal data it sees, where it processes it, the transfer safeguard it relies on, and any of its own sub-processors that process your data outside the UK. It may include hosting and backup providers, Cloudflare, email sending services, social scheduling and inbox tools, AI services (including Anthropic, which provides Claude), email verification services and contractors with access to personal data.

7.2 Where your Proposal says Sub-processors need your written authorisation, you approve the list before go-live, and we add or replace a Sub-processor only with your written authorisation, which you will not unreasonably withhold or delay. We ask at least 30 days ahead (or as clause 20.3 says for individual contractors), except in an emergency under paragraph 7.4 or urgent cover under clause 20.3.

7.3 Otherwise, we give you at least 30 days’ written notice before adding or replacing a Sub-processor (or the notice in clause 20.3 for individual contractors), saying who it is, what it will do, what personal data it will see, where it will process that data and the transfer safeguard it relies on. You may object on reasonable data protection grounds within that time. We will not let the new Sub-processor process your personal data until the notice period has ended or, if you object, until your objection is resolved. If we cannot offer a reasonable alternative within 30 days of your objection, you may end the affected Service without penalty, and we refund Plan fees paid in advance for the period after it ends.

7.4 If a Sub-processor fails or stops serving us without warning, and we must replace it to keep your Services running, we may move your personal data to a replacement before the notice period ends, but only to a provider that gives at least the same protection and processes the data in the same country or under the same transfer safeguard. We tell you in writing before the move or, if that is impossible, within 2 Working Days after it, and you keep the same right to object and the same remedy.

7.5 Before a Sub-processor processes your personal data, we put in place a written contract that imposes the obligations required by Article 28(3) of the UK GDPR, including security measures suited to the data it sees, and requires it to tell us promptly of any personal data breach. Where a Sub-processor offers only its standard terms, as large hosting, network and AI providers do, we check that those terms meet this standard before we use it, and record any difference that matters to you (such as its breach notice time, audit rights or data location) in the Sub-processor list. We remain fully responsible to you for each Sub-processor’s performance of its data protection obligations.

7.6 Google and other tools held in your own accounts are your processors, not our Sub-processors.

  1. Transfers. For Systems on Platform, Dedicated or Client Hosting, Client Data, including backups, is stored in the UK unless your Proposal says otherwise. For other Services, the Sub-processor list states where each provider stores your data. We transfer personal data outside the UK only to listed Sub-processors, each with its location and safeguard: UK adequacy regulations (data bridges, including the UK Extension to the EU-US Data Privacy Framework, where we have checked the provider is certified for UK data), or the International Data Transfer Agreement (IDTA) or UK Addendum to the EU Standard Contractual Clauses, after assessing that the protection is not materially lower than in the UK. For each US provider relying on the UK Extension, the Sub-processor list names the fallback safeguard. There is no other transfer without your written authorisation. Our employees access your personal data from the UK; if one needs to do so from outside the UK, for example for urgent support while travelling, they use only company-approved devices with two-step sign-in. If a safeguard stops being valid, we tell you within 5 Working Days and move to another lawful safeguard or stop the transfer.

  2. Breaches and Security Incidents.

9.1 We tell your named contacts, your decision-maker and any group or legal contact in your Proposal, by phone and email, without undue delay and in any case within 24 hours for Systems and for Dedicated or Client Hosting, and within 48 hours for other Services, of becoming aware of a personal data breach or Security Incident, unless your Proposal sets a shorter time. These times are clock hours and include evenings, weekends and bank holidays. We are aware when any of our people or contractors knows of it, or a Sub-processor tells us. Security alerts from our monitoring reach a named person at all times so that we can meet these times. This is not out-of-hours support: fixing work follows Schedule 1.

9.2 We tell you what happened, the data and people affected (approximate numbers are fine), the likely consequences, what we have done and propose to do, and who to contact, in stages if we do not yet know everything.

9.3 We update you at least daily until the incident is closed, and send a written report of the cause and what we changed within 10 Working Days of closing it.

9.4 We help you meet your duties to notify the Information Commission (where required, within 72 hours of you becoming aware, where feasible) and affected people, but do not notify them for you unless you ask or the law requires. Telling you about an incident is not an admission of fault. Our insurers and the incident response specialists they appoint may take part in the investigation.

9.5 We keep logs and other evidence of a Security Incident for at least 12 months, give you or investigators you appoint reasonable access to them, and make no public statement naming you or your customers about it without your agreement, unless the law requires it. Incidents at a Sub-processor that affect your data are covered by this paragraph 9.

  1. Help we give you. We pass on to you within 2 Working Days any request, objection or complaint from an individual about their personal data, including a complaint under section 164A of the Data Protection Act 2018, and do not answer it ourselves except to acknowledge it, unless you ask us to. Where a System holds the data, it lets you find, export, correct and delete a person’s data, or we do it for you within 5 Working Days of your request. Our searches for a person’s data are reasonable and proportionate, and we tell you promptly if we need clarification so you can pause the time limit. We help with data protection impact assessments, legitimate interests assessments, consultation with the Information Commission, and your duties under Articles 32 to 36 of the UK GDPR. This help is free for routine matters; large or unusual requests not caused by our breach are charged at the Hourly Rate, agreed with you first.

  2. Information and audits. We give you the information needed to show we comply with Article 28 of the UK GDPR, this Schedule, Schedule 2 and your Security Pack. You, or an auditor you appoint (including your group’s internal audit team), may audit our compliance with them once a year on 30 days’ notice, and also after any Security Incident affecting your data or where the Information Commission requires. An audit starts with a review of documents and evidence we send; a visit follows if that review does not answer your reasonable questions. Audits take place in Working Hours, auditors are bound by confidentiality and are not our competitors, and no audit gives access to other clients’ data. We show Sub-processors’ compliance through their own certifications and reports where we can. Each side bears its own costs, but if audits need more than 2 Working Days of our time in a year, we may charge the extra at the Hourly Rate unless the audit finds a material breach by us.

  3. Return and deletion. When the Services end, you choose whether we return your personal data and then delete it, or delete it without returning it. Return follows Schedule 4. We then delete it from live systems, test copies, our own devices, email and file stores, AI tool histories, and every Sub-processor and contractor, within 30 days of you confirming you have what you need or, if you do not confirm, within 60 days after the later of the end of the Agreement and the end of any continued service under Schedule 4. We remind you in writing at least 10 Working Days before deleting without your confirmation. Backups containing it expire within a further 30 days, and where a Sub-processor deletes on its own fixed schedule, the Sub-processor list states that period. We send a deletion certificate, signed by a director, listing each system and Sub-processor: always for Systems, and on request otherwise. If the law requires us to keep any data, we tell you what and why, protect it, and use it only for that purpose.

  4. Records and contact. We keep a written record of the categories of processing we carry out for you, as Article 30(2) of the UK GDPR requires, including the Sub-processors used, any transfers outside the UK and their safeguards, and a general description of our security measures. We give you or the Information Commission a copy on request. Our Information Commission registration number is in our privacy notice and Security Pack. Our data protection contact is Luke Hilditch (luke@thinkmad.co.uk), or the person named in your Proposal or Security Pack.

  5. Your duties as controller. You confirm that you have a lawful basis for the processing, that your privacy notices (including notices under Articles 13 and 14 of the UK GDPR, in your name) and any consents are in place, and that your instructions comply with Data Protection Law. You tell us about any restriction or objection affecting our processing.

  6. Other points. Clause B5.4 (data before approval), clause 19 (AI services that see personal data are Sub-processors, and no solely automated significant decisions) and clause B4.15 (prospect research controls, which form part of your instructions) apply, as do clause 3.4 on demo data and clause 21.

Schedule 4: Exit, data return and transition

  1. Your data at any time. For Systems, you can export your data at any time through the System’s own export tools where it has them, and on request we send it as CSV and JSON files (the exit pack format) within 5 Working Days, free up to 4 times a year; further manual exports use your hours. Where your Proposal says so, we test the export with you in the first 3 months.

  2. Exit pack for Systems. Within 10 Working Days of either of us giving notice to end, we send once, free of charge: all your Client Data as CSV and JSON, with a short description of each file and field so another supplier can load it; documents, images and other uploaded files in their original formats, with their folder structure; your Users and their roles; the audit log; on request, a full database export; any product catalogue with its categories, attributes, images and datasheets, in CSV with images in folders, or in another format your Proposal states; your website’s pages, media and redirect list where we host it; your setup documentation; the list of components under clause 14.5; and, if the Ownership Date has been reached, the Source Code under clause B5.13(c). Further full exit packs before notice to end use your hours.

  3. Websites. Within 10 Working Days of your request, we give you a full copy of your website’s content, media and database and, once the Website Fee is paid or ownership has otherwise passed to you under clause B1.8, its files and design, in a standard format, with no release fee. Your domain transfer follows clause B3.3 (within 2 Working Days). After hosting ends, we keep your website and a backup so you can move it, and delete them under Schedule 3, paragraph 12 (including its reminder before deleting), or after 30 days where they hold no personal data.

  4. Marketing and social. We give you your reports, the content you own, the link log under clause B4.3 and the stock asset list under clause B4.13, and hand back your accounts under clause 15.3.

  5. Help moving. We include the help hours in your Proposal or, if none are stated, up to 2 hours. Further help is at the Hourly Rate.

  6. Continued service. If you need time to move a System or hosting, and ask before the end date, we provide up to 3 months of continued service after it at the same monthly fee, paid monthly in advance, with the Agreement continuing to apply. If we ended the Agreement under clause 13.1 because of your breach, continued service is available only once undisputed overdue sums are paid. This never affects your data, which paragraph 9 protects.

  7. Access. We remove all our access to your accounts and systems, revoke or hand over any API keys, tokens, SSH keys and integration credentials we held, and confirm this in writing. Under Client Hosting, we hand over any administrator details and make sure they are changed. Where you own the System, we hand over securely the passwords and other secrets needed to run it, and you change them.

  8. Deletion. Client Data is then deleted under Schedule 3, paragraph 12, with a deletion certificate.

  9. Free and never held back. The exit pack, data return at the end of the Agreement, the deletion certificate and domain transfers are free and never use your hours. Returning your data, the exit pack, domain transfers and handing back your accounts never depend on payment of any sum. Extra help hours and continued service are paid as stated above.

Schedule 5: Acceptable use for app and portal users

  1. This Schedule applies to everyone who uses a System we provide. In this Schedule, “you” means each User, and “the business that invited you” means our client. That business may add its own rules.

  2. You must keep your login to yourself and secure, use two-step sign-in where required, follow the instructions of the business that invited you, and report suspected misuse or security problems straight away.

  3. You must not: share your login or use someone else’s; try to reach data or features you are not allowed to see, such as another customer’s prices, lists or quotes; probe, scan or test the System’s security unless authorised in writing; upload malware or anything harmful; scrape, bulk-download or run automated tools or bots against the System beyond its normal features without permission; overload or disrupt it; post or send anything unlawful, defamatory, harassing, discriminatory, obscene or infringing; send spam or unsolicited marketing; pretend to be someone else; copy, decompile or reverse engineer the System except as the law allows; store payment card details or passwords for other systems in it; or enter special category data (such as health information) unless the System is designed for it.

  4. If these rules are broken, your access may be suspended or removed, and serious matters may be reported to the authorities.

Schedule 6: Consumer customers

  1. This Schedule applies only if you are a consumer: an individual buying wholly or mainly for purposes outside your trade, business, craft or profession. Where it differs from the rest of these Terms, it applies.

  2. Your right to cancel. You may cancel within 14 days of the day the Agreement is made, without giving a reason, by telling us clearly (for example by email to projects@thinkmad.co.uk, or with the form below). We start work within those 14 days only if you expressly ask us to, in writing. If you then cancel, you pay a fair proportion of the price for what we provided before you told us. If we finish the work within the 14 days at your request, you lose the right to cancel once it is finished, but only if you confirmed when you asked us to start that you understood this. For an app, software or other digital content supplied online, you lose the right to cancel once supply starts, if you agreed to it starting and confirmed you understood you would lose that right. We refund any money due within 14 days of being told, by the same payment method.

  3. Model cancellation form. “To Think Mad Ltd, Cheshire House, Gorsey Lane, Widnes WA8 0RP, projects@thinkmad.co.uk: I/We hereby give notice that I/We cancel my/our contract for the supply of the following service: [service]. Ordered on: [date]. Name of consumer(s): [name]. Address of consumer(s): [address]. Signature of consumer(s) (only if this form is sent on paper): [signature]. Date: [date].”

  4. Your legal rights. Under the Consumer Rights Act 2015, services must be provided with reasonable care and skill, and digital content must be as described, fit for purpose and of satisfactory quality. Nothing in these Terms affects these rights.

  5. Our responsibility to you. We are responsible for loss you suffer that is a foreseeable result of our breach or failure to use reasonable care and skill. Clause 21 applies only as far as the law allows, and nothing in it limits our liability to you to less than the price you paid. Any early exit charge under clause 12.7 will be no more than a fair estimate of our loss.

  6. Renewals. We remind you before any renewal and make it easy to end your Plan. The subscription contract rules under the Digital Markets, Competition and Consumers Act 2024 (expected from January 2027) will apply to your Plan from their start date.

  7. Courts. You may bring proceedings in the courts of the part of the UK where you live.

  8. Prices. Every price we give you, including the Hourly Rate and any reactivation fee, includes VAT, and your Proposal shows the VAT-inclusive total.

  9. Terms that work differently for you. If the Agreement ends, we refund unused hours you have paid for, whatever clause 7.6 says. We change your Terms under clause 4.7 only for a valid reason stated in our notice. The last sentence of clause 10.5, clauses 21.11 and 25.5, and the deemed approval in clause B1.4 do not apply to you.