B2B CLIENT MASTER SERVICE AGREEMENT

DX Digital Design (trading as DXDD Recovery)

Document reference: recovery-msa-v4-FINAL · Revision date: 24th July 2026 · Amendment: rev-O (post-payout refunds & chargebacks) · Governing law: England & Wales

This Agreement supersedes recovery-msa-v1, recovery-msa-v2, recovery-msa-v3, and all prior drafts of recovery-msa-v4. Only one document shall carry the reference "recovery-msa-v4-FINAL" at any time.

Amendment rev-B summary (for internal reference; not a term of the Agreement): (1) Tier 2 data-source declarations corrected throughout — MOT/VED are retrieved via the Vehicle Data Aggregator (UK Vehicle Data Ltd), not directly from DVSA/DVLA, with an "as is" reliance disclaimer and zero-liability for aggregator downtime, latency, and inaccurate data (new definitions; Clauses 2.1(d)(iii), 2.3(l), 5.1(c)(iii), 5.2(c), 5.7, 5.9(c), 5.10(h), 15.7, 15.9(d); Schedule 6 Part A.3). (2) New Clause 2.8 disclosing the Companies House REST API onboarding check, ring-fenced as administrative contract-formation verification only, creating no duty and not diluting the Section 5 shields. (3) Schedule 5 (Data Processing Agreement) drafted in full — Article 28(3) processing record, Article 10 strict exclusion, Companies House Article 6(1)(f) basis, and approved Sub-Processors (Supabase, Vercel/AWS, Mapbox, Stripe, UK Vehicle Data Ltd). (4) rev-C: the two Multi-Year charges separated so the schedule matches billing — the Prepaid Territory Fee prepays territory + Exclusivity only, while the MRR Fee (Locked Fee) continues monthly for Platform access throughout a Multi-Year Term (MRR and Prepaid Territory Fee definitions; Clauses 9.1A, 9.2; Schedule 3 Part A, Part B, Part D.1). Clause 9.1A governs renewal. (6) rev-E: Section 5 reconciled to actual system behaviour — new Clause 5.1A distinguishes the Flagging Function (all credentials: status/alerts only) from the Blocking Function (automated block, limited to MOT, VED, fleet insurance expiry, and Operator Stale Check); AVRO, PAS 43, O-Licence, LOLER, tachograph calibration, licence/CPC/tacho-card expiry are flag-only. Section 6 payment-default forfeiture softened to a past-due status + right to forfeit (not automatic). Schedule 5 sub-processors completed (added Resend, Twilio, Expo/EAS, Companies House) and card-digit claim removed. Tier 4: DVLA recency stated as 180 days; Companies House check "where available"; Courtesy Attempt intervals generalised; tachograph initial-state carve-out added; Audit Log evidential claim right-sized to what is recorded. (7) rev-F (shared payment rail): new Clause 8.7(h) — the Client authorises Towpal Ltd to use a third-party payment-collection service provider (currently the Company/DXDD) to operate the shared Stripe platform account, as conduit taking no cut, without transferring Merchant-of-Record obligations; and Clauses 8.1 and 8.5(a) corrected to describe the actual platform-account-then-transfer flow rather than a direct-to-Client-account charge, preserving the Merchant-of-Record characterisation. (8) rev-G (pricing & routing reconciled to system): consumer pricing for claimed territories is set by the Client, not Towpal (Clauses 8.7(a),(e),(f), 8.8(a)); new Clause 4.2(c) Job-Completion Fallback discloses that after five operator rejections a Towpal Lead opens to all fleets regardless of exclusivity (never for manual dispatch); new Clause 4.2A and 8.3A define Unclaimed-Territory and Out-of-Bounds Recoveries (Towpal sets price; Towpal holds funds 24h before passing to the accepting Client); new definitions added. (9) rev-H: new Clause 8.3B reflects the two Manual (telephone) Dispatch payment paths — direct charge into a white-label Client's own Connected account (Company holds nothing, takes no fee), versus platform-account collection for all other Clients — with immediate capture and Client-set pricing/refund responsibility. (10) rev-I: new Clause 8.3B(e) records that Manual Dispatch is the Client's own direct sale — not a TowPal transaction, not governed by the TowPal consumer ToS/Privacy — and warrants the Client will provide and surface its own compliant consumer terms and privacy notice at the payment link (DXDD/Towpal disclosed as software/payment provider only). A fleet-issued terms template and privacy-notice template are provided as unwarranted convenience. (11) rev-J: new Clause 8.2A and definition record that VIP / Partner Jobs (police, motor-club, account contracts) settle on a weekly payout cycle (~Friday, up to ~7 days), not the 24-hour lane; Clause 8.2 qualified accordingly; Operator pay timing for such jobs is the Client's responsibility. Matches Operator App terms v2. (12) rev-K: new Clause 2.5A allocates Operator account control (create/suspend/ban/deactivate/remove) to the Client as its own function, exercised for its own reasons, with DXDD as software executor only, not the Operator's employer/decision-maker, and not liable for the Client's account decisions; indemnity extended. Mirrored in Operator App terms and Operator privacy notice. (13) rev-L: Clause 2.5A(a) corrected — Operators self-register using a fleet code issued by the Company to the Client on onboarding and distributed by the Client, rather than accounts being created by a Client Admin; the Client still controls access (admit via code, suspend/ban/remove), and the Company does not determine who the Client admits. (14) rev-M: new Clause 8.3C covers Scheduled Recoveries (booked 3 hours to 5 days ahead, TowPal and Manual Dispatch) — pre-authorisation hold captured on completion; auto-cancel with full refund if no Operator begins travel by the scheduled time; job continues if the Operator has begun but is late; standard cancellation otherwise. Clause 8.3B(c) capture-timing reconciled to cover both immediate and scheduled. (15) rev-N: new Clause 5.15 — the Client warrants it holds all licences, permits, and accreditations its operations require (O-Licence, local-authority/police approved-operator status, PAS 43, waste-carrier registration), will not use the Platform for work it isn't licensed to perform, must provide PAS 43 evidence at onboarding, and acknowledges the Company does not verify or police licensing; indemnity extended. (16) rev-O: new Clause 8.3D governs post-payout refunds and chargebacks — the Client bears them for every job type (including Unclaimed-Territory/Out-of-Bounds, because the Client is the supplier even where Towpal set the price); where Stripe debits the platform account, the amount is a debt recoverable by set-off against the Client's future payouts; the Company does not itself claw back from the Operator — though the card-network chargeback process operated by Stripe may automatically reverse an Operator's linked Transfer, which is outside the Company's control — with any further fleet→operator recovery a separate employment matter, preserving the non-employer position. Clause 8.3D(f) adds a reserve / hold-back right — the Company may retain a reasonable rolling reserve from the Client's payouts (the Client's own money held as security) to cover the Client's potential refund/chargeback liabilities, released after the chargeback window. (5) rev-D: Clause 9.1A rewritten to a renewal-by-election model — renewal requires the Client to re-purchase the territory/Exclusivity element and execute a new Order Form within the Renewal Window (30 days pre-expiry + 7-day post-expiry cure period); the renewed term begins the day after expiry with seamless access if renewed in time; access is suspended on expiry pending cure and the Agreement terminates automatically if the Renewal Conditions are not met (new definitions Renewal Conditions / Renewal Window; Clauses 9.1A, 9.7(e), 11.1; Schedule 3 Part B).

This Master Service Agreement ("Agreement") governs the access to and use of the DXDD Recovery platform. This Agreement is entered into by and between:

DX Digital Design, a company registered in England and Wales (Company No. [COMPANY NUMBER]), trading as DXDD Recovery, whose registered office is at [REGISTERED ADDRESS] ("the Company"); and

The individual or legal entity executing an Order Form that incorporates this Agreement by reference ("the Fleet" or "the Client").

Each a "Party" and together "the Parties."

Effective Date: This Agreement becomes legally binding and effective on the date the Client executes the corresponding Order Form, electronically accepts these terms within the DXDD Recovery portal, or otherwise begins using the Platform (the "Effective Date").

CONTENTS

SECTION 1 — DEFINITIONS

In this Agreement, the following terms shall have the meanings ascribed to them below. Unless the context requires otherwise, references to the singular include the plural and vice versa, and references to a Clause, Section, or Schedule are to a Clause, Section, or Schedule of this Agreement.

SECTION 2 — NATURE OF THE PLATFORM, SOFTWARE-ONLY LIABILITY SHIELD, AND ENTITY SEPARATION

2.1 Technology Provider Only

The Company is a software-as-a-service technology provider exclusively. The Platform constitutes software infrastructure for dispatch coordination, GPS-based routing, driver tracking, payment facilitation, compliance record-keeping, and — where the Towpal Integration is active — the transmission of Towpal Leads into the Client's dispatch workflow. The Company does not provide, and shall not at any time be deemed to provide, Recovery Services of any kind. For the avoidance of all doubt:

(a) the Company is not a motor carrier, haulage operator, freight broker, dispatch broker, recovery broker, recovery operator, or transport undertaking as defined under any applicable UK legislation. The Company does not solicit, negotiate, arrange, or broker recovery work on behalf of the Client, and does not hold itself out as doing so;

(b) the Company is not the employer, principal, agent, partner, joint venturer, or franchisor of the Client, its drivers, its Operators, its Client Admins, or any operative deployed in connection with the Platform;

(c) Recovery Services are provided solely by the Client acting as an independent business operator. The Company exercises no direction, supervision, or control over the manner in which the Client provides Recovery Services, including in respect of any job originating from a Towpal Lead;

(d) the Company is not a compliance auditor, regulator, certification body, inspector, insurance broker, tachograph analysis bureau, licence-checking bureau, vetting or screening service, employment agency, employment business, or adviser of any kind. The Compliance Module, the Approval Workflow, and the Enforcement Matrix are software record-keeping, data-relay, and access-control tools only, as further set out in Section 5. Specifically:

(i) in respect of Tier 1A Self-Certified Credentials, the Company conducts zero review and relies blindly on the Client-inputted expiry date, per Clause 5.5. The Company does not open, read, examine, verify, audit, validate, authenticate, endorse, or warrant any document, certificate, calibration record, expiry date, timestamp, or declaration recorded by the Client;

(ii) in respect of Tier 1B Operator-Level Client-Approved Credentials, the Company never views any Operator Document and plays no part in any Client Approval, which is an attestation by the Client alone, per Clause 5.6. The Company is not a vetting, screening, or employment service;

(iii) in respect of Tier 2 Government-Sourced Credentials (being MOT and VED, as declared in Schedule 6 Part A.3), the Company merely retrieves and relays Aggregator Data supplied to the Platform by the Vehicle Data Aggregator (UK Vehicle Data Ltd), an independent third-party commercial data aggregator which in turn sources that data from a Government Data Source. There are therefore two independent links in the data chain — the Government Data Source and the Vehicle Data Aggregator — over neither of which the Company has any control. The Company does not verify that data, does not audit it against the underlying statutory position, does not control its accuracy, timeliness, completeness, or availability at either link, and gives no warranty of any kind in respect of it. Clause 5.7(d) applies in full;

(iv) in respect of driver licence compliance, the Company does not access the DVLA Portal, does not view, retrieve, receive, store, assess, interpret, score, or evaluate any driving licence record, holds no information as to any Operator's endorsements, penalty points, disqualifications, or fitness to drive, and expresses no view whatsoever on any Operator's suitability. The Company processes a date only, in accordance with Clauses 5.13 and 14.2(d)(iii); and

(v) in every case, the Client remains at all times solely responsible for its own regulatory compliance, irrespective of what the Platform records, relays, permits, or displays; and

(e) the Company assumes zero liability for physical damage to any vehicle, any traffic or road traffic violation, or any failed, aborted, or defective recovery, in accordance with Clause 2.3.

2.2 Separation of Entities — Towpal Ltd and the Company

The Client expressly acknowledges and agrees that:

(a) Towpal Ltd is a legally distinct and separate commercial entity from the Company. The Company's sole role in respect of the Towpal Marketplace is to build, maintain, and operate the Towpal Integration — the API software bridge that transmits Towpal Leads into the Platform. The Company does not own, operate, manage, govern, or exercise any editorial, commercial, or operational control over the Towpal Marketplace, its consumer-facing terms of service, its pricing algorithm, its consumer data practices, or its contractual relationships with End-Users;

(b) the transmission of Towpal Leads to the Client via the Towpal Integration is a software routing function only. The existence of the Towpal Integration does not create any agency, partnership, joint venture, or other relationship between the Company and Towpal Ltd that would cause the acts, omissions, or liabilities of one entity to be attributed to the other; and

(c) any liability arising from the operation of the Towpal Marketplace — including in respect of consumer-facing pricing decisions, marketplace availability, consumer data protection obligations arising from Towpal Ltd's own operations, End-User disputes, or the volume of leads generated — rests exclusively with Towpal Ltd as the marketplace operator and, where applicable, with the Client in its capacity as Merchant of Record under Clause 8.5.

2.3 Exclusion of Company Liability

To the fullest extent permitted by applicable law, the Company hereby expressly excludes all liability — whether in contract, tort (including negligence), breach of statutory duty, misrepresentation, or otherwise — to the Client or any third party for:

(a) damage to, deterioration of, or total loss of any vehicle, property, or cargo arising from or in connection with a Recovery Service, including any job originating from a Towpal Lead;

(b) personal injury, death, or physical harm of any person arising from the provision of Recovery Services by the Client, regardless of whether the job originated natively through the Platform or via the Towpal Integration;

(c) any traffic incident, road traffic accident, or collision involving the Client's drivers, Operators, or vehicles, whether dispatched through the Platform or in response to a Towpal Lead;

(d) any traffic violation, road traffic offence, fixed penalty notice, prohibition notice, or enforcement action incurred by the Client, its drivers, or its Operators, including any offence arising from the use of an untaxed, untested, uninsured, or improperly calibrated vehicle, or from the deployment of a disqualified, endorsed, unlicensed, or otherwise unfit driver, whether or not the Platform permitted that vehicle or Operator to be deployed and whether or not a Government Data Source indicated that vehicle to be compliant;

(e) any failed, aborted, incomplete, or defective recovery, including any recovery not attended, not completed, or completed to a standard the End-User or any third party considers inadequate;

(f) delayed, inaccurate, or failed ETA calculations displayed through the Platform, including where caused by GPS inaccuracy, mobile network failure, or adverse conditions;

(g) driver or Operator negligence, misconduct, or criminal behaviour;

(h) the fitness, suitability, entitlement, identity, right to work, competence, or driving record of any Operator, the Company holding no data capable of informing any such assessment and performing no such assessment, in accordance with Clauses 2.1(d)(ii), 2.1(d)(iv), 5.6, and 5.13;

(i) the volume, frequency, quality, accuracy, or commercial value of Towpal Leads transmitted to the Client via the Towpal Integration, including any period during which no Towpal Leads are generated within the Assigned Territory;

(j) any downtime, outage, interruption, or technical failure of the Towpal Marketplace operated by Towpal Ltd, whether or not such failure affects the transmission of Towpal Leads through the Towpal Integration;

(k) any consumer dispute, complaint, chargeback, refund claim, or regulatory action arising from a transaction originating in the Towpal Marketplace, for which the Client is Merchant of Record under Clause 8.5;

(l) any error, inaccuracy, omission, staleness, delay, latency, outage, downtime, unavailability, withdrawal, change of interface, suspension, or cessation of the Vehicle Data Aggregator (UK Vehicle Data Ltd) or of any Government Data Source, and any Vehicle Lock applied, or not applied, in consequence of the same, in accordance with Clause 5.7(d);

(m) any lost earnings, lost jobs, lost leads, lost revenue, lost profit, operational downtime, idle driver or vehicle cost, or breach by the Client of any contract with any third party, arising from or in connection with any Compliance Suspension, Vehicle Lock, or Operator Lock triggered by the Enforcement Matrix under Section 5, whether such suspension arises under Clause 5.4, 5.7, or 5.13, and whether or not the underlying Compliance Credential was in fact valid;

(n) any regulatory enforcement action, prosecution, fine, penalty, licence revocation or curtailment, Traffic Commissioner action, prohibition, insurance repudiation, or civil claim brought against the Client arising from the Client's actual non-compliance with AVRO requirements, PAS 43, its O-Licence conditions, LOLER, Tachograph Calibration requirements, MOT, VED, driver licensing requirements, insurance conditions, or any other legal or regulatory obligation, whether or not the Compliance Module recorded or relayed that credential as current at the relevant time and whether or not the Platform permitted deployment;

(o) any consequence of an incorrect Tachograph Exemption Declaration made by the Client under Clause 5.3, in accordance with Clause 5.3(e);

(p) the absence, failure, non-generation, non-display, or non-delivery of any Courtesy Attempt, in accordance with Clause 5.8(e);

(q) any indirect, consequential, special, exemplary, or punitive loss of any nature, including loss of revenue, profit, business, goodwill, data, or anticipated savings, whether arising from the Platform's native functionality, the Compliance Module, the Approval Workflow, the Enforcement Matrix, or the Towpal Integration; and

(r) any Client Approval recorded by a Client Admin, including the approval of any forged, expired, invalid, or defective Operator Document, and any consequence of the deployment of any Operator in respect of whom a Client Approval subsisted, in accordance with Clause 5.6(e).

2.4 Aggregate Liability Cap

Without prejudice to Clause 2.3, the Company's total aggregate liability to the Client under or in connection with this Agreement — including in respect of the Towpal Integration, the Compliance Module, the Approval Workflow, and the Enforcement Matrix — shall not in any circumstances exceed the total MRR Fees paid by the Client in the three (3) calendar months immediately preceding the event giving rise to the claim, or, where the Client is on a Multi-Year Term, a sum equal to three (3) months' worth of the Prepaid Territory Fee calculated on a straight-line monthly apportionment. For the avoidance of doubt, the value of Towpal-originated consumer transactions processed through the Client's Connected Stripe Account, and the value of any earnings foregone during a Compliance Suspension, Vehicle Lock, or Operator Lock, shall not be taken into account when calculating this cap.

2.5 Client's Sole Operational Responsibility — 100% Liability

The Client acknowledges and agrees that it is the sole operator of its vehicle recovery business and bears 100% operational and statutory compliance liability for all aspects of its business, including without limitation:

(a) the licensing, entitlement, training, competence, conduct, identity, right to work, fitness to drive, and insurance of all drivers, Operators, and recovery operatives, including in respect of any job originating from a Towpal Lead;

(b) the roadworthiness, testing, taxation, maintenance, tachograph calibration, and regulatory compliance of all vehicles and lifting equipment used in connection with the Platform;

(c) compliance with all applicable legislation, standards, and accreditation requirements, including without limitation the Road Traffic Act 1988, the Vehicle Excise and Registration Act 1994, the Goods Vehicles (Licensing of Operators) Act 1995, the Health and Safety at Work etc. Act 1974, the Lifting Operations and Lifting Equipment Regulations 1998, the Provision and Use of Work Equipment Regulations 1998, the Transport Act 1968 and retained Regulation (EU) 165/2014 in respect of tachographs, the Road Traffic (Vehicle Testing) Act 1999, PAS 43 where applicable, and AVRO membership rules where applicable;

(d) the accuracy, currency, authenticity, and completeness of every Compliance Credential, inputted expiry date, calibration record, certificate, timestamp, declaration, Client Approval, and item of Compliance Data recorded within the Compliance Module, and the maintenance of the underlying credentials themselves in the real world irrespective of what the Platform records, relays, or permits;

(e) the examination and validation of every Operator Document, in accordance with Clause 5.6;

(f) the independent review of each Operator's driving licence record via the DVLA Portal, the assessment of that record against the Client's own fitness-to-drive criteria, and the acting upon that assessment, in accordance with Clauses 5.13 and 14.2(d)(iii), the Platform holding a date only and expressing no view on any outcome;

(g) the quality, safety, timeliness, and outcome of every Recovery Service provided to an End-User, whether originating natively through the Platform or via a Towpal Lead; and

(h) all interactions, contractual relationships, consumer disputes, chargeback liabilities, and refund obligations with End-Users, including those whose initial request originated through the Towpal Marketplace.

2.5A Operator Account Control — the Client's Function

The Client acknowledges and agrees that the creation, configuration, management, suspension, banning, deactivation, and removal of its Operators' accounts on the Platform is the Client's own function, performed by the Client's own Client Admins, for the Client's own operational, employment, engagement, disciplinary, performance, or compliance reasons. In particular:

(a) Operators join by self-registering in the Operator App using a fleet code issued to the Client (such codes originating from the Company and provided to the Client's administrators on onboarding, which the Client then distributes to the Operators it authorises); an Operator cannot join without the Client's code, and once joined the Operator's account is controlled by a Client Admin, who alone can suspend, ban, deactivate, reinstate, or remove that Operator's access. The Company does not determine which individuals the Client admits or retains;

(b) where a Client Admin suspends, bans, deactivates, or removes an Operator, that is a decision of the Client alone. The Company neither makes, directs, reviews, approves, nor participates in that decision, and the Platform merely executes, as software, the access change the Client has chosen, and surfaces to the affected Operator that the action was applied by their fleet;

(c) any dispute, grievance, or claim by an Operator arising from the suspension, banning, deactivation, or removal of their account — including any employment, worker-status, discrimination, unlawful-deduction, or wrongful-treatment claim — is a matter between the Operator and the Client, consistent with Clauses 2.1 and 2.5, and the Company is not the Operator's employer, engager, or decision-maker and bears no liability for it;

(d) the Client is solely responsible for exercising this power lawfully and fairly, including for compliance with employment law, the Equality Act 2010, and any applicable disciplinary or contractual process owed to the Operator; and

(e) the Company's separate right to suspend or restrict Platform or App access for its own reasons (for example security, non-payment under Section 6, breach of the operator-facing terms, or maintenance) is unaffected by this Clause and is exercised independently of, and does not substitute for, the Client's own account-control function.

The indemnity at Clause 2.6 extends to any claim brought against the Company by an Operator arising from the Client's exercise of, or failure to exercise, its account-control function under this Clause 2.5A.

2.6 Client Indemnity

The Client shall fully and effectively indemnify, defend, and hold harmless the Company, its directors, officers, employees, contractors, and agents from and against any and all third-party claims, losses, damages, costs, expenses (including legal fees on a solicitor-and-client basis), fines, and liabilities arising out of or in connection with:

(a) the Client's provision of Recovery Services, including the fulfilment of any job originating from a Towpal Lead;

(b) any act, omission, negligence, or misconduct of the Client's drivers, Operators, Client Admins, or operatives;

(c) the Client's breach of applicable law or regulation, including any breach of AVRO rules, PAS 43, O-Licence conditions, LOLER, tachograph requirements, MOT or VED requirements, driver licensing requirements, or insurance conditions;

(d) any claim by an End-User against the Company arising from the Client's services, whether or not that End-User's request originated through the Towpal Marketplace;

(e) any chargeback, refund obligation, Stripe penalty, or financial liability arising from the Client's status as Merchant of Record under Clause 8.5 in respect of Towpal-originated transactions;

(f) any false, inaccurate, incomplete, expired, forged, or misleading Client-inputted expiry date, Compliance Credential, Client Approval, Operator Document, Tachograph Exemption Declaration, Last DVLA Check Date, or item of Compliance Data uploaded or recorded by or on behalf of the Client, including any claim brought against the Company by a third party in reliance upon, or in consequence of, the same;

(g) the Client's deployment of any Operator who is disqualified, unlicensed, without appropriate entitlement or CPC, without right to work, impersonating another person, or otherwise unfit to drive or work, notwithstanding that the Platform did not apply an Operator Lock to that Operator and notwithstanding any subsisting Client Approval, in accordance with Clauses 5.6(e) and 5.13(e);

(h) any claim brought by an Operator, employee, contractor, or Client Admin of the Client in respect of the collection, processing, storage, or disclosure of Operator Data, Operator Documents, Licence Check Recency Data, tachograph card data, camera verification captures, or Walkaround Records, including any claim under the UK GDPR or the Data Protection Act 2018, save to the extent such claim arises from the Company's breach of its own obligations as Data Processor under Section 14; and

(i) the Client's upload to the Platform of any DVLA check code, outcome flag, fitness determination, or detailed driving offence record in breach of Clause 14.2(f), including any regulatory action or data subject claim arising from the presence of such data within the Platform.

The indemnities at Clauses 5.5(f) and 5.6(f) are in addition to, and do not limit, this Clause 2.6.

2.7 Statutory Savings

Nothing in this Section 2 shall exclude or limit the Company's liability for death or personal injury caused by the Company's own negligence, fraud or fraudulent misrepresentation, or any other liability that cannot be lawfully excluded under English law.

2.8 Companies House Verification — Administrative Contract-Formation Check Only

(a) What the Company does. During onboarding, and where the service is available, the Platform queries the UK Companies House REST API to retrieve certain corporate identity particulars of the prospective Client — namely its registered company name, company number, registered office address, and registered status (for example "active", "dissolved", or "in liquidation"). This is referred to in this Agreement as the "Companies House Verification".

(b) Its sole and limited purpose. The Companies House Verification is an administrative identity check performed solely for the purposes of contract formation — confirming that the entity purporting to contract with the Company exists as a registered legal person, is correctly named, and is correctly identified on the Order Form and in this Agreement, so that the Company knows who it is contracting with. It exists for the Company's own onboarding, anti-impersonation, and record-keeping purposes. It is nothing more than that.

(c) Strict ring-fence — no compliance review, no duty, no assumption of responsibility. The Client expressly acknowledges and irrevocably agrees that the Companies House Verification:

(i) is confined entirely to the corporate legal-identity particulars listed at Clause 2.8(a), and to nothing else whatsoever;

(ii) does not constitute, include, imply, or extend to any review, audit, check, verification, validation, assessment, monitoring, or endorsement by the Company of the Client's operational, statutory, regulatory, insurance, accreditation, licensing, or fleet compliance, or of the Client's financial standing, solvency, creditworthiness, trading history, beneficial ownership, directors, or fitness to operate;

(iii) creates no duty — whether in contract, in tort (including any duty of care or any duty in negligence), by way of assumption of responsibility, by course of dealing, or otherwise — on the part of the Company to the Client or to any third party to conduct, continue, repeat, update, monitor, or act upon the Companies House Verification, or to detect, investigate, report, or act upon any matter disclosed, or capable of being disclosed, by Companies House or any other source;

(iv) involves no assumption of responsibility of any kind by the Company for the accuracy, completeness, or currency of the data held by Companies House, which is a public register maintained by a third party wholly outside the Company's control and relied upon "as is", and the Company bears zero liability for any error, omission, staleness, or unavailability in it, or for any consequence of a Vehicle, asset, or Operator being permitted or restricted by reference to it (it not being so used); and

(v) is a one-time or occasional administrative step which the Company is under no obligation to repeat, and the Company owes no duty to monitor the Client's continuing registered status, any change of control, any insolvency event, or any strike-off, notwithstanding that such matters may be publicly recorded at Companies House — the Client's own notification obligations under Clauses 4.6 and 11.1 being unaffected and continuing to rest solely with the Client.

(d) No dilution of the Section 5 shields. For the avoidance of all doubt, and without limitation, the Companies House Verification does not dilute, qualify, narrow, waive, or create any exception to any provision of Section 5, including without limitation:

(i) the Company's absolute passivity and zero-review position at Clause 5.1(b);

(ii) the Tier 1A self-certification and blind-reliance shield at Clause 5.5, under which the Company verifies nothing and relies exclusively on the Client-inputted expiry date;

(iii) the Tier 1B Approval Workflow shield at Clause 5.6, under which the Company never views any Operator Document and plays no part in any Client Approval; and

(iv) the principle at Clause 5.1(d) that the Platform permitting a Client to onboard, or to be issued an Order Form, is never authority, clearance, verification, or approval of that Client's compliance, fitness, or entitlement to operate.

The fact that the Company has confirmed a Client's corporate existence for the purpose of knowing whom it is contracting with shall never be construed, relied upon, or represented as the Company having reviewed, verified, or assumed any responsibility for that Client's compliance. The self-certification architecture of Section 5 applies to every Client with full and undiminished force, whether or not a Companies House Verification was performed in respect of that Client.

(e) Data protection. The Companies House Verification processes publicly available corporate-register data and, incidentally, the personal data of any director or officer appearing in those particulars. The Company processes such data as controller for the limited administrative purpose stated at Clause 2.8(b), on the lawful basis of its legitimate interests in verifying the identity of its counterparties and preventing impersonation and fraud (Article 6(1)(f) UK GDPR), and in accordance with its Privacy Policy.

SECTION 3 — GRANT OF SOFTWARE LICENCE

3.1 Licence Grant

Subject to the Client's full and continued compliance with this Agreement, including timely payment of all Fees and maintenance of current Compliance Credentials within the Compliance Module, the Company grants to the Client a limited, non-exclusive by default, non-transferable, revocable licence to access and use the Platform solely for the purpose of operating the Client's vehicle recovery business within the Assigned Territory during the Subscription Term.

3.2 Licence Restrictions

The Client shall not, and shall procure that its employees, Client Admins, Operators, and contractors do not:

(a) sublicense, resell, transfer, assign, or otherwise make the Platform available to any third party;

(b) reverse-engineer, decompile, disassemble, or attempt to derive the source code of the Platform or any component thereof, save to the extent expressly permitted by section 50B of the Copyright, Designs and Patents Act 1988 and only then in the strictly limited circumstances provided therein;

(c) copy, modify, translate, adapt, or create derivative works based on the Platform or any part thereof;

(d) remove, alter, or obscure any proprietary notices, branding, or marks displayed within the Platform;

(e) use the Platform in any unlawful manner or for any purpose other than that for which it is licensed under this Agreement;

(f) access or use the Platform to build a competing or substantially similar product or service;

(g) circumvent, disable, spoof, falsify data within, or otherwise interfere with the Compliance Module, the Approval Workflow, the Enforcement Matrix, the Audit Log, any Vehicle Lock, or any Operator Lock, including by inputting a falsified, backdated, post-dated, or knowingly inaccurate expiry date, by uploading a forged or altered document, by recording a Client Approval in respect of a document not actually examined, or in respect of a document known or suspected to be forged, expired, or invalid, by recording a Last DVLA Check Date in respect of a check not actually performed, by making a knowingly incorrect Tachograph Exemption Declaration, or by deploying a locked vehicle or locked Operator by any means outside the Platform in order to conceal a lapsed credential;

(h) attempt to alter, overwrite, delete, or suppress any entry in the Audit Log; or

(i) upload to, enter into, or store within the Platform any DVLA check code, pass/fail or other outcome flag, fitness-to-drive determination, driving offence record, endorsement code, penalty point count, disqualification particular, or conviction detail, in breach of Clause 14.2(f).

Any conduct falling within Clause 3.2(g) or 3.2(h) shall constitute a material breach of this Agreement entitling the Company to terminate immediately under Section 11 without a cure period.

3.3 White-Label Use

Where the Company has agreed in writing that the Client may deploy the Platform under its own trading name or branding pursuant to a white-label arrangement, such deployment shall be subject to the additional terms set out in Schedule 4 (where applicable) and shall not confer any Intellectual Property Rights on the Client.

SECTION 4 — TERRITORIAL EXCLUSIVITY, THE SOFTWARE MONOPOLY MODEL, AND TOWPAL LEAD ACCESS

4.1 The Software Monopoly Model — Default Non-Exclusive Licence

The licence granted under Clause 3.1 is non-exclusive by default. Exclusivity — the "Software Monopoly" — is a commercial upgrade under which the Client acquires, for the duration of the Subscription Term and subject to continued good standing, the exclusive right to operate the Platform and receive Towpal Leads within a defined set of Ordnance Survey postcodes. Exclusivity is only operative where expressly confirmed in writing in a signed Order Form or Schedule 1.

4.2 Grant of Exclusivity

Where the Company has confirmed in writing that the Client is granted Exclusive Territory Rights, the following shall apply for so long as Exclusivity remains in force in accordance with this Section 4:

(a) Platform Exclusivity — the Company will not knowingly onboard a directly competing independent towing or vehicle recovery operator under the same Platform tier within the identical Ordnance Survey postcode boundaries comprising the Assigned Territory; and

(b) Towpal Lead Exclusivity — as a component of Exclusive Territory Rights, the Client shall receive first and priority access, via the Towpal Integration, to Towpal Leads generated within the Assigned Territory postcodes. The Company will configure the Towpal Integration so that a Towpal Lead originating within the Assigned Territory is offered first to the Client's own operators — routed to the nearest matched operator and, on rejection, to the next-nearest matched operator of the Client — and is not, in the ordinary course, simultaneously offered to any other Fleet Operator client operating within the same postcodes. This Towpal Lead routing preference is a software configuration function and is conditional on Exclusivity remaining in force under this Agreement. This Clause 4.2(b) is subject to the Job-Completion Fallback at Clause 4.2A.

(c) The Job-Completion Fallback — exclusivity yields to save a stranded consumer. The Client expressly acknowledges and agrees that, because a Towpal Lead concerns a stranded member of the public who must not be left without recovery, the Client's Towpal Lead exclusivity is subject to the following fallback, and that the operation of this fallback is not a breach of, or a derogation from, the Exclusive Territory Rights:

(i) where a Towpal Lead within the Assigned Territory has been offered to and rejected by the Client's matched operators, and the number of rejections from the Client's fleet reaches five (5), the Lead becomes "open to all" — it is offered to the nearest matched operators of any Fleet Operator client, regardless of territorial exclusivity, so that the recovery can be completed rather than cancelled;

(ii) once a Lead is open to all, an operator of another fleet may accept and complete it, and the accepting fleet (not the Client) is the party that performs and is paid for that job;

(iii) the Job-Completion Fallback applies only to Towpal Marketplace recoveries. It does not apply to the Client's manual (telephone) dispatch recoveries, which are never opened to other fleets; and

(iv) the Client acknowledges that the fallback exists to protect consumer welfare and the integrity of the Towpal Marketplace, that it operates only after the Client's own operators have had first refusal and have declined (or not accepted) the Lead the requisite number of times, and that no compensation, and no adjustment to any Fee or Exclusivity Premium, is due to the Client in respect of a Lead completed by another fleet under this fallback.

4.2A Unclaimed-Territory and Out-of-Bounds Recoveries

The Client acknowledges that not every Towpal recovery arises within a claimed Assigned Territory, and that the following categories fall outside the Client's exclusivity entirely:

(a) "Unclaimed-Territory Recovery" — a Towpal recovery arising within a territory that no Client owns. For such recoveries, Towpal Ltd sets the consumer price (via its own pricing controls), the job is offered to nearest matched operators without territorial exclusivity, and the funds are handled in accordance with Clause 8.3A; and

(b) "Out-of-Bounds Recovery" — a Towpal recovery arising outside the borders of any territory. For such recoveries, Towpal Ltd sets the consumer price, and the job is offered without territorial exclusivity.

Unclaimed-Territory Recoveries and Out-of-Bounds Recoveries are outside the Client's Assigned Territory and outside its Exclusive Territory Rights. The Client has no exclusivity in, and no entitlement to, such recoveries; where the Client's operator accepts one, the Client performs and is paid for it in the ordinary way, subject to the fund-holding arrangement in Clause 8.3A.

4.3 Critical Limitation — No Volume Guarantee

The Client expressly acknowledges and irrevocably agrees that the grant of Exclusive Territory Rights — including the Towpal Lead exclusivity component under Clause 4.2(b) — carries absolutely no guarantee, representation, or warranty of any kind regarding lead volume, job frequency, revenue generation, or any other commercial outcome.

Without limiting the generality of the foregoing and for the complete avoidance of doubt:

(a) neither the Company nor Towpal Ltd makes any representation, warranty, or forecast — express or implied, contractual or otherwise — as to the minimum number of Towpal Leads that will be generated within the Assigned Territory during any billing period, month, quarter, or year;

(b) neither the Company nor Towpal Ltd guarantees any minimum GTV, revenue, income, or profit to the Client in respect of Towpal Lead-originated jobs at any time;

(c) the volume of consumer recovery requests submitted through the Towpal Marketplace within any given territory is determined entirely by consumer demand, market conditions, and Towpal Ltd's own operational and marketing decisions, all of which are wholly outside the control of the Company;

(d) the MRR Fee, any Exclusivity Premium, and any Prepaid Territory Fee payable by the Client constitute consideration for: (i) licensed access to the Platform software and its functionality, including the Compliance Module; and (ii) the contractual right to Exclusivity within the Assigned Territory, including the right to be the sole recipient of any Towpal Leads that do arise — and not for any guaranteed volume of leads, any guaranteed level of GTV, or any guaranteed commercial return;

(e) the Client confirms that it has not entered into this Agreement in reliance on any projection, estimate, forecast, or representation regarding expected Towpal Lead volumes or revenues, and that any such figures communicated during the sales or onboarding process were illustrative of market potential only and did not constitute representations, warranties, or contractual commitments on the part of the Company or Towpal Ltd; and

(f) no lead, job, or revenue will be routed to the Client during any period of fleet-level Compliance Suspension under Section 5. Any leads arising within the Assigned Territory during such a suspension are irretrievably lost to the Client, and the Company shall bear no liability whatsoever in respect of them.

4.4 Nature and Limitations of Exclusivity

The Client acknowledges that:

(a) Exclusivity is a contractual right only and does not confer any proprietary, intellectual property, or other interest in the Assigned Territory, any postcode data, the Towpal Marketplace, or any consumer relationship or database maintained by Towpal Ltd;

(b) Exclusivity does not prevent the Company from operating the Platform, or Towpal Ltd from operating the Towpal Marketplace, for any other purpose within the Assigned Territory, including for non-competing industries or operator categories; and

(c) Exclusivity is personal to the Client and may not be transferred, sublicensed, or assigned under any circumstances, whether or not the Client has prepaid a Multi-Year Term.

4.5 Non-Transferability

The Assigned Territory and any Exclusive Territory Rights are strictly non-transferable. The Client shall not:

(a) assign, sublicense, or transfer its territorial rights — including the right to receive Towpal Leads within the Assigned Territory — or any benefit thereof to any third party by any means;

(b) permit any third party to access or benefit from the Platform or any Towpal Lead routing under the Client's account or territory allocation; or

(c) purport to transfer territorial rights as part of any sale, merger, acquisition, or restructuring of its business.

4.6 Automatic Territory Reversion on Change of Control or Business Cessation

Exclusive Territory Rights — including the Towpal Lead routing preference — shall immediately and automatically revert to the Company, without notice, without compensation, and (subject only to Clause 9.8) without refund of pre-paid Fees, upon:

(a) a Change of Control of the Client;

(b) the Client ceasing to trade, entering into administration, liquidation, receivership, or proposing a Company Voluntary Arrangement; or

(c) the transfer or sale of the Client's business or substantially all of its assets to a third party.

The Client shall notify the Company in writing within 48 hours of becoming aware that any such event is likely or has occurred.

4.7 Exclusivity Trapdoors — Consolidated Cross-Reference

The Client expressly acknowledges that Exclusive Territory Rights are a conditional, revocable privilege and not a vested or proprietary right, and that they are subject to immediate suspension, forfeiture, revocation, or reversion under each and all of the following provisions, each of which operates independently of the others, and each of which applies equally whether the Client is on an Annual Term or a prepaid Multi-Year Term:

(a) Section 5 — Compliance Suspension, Vehicle Lock, and Operator Lock under the Enforcement Matrix, and Exclusivity forfeiture on prolonged Compliance Suspension under Clause 5.11(b);

(b) Section 6 — immediate and automatic forfeiture on failed, reversed, or late payment of the MRR Fee, including failure arising from a Stripe payment event or a failed Stripe Connect onboarding;

(c) Section 7 — revocation for failure to meet the Minimum Operational Volume, including where the Client registers zero or negligible jobs within the Assigned Territory;

(d) Section 11 — Territory Reversion on termination for cause following any Event of Default; and

(e) Section 12 — Territory Reversion on termination for convenience by either Party on 30 or 60 days' notice.

SECTION 5 — AUTOMATED COMPLIANCE AND THE ENFORCEMENT MATRIX

5.1 Purpose, Nature, and the Company's Absolute Passivity

The Platform incorporates a Compliance Module within which the Client records its Compliance Credentials, their respective expiry dates, and certain timestamps and attestations, and into which the Platform relays data in respect of Government-Sourced Credentials. The Enforcement Matrix is an automated, rules-based access-control mechanism which reads that data and, upon expiry, lapse, staleness, revocation, or absence of a Compliance Credential, automatically restricts the Client's ability to receive or action work through the Platform in accordance with Clauses 5.4 to 5.7 and 5.13.

The Client acknowledges and agrees that:

(a) Access control only. The Enforcement Matrix is a software access-control function only. It is not a compliance audit, certification, inspection, verification, validation, approval, or assurance service of any kind, and is not held out as one.

(b) Absolute passivity — the Company reviews nothing. The Company conducts, and shall conduct, ZERO manual review, inspection, verification, validation, authentication, assessment, or approval of any document, certificate, record, image, expiry date, timestamp, declaration, or attestation uploaded to, entered into, or recorded within the Compliance Module by or on behalf of the Client. The Company:

(i) does not open, read, examine, or look at any document uploaded by the Client for any compliance purpose;

(ii) does not check any inputted expiry date against the document to which it purports to relate, against any register, or against anything else;

(iii) does not verify the authenticity, genuineness, provenance, currency, completeness, or sufficiency of any document or record;

(iv) does not assess whether any document satisfies any legal, regulatory, insurance, accreditation, or contractual requirement applicable to the Client; and

(v) does not approve, endorse, certify, clear, or pass any document, credential, vehicle, asset, or Operator, and holds no opinion whatsoever on any of them.

(c) Data provenance. As declared in Schedule 6 Part A, the Enforcement Matrix operates on three and only three classes of data:

(i) Tier 1A — Self-Certified Credentials. Data input by the Client, upon which the Platform relies exclusively, automatically, and without verification, question, or independent check of any kind. Clause 5.5 applies;

(ii) Tier 1B — Operator-Level Client-Approved Credentials. Data recorded and attested by a Client Admin through the Approval Workflow, upon which the Platform relies exclusively, automatically, and without verification, question, or independent check of any kind. Clause 5.6 applies. The Company is not a party to, and has no involvement in, any Client Approval; and

(iii) Tier 2 — Government-Sourced Credentials. Data retrieved and relayed from the Vehicle Data Aggregator (UK Vehicle Data Ltd), which in turn sources it from Government Data Sources operated by the DVSA and DVLA, in respect of which the Company acts as a mere conduit at the end of a two-link third-party chain. Clause 5.7 applies.

(d) Permission is never clearance. The absence of a Compliance Suspension, Vehicle Lock, or Operator Lock does not constitute confirmation, certification, approval, or any representation whatsoever by the Company that the Client is compliant with AVRO requirements, PAS 43, its O-Licence conditions, LOLER, tachograph requirements, MOT, VED, driver licensing requirements, its insurance obligations, or any other legal or regulatory requirement.

The Platform permitting a vehicle, asset, or Operator to be deployed is not, and shall never be relied upon as, authority, clearance, verification, or approval to deploy that vehicle, asset, or Operator lawfully. This applies with equal and undiminished force where the permission arises from: a Client-inputted expiry date; a Client Approval recorded by a Client Admin; data relayed from a Government Data Source; or the mere recency of a Last DVLA Check Date. The Client remains solely and exclusively responsible for its own regulatory compliance at all times, entirely independently of what the Platform records, relays, permits, or displays.

(e) Built for the Company, not for the Client. The Enforcement Matrix, the Approval Workflow, and the Audit Log are provided as a commercial risk-management and record-keeping feature for the benefit of the Company, its wider client base, and End-Users. They are not provided as a compliance service, compliance system, or compliance assurance to the Client, and the Client shall not rely upon them as such.

(f) The tools are not a checklist of the law. The Compliance Module records the credentials enumerated in Schedule 6 and no others. The Company does not represent, and the Client shall not assume, that those credentials constitute a complete, sufficient, or current statement of the legal, regulatory, insurance, or accreditation requirements applicable to the Client's business. The Client's obligations extend beyond what the Platform records, and the Client alone is responsible for identifying and discharging them.

5.1A What the Platform Flags, and What It Blocks

This Clause governs, and prevails over any contrary implication elsewhere in this Section 5 or in Schedule 6, as to which Compliance Credentials produce an automated block and which produce only a flag.

(a) The Flagging Function (all credentials). For every Compliance Credential it monitors, the Enforcement Matrix computes a status and, on or before expiry, surfaces that status to the Client through dashboard indicators, colour states, compliance scores, and Courtesy Attempts (Clause 5.8). The Flagging Function displays information. It does not, of itself, prevent the deployment of any vehicle, asset, or Operator. Acting upon a flag — including standing down a vehicle or Operator whose credential has lapsed — is the Client's responsibility, consistent with Clauses 5.1(d) and 5.14.

(b) The Blocking Function (Blocking Credentials only). The Enforcement Matrix additionally applies an automated Compliance Suspension, Vehicle Lock, or Operator Lock in respect of the following, and only the following, Compliance Credentials (the "Blocking Credentials"):

(i) MOT (VT20) — vehicle-level Vehicle Lock at expiry, per Clause 5.7;

(ii) Road Tax (VED) — vehicle-level Vehicle Lock at expiry, per Clause 5.7;

(iii) Fleet insurance expiry — a fleet-level Compliance Suspension on expiry of the Client-inputted expiry date for the fleet-level insurance credentials designated as Blocking Credentials in Schedule 6 (as at the Revision Date, employers' liability, public liability, and goods-in-transit insurance); and

(iv) Operator licence-check recency (Stale Check) — Operator-level Operator Lock where the Last DVLA Check Date is older than the Check Recency Period or absent, per Clause 5.13.

(c) Everything else is flag-only. All other Compliance Credentials monitored by the Compliance Module — including without limitation AVRO membership, PAS 43 certification, O-Licence status, LOLER thorough-examination records, Tachograph Calibration, driving-licence and entitlement expiry, Driver CPC expiry, tachograph driver-card expiry, training and competence records, and right-to-work records — are subject to the Flagging Function only. Their expiry, lapse, or absence causes the Platform to display an alert or an adverse status, but does not automatically suspend the Dispatch Queue and does not automatically lock the affected vehicle, asset, or Operator. The Client remains solely responsible for acting on the flag and standing the vehicle, asset, or Operator down.

(d) Why it is built this way. The Client acknowledges that the Blocking Function is deliberately confined to a narrow set of credentials for which a reliable, objective, machine-readable trigger exists, and that the deliberate consequence is that the Platform will continue to permit the deployment of a vehicle, asset, or Operator whose flag-only credential has lapsed. This is not a defect. It reflects the allocation of responsibility throughout this Agreement: compliance is the Client's obligation, the Platform surfaces information to assist the Client, and the Client must act on it. Clause 5.1(d) (permission is never clearance) applies with full force to every flag-only credential.

(e) Variation. The Company may add credentials to, or remove credentials from, the Blocking Credentials list, or change a credential between flag-only and blocking, on notice under Clause 5.2(d), by amending Schedule 6. No such change expands the Company's duties or liabilities, and the Client acquires no right to require that any particular credential block.

5.2 Monitored Compliance Credentials

The Enforcement Matrix monitors, at minimum, the Compliance Credentials set out below. The full enumeration, monitoring granularity, declared data source, and compliance mechanism for each credential is set out in Schedule 6 Part A, which forms part of this Agreement.

(a) Tier 1A — Self-Certified Credentials · Client Upload + Client-Inputted Date (Clause 5.5) · Flag-only except insurance (Clause 5.1A)

(b) Tier 1B — Operator-Level Client-Approved Credentials · Approval Workflow (Clause 5.6) · Flag-only except licence-check recency (Clause 5.1A)

(c) Tier 2 — Government-Sourced Credentials · Aggregator Relay (UK Vehicle Data Ltd → DVSA/DVLA) · Vehicle Lock at expiry (Clause 5.7)

(d) Variation of the Matrix

The Company reserves the right to add further Compliance Credentials to the Enforcement Matrix, to vary the scope or granularity of monitoring, to vary the Check Recency Period or the Tachograph Threshold Weight, to re-designate any credential between Tier 1A, Tier 1B, and Tier 2, or to change the declared mechanism or data source of any credential, on no less than 30 days' written notice to the Client, by updating Schedule 6 in accordance with Clause 15.3. Any change to a declared mechanism or data source shall be stated expressly in the updated Schedule 6. (This Clause 5.2(d) is referred to elsewhere in this Agreement as the variation right; where any provision refers to variation "under Clause 5.2(g)" or "under Clause 5.3", the reference shall be construed as a reference to this Clause 5.2(d).)

5.3 Tachograph Calibration — Default, Exemption Toggle, and Audit Log

(a) Default by gross vehicle weight. The Enforcement Matrix defaults to requiring and monitoring Tachograph Calibration in respect of every vehicle whose gross vehicle weight, as recorded by the Client, exceeds the Tachograph Threshold Weight of 3,500kg. Where a vehicle's recorded gross vehicle weight is 3,500kg or below, Tachograph Calibration monitoring is not applied by default, but the Client may elect to apply it under Clause 5.3(c).

The Client acknowledges that the Tachograph Threshold Weight is an operational configuration default adopted by the Company for the purposes of the Platform. It is not, and does not purport to be, a statement of the applicable statutory test. The scope of tachograph requirements depends upon the vehicle, the nature and purpose of the operation undertaken, the composition of any vehicle-and-trailer combination, and any applicable derogation or exemption — none of which the Company assesses, monitors, or advises upon. The Client alone is responsible for determining the true scope of tachograph requirements applicable to each of its vehicles and operations.

(b) The Tachograph Exempt toggle — active declaration only. The Compliance Module provides, in respect of each vehicle registered by the Client, a manual dashboard toggle by which the Client may actively declare that vehicle to be "Tachograph Exempt". Setting that toggle constitutes a Tachograph Exemption Declaration by the Client in respect of that vehicle. The toggle:

(i) defaults, for every vehicle with a recorded gross vehicle weight exceeding the Tachograph Threshold Weight, to "Tachograph Applicable";

(ii) is not set to Exempt by the Platform on an ongoing basis, and exemption is not inferred, presumed, or applied automatically by the Company from vehicle weight, class, body type, usage pattern, or any other datum on an ongoing basis. The sole exception is the initial configuration state: for a vehicle with a recorded gross vehicle weight at or below the Tachograph Threshold Weight, the toggle may be set to a default initial state (reflecting that such a vehicle is, by default, not tachograph-monitored under Clause 5.3(a)). The Client acknowledges this initial state, warrants that it will review and, where required, actively re-set the toggle to reflect the true position for each such vehicle in accordance with Clause 5.3(c) and (e), and accepts that the initial state is not a representation by the Company that any vehicle is in fact exempt; and

(iii) where the Platform provides a free-text field for it, invites the Client to record a stated ground of exemption at the point of declaration. The Company does not review, assess, verify, question, or advise upon any stated ground, which is recorded solely for the Client's own audit purposes, consistent with Clause 5.1(b). The Client should in any event retain its own record of the ground for each exemption it declares.

(c) Voluntary opt-in for sub-threshold vehicles. The Client may, at its election, set the toggle to "Tachograph Applicable" in respect of any vehicle with a recorded gross vehicle weight of 3,500kg or below. The Client acknowledges that a vehicle at or below the Tachograph Threshold Weight may nonetheless fall within scope of tachograph requirements, including where the vehicle forms part of a combination whose aggregate weight exceeds the threshold, and that the default configuration will not monitor such a vehicle unless the Client positively elects otherwise under this Clause 5.3(c). The Company gives no prompt, warning, or indication that any such election may be required.

(d) Effect of a Tachograph Exemption Declaration. Where a Tachograph Exemption Declaration is in force for a vehicle, the Enforcement Matrix shall disapply Tachograph Calibration monitoring in respect of that vehicle only, such that no Vehicle Lock will be applied to that vehicle by reason of the absence or expiry of a Tachograph Calibration record. All other Tier 1A, Tier 1B, and Tier 2 monitoring continues to apply to that vehicle without modification.

(e) Client warranty and sole liability. The Client warrants, represents, and undertakes on a continuing basis that every Tachograph Exemption Declaration it makes is accurate, made in good faith on informed grounds, and correctly reflects the applicable statutory position for that vehicle and the operations for which it is deployed, and that it will withdraw the Declaration immediately upon the vehicle ceasing to be exempt, whether by reason of a change of vehicle, a change in the nature of its deployment, a change in combination, or a change in law. The Company does not monitor for, and will not detect, any such change.

The Client holds sole and exclusive liability for any false, inaccurate, or outdated Tachograph Exemption Declaration. The Company gives no warranty that any vehicle so declared is in fact exempt, and bears zero liability — in accordance with Clauses 2.3(o) and 5.10 — for any consequence of an incorrect Declaration, including any prohibition, prosecution, fixed penalty, Traffic Commissioner action, insurance repudiation, or O-Licence consequence arising from the deployment of a non-exempt vehicle without valid calibration where the Platform did not lock that vehicle by reason of the Client's own Declaration. The indemnity at Clause 2.6(f) applies.

(f) Audit Log. Every setting, amendment, and withdrawal of the toggle is recorded in the Audit Log in accordance with Clause 5.12, capturing the registration mark, the prior and new toggle state, any stated ground where the Platform captures one, the identity of the individual user account performing the action, and the date and time.

5.4 Automated Effect on Expiry — Blocking Credentials and Flag-only Credentials

The automated effect of the expiry, lapse, staleness, revocation, or absence of a Compliance Credential depends on whether it is a Blocking Credential or a flag-only credential, as determined by Clause 5.1A.

(a) Blocking Credentials. Upon the expiry, lapse, staleness, or absence of a Blocking Credential (Clause 5.1A(b)) according to the data held within or relayed into the Compliance Module, the Enforcement Matrix shall automatically and immediately:

(i) where the credential is fleet-level insurance (employers' liability, public liability, or goods-in-transit), suspend the Client's entire Dispatch Queue, such that no further recovery jobs — native or Towpal Leads — are routed to, offered to, or capable of acceptance by the Client or any Operator;

(ii) where the credential is a vehicle-level MOT or VED (Clause 5.7), apply a Vehicle Lock to that vehicle only; and

(iii) where the condition is an Operator Stale Check (Clause 5.13), apply an Operator Lock to that Operator only.

(b) Flag-only credentials. Upon the expiry, lapse, revocation, or absence of any flag-only credential (Clause 5.1A(c)), the Enforcement Matrix shall surface an adverse status or alert to the Client, and shall attempt a Courtesy Attempt under Clause 5.8, but shall not automatically suspend the Dispatch Queue and shall not automatically lock the affected vehicle, asset, or Operator. Standing the affected vehicle, asset, or Operator down is the Client's responsibility (Clauses 5.1A(a), 5.14).

(c) Notification. In either case the Platform will attempt to surface the lapsed status to the Client's registered account contact, subject in its entirety to Clause 5.8.

Where a Blocking Function applies, it is strict. No grace period, tolerance window, transitional period, advance-warning obligation, or discretionary override applies to a Blocking Credential, and none shall be implied; the block takes effect at expiry irrespective of the time of day, the day of the week, or whether the Client has any live or in-progress job. Where only the Flagging Function applies, the Platform does not block, and the Client must act on the flag itself.

5.5 Tier 1A — Self-Certification and Blind Reliance

This Clause governs the Company's treatment of Self-Certified Credentials in its entirety.

(a) The mechanism. For each Tier 1A Credential, the Client: (i) uploads a document file to the Compliance Module; and (ii) inputs an expiry date. Nothing further is required, and nothing further occurs.

(b) The document is stored, never read. The uploaded file is stored as an inert record for the Client's own convenience and audit purposes. It is not read, opened, examined, parsed, extracted, checked, or looked at by the Company or by the Enforcement Matrix for any purpose whatsoever. The Company does not know, and has no means of knowing, what any uploaded file contains, whether it is genuine, whether it is legible, whether it relates to the credential claimed, whether it relates to the Client at all, or whether it is a document of any kind.

(c) Blind reliance on the inputted date. The Enforcement Matrix operates exclusively upon the expiry date inputted by the Client, and upon nothing else. The Company:

(i) relies upon that inputted date absolutely, automatically, and without verification, question, cross-check, or independent enquiry of any kind;

(ii) does not compare the inputted date against the uploaded document, against any register, or against any other source;

(iii) has no knowledge of, and no means of discovering, whether the inputted date is true, false, mistaken, mis-keyed, fabricated, or fraudulent; and

(iv) applies the inputted date as fact for enforcement purposes regardless of its truth.

The Client acknowledges that the inputted date is the sole operative datum, that a false date will produce a false enforcement outcome, and that the Company will neither detect nor prevent this.

(d) Client warranty — accuracy of self-certified data. The Client warrants, represents, and undertakes on a continuing basis throughout the Subscription Term that:

(i) every expiry date it inputs is true, accurate, and current, and corresponds exactly to the expiry date of a genuine, subsisting, and valid credential actually held by the Client;

(ii) every document it uploads is genuine, authentic, unaltered, and relates to the credential and the entity claimed;

(iii) it holds, and will continue to hold, every credential it records, irrespective of what the Compliance Module contains; and

(iv) it will correct any inputted date immediately upon becoming aware of any inaccuracy, and will update the Compliance Module immediately upon the expiry, suspension, revocation, curtailment, cancellation, or repudiation of any credential, whether or not the inputted expiry date has been reached and whether or not any Courtesy Attempt has been made or received.

(e) False entry is a material breach. Any false, fabricated, forged, altered, backdated, post-dated, knowingly inaccurate, or recklessly inaccurate entry of an expiry date, and any upload of a forged, altered, or non-genuine document, constitutes a MATERIAL BREACH of this Agreement, entitling the Company to terminate immediately and without a cure period under Clauses 11.1(h) and 11.2, and to exercise every remedy available to it at law or in equity.

(f) Full indemnity. The Client shall fully and effectively indemnify, defend, and hold harmless the Company, its directors, officers, employees, contractors, and agents against any and all third-party claims, actions, proceedings, losses, damages, costs, expenses (including legal fees on a solicitor-and-client basis), fines, penalties, and liabilities of any nature arising out of or in connection with any false, inaccurate, incomplete, expired, forged, or misleading expiry date or document recorded by or on behalf of the Client — including without limitation any claim, action, or proceeding brought against the Company by any End-User, insurer, regulator, Traffic Commissioner, enforcement authority, motor club, contracting counterparty, or other third party who suffers loss, or takes action, in reliance upon or in consequence of the Client having been permitted to operate through the Platform on the strength of that entry. This indemnity is in addition to and does not limit the indemnity at Clause 2.6, and survives termination.

(g) No detection, no duty to detect. For the avoidance of all doubt, the Company owes no duty — in contract, tort, or otherwise — to detect, identify, question, investigate, or act upon any false or inaccurate entry, and no such duty shall be implied from the existence of the Compliance Module, the Approval Workflow, the Enforcement Matrix, the Audit Log, any Courtesy Attempt, or any right reserved under Clause 5.9(d).

5.6 Tier 1B — The Approval Workflow and the Client's 100% Validation Liability

This Clause governs the Company's treatment of Operator Documents and the Approval Workflow in its entirety.

(a) What the Approval Workflow is. The Compliance Module provides the Client with workflow tools — a "digital clipboard" — enabling a Client Admin to view, record, approve, reject, revoke, and re-approve the Client's own Operators' Operator Documents, and to record associated expiry dates.

(b) What the Approval Workflow is not. The Approval Workflow is a record-keeping and administrative convenience made available to the Client for the Client's own internal use. It is not:

(i) an approval, vetting, screening, or verification service provided by the Company;

(ii) a representation that the Company has reviewed, seen, checked, or formed any view on any Operator Document, any Operator, or any Client Approval;

(iii) a statement of the legal, regulatory, insurance, or accreditation requirements applicable to the Client's Operators, or a complete or sufficient checklist of them (Clause 5.1(f) applies); or

(iv) any assumption by the Company of any responsibility for the competence, entitlement, honesty, identity, right to work, or fitness to drive of any Operator.

(c) The Company's absolute non-involvement. The Company plays no part in any Client Approval. The Company:

(i) does not view, open, read, examine, or look at any Operator Document for any purpose;

(ii) does not review, assess, verify, authenticate, or check any Operator Document, or any expiry date recorded against it;

(iii) does not approve, reject, endorse, clear, or pass any Operator Document or any Operator, and holds no view whatsoever on any of them;

(iv) does not vet, screen, or assess any Operator, and is not an employment agency, employment business, vetting service, or screening service; and

(v) does not select, appoint, authorise, control, supervise, direct, or instruct any Client Admin, each of whom is appointed, authorised, controlled, and supervised solely by the Client and acts solely as the Client's representative.

(d) What clicking "Approve" means — the Client's attestation. A Client Approval is an attestation by the Client, made by the Client's own representative, in the Client's own account, applying the Client's own criteria. It is not, and shall never be construed as, an approval granted by, endorsed by, participated in by, or known to the Company.

When a Client Admin records a Client Approval in respect of an Operator Document, the Client thereby attests, warrants, and represents that:

(i) an appropriately competent and authorised person appointed by the Client has actually examined the relevant Operator Document;

(ii) that person has satisfied themselves that the Operator Document is genuine, authentic, unaltered, current, and valid, and that it relates to the Operator against whom it is recorded;

(iii) the expiry date recorded is true and accurate and corresponds exactly to the expiry date of that genuine document;

(iv) the Client has applied its own criteria and its own independent judgement in determining that the Operator Document is sufficient for the Client's purposes and for the deployment of that Operator; and

(v) the Client has satisfied itself independently of the Platform that the Operator holds every credential, entitlement, and qualification required by law, by the Client's insurers, by the Client's O-Licence undertakings, and by the Client's own contracts, whether or not that credential is recorded within the Compliance Module.

(e) The Client assumes 100% liability for the validation. Upon a Client Admin recording a Client Approval, the Client — in its capacity as employer or engager of the Operator, and as Data Controller — assumes ONE HUNDRED PERCENT (100%) of the legal liability for that validation, and for every consequence flowing from it. The Client acknowledges and agrees that:

(i) the validation is the Client's act alone. The Company neither performs it, participates in it, contributes to it, reviews it, nor has any knowledge of it;

(ii) the Company assumes ZERO liability — whether in contract, tort (including negligence), breach of statutory duty, misrepresentation, restitution, or otherwise — where a Client Admin records a Client Approval in respect of an Operator Document which is forged, counterfeit, altered, expired, invalid, revoked, suspended, fraudulent, belongs to another person, or is in any way defective, insufficient, or misleading;

(iii) the Company assumes ZERO liability for the deployment of any Operator who — notwithstanding a subsisting Client Approval — is disqualified, unlicensed, without appropriate entitlement, without valid CPC, without right to work, incompetent, dishonest, impersonating another person, or otherwise unfit to drive or work; and

(iv) the Enforcement Matrix will not, and cannot, detect any of the matters at (ii) or (iii). It reads only the fact of a subsisting Client Approval and the Client-inputted expiry date. A green, approved, or unrestricted status in respect of an Operator means only that a Client Admin clicked a button and typed a date. It means nothing else, and the Client shall not treat it as meaning anything else.

(f) Full indemnity — Client Approvals. The Client shall fully and effectively indemnify, defend, and hold harmless the Company, its directors, officers, employees, contractors, and agents against any and all third-party claims, actions, proceedings, losses, damages, costs, expenses (including legal fees on a solicitor-and-client basis), fines, penalties, and liabilities of any nature arising out of or in connection with any Client Approval, including without limitation any claim arising from the approval of a forged, expired, invalid, or defective Operator Document, or from the deployment of an unfit, unlicensed, or disqualified Operator in respect of whom a Client Approval subsisted. This indemnity is in addition to and does not limit the indemnities at Clauses 2.6 and 5.5(f), and survives termination.

(g) The Client's continuing obligation to act. The Client acknowledges that a Client Approval is a point-in-time attestation and that circumstances change. The Client shall:

(i) revoke a Client Approval immediately upon becoming aware of any matter rendering the underlying Operator Document invalid, or the Operator unfit, unlicensed, disqualified, or otherwise unsuitable; and

(ii) immediately deactivate, suspend, or remove that Operator from the Platform by its own action, and stand that Operator down from all duties.

The Platform will not do this, cannot do this, and must never be relied upon to do this. The Company does not monitor for, and will not detect, any change in any Operator's circumstances.

(h) Audit Log. Every Client Approval, rejection, revocation, and re-approval — recording the Operator, the document type, the identity of the Client Admin, and the date and time to the second — is recorded in the Audit Log in accordance with Clause 5.12. The Client acknowledges that the Audit Log is conclusive evidence of who attested to what, and when.

(i) Prohibited content. The Client shall not record, upload, or store within the Approval Workflow any material prohibited by Clause 14.2(f), including any DVLA check code, outcome flag, fitness determination, driving offence record, endorsement code, penalty point count, disqualification particular, or conviction detail. The digital clipboard is for documents evidencing entitlement and qualification. It is not, and shall not be used as, a repository for driving records or offence data. Clause 14.2(f)(i) to (iii) and the indemnity at Clause 2.6(i) apply to any breach.

5.7 Tier 2 — MOT and Road Tax: Vehicle Data Aggregator Relay

(a) The data chain. MOT (VT20) and Road Tax (VED) status are not retrieved by the Platform directly from any Government Data Source. They are retrieved from the Vehicle Data Aggregator (UK Vehicle Data Ltd) — an independent third-party commercial data aggregator — which in turn sources that data from a Government Data Source operated by the DVSA or DVLA respectively. The data therefore passes through two independent third-party links before reaching the Platform: first the Government Data Source, then the Vehicle Data Aggregator. The Company owns, operates, and controls neither link. In relaying that data into the Enforcement Matrix, the Company acts as a mere conduit at the end of that chain.

(b) Vehicle Lock at zero days. If a Tier 2 Credential is not renewed, and that renewal is not reflected in the Aggregator Data returned to the Platform, by the expiry date indicated by that data, the Enforcement Matrix shall, on the day of expiry and at zero days, automatically apply a Vehicle Lock to that vehicle. A locked vehicle cannot be selected by any Operator, cannot be assigned to or accept any job (whether native or a Towpal Lead), and remains locked until resolved under Clause 5.9.

The Vehicle Lock operates automatically and unconditionally at zero days regardless of whether any Courtesy Attempt was generated, issued, transmitted, delivered, received, opened, read, understood, or acted upon, and regardless of whether any Courtesy Attempt was made at all.

(c) Vehicle-level only. A Vehicle Lock under this Clause restricts the affected vehicle only and does not of itself suspend the Dispatch Queue. The Company reserves the right, where a majority of the Client's recorded fleet is subject to concurrent Vehicle Locks, to treat the position as a fleet-level suspension.

(d) "As is" reliance on the Vehicle Data Aggregator — express disclaimer. The Client acknowledges and expressly agrees that:

(i) the Company relies upon the Vehicle Data Aggregator and its application programming interface strictly on an "as is" and "as available" basis. The Company does not generate, own, control, verify, audit, correct, second-guess, or warrant any Aggregator Data, and gives no warranty, representation, or undertaking of any kind as to its accuracy, completeness, correctness, currency, timeliness, continuity, or availability;

(ii) the Vehicle Data Aggregator is a third party wholly outside the Company's control, and both it and the Government Data Sources from which it draws are subject to error, omission, mis-keying, registration-mark mismatch, mismatched or transposed records, latency between a real-world event and its appearance in the data, caching and refresh lag introduced by the aggregator itself, scheduled and unscheduled downtime, rate limiting, throttling, quota exhaustion, API interface change, versioning change, deprecation, suspension, and withdrawal — at either link in the chain;

(iii) THE COMPANY BEARS ZERO LIABILITY, HOWSOEVER ARISING, FOR:

(A) any downtime, outage, unavailability, latency, delay, throttling, or rate limiting of the Vehicle Data Aggregator or its API;

(B) any inaccurate, incomplete, stale, corrupted, mismatched, or erroneous data returned by the Vehicle Data Aggregator, whether the error originated with the aggregator or with the underlying Government Data Source;

(C) any Vehicle Lock applied, or not applied, in consequence of any of the foregoing — including without limitation (1) a Vehicle Lock applied to a vehicle whose MOT or VED was in fact valid and current, because the Aggregator Data had not updated, was cached, was delayed, or was in error; and (2) the absence of a Vehicle Lock on a vehicle whose MOT or VED had in fact expired, because the Aggregator Data indicated otherwise, was stale, was unavailable, or was not returned at all; and

(D) any act, omission, insolvency, breach, suspension of service, change of terms, price change, or cessation of the Vehicle Data Aggregator, including any interruption to Tier 2 monitoring arising from the Company's relationship with that aggregator coming to an end for any reason;

(iv) the Client acquires no defence, and is relieved of no obligation, by reason of the Aggregator Data (or any underlying Government Data Source) indicating a vehicle to be compliant. Clause 5.1(d) applies with full force. The Client remains solely responsible for ensuring that every deployed vehicle holds a current MOT and valid VED irrespective of what the Platform relays, records, or permits; and

(v) where the Vehicle Data Aggregator is unavailable, returns no data, or returns data the Platform cannot parse, the Platform may, at the Company's sole discretion, retain the last-known status, apply a precautionary Vehicle Lock, or suspend Tier 2 monitoring for the affected vehicle or fleet. The Company bears no liability for any of those outcomes, and the Client shall have no claim in respect of a precautionary lock or a lapse in monitoring so arising.

(e) Substitution of aggregator. The Company may change, add, or remove the Vehicle Data Aggregator, or revert to querying a Government Data Source directly, at any time on notice under Clause 5.2(d), by updating Schedule 6 Part A.3. Any such change does not require the Client's consent, and the disclaimers in this Clause 5.7 apply equally to any substitute aggregator or direct source.

5.8 Courtesy Attempts — All Credentials

This Clause applies to every Compliance Credential monitored by the Enforcement Matrix, whether Tier 1A, Tier 1B, or Tier 2.

(a) Attempted courtesy behaviour — system configuration, not obligation. The Platform is configured to attempt to generate and issue Courtesy Attempts — comprising attempted user-interface banners displayed within the Compliance Module dashboard and attempted email notifications to the Client's registered account contact — at one or more points prior to the expiry date applicable to a Compliance Credential, the number, timing, and spacing of which are determined by the Company in its sole discretion and may differ between credentials, and may consist of a single attempt.

This Clause 5.8(a) is a description of an attempted courtesy automated system behaviour. It is expressly NOT, and shall in no circumstances be construed as, a warranty, undertaking, guarantee, representation, promise, assurance, service level, or contractual obligation of any kind on the part of the Company to generate, display, issue, transmit, deliver, or successfully communicate any warning, banner, or notification whatsoever. The Company owes NO DUTY TO WARN. This Clause is subject in its entirety, and without qualification or exception, to Clause 5.8(e).

(b) Source of the warning date. The Client acknowledges that, for Tier 1A and Tier 1B Credentials, any Courtesy Attempt is calculated from the expiry date the Client itself inputted. A Courtesy Attempt is therefore only ever as accurate as the Client's own data entry. Where the Client has inputted an incorrect date, any Courtesy Attempt will be issued at an incorrect time, or not at all, and the resulting enforcement outcome will follow the inputted date and not the truth. The Company bears no liability for this, in accordance with Clauses 5.5(c) and 5.10(f).

(c) Recipients. Courtesy Attempts are configured to be directed to the Client's registered account contact and, where the Client has so configured the Platform, to relevant Client Admins and to Operators. The Client is solely responsible for maintaining accurate, current, and monitored registered contact details at all times, and accurate vehicle registration marks, and for ensuring that any mailbox to which Courtesy Attempts are directed is actually read.

(d) Blocking applies regardless of any Courtesy Attempt. Where the Blocking Function applies (Clause 5.1A(b)), the Compliance Suspension, Vehicle Lock, or Operator Lock operates automatically and unconditionally upon expiry, and does so regardless of whether any Courtesy Attempt was generated, displayed, transmitted, delivered, received, opened, read, understood, or acted upon, and regardless of whether any Courtesy Attempt was made at all. The operation of the lock is not conditional upon, and is in no way qualified, deferred, or suspended by, the attempted courtesy behaviour described at Clause 5.8(a).

(e) Maximal disclaimer — generation, display, transmission, delivery, receipt, and reading. Notwithstanding Clause 5.8(a), and to the fullest extent permitted by applicable law:

(i) the Company gives no warranty, representation, guarantee, undertaking, assurance, or promise of any kind, express or implied, that any Courtesy Attempt will be generated, triggered, calculated, composed, rendered, displayed, queued, transmitted, dispatched, routed, delivered, received, opened, read, understood, or acted upon, whether at all, at any particular time, on any particular date, at any particular interval, by any particular channel, or to any particular recipient. The Company does not guarantee generation. The Company does not guarantee display. The Company does not guarantee transmission. The Company does not guarantee delivery. The Company does not guarantee receipt. The Company does not guarantee reading.

(ii) the Client acknowledges that the generation and delivery of a Courtesy Attempt depends upon a chain of matters substantially or wholly outside the Company's control, including without limitation: the accuracy of the expiry date the Client itself inputted; the availability, accuracy, and latency of any Government Data Source; the correctness and currency of the vehicle registration marks recorded by the Client; the correctness, currency, and monitoring of the Client's registered contact details; the Client's own email, mail-server, mailbox, storage-quota, filtering, quarantine, and spam configuration; carrier, network, and deliverability conditions; browser, session, cache, and rendering behaviour affecting the display of any user-interface banner; whether any Client Admin logs in at all; device settings, notification permissions, do-not-disturb states, battery-optimisation behaviour, application uninstallation, and operating-system restrictions; staff turnover, absence, and mailbox monitoring practices at the Client; and any general network, hosting, or third-party service failure;

(iii) no failure, defect, delay, non-generation, non-display, non-delivery, mis-delivery, partial delivery, or complete absence of any Courtesy Attempt shall: (A) give rise to any liability on the part of the Company of any kind; (B) postpone, defer, suspend, invalidate, or provide grounds to reverse any Compliance Suspension, Vehicle Lock, or Operator Lock; (C) constitute a breach of this Agreement or of any duty owed by the Company; (D) constitute a defence, excuse, mitigation, or answer to any lock or to any consequence flowing from it, including any consequence under Clauses 4.3(f), 5.10, 5.11, or 7.5; or (E) found any claim in contract, tort (including negligence), breach of statutory duty, misrepresentation, restitution, or otherwise;

(iv) the Client acknowledges that it has not entered into this Agreement in reliance upon the attempted courtesy behaviour described at Clause 5.8(a), that the availability of that behaviour formed no part of the consideration for the Fees, and that it would have entered into this Agreement on identical terms had that behaviour not existed; and

(v) the Company may modify, suspend, degrade, reduce, re-interval, or discontinue the Courtesy Attempt behaviour described at Clause 5.8(a), in whole or in part, at any time and without notice, consultation, or liability, without prejudice to the continued operation of the Blocking Function at Clauses 5.1A(b), 5.7, and 5.13.

(f) The burden does not move. Courtesy Attempts are a discretionary convenience only and do not transfer to the Company any part of the Client's obligation to monitor, renew, and maintain its own Compliance Credentials, or to monitor the recency of every Operator's Last DVLA Check Date. The burden of monitoring the currency of its own Compliance Credentials rests entirely and exclusively with the Client. The Company has no obligation to warn, and the Client shall not rely on being warned.

5.9 Lifting a Compliance Suspension, Vehicle Lock, or Operator Lock

(a) Tier 1A. A suspension or lock arising from a Self-Certified Credential lifts automatically upon the Client uploading a replacement document and inputting a new expiry date bearing a future date. The Company does not review the replacement document or check the new date — Clauses 5.5(b) and 5.5(c) apply identically to any renewal. The lock lifts because a future date has been inputted, and for no other reason.

(b) Tier 1B. An Operator Lock arising from an Operator Document lifts automatically upon a Client Admin recording a fresh Client Approval with a future expiry date. Clause 5.6(d) applies identically to any re-approval, and the Client's attestation and 100% liability attach afresh. An Operator Lock arising from a Stale Check lifts upon the Client recording a new last_dvla_check_date within the Check Recency Period, in accordance with Clause 5.13. The Client warrants that it will not record a Last DVLA Check Date in respect of a check it has not actually performed.

(c) Tier 2. A Vehicle Lock arising from a Government-Sourced Credential lifts automatically upon the Aggregator Data returned by the Vehicle Data Aggregator reflecting a renewed status for that vehicle. The Client acknowledges that this is subject to the update, caching, and refresh cycle of the Vehicle Data Aggregator, and behind it the update cycle, processing time, and availability of the DVSA or DVLA (as applicable), for none of which the Company accepts any responsibility whatsoever, and that a lock may accordingly persist after the Client has in fact renewed the credential in the real world.

(d) Fraud response — a right, not a review, and not a duty. The Company reserves the right, at its absolute discretion, to suspend, lock, or decline to lift any suspension or lock, and to require the Client to produce evidence, where the Company forms a suspicion that any entry, document, date, or Client Approval is fraudulent, forged, or knowingly false. The Client acknowledges and agrees that this right:

(i) exists solely for the protection of the Company's own commercial, reputational, and legal interests, and for the protection of End-Users and the Company's wider client base. It is not a service provided to the Client and confers no benefit on the Client;

(ii) is not, and shall never be construed as, a review, verification, validation, audit, or check of any document, date, or approval, and does not qualify, dilute, or create any exception to Clause 5.1(b), Clause 5.5(c), or Clause 5.6(c);

(iii) is exercisable only if, when, and to the extent the Company chooses, in its absolute discretion. The Company is under NO DUTY — in contract, tort, or otherwise — to form any suspicion, to look for any fraud, to investigate any matter, or to exercise this right at all, and no such duty shall be implied from the existence of this Clause 5.9(d), from any prior exercise of the right, or from any failure to exercise it;

(iv) creates no expectation, course of dealing, or precedent. Exercise on one occasion imports no obligation to exercise on any other, in accordance with Clause 15.4; and

(v) carries zero liability for the Company — for exercising this right, for declining to exercise it, for exercising it wrongly, or for failing to detect any fraud whatsoever.

Where the Company exercises this right and the Client submits evidence, the Client warrants the accuracy of that evidence, the exercise is recorded in the Audit Log, and Clauses 2.6(f) and 5.10 apply.

(e) General. The Client further acknowledges that: (i) reinstatement may be subject to a reasonable processing interval following upload or data refresh, and the Company gives no warranty as to the speed of reinstatement; and (ii) no compensation, credit, or make-good in respect of leads, jobs, or revenue foregone during any suspension or lock shall be due, and any leads arising within the Assigned Territory during a fleet-level suspension are irretrievably lost.

5.10 Zero Liability for Loss of Earnings and Operational Downtime

The Client expressly acknowledges and irrevocably agrees that the Company shall bear absolutely no liability of any kind — whether in contract, tort (including negligence), breach of statutory duty, restitution, or otherwise — for any loss whatsoever arising from or in connection with any Compliance Suspension, Vehicle Lock, or Operator Lock, whether arising under Clause 5.4, 5.7, or 5.13, including without limitation:

(a) lost earnings, lost revenue, lost profit, or lost margin;

(b) lost jobs, lost Towpal Leads, or lost dispatch opportunities within the Assigned Territory during the period of suspension or lock;

(c) operational downtime, idle driver, Operator, vehicle, or equipment cost;

(d) loss of business, goodwill, reputation, or commercial opportunity;

(e) any breach by the Client of any contract with any third party — including any motor club, insurer, police recovery contract, main dealer, or End-User — arising from the Client's inability to accept, attend, or complete a job during any suspension or lock, and any liquidated damages, service credits, penalties, or contract termination suffered by the Client in consequence;

(f) any loss arising where the suspension or lock was triggered by an inaccurate, incomplete, mis-keyed, or out-of-date expiry date inputted by or on behalf of the Client, including where the underlying credential was in fact valid and current at the relevant time;

(g) any loss arising where the suspension or lock was triggered by the absence, lapse, or revocation of a Client Approval, including where the underlying Operator Document was in fact valid and current and the Client Admin had simply not recorded an approval;

(h) any loss arising where a Vehicle Lock was triggered, or not triggered, by reason of any error, inaccuracy, omission, staleness, delay, latency, outage, unavailability, or cessation of the Vehicle Data Aggregator or of any Government Data Source, in accordance with Clause 5.7(d);

(i) any loss arising from the absence, failure, non-generation, non-display, or non-delivery of any Courtesy Attempt, in accordance with Clause 5.8(e);

(j) any loss arising from an incorrect Tachograph Exemption Declaration made by the Client, in accordance with Clause 5.3(e); and

(k) any loss arising from an Operator Lock triggered by a Stale Check, including where the Operator's driving record was in fact clear and the Client had simply not recorded a current Last DVLA Check Date.

No MRR Fee, Exclusivity Premium, Prepaid Territory Fee, or other Fee shall be refunded, reduced, waived, credited, or abated in respect of any period during which any Compliance Suspension, Vehicle Lock, or Operator Lock is in force. The Client remains liable for all Fees falling due throughout any such period, and no extension of any Multi-Year Term shall be granted on account of any such period.

5.11 Prolonged Compliance Suspension — Exclusivity Forfeiture and Termination

The Client acknowledges that a fleet-level Compliance Suspension — which, as at the Revision Date, arises automatically only on the expiry of a fleet-level insurance Blocking Credential (Clause 5.1A(b)(iii)), or on the Company's exercise of a suspension right elsewhere in this Agreement — has consequences beyond the suspension itself:

(a) Volume Impact — no job can be completed during a fleet-level Compliance Suspension, because no job can be dispatched. The Client accepts that a Compliance Suspension is therefore likely to cause it to fail its Minimum Operational Volume, and that such failure shall be treated as a failure in the ordinary course under Section 7 without any allowance, adjustment, or excuse on account of the suspension;

(b) Exclusivity Forfeiture — where a fleet-level Compliance Suspension remains in force for a continuous period of [14] calendar days, the Company shall be entitled, at its sole discretion and upon written notice, to revoke the Client's Exclusive Territory Rights, releasing the Assigned Territory and its associated Towpal Lead routing to the open market, without any obligation to compensate the Client and without refund of any Exclusivity Premium; and

(c) Event of Default — where a fleet-level Compliance Suspension remains in force for a continuous period of [30] calendar days, or where the Client records any falsified, forged, or knowingly inaccurate Compliance Data or Client Approval at any time, this shall constitute an Event of Default under Clause 11.1(g) or 11.1(h) as applicable, entitling the Company to terminate this Agreement in accordance with Section 11.

5.12 The Audit Log

(a) Scope. The Compliance Module maintains an append-only Audit Log which records such of the following actions as are enabled within the Platform from time to time, and in respect of each action so recorded captures: (i) the identity of the individual user account performing it; (ii) the date and time; and (iii) the substance of the action. The categories the Audit Log is designed to record include:

— every input, amendment, or correction of any expiry date (Tier 1A and Tier 1B), capturing the prior and new value;

— every document upload, replacement, or deletion;

— every Client Approval, rejection, revocation, and re-approval recorded through the Approval Workflow, capturing the Operator, the document type, and the identity of the Client Admin;

— every setting, amendment, or withdrawal of the Tachograph Exempt toggle, capturing the registration mark, the prior and new state, and any stated ground where captured;

— every entry or amendment of a last_dvla_check_date;

— every exercise of the right reserved at Clause 5.9(d), and any evidence submitted in response; and

— every Compliance Suspension, Vehicle Lock, and Operator Lock applied and lifted, and the triggering datum.

(b) Unalterable. The Audit Log cannot be edited, overwritten, suppressed, or deleted by the Client, and any attempt to do so constitutes a material breach under Clause 3.2(h) and an Event of Default under Clause 11.1(h).

(c) Evidential status. In respect of the events it does record, the Audit Log shall be strong evidence of who recorded or approved what, and when, in any dispute, investigation, or proceeding, absent manifest error. The Client acknowledges that the Audit Log records only those event categories enabled within the Platform from time to time, and that the absence of an entry is not evidence that an event did not occur where logging of that category was not enabled.

(d) Retention and production. The Company shall retain the Audit Log for the duration of the Subscription Term and for [6] years thereafter, and may produce it to any regulator, court, insurer, or enforcement authority upon lawful request without the Client's further consent.

(e) Not a monitoring undertaking. The Client acknowledges that the Audit Log is a passive record. The Company does not review, monitor, analyse, or act upon it, owes no duty to do so, and no such duty shall be implied from its existence. Clause 5.5(g) applies.

5.13 Driver Licence Compliance — Process-Only Enforcement on Check Recency

(a) The Platform processes a date, and nothing else. The Compliance Module records against each Operator a Last DVLA Check Date — a timestamp only, denoting the date on which the Client last independently reviewed that Operator's driving licence record via the DVLA Portal. The Platform holds no other information whatsoever relating to any Operator's driving record.

For the avoidance of all doubt, and by design, the Platform does not hold, receive, request, store, process, or have any visibility of: any DVLA check code; any pass, fail, or other outcome flag; any assessment, determination, or record of fitness to drive; any endorsement, endorsement code, or offence record; any penalty point count; any disqualification particular; any conviction detail; or any offence narrative. The Last DVLA Check Date records that a process occurred. It records no outcome of any kind.

(b) The Company performs no part of the check. The Company does not access the DVLA Portal, holds and uses no check code, does not view, retrieve, or receive any driving licence record, does not assess, interpret, score, or evaluate any driving record, and does not determine — and holds no view on — whether any Operator is fit to drive. The Company is not a licence-checking bureau and does not hold itself out as one.

(c) The Client is the sole Controller and sole checker. The Client acknowledges and agrees that it alone, as Data Controller:

(i) is responsible for obtaining each Operator's consent and check code as required, for accessing the official DVLA Portal, and for reviewing that Operator's physical driving licence record — including any endorsement, penalty point, disqualification, restriction, or entitlement limitation disclosed by it;

(ii) is responsible for determining, documenting, and applying its own fitness-to-drive criteria to that record, and for acting upon that determination, including by standing an Operator down, restricting their duties, revoking their Client Approval, or removing them from the Platform entirely;

(iii) is responsible for recording the Last DVLA Check Date within the Compliance Module promptly following each such review, and for retaining all check outcomes within its own systems, outside the Platform; and

(iv) is responsible for repeating that review at intervals no less frequent than the Check Recency Period, and more frequently where its own risk assessment, its insurers, its O-Licence undertakings, or applicable law so require.

(d) Enforcement is on recency alone. The Enforcement Matrix monitors the Last DVLA Check Date as a Tier 1B Credential and applies an Operator Lock, automatically and at zero days in accordance with Clause 5.4, where:

(i) the elapsed period since the recorded Last DVLA Check Date exceeds the Check Recency Period of 180 days, such that the record becomes a Stale Check; or

(ii) no Last DVLA Check Date has been recorded for that Operator at all.

A Stale Check is an administrative condition. It denotes only that a required process is overdue. It is not, and shall not be represented, construed, or communicated by the Client as, any adverse finding, allegation, inference, or suggestion regarding the affected Operator's driving record, conduct, or fitness to drive.

(e) The critical limitation — the Platform does not know whether the driver is fit. The Client expressly acknowledges and agrees that:

(i) a current Last DVLA Check Date means only that the Client says a check was performed within the last 180 days. It means nothing else. It is not, and shall never be relied upon as, an indication that the check was actually performed, that it was performed competently, that the record was clear, that the Operator holds valid entitlement, that the Operator is not disqualified, or that the Operator is fit to drive;

(ii) the Enforcement Matrix will NOT apply an Operator Lock to an Operator whom the Client has checked and found to be disqualified, endorsed, unlicensed, or otherwise unfit, because that Operator's Last DVLA Check Date will be current and their Client Approval will subsist. The Platform has no knowledge of the outcome of any check and is structurally incapable of enforcing upon it;

(iii) it is therefore the Client's absolute and non-delegable responsibility, upon identifying any adverse matter in any Operator's licence record, to revoke that Operator's Client Approval and immediately deactivate, suspend, or remove that Operator from the Platform by its own action, in accordance with Clause 5.6(g), and to stand that Operator down from all duties. The Platform will not do this, cannot do this, and must never be relied upon to do this; and

(iv) the Company accordingly bears zero liability — in accordance with Clauses 2.3(d), 2.3(g), 2.3(h), 2.3(r), and 5.10 — for the deployment of any Operator who is disqualified, unlicensed, without appropriate entitlement, or otherwise unfit to drive, whether or not that Operator's Last DVLA Check Date was current, whether or not a Client Approval subsisted, and whether or not the Platform permitted their deployment. The indemnities at Clauses 2.6(g) and 5.6(f) apply.

(f) No inference from a lock. Because enforcement operates solely on the age of a timestamp, an Operator Lock arising under this Clause 5.13 discloses nothing about that Operator save that an administrative check is overdue. The Client shall not represent otherwise to any Operator, insurer, regulator, or third party.

5.14 Client Warranties Regarding Compliance Data

The Client warrants, represents, and undertakes on a continuing basis throughout the Subscription Term that:

(a) every Compliance Credential, inputted expiry date, calibration record, certificate, timestamp, declaration, Client Approval, and document recorded within the Compliance Module is true, accurate, complete, current, authentic, and not misleading at the time of recording;

(b) it will update the Compliance Module immediately upon becoming aware of the expiry, suspension, revocation, curtailment, cancellation, or repudiation of any Compliance Credential, whether or not the inputted expiry date has been reached, whether or not any Government Data Source reflects the change, and whether or not any Courtesy Attempt has been made or received;

(c) it holds, and will continue to hold, all Compliance Credentials required by law or by its own regulators, insurers, and accreditation bodies, irrespective of what the Compliance Module records, relays, or permits;

(d) every Tachograph Exemption Declaration it makes is accurate and made in good faith on informed grounds, in accordance with Clause 5.3(e);

(e) every Client Approval recorded by a Client Admin is made in accordance with, and satisfies in full, the attestation at Clause 5.6(d);

(f) every Last DVLA Check Date it records corresponds to a review of that Operator's licence record via the DVLA Portal actually performed by the Client on that date, in accordance with Clause 5.13;

(g) it will not deploy, and will not permit any Operator to deploy, any vehicle subject to a Vehicle Lock, any Operator subject to an Operator Lock, or any asset subject to an asset restriction, on any job — whether or not that job was obtained through the Platform;

(h) it will not deploy any vehicle lacking a current MOT or valid VED, notwithstanding that the Platform has not applied a Vehicle Lock to that vehicle;

(i) it will not deploy any Operator who is disqualified, unlicensed, without appropriate entitlement or CPC, without right to work, impersonating another person, or otherwise unfit to drive or work, notwithstanding that the Platform has not applied an Operator Lock to that Operator and notwithstanding any subsisting Client Approval, in accordance with Clauses 5.6(e) and 5.13(e); and

(j) it has obtained all necessary consents, notices, and lawful bases required to record Operator Data, Operator Documents, Licence Check Recency Data, tachograph card data, camera verification captures, and Walkaround Records within the Platform, in accordance with Section 14, and it has not recorded any check code, outcome flag, fitness determination, or offence detail in breach of Clause 14.2(f).

Breach of any warranty in this Clause 5.14 shall constitute a material breach of this Agreement.

5.15 Client Licensing, Permits, and Accreditation

5.15.1 The Client warrants, represents, and undertakes on a continuing basis throughout the Subscription Term that it holds, maintains in force, and complies with all licences, permits, registrations, authorisations, and accreditations required by law or by any competent authority for the recovery, roadside-assistance, transport, storage, and disposal activities it carries out, including (to the extent applicable to its operations):

(a) any Operator's Licence (goods vehicle operator licensing) required by the Traffic Commissioner for the vehicles it operates;

(b) any local authority, police, or highway-authority approved-operator status, licence, or scheme membership required to undertake statutory, police-instructed, or local-authority-instructed recoveries and removals in the areas in which it operates;

(c) PAS 43 (or equivalent then-current) safe-working accreditation for roadside recovery;

(d) any waste carrier registration or environmental permit required where its activities involve the movement or disposal of end-of-life or written-off vehicles or parts; and

(e) any other statutory or regulatory permission applicable to its business.

5.15.2 The Client will not use the Platform for work it is not licensed to perform. In particular, the Client shall not accept, undertake, or hold itself out as able to undertake, through the Platform, any category of recovery for which it does not hold the licences, permits, or approvals required — including, without limitation, police, statutory, or local-authority work for which it is not an approved operator.

5.15.3 PAS 43 evidence. Because the Company's consumer-facing services may describe recovery firms as PAS 43-certified, the Client shall, on request and at onboarding, provide the Company with evidence of its current PAS 43 certification (or equivalent), and shall notify the Company promptly if that certification lapses, is suspended, or is withdrawn. The Client acknowledges the Company may suspend the Client's access to consumer-originated jobs if it ceases to hold valid PAS 43 certification.

5.15.4 The Company does not verify or police the Client's licensing. The Client acknowledges that the Company is a software provider, is not a licensing authority, and does not verify, monitor, or take responsibility for the Client's licences, permits, or approvals beyond the limited PAS 43 evidence step in Clause 5.15.3. Compliance with this Clause 5.15 is the Client's sole and non-delegable responsibility, consistent with Clauses 2.1 and 2.5, irrespective of what the Platform records or permits.

5.15.5 Breach of any warranty or undertaking in this Clause 5.15 shall constitute a material breach of this Agreement, and the indemnity at Clause 2.6 extends to any claim, penalty, or loss arising from the Client's use of the Platform for work it was not licensed, permitted, or accredited to perform.

SECTION 6 — THE MONOPOLY TRAPDOOR: PAYMENT DEFAULT, STRIPE FAILURE, AND TERRITORY FORFEITURE

6.1 Exclusivity Conditional on Payment

Exclusive Territory Rights — including the right to receive exclusive Towpal Lead routing under Clause 4.2(b) — are entirely conditional upon the Client's timely payment of all Fees due under this Agreement and upon the Client maintaining a functioning Connected Stripe Account. Exclusivity is not a vested right; it is a privilege maintained by continued good standing.

6.2 Payment Default — Past-Due Status and Right to Forfeit

(a) Past-due status. In the event that the Client's MRR Fee payment fails, is declined, is charged back, is reversed, or remains unpaid for more than [3] calendar days beyond its due date — including where such failure arises from a decline, dispute, reversal, freeze, or other event affecting the Client's payment method or Connected Stripe Account — the Client's account enters a past-due state, and the Company may (in addition to its rights under Clause 9.4) suspend Platform access pending payment.

(b) Right to forfeit Exclusivity. Where the Client's account remains in a past-due state, the Company shall be entitled, at its discretion and upon written notice (which may be given electronically through the Platform), to forfeit the Client's Exclusive Territory Rights, including all Towpal Lead routing preferences within the Assigned Territory, whereupon the Assigned Territory reverts to the Company's open market and the Company shall be at liberty to offer it, and its associated Towpal Lead routing, to any third party.

(c) No obligation to forbear, no waiver. The Company's continuation of a Client in a past-due state, or any delay in exercising its right to forfeit under Clause 6.2(b), does not waive that right, does not entitle the Client to retain Exclusivity as of right, and creates no course of dealing (Clause 15.4). The Client acknowledges that Exclusivity during a past-due period is permitted as a matter of the Company's forbearance, not held as of right, and that the Company may exercise its forfeiture right at any time while the account remains past due.

6.3 Stripe Connect Onboarding Failure

Where the Client:

(a) fails to complete Stripe Connect onboarding and verification to the Company's technical requirements within [14] days of the Effective Date;

(b) fails Stripe's KYC, AML, or identity verification requirements at any time;

(c) has its Connected Stripe Account rejected, restricted, frozen, reserved, suspended, or terminated by Stripe for any reason; or

(d) fails to maintain a valid, verified Connected Stripe Account capable of receiving payouts throughout the Subscription Term,

then the Client's Exclusive Territory Rights shall be immediately forfeit in accordance with Clause 6.2, and the circumstance shall additionally constitute an Event of Default under Clause 11.1(b), entitling the Company to terminate in accordance with Section 11.

6.4 Reinstatement

Following a forfeiture under Clause 6.2 or 6.3, the Company may, entirely at its discretion, offer to reinstate Exclusivity to the Client upon settlement of all outstanding Fees, restoration of a compliant Connected Stripe Account, and on such revised commercial terms as the Company considers appropriate. The Company is under no obligation to offer reinstatement, and the Assigned Territory — together with its Towpal Lead routing — may by that time have been allocated to a third party.

6.5 No Liability for Forfeiture

The Company shall bear no liability to the Client for any loss of business, revenue, Towpal Leads, or commercial opportunity resulting from a Territory Reversion under this Section 6.

6.6 Application to Multi-Year Terms

For the avoidance of doubt, this Section 6 applies with full force to a Client on a prepaid Multi-Year Term. Where a Multi-Year Term Client's Connected Stripe Account fails within the meaning of Clause 6.3, Exclusivity is forfeit notwithstanding that the Prepaid Territory Fee has been paid, and the refund position is governed exclusively by Clause 9.8.

SECTION 7 — MINIMUM OPERATIONAL VOLUME AND ANTI-SQUATTING PROVISION

7.1 Minimum Volume Obligation

As a condition of maintaining Exclusive Territory Rights, the Client agrees to process through the Platform, on a completed and settled basis, the Minimum Operational Volume specified in Schedule 2 during each calendar month of the Subscription Term. For the avoidance of doubt, completed jobs originating from both the Platform's native dispatch functionality and Towpal Leads shall count towards the Minimum Operational Volume, provided they are completed and settled through the Platform's integrated payment infrastructure.

7.2 Zero or Negligible Activity — Anti-Squatting

The Client acknowledges that the Software Monopoly model depends upon licensed territories being actively worked. Where the Client registers zero completed jobs, or a volume of completed jobs falling below the Minimum Operational Volume specified in Schedule 2, within its Assigned Territory, the Client is treated as squatting on that territory and the remedies at Clause 7.4 apply.

7.3 Monitoring Period

Where the Client fails to meet the Minimum Operational Volume in any single calendar month, the Company shall issue a written Performance Warning Notice to the Client. If the Client fails to meet the Minimum Operational Volume for a continuous period of sixty (60) days from the date of that notice, the Company shall be entitled, at its sole discretion, to exercise the remedies set out in Clause 7.4.

7.4 Remedies for Volume Failure

Upon the expiry of the 60-day monitoring period without adequate remedy by the Client, the Company may, by written notice:

(a) revoke Exclusivity in respect of the Assigned Territory immediately — releasing the postcodes to the open market and ceasing exclusive Towpal Lead routing to the Client within that territory — without any obligation to compensate the Client for the loss of such Exclusivity or future Towpal Leads; and/or

(b) terminate this Agreement in accordance with Section 11 or Section 12, as applicable.

7.5 No Allowance for Compliance Suspension, Vehicle Lock, or Operator Lock

The Client expressly acknowledges that any period during which its Dispatch Queue is subject to a Compliance Suspension, or during which any of its vehicles or Operators are subject to a Vehicle Lock or Operator Lock, under Section 5 shall be counted in the ordinary course for the purposes of this Section 7. No adjustment, extension, allowance, tolerance, or excuse shall be granted in respect of a failure to meet the Minimum Operational Volume caused in whole or in part by any such suspension or lock, whether or not the underlying credential lapse was inadvertent, whether or not any Courtesy Attempt was generated, displayed, or delivered, and whether or not the lock arose from Government Data Source error.

7.6 Platform Records as Authoritative Measure

The job completion and transaction volume data recorded in the Company's system of record — which includes data transmitted via the Towpal Integration and data reflecting periods of Compliance Suspension, Vehicle Lock, and Operator Lock — shall constitute the definitive measure of operational volume for the purposes of this Section 7 and shall prevail in any dispute, absent manifest error.

7.7 No Entitlement to Refund

Subject only to Clause 9.8, no refund of any Exclusivity Premium, MRR Fee, or Prepaid Territory Fee shall be due to the Client upon revocation of Exclusivity under this Section 7. The Client acknowledges that the Exclusivity Premium constitutes consideration for the period during which Exclusivity and Towpal Lead routing were made available — not for any particular volume of leads delivered during that period.

SECTION 8 — STRIPE CONNECT, PAYMENTS, PAYOUT WITHHOLDING, AND MERCHANT OF RECORD

8.1 Payment Infrastructure

The Platform utilises Stripe Connect to facilitate the collection of End-User payments and the routing of funds in respect of completed jobs to the Client and its Operators. The Client acknowledges that:

(a) in respect of Towpal-originated consumer transactions, consumer payments are charged through a Stripe platform account operated by the Company as Towpal Ltd's payment-collection service provider (Clause 8.7(h)), and are then transferred to the Client's Connected Stripe Account and, where applicable, split to Operator Connect accounts, via Stripe Connect. The Company operates that account as a conduit and takes no commission or beneficial interest in the funds (Clause 8.7(h)(ii));

(b) the routing of funds through the platform account before transfer is a payment-processing mechanic and does not alter the Client's status as Merchant of Record for those transactions under Clause 8.5, nor the beneficial ownership of the funds, which (net of Stripe fees and any sum properly withheld) belong to the Client and its Operators; and

(c) all payment processing — including in respect of Towpal-originated transactions — is subject to Stripe's Connected Account Agreement and Stripe's standard terms of service, as amended from time to time by Stripe.

8.2 Payout Withholding Period

All standard End-User transaction funds collected through the Platform — including funds received in respect of Towpal Leads — shall be subject to a mandatory Payout Withholding Period of twenty-four (24) hours from the time of transaction settlement, except for VIP / Partner Jobs, which settle on the weekly cycle described in Clause 8.2A. During the Payout Withholding Period, funds will be held within the Stripe Connect infrastructure and will not be released to the Client's Connected Stripe Account. This withholding period exists to allow the Company and Stripe to assess and accommodate:

(a) End-User refund requests arising from disputed or cancelled jobs, including Towpal-originated jobs subject to Towpal Ltd's consumer-facing cancellation policy;

(b) Late Cancellation Fee adjustments or reversals processed in accordance with the applicable consumer terms;

(c) Chargeback notifications received from Stripe in respect of any transaction, including Towpal-originated transactions; and

(d) any other payment dispute or correction required under this Agreement or Stripe's policies.

8.2A VIP / Partner Jobs — Weekly Payout Cycle

The Client acknowledges that certain jobs it carries out through the Platform are "VIP / Partner Jobs" — jobs performed under the Client's own commercial, membership, or account arrangements (for example police recovery contracts, motor-club, or business-account partners), rather than jobs paid per-transaction by an End-User at the point of service. In respect of VIP / Partner Jobs:

(a) Weekly settlement, not 24-hour. VIP / Partner Job funds are not subject to the 24-hour Payout Withholding Period. They are settled on a weekly payout cycle (as at the Revision Date, a weekly batch processed on [Friday]), such that a VIP / Partner Job completed during a given week is paid out in that week's batch, which may be up to approximately seven (7) days after job completion.

(b) Why. This reflects that VIP / Partner Jobs are billed and reconciled under the relevant partner's commercial arrangement, which the Client (not the Company) holds and administers.

(c) Client's own partner contracts. The commercial terms, pricing, billing, and payment timing of the underlying partner arrangement are matters between the Client and its partner. The Company operates the weekly payout mechanic only, takes no commission or beneficial interest in the funds (Clause 8.7(h)(ii) applies), and gives no warranty as to the partner's payment to the Client.

(d) Operator pay timing. The Client acknowledges that the weekly cycle affects when funds reach the Client, and therefore may affect when the Client pays its Operators for VIP / Partner Jobs. As between the Client and its Operators, the timing and amount of Operator pay is solely the Client's responsibility (consistent with the Operator App terms and Clause 2.5); the Company does not set Operator pay or its timing.

(e) Variation. The Company may vary the weekly payout day or cycle on notice under Clause 5.2(d) / Clause 15.3, without liability, provided any change is applied consistently.

8.3 Release of Funds

Subject to there being no active dispute, chargeback, or refund instruction in respect of a transaction, settled funds shall be released to the Client's Connected Stripe Account upon expiry of the Payout Withholding Period, in accordance with Stripe's standard payout schedule.

8.3A Unclaimed-Territory and Out-of-Bounds Recoveries — Fund Handling

For an Unclaimed-Territory Recovery or an Out-of-Bounds Recovery (Clause 4.2A), where Towpal Ltd sets the consumer price and no Client owns the territory:

(a) the consumer payment is collected through the Company-operated Stripe platform account (Clauses 8.1 and 8.7(h)) and is held for twenty-four (24) hours following job completion before being passed to the Client whose operator accepted and completed the recovery;

(b) the 24-hour hold operates for the same dispute-resolution purpose as the Payout Withholding Period, and the disclaimers in Clauses 8.6 and 5.8(e) apply; and

(c) in respect of such recoveries, the fund-holding and routing are performed by the Company as Towpal Ltd's payment-collection service provider (Clause 8.7(h)), as a conduit taking no commission or beneficial interest; the funds (net of Stripe fees and any sum properly withheld) belong to the accepting Client on completion.

8.3B Manual (Telephone) Dispatch Payments — Two Payment Paths

The Client acknowledges that recoveries it arranges directly with End-Users by telephone ("Manual Dispatch Recoveries"), where payment is collected by a Stripe payment link sent to the End-User, are processed by one of two paths depending on the Client's configuration:

(a) Direct charge (white-label Clients with Connect charges enabled). Where the Client is white-label active with a ready Stripe Connect account, the payment is created as a direct charge on the Client's own Connected Stripe Account, such that the full amount is collected into the Client's own Stripe balance. The Company takes no application fee and no job revenue; the Operator's share is transferred out of the Client's balance via the Platform's escrow mechanism. In this path the Company does not hold the funds at any point.

(b) Platform-account collection (all other Clients). Where the Client is not white-label active, or its Connect account is not onboarded or does not have charges enabled, the payment is collected through the Company-operated Stripe platform account (Clauses 8.1 and 8.7(h)), displaying the Client's name via branding settings, and routed to the Client. In this path the Company acts as conduit and takes no commission or beneficial interest (Clause 8.7(h)(ii)).

(c) Capture timing — immediate and scheduled. The Client acknowledges that Manual Dispatch payment links are configured for immediate capture for immediate call-outs (the End-User is charged on payment), and, for Scheduled Recoveries (Clause 8.3C), for a pre-authorisation hold captured on job completion, with the hold released if the job does not complete. In each case the refund and late-cancellation treatment the Client discloses to the End-User applies.

(d) Client responsibility for its own pricing and refunds. The price on a Manual Dispatch payment link is the Client's own price (Clause 8.7(a)), and the Client is responsible for its lawfulness and for honouring the refund and cancellation outcomes disclosed to the End-User, irrespective of which payment path applies. The Company's Merchant-of-Record, liability, and no-cut positions in this Section 8 apply to Manual Dispatch Recoveries as they do to Towpal-originated transactions.

(e) Manual Dispatch is the Client's own direct sale — the Client's terms govern. The Client acknowledges that a Manual Dispatch Recovery is a direct transaction between the Client and the End-User, arranged by the Client by telephone using the Platform's dispatch and payment-link tooling. Neither the Company nor Towpal Ltd is a party to that transaction, and neither the TowPal consumer Terms of Service nor the TowPal consumer Privacy Policy governs it. The Client is the trader and the supplier of the recovery, and the Client is the data controller for the End-User's booking. The Client warrants and undertakes that, for every Manual Dispatch Recovery, it will:

(i) make available to the End-User, before or at the point of payment, its own consumer terms of service and privacy notice that are accurate and compliant with the Consumer Rights Act 2015, the Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013, the Consumer Protection from Unfair Trading Regulations 2008, and the UK GDPR;

(ii) ensure those terms correctly identify the Client as the supplier and trader, disclose the Company's/Towpal Ltd's role as software and payment-technology provider only, and accurately state the payment, immediate-capture, 10-minute link expiry, refund, and late-cancellation position actually operated; and

(iii) surface those terms at the Stripe payment link (for example via Stripe Checkout terms-of-service acceptance) so that the End-User is bound by them before paying.

The Company may make a template available to assist the Client, but any template is provided as a convenience only, without warranty, and the Client remains solely responsible for the adequacy, accuracy, and surfacing of its own consumer terms. The indemnity at Clause 2.6 extends to any claim arising from the Client's failure to comply with this Clause 8.3B(e).

8.3C Scheduled Recoveries

The Platform supports Scheduled Recoveries — recoveries booked in advance, from 3 hours up to 5 days ahead — for both Towpal Marketplace and Manual Dispatch jobs. The Client acknowledges that:

(a) Payment. A Scheduled Recovery is paid by a pre-authorisation hold placed at booking for the quoted amount, captured on completion of the recovery (the 5-day cap reflects the validity window of a card authorisation hold). If the recovery does not complete, the hold is released or refunded, and the End-User is not charged.

(b) Operator start ("Begin"). For a Scheduled Recovery, the assigned Operator must commence travel to the End-User (the "Begin" action) by the scheduled time. If no Operator has begun travel by the scheduled time, the Platform automatically cancels the recovery and the End-User receives a full refund / the hold is released. If an Operator has begun travel but is running late, the recovery continues until the Operator arrives and is not auto-cancelled for lateness.

(c) Cancellation. End-User cancellation of a Scheduled Recovery follows the same standard cancellation and late-cancellation treatment as immediate jobs (full refund where cancelled before an Operator is en route or while the Operator is more than 10 minutes away; call-out fee retained only where the Operator is en route and within 10 minutes).

(d) Responsibility. For Manual Dispatch Scheduled Recoveries, the Client remains the supplier and is responsible for its own pricing, terms, and refund outcomes (Clauses 8.3B(d), (e)). For Towpal Scheduled Recoveries, Operator pay and the underlying recovery remain the Client's responsibility in the ordinary way.

8.3D Post-Payout Refunds and Chargebacks — the Client Bears Them

The Payout Withholding Period (Clause 8.2) is designed to resolve most disputes before funds are released. This Clause 8.3D governs the position where a justified refund, chargeback, or refund-worthy dispute arises after funds for a job have already been released from escrow (whether to the Operator's connected account, the Client's connected account, or otherwise).

(a) The Client bears the refund — for every job type. As between the Company, Towpal Ltd, and the Client, the Client bears the financial cost of any justified post-payout refund or chargeback in respect of a recovery its Operator accepted and completed. This applies to all job types the Client performs through the Platform — Towpal-originated jobs, Manual Dispatch jobs, VIP / Partner Jobs, and Unclaimed-Territory and Out-of-Bounds Recoveries — the Client acknowledging that, although Towpal Ltd sets the price on Unclaimed-Territory and Out-of-Bounds Recoveries, the Client is the supplier of the recovery (its Operator accepts and completes the job), and refund liability follows the supplier. This is consistent with the Client's status as Merchant of Record (Clause 8.5) and its assumption of all End-User refund and chargeback liabilities (Clauses 2.5(h), 2.6(e), (k)).

(b) How the cost is borne — and the Company's right to recover it. The Client acknowledges that, depending on Stripe Connect configuration and card-network rules, a post-payout refund or chargeback may be debited by Stripe from the Company-operated platform account, from the Client's connected account, or from another account, and that the Client does not control which. Accordingly:

(i) where the refund or chargeback is debited from the Client's own connected account, the Client bears it directly and no further step is required;

(ii) where it is debited from the Company-operated platform account (or otherwise from an account other than the Client's), the debited amount (together with any associated Stripe or card-network fee or penalty) becomes an immediate debt due from the Client to the Company, and the Client authorises the Company to recover it by set-off against, or deduction from, any funds otherwise payable to the Client (including future payouts and future Towpal Lead settlements), or to charge it to the Client's connected account or payment method on file; and

(iii) the Client shall keep sufficient funds available to meet its potential refund and chargeback liabilities, and shall pay any shortfall on demand where set-off is insufficient.

(c) The Company does not itself claw back from the Operator — but the card network's process may reverse a payout. The Company does not, by its own decision or action, recover a post-payout refund or chargeback by taking funds from an Operator's account, and does not determine Operator pay. The Client and Operator acknowledge, however, that because Operator payouts are made as Stripe Transfers linked to the original charge, the card-network chargeback process operated by Stripe may automatically reverse an Operator's Transfer (which can take the Operator's Stripe balance negative) when a customer chargeback occurs — this is a function of Stripe and the card networks, not a discretionary clawback by the Company, and is outside the Company's control. If the Client wishes to recover any further part of a refunded job from the Operator, that is solely a matter between the Client and the Operator under their own engagement arrangement, subject to the Client's obligations under employment law and any applicable rules on deductions from pay. The Company is not a party to, and bears no responsibility for, any such recovery or for any automatic Transfer reversal effected by Stripe. (This preserves the position that the Company is not the Operator's employer or paymaster — see Clauses 2.1 and 2.5A.)

(d) Unclaimed-Territory and Out-of-Bounds — the 24-hour hold and residual liability. For Unclaimed-Territory and Out-of-Bounds Recoveries, the 24-hour hold in Clause 8.3A gives a first line of protection, but where a justified refund or chargeback arises after that hold has released funds to the Client, sub-clauses (a)–(c) apply and the Client bears it.

(e) Justified refunds only; disputes. This Clause concerns refunds and chargebacks that are justified (whether by the End-User's statutory rights, the applicable consumer terms, or a card-network chargeback outcome). Nothing here requires the Client to fund a refund that is not due; but the Client acknowledges that a card-network chargeback outcome is determined by the card network, not the Company, and that the Company's recovery right in (b) applies to any amount the Company is in fact debited as a result.

(f) Reserve / hold-back right. To provide for the Client's potential refund and chargeback liabilities under this Clause 8.3D, the Company (or Towpal Ltd) may retain a reserve by holding back a reasonable proportion of, or a reasonable rolling amount from, funds otherwise payable to the Client, and/or holding funds for a reasonable period, in each case proportionate to the Client's transaction volume and chargeback/refund history. Any such reserve is the Client's money held as security against its own refund and chargeback liabilities; it is applied to meet those liabilities as they arise and the balance is released to the Client after the applicable card-network chargeback window, subject to any deductions properly made under this Clause. The Company will act reasonably in setting and adjusting any reserve and will not use it as a means of withholding sums genuinely due to the Client beyond what is needed to cover its potential liabilities.

8.4 Client's Stripe Obligations

The Client shall at all times:

(a) maintain its Connected Stripe Account in good standing and in full compliance with Stripe's Connected Account Agreement;

(b) promptly notify the Company in writing within 24 hours of becoming aware of any suspension, restriction, freeze, or adverse action taken by Stripe in relation to the Connected Stripe Account, including where such action is triggered by chargeback activity on Towpal-originated transactions;

(c) maintain a chargeback ratio — across all transactions processed through the Connected Stripe Account, including Towpal-originated jobs — within Stripe's acceptable thresholds; and

(d) not take any action that causes the Company's Stripe Platform account to be flagged, restricted, or penalised.

8.5 Merchant of Record — Towpal-Originated Transactions

The Client acknowledges and expressly agrees that, in respect of all consumer transactions originating from the Towpal Marketplace and processed through the Platform via Stripe Connect:

(a) the Client is and shall at all times be the Merchant of Record for all such transactions, in the sense that the Client is the party supplying the Recovery Service, the party to whom the consumer funds beneficially belong (net of Stripe fees and any sum properly withheld), and the party from whose account and resources all associated financial obligations are ultimately discharged. The Client acknowledges that, as a payment-processing mechanic, consumer funds are first charged through the Company-operated Stripe platform account (Clauses 8.1 and 8.7(h)) and then transferred to the Client's Connected Stripe Account; this routing does not alter the Client's Merchant-of-Record status or the beneficial ownership of the funds;

(b) the Client assumes full, exclusive, and unconditional financial liability for: (i) all consumer refunds arising from cancellations or service failures in respect of Towpal-originated jobs, including Late Cancellation Fee adjustments processed in accordance with Towpal Ltd's consumer-facing terms; (ii) all chargeback claims initiated by consumers in respect of Towpal-originated transactions, including any chargeback dispute fees, penalties, or reserve requirements levied by Stripe as a consequence; and (iii) all driver and operative payouts due in respect of completed Towpal-originated jobs processed through the Platform's payout infrastructure;

(c) the Company accepts no financial liability whatsoever for any refund, chargeback, Stripe penalty, payout obligation, or other financial consequence arising from any Towpal-originated transaction. The Company's role in respect of such transactions is limited entirely to operating the software integration bridge through which the Towpal Lead data and associated payment authorisation flow is transmitted;

(d) the Client agrees to maintain sufficient cleared funds or credit facilities accessible to its Connected Stripe Account at all times to meet foreseeable refund and chargeback obligations arising from Towpal-originated activity within its Assigned Territory; and

(e) if chargeback or refund activity arising from Towpal-originated transactions causes the Client's Connected Stripe Account to be flagged, placed in a reserve programme, restricted, or suspended by Stripe, this shall constitute an Event of Default under Clause 11.1(b) and the provisions of Clauses 11.2 and 11.3 shall apply accordingly.

8.6 Company Not Liable for Stripe Actions

The Company shall bear no liability to the Client for any delay in payment, withholding of funds, or account restriction imposed by Stripe, including where such action is taken by Stripe at the Company's instruction following a legitimate dispute, or where such action arises from chargeback activity on Towpal-originated transactions for which the Client is Merchant of Record.

8.7 Commercial Agency — Towpal Ltd Acting as Commercial Agent

The Client acknowledges and agrees that, in respect of consumer-facing transactions originating through the Towpal Marketplace, Towpal Ltd acts as the Client's disclosed commercial agent for the following strictly limited purposes:

(a) Pricing — presenting to consumers, within the Towpal Marketplace, the Client's own recovery prices. The Client sets and controls its own prices through the pricing controls in its dashboard, and those same Client-set prices are used for both the Client's manual (telephone) dispatch recoveries and its Towpal Marketplace recoveries. For a Towpal recovery arising within the Client's Assigned Territory, the price the consumer sees is the price set by the Client that owns that territory. Towpal Ltd's role in respect of such pricing is limited to displaying and collecting the Client's price; Towpal Ltd does not set, determine, mark up, or apply a surcharge to the Client's price for jobs within a claimed territory. (Towpal Ltd sets pricing only for Unclaimed-Territory Recoveries and Out-of-Bounds Recoveries, as defined in Section 4, in which no Client owns the territory.)

(b) Authorisation Holds — placing payment authorisation holds on consumers' payment methods via Stripe Connect in connection with Towpal Leads accepted by the Client, processed through the Company-operated Stripe platform account (Clauses 8.1 and 8.7(h)) on the Client's behalf as Merchant of Record; and

(c) Consumer Cancellation and Refund Flow — managing the consumer-facing cancellation and refund process in accordance with Towpal Ltd's published consumer terms of service, which may result in the release or capture of authorisation holds processed through the Client's Connected Stripe Account.

The Client further acknowledges and agrees that:

(d) the commercial agency arrangement described in this Clause 8.7 is a relationship between the Client and Towpal Ltd only. The Company is not a party to that agency relationship and accepts no liability in respect of it, including no liability for any pricing decision made by Towpal Ltd, any authorisation hold placed by Towpal Ltd, or any consumer-facing refund or cancellation outcome administered by Towpal Ltd;

(e) the consumer price for a Towpal recovery within the Assigned Territory is the Client's own price, set and controlled by the Client through its dashboard pricing controls. The Client is solely responsible for the prices it sets, including for their lawfulness, transparency, and fairness to consumers, and warrants that its prices comply with all applicable consumer-protection and pricing law. Neither the Company nor Towpal Ltd sets, endorses, or takes responsibility for the level of the Client's prices;

(f) in respect of any individual Towpal Lead, the Client may accept or reject that dispatch on a per-job basis, in accordance with Clause 8.8. The consumer price for a claimed-territory job is the Client's own price (Clause 8.7(a)); the Client may change its prices for future jobs through its dashboard at any time, but may not vary the price of a job already presented and paid for by a consumer; and

(g) where the commercial agency relationship between the Client and Towpal Ltd is governed by a separate agreement executed directly between those parties, the terms of that agreement shall govern the agency arrangement, and the Company is not a party to or bound by any such agreement; and

(h) Authority to use a payment-collection service provider (including the Company). The Client expressly authorises Towpal Ltd, in performing its collection and payment-routing functions as the Client's disclosed agent, to appoint and use a third-party payment-collection service provider to operate the underlying Stripe platform account and to perform the mechanics of collection, holding pending settlement, routing, refund, and chargeback handling on Towpal Ltd's behalf. The Client acknowledges and agrees that:

(i) the Company (DX Digital Design Ltd) currently performs that payment-collection service-provider role for Towpal Ltd, operating the shared Stripe platform account through which Towpal-originated consumer payments are collected and routed;

(ii) in performing that role the Company acts as Towpal Ltd's service provider and as a conduit only. The Company takes no commission, fee, deduction, or percentage from the consumer payment for a recovery job, acquires no beneficial ownership of those funds, and does not hold them for its own account; save for Stripe's own processing fees, consumer funds (net of any amount properly withheld under the consumer terms) are routed to the Client and its Operators;

(iii) this authority to sub-delegate collection to a service provider does not transfer to the Company any of the Client's Merchant-of-Record obligations under Clause 8.5, does not make the Company the supplier of any Recovery Service, and does not enlarge the Company's liability, which remains as limited by Section 2 and Clause 8.5(c); and

(iv) the arrangements between Towpal Ltd and the Company governing that service-provider role are a matter between those two entities and do not create any obligation of the Company to the Client beyond those expressly stated in this Agreement.

8.8 Client's Right to Accept or Reject Towpal Leads

The Client retains the right to accept or reject any individual Towpal Lead dispatched to it via the Towpal Integration on a per-job basis. The Client acknowledges that:

(a) rejecting a Towpal Lead does not entitle the Client to alter the price of that job, which has already been presented to and paid by the consumer at the Client's own then-current price; the Client may adjust its prices for future jobs through its dashboard pricing controls at any time;

(b) the Client's right to reject individual Towpal Leads does not affect any authorisation hold that may already have been placed on the consumer's payment method by Towpal Ltd acting as commercial agent, which is governed by Towpal Ltd's consumer-facing terms and the Stripe Connect flow applicable to that transaction;

(c) systematic or habitual rejection of Towpal Leads within the Assigned Territory may, at the Company's discretion, be considered in the context of the Client's Minimum Operational Volume performance under Section 7 and may constitute grounds for a Performance Warning Notice under Clause 7.3; and

(d) during a fleet-level Compliance Suspension, no Towpal Lead will be dispatched to the Client at all. The Client's right of acceptance or rejection under this Clause 8.8 is of no effect during any such period.

SECTION 9 — FEES, BILLING, SUBSCRIPTION TERMS, AND THE MULTI-YEAR PREPAID MODEL

9.1 Subscription Term Election

The Client shall elect in the Order Form one of the Subscription Terms set out in Schedule 3. The Client acknowledges that the Annual Term and the Multi-Year Terms are genuinely alternative bargains priced differently, that it has been offered each, and that its election is a free commercial choice made with knowledge of the terms and consequences of each. The elected Subscription Term, the applicable Fees, and the Termination Notice Period shall be as specified in Schedule 3 and the Order Form.

9.1A Renewal — Territory Re-Purchase and New Order Form

Renewal of the Subscription Term is conditional upon the Client affirmatively re-purchasing the territory and Exclusivity element for the next term and executing a new Order Form. It is not automatic in the sense of continuing by default on the Client's silence; it continues only if the Renewal Conditions are met within the Renewal Window. This Clause 9.1A applies to the expiry of an Annual Term and, in place of Clause 9.7(e), to the expiry of a Multi-Year Term.

(a) The Renewal Conditions. To renew, the Client must, in respect of the next term:

(i) pay the Prepaid Territory Fee (or, for an Annual Term with no separate prepaid territory element, the territory/Exclusivity fee) applicable to the renewed term, in full and in cleared funds; and

(ii) execute a new Order Form for the renewed term.

The new Order Form is where the Parties record the renewed territory configuration — including any territories added or removed — and the applicable Fees for the renewed term.

(b) Continuity of monthly Fees and pricing. Unless the new Order Form records otherwise:

(i) the monthly MRR Fee continues at the same rate as under the expiring term; and

(ii) the territory/Exclusivity price for the renewed term may be the same as, higher than, or lower than the expiring term, and may change to reflect any change in the territories held. The applicable figures are those stated in the new Order Form.

(c) The Renewal Window.

(i) Pre-expiry period. The Client should satisfy both Renewal Conditions during the thirty (30) days before the expiry of the current term.

(ii) Post-expiry cure period. If both Renewal Conditions are not satisfied by the expiry date, the Client has a further seven (7) days after the expiry date within which to satisfy them. This is a cure period only, and is not a period of continued access — Clause 9.1A(e) applies during it.

(d) Effect of timely renewal — seamless continuation. Where both Renewal Conditions are satisfied before expiry, or within the 7-day post-expiry cure period, the Subscription Term renews, and the renewed term is deemed to begin on the day immediately following the expiry date of the previous term, with no gap in the term. Where the Renewal Conditions are satisfied before expiry, access continues without interruption. Where they are satisfied during the cure period, access is restored and the renewed term nonetheless runs from the day after expiry in accordance with this Clause.

(e) Access on and after expiry pending renewal. The Client acknowledges and agrees that:

(i) on expiry of the current term, if the Renewal Conditions have not been satisfied, Platform access is suspended. During the 7-day cure period the Client does not have access to the client dashboard, and the Client's Operators do not have access to the Operator App;

(ii) access is restored only upon both Renewal Conditions being satisfied within the cure period, at which point Clause 9.1A(d) applies; and

(iii) no fee credit, refund, service credit, compensation, or make-good is due in respect of any period of suspension during the cure period, and no leads, jobs, or revenue foregone during it are recoverable, consistent with Clause 5.10. The Client is responsible for renewing in good time to avoid any such suspension.

(f) Failure to renew — termination. If both Renewal Conditions are not satisfied by the end of the 7-day post-expiry cure period, the Agreement terminates automatically at the end of that cure period without further notice. On such termination:

(i) the monthly MRR subscription ceases, and no further MRR Fee falls due in respect of any period after termination;

(ii) the Client loses all access to the client dashboard, and the Client's Operators lose all access to the Operator App;

(iii) the Assigned Territory and all Exclusive Territory Rights revert to the Company in accordance with Section 4, and the Company is at liberty to re-licence them to any third party; and

(iv) the consequences of termination at Clauses 11.3(a), (b), (e), and (f) apply as though the Agreement had terminated on that date, and Clause 12.3(e) (data export) applies.

(g) No waiver by forbearance. The Company's acceptance of a late renewal on any occasion, or any extension of the cure period on any occasion, does not waive the Company's right to enforce the Renewal Window strictly on any subsequent occasion (Clause 15.4).

9.2 Monthly Recurring Fee — Annual and Multi-Year Terms

Annual Term. Where the Client is on an Annual Term, the Client shall pay the Company the MRR Fee of £[MONTHLY FEE] + VAT on or before the [1st] day of each calendar month during the Subscription Term, by the payment method authorised in the Order Form.

Multi-Year Term. Where the Client is on a Multi-Year Term, the Client shall in addition to the Prepaid Territory Fee pay the MRR Fee monthly in advance on or before the [1st] day of each calendar month throughout the term, at the Locked Fee fixed under Clause 9.7. The Prepaid Territory Fee and the monthly MRR Fee are two separate and distinct charges (Schedule 3 Part A and Part D.1): the former prepays the territory reservation and Exclusivity element once, in advance; the latter is paid monthly for ongoing Platform access. The monthly MRR Fee continues to fall due in full during any period described in Clause 9.3.

9.3 Fees Payable During Suspension

For the avoidance of all doubt, the MRR Fee, any Exclusivity Premium, and any Prepaid Territory Fee continue to fall due, remain payable in full, and are not abated, credited, refunded, or reduced during any period of Compliance Suspension, Vehicle Lock, or Operator Lock under Section 5, and during any period of suspension under Clause 9.4(b) or Clause 11.4. No Multi-Year Term shall be extended, and no additional months shall be granted, on account of any such period.

9.4 Late Payment

Without prejudice to any other right or remedy available to the Company, if the Client fails to pay any sum due under this Agreement by the due date, the Company shall be entitled to:

(a) charge interest on the overdue sum at the rate of 8% per annum above the Bank of England base rate, accruing daily from the due date until actual payment, pursuant to the Late Payment of Commercial Debts (Interest) Act 1998; and

(b) suspend the Client's access to the Platform — including suspension of all Towpal Lead routing and the Compliance Module — immediately upon written notice, pending payment.

9.5 Multi-Year Terms — Primary Commitment

The Client may elect a 2-Year Term or a 3-Year Term in respect of its Assigned Territory. Where a Multi-Year Term is elected:

(a) the committed duration is a primary obligation of the Client and a primary term of the bargain, and is not a secondary obligation, sanction, or consequence of breach. The Subscription Term is fixed for the full elected duration and is not terminable by the Client for convenience during the Committed Period defined in Schedule 3 Part D, save as expressly provided in Clause 12.1;

(b) the Client's Exclusive Territory Rights, where granted, subsist for the duration of the Multi-Year Term subject in all respects to the trapdoors at Clause 4.7, which apply with undiminished force notwithstanding prepayment; and

(c) the Client acknowledges that a Multi-Year Term confers price certainty and territory security of tenure only. It confers no guarantee of lead volume, job volume, revenue, or commercial return whatsoever, and Clause 4.3 applies in full.

9.6 Prepaid Territory Fee — Payment in Full and in Advance

Where the Client elects a Multi-Year Term:

(a) the Prepaid Territory Fee covering the entirety of the elected Multi-Year Term becomes due and payable in full, in cleared funds, and in advance, on or before the Effective Date, in the amount specified in Schedule 3. The Prepaid Territory Fee is the price of the committed term. It is a primary obligation, in accordance with Schedule 3 Part D;

(b) the Company is under no obligation to activate the Platform, to configure the Assigned Territory, to grant Exclusivity, or to enable Towpal Lead routing until the Prepaid Territory Fee has been received in full in cleared funds;

(c) the Prepaid Territory Fee may not be paid by instalments, staged payments, deferred terms, or third-party finance without the Company's prior express written consent, which may be withheld at its absolute discretion; and

(d) where the Company has consented to any instalment or deferred arrangement, failure to pay any instalment on its due date shall constitute an Event of Default under Clause 11.1(a) and shall additionally trigger Territory Forfeiture under Clause 6.2.

9.7 Fee Lock — The Company's Undertaking

In consideration of, and strictly conditional upon, the Client's payment of the Prepaid Territory Fee in full and in cleared funds in accordance with Clause 9.6, the Company undertakes that the Fees applicable to the Client's Assigned Territory shall be locked at the discounted rate specified in Schedule 3 (the "Locked Fee") for the entire duration of the elected Multi-Year Term.

Accordingly:

(a) the Company shall not exercise its fee review right under Clause 9.9 in respect of that Client during the Multi-Year Term, and the Client is thereby protected from any year-on-year uplift, indexation, inflationary adjustment, or repricing of the Locked Fee that the Company may apply to its wider client base during that period;

(b) the Fee Lock attaches to the Assigned Territory and Platform tier as configured at the Effective Date. It does not extend to: (i) any additional postcodes, territory expansion, or Exclusivity upgrade acquired after the Effective Date, which shall be priced at the Company's then-current rates and may be subject to a separate Locked Fee for the balance of the Multi-Year Term by agreement in writing; (ii) any additional Platform module, tier upgrade, or optional feature acquired after the Effective Date; (iii) any third-party pass-through cost, including Stripe processing fees or any charge levied by a Government Data Source operator, which are outside the Company's control; or (iv) VAT, which shall be charged at the prevailing rate from time to time;

(c) the Fee Lock survives any Compliance Suspension, Vehicle Lock, Operator Lock, Exclusivity forfeiture, or Exclusivity revocation, but confers no right to any refund, credit, or abatement in any such circumstance, and the Client remains bound by the Multi-Year Term notwithstanding loss of Exclusivity;

(d) the Fee Lock terminates automatically on the expiry of the Multi-Year Term, on any earlier termination of this Agreement, or upon any refund of the Prepaid Territory Fee under Clause 9.8; and

(e) the renewal of a Multi-Year Term on its expiry is governed by Clause 9.1A (territory re-purchase and new Order Form within the Renewal Window; failing which the Agreement terminates). The Company shall notify the Client of the applicable renewal terms and figures no less than 60 days before the Multi-Year Term expires, so that the Client has adequate time to satisfy the Renewal Conditions within the Renewal Window.

9.8 Prepaid Territory Fee — Refund Treatment on Early Termination

The following exhaustively governs the treatment of any unexpired portion of a Prepaid Territory Fee on early termination. In this Clause, "Unexpired Portion" means the Prepaid Territory Fee apportioned on a straight-line monthly basis over the elected Multi-Year Term, in respect of complete calendar months falling after the effective date of termination. This Clause 9.8 is to be read with Schedule 3 Part D.

The Company shall provide the Client with a written statement itemising the calculation of any refund and any deduction made from it within 30 days of the termination date. Nothing in this Clause 9.8 limits the Company's right to recover any further sums properly due to it.

9.9 Fee Reviews — Annual Term Clients

The Company reserves the right to review and adjust the MRR Fee on no less than 30 days' written notice to the Client. This Clause 9.9 does not apply to a Client on a Multi-Year Term during the currency of that term, whose Fees are protected by the Fee Lock at Clause 9.7. Where an Annual Term Client does not accept a revised Fee, it may terminate this Agreement under Section 12 by providing the requisite notice before the revised Fee takes effect.

9.10 VAT

All Fees are exclusive of value added tax, which shall be charged at the prevailing rate where applicable and payable by the Client in addition to the relevant Fee. Any change to the rate of VAT is not a Fee increase and is not caught by the Fee Lock.

SECTION 10 — INTELLECTUAL PROPERTY

10.1 Ownership

All Intellectual Property Rights in and to the Platform — including its underlying software, algorithms, source code, databases, user interface, visual design, branding, and documentation, and including the Compliance Module, the Approval Workflow, the Enforcement Matrix, the Audit Log, and the Towpal Integration — are and shall remain the exclusive property of the Company at all times. Nothing in this Agreement shall operate to transfer, assign, or license any Intellectual Property Rights to the Client beyond the limited software licence granted under Section 3. For the avoidance of doubt, nothing in this Agreement confers on the Client any right in or to any data obtained from a Government Data Source, which remains subject to the terms of the relevant public body.

10.2 Client Data

The Client retains ownership of all Client Data, including Compliance Data, Operator Data, Operator Documents, Vehicle Data, Licence Check Recency Data, and Walkaround Records. The Client grants to the Company a non-exclusive, royalty-free licence to access, process, and use Client Data solely to the extent necessary to provide the Platform — including the operation of the Enforcement Matrix and the maintenance of the Audit Log — and to perform the Company's obligations under this Agreement. The Company shall handle Client Data in accordance with its Privacy Policy, Section 14 of this Agreement, and applicable data protection legislation, including the UK GDPR and the Data Protection Act 2018.

10.3 Feedback

If the Client provides the Company with any feedback, suggestions, or recommendations relating to the Platform, the Compliance Module, the Approval Workflow, or the Towpal Integration ("Feedback"), the Company shall be free to use, incorporate, and exploit such Feedback without restriction or compensation to the Client, and the Client assigns to the Company all Intellectual Property Rights in such Feedback.

10.4 Prohibition on Reverse Engineering

The Client expressly acknowledges that any attempt to reverse-engineer, decompile, disassemble, copy, or reproduce the Platform — including the Compliance Module, the Approval Workflow, the Enforcement Matrix, the Audit Log, or the Towpal Integration — or any part of its underlying code or architecture constitutes a material breach of this Agreement and an infringement of the Company's Intellectual Property Rights, entitling the Company to immediate termination under Section 11 and to seek injunctive relief and all available remedies without requirement to demonstrate actual loss.

SECTION 11 — TERMINATION FOR CAUSE

11.1 Events of Default

Each of the following shall constitute a material Event of Default entitling the Company to terminate this Agreement upon written notice, subject to Clause 11.2:

(a) Subscription Payment Failure — the Client's MRR Fee payment, or any consented instalment of a Prepaid Territory Fee, fails, is declined, charged back, or reversed and remains unpaid for more than [3] calendar days following the due date, and the Client has failed to remedy the failure within a 7-day cure period following written notice from the Company;

(b) Stripe Account or Stripe Connect Failure — the Client fails to complete Stripe Connect onboarding within the period specified in Clause 6.3(a), or the Client's Connected Stripe Account is rejected, suspended, frozen, restricted, reserved, or terminated by Stripe for any reason — including elevated chargeback ratios arising from Towpal-originated transactions for which the Client is Merchant of Record — and the Client fails to establish or reinstate a compliant, active Connected Stripe Account within 7 days of written notice from the Company;

(c) Reverse Engineering — the Client or any of its employees, contractors, Client Admins, Operators, or agents attempts to reverse-engineer, decompile, disassemble, copy, or replicate the Platform or any component thereof, including the Compliance Module, the Approval Workflow, or the Towpal Integration;

(d) Insolvency — the Client becomes insolvent, enters administration, proposes a CVA, or has a winding-up petition presented against it;

(e) Misrepresentation — the Client has made a material misrepresentation in its onboarding documentation, Order Form, or Stripe application;

(f) Breach of Licence — the Client assigns, sublicenses, or otherwise transfers the Platform licence or territorial rights — including any purported transfer of Towpal Lead routing access — in breach of this Agreement;

(g) Prolonged Compliance Suspension — a Compliance Suspension under Section 5 remains in force in respect of any fleet-level Tier 1A Credential for a continuous period of [30] calendar days;

(h) Compliance Data Falsification, False Attestation, Audit Log Interference, or Circumvention — the Client or any of its employees, Client Admins, Operators, contractors, or agents:

(i) inputs or records any falsified, forged, altered, backdated, post-dated, knowingly inaccurate, or recklessly inaccurate expiry date or item of Compliance Data, or uploads any forged, altered, or non-genuine document, in breach of Clause 5.5;

(ii) records any Client Approval in respect of a document not actually examined, or in respect of a document known or suspected to be forged, expired, or invalid, in breach of Clause 5.6(d);

(iii) records a Last DVLA Check Date in respect of a check not actually performed, in breach of Clause 5.13;

(iv) makes any knowingly incorrect Tachograph Exemption Declaration, in breach of Clause 5.3(e);

(v) attempts to alter, overwrite, delete, or suppress any entry in the Audit Log, in breach of Clause 3.2(h); or

(vi) attempts to circumvent, disable, spoof, or interfere with the Compliance Module, the Approval Workflow, the Enforcement Matrix, any Vehicle Lock, or any Operator Lock, in breach of Clause 3.2(g) or Clause 5.14;

(i) Deployment of Locked or Non-Compliant Assets or Operators — the Client deploys, or permits the deployment of, any vehicle subject to a Vehicle Lock, any Operator subject to an Operator Lock, any vehicle lacking a current MOT or valid VED, or any Operator who is disqualified, unlicensed, without appropriate entitlement, or without right to work, in breach of Clause 5.14(g), 5.14(h), or 5.14(i); or

(j) Sustained Volume Failure — the Client fails to meet the Minimum Operational Volume for the period specified in Clause 7.3 and the Company elects to terminate under Clause 7.4(b).

Non-renewal is a separate route. For the avoidance of doubt, the automatic termination on failure to satisfy the Renewal Conditions within the Renewal Window under Clause 9.1A(f) is not an Event of Default and requires no election or notice by the Company. It operates automatically at the end of the 7-day post-expiry cure period, with the consequences stated in Clause 9.1A(f). The cure period in Clause 11.2 does not apply to it (Clause 9.1A sets its own window).

11.2 Cure Period

Save for the Events of Default specified in Clauses 11.1(c), 11.1(d), 11.1(f), 11.1(h), and 11.1(i) — which shall entitle the Company to terminate immediately and without a cure period — the Company shall provide the Client with 7 days' written notice specifying the Event of Default and requiring the Client to remedy it. If the Client fails to remedy the default within that period, the Company may terminate immediately by further written notice.

11.3 Effect of Termination for Cause

Upon termination under this Section 11:

(a) all Platform access — including access to the Compliance Module, the Approval Workflow, the Towpal Integration, and all Towpal Lead routing — shall be permanently and immediately revoked;

(b) the Assigned Territory and all Exclusive Territory Rights shall immediately revert to the Company, and the Company shall take reasonable steps to notify Towpal Ltd to cease routing Towpal Leads to the Client within that territory;

(c) where the Client is on an Annual Term, all outstanding Fees for the remainder of the then-current Subscription Term shall become immediately due and payable in full;

(d) where the Client is on a Multi-Year Term, the treatment of the Unexpired Portion of the Prepaid Territory Fee shall be governed exclusively by Clause 9.8 and Schedule 3 Part D;

(e) the Client shall immediately cease all use of the Platform and any associated branding; and

(f) the Company reserves all rights to pursue damages and other remedies at law, including in respect of any chargeback or Stripe liability arising from the Client's Merchant of Record obligations that remains outstanding at the date of termination.

11.4 Suspension Pending Termination

Nothing in this Section 11 limits the Company's right to suspend the Client's Dispatch Queue, apply a Vehicle Lock or Operator Lock, or suspend Platform access immediately and without notice under Section 5 or Clause 9.4(b), and any such suspension may run concurrently with a cure period without prejudicing the Company's right to terminate.

SECTION 12 — TERMINATION FOR CONVENIENCE

12.1 Right to Terminate

Either Party may terminate this Agreement for any reason or for no reason by providing not less than thirty (30) days' written notice to the other Party, save where the Order Form or Schedule 3 specifies a longer notice period of sixty (60) days, in which case that longer period shall apply to both Parties equally. The applicable Termination Notice Period shall be as stated in the Order Form.

Multi-Year Term. Where the Client is on a Multi-Year Term:

(a) the Company may terminate for convenience at any time on the applicable Termination Notice Period, with the full refund consequence at Clause 9.8;

(b) the Client may terminate for convenience at any time on the applicable Termination Notice Period, provided that where notice is served during the Committed Period defined in Schedule 3 Part D, the refund consequence at Clause 9.8 applies and no refund of the Unexpired Portion is due. This reflects the primary commercial bargain recorded at Schedule 3 Part D and is not a sanction, penalty, deterrent, or consequence of breach; and

(c) nothing in this Clause 12.1 restricts either Party's right to terminate for cause under Section 11, nor the Client's right to terminate in response to a Fee increase under Clause 9.9 (which does not arise during a Multi-Year Term by operation of the Fee Lock).

12.2 Obligations During Notice Period

During the Termination Notice Period:

(a) both Parties shall continue to fulfil their obligations under this Agreement in full;

(b) the Client shall continue to pay all Fees falling due during the notice period;

(c) the Client shall continue to maintain current Compliance Credentials within the Compliance Module, and the Enforcement Matrix shall continue to operate in full in accordance with Section 5 throughout the notice period, including the Blocking Function at Clauses 5.1A(b), 5.7, and 5.13, and the Flagging Function for all other credentials; and

(d) the Company shall continue to provide Platform access and Towpal Lead routing, subject to the Client's ongoing compliance with this Agreement and to any Compliance Suspension, Vehicle Lock, or Operator Lock in force.

12.3 Effect of Termination for Convenience

Upon expiry of the Termination Notice Period:

(a) Platform access — including the Compliance Module, the Approval Workflow, all Towpal Integration functionality, and Towpal Lead routing — shall be permanently disabled;

(b) the Assigned Territory and all Exclusive Territory Rights shall immediately and automatically revert to the Company, and the Company shall take reasonable steps to notify Towpal Ltd to cease routing Towpal Leads to the Client within the Assigned Territory forthwith. The Company shall be at liberty to licence the Assigned Territory — and offer Towpal Lead routing within it — to any third party without restriction or obligation to the Client;

(c) where the Client is on an Annual Term, any pre-paid MRR Fees covering a period beyond the termination date shall be refunded to the Client on a pro-rata basis within 30 days, save that no refund shall be due in respect of any Exclusivity Premium, which is non-refundable in accordance with Clauses 5.10, 6.5, and 7.7;

(d) where the Client is on a Multi-Year Term, the Unexpired Portion of the Prepaid Territory Fee shall be treated exclusively in accordance with Clause 9.8 and Schedule 3 Part D; and

(e) the Client shall have 14 days to request an export of its Client Data — including its Compliance Data, Vehicle Data, Operator Documents, Licence Check Recency Data, Operator Data, and Audit Log — after which the Company shall have no obligation to retain or provide access to that data, save as required by law, as set out in Section 14, or as provided at Clause 5.12(d) in respect of the Audit Log.

12.4 No Liability

Neither Party shall have any liability to the other solely as a result of exercising its right to terminate for convenience under this Section 12, provided all accrued payment obligations are honoured and any refund due under Clause 9.8 is paid. For the avoidance of doubt, the cessation of Towpal Lead routing upon termination shall not give rise to any liability on the part of the Company, consistent with the No Volume Guarantee in Clause 4.3.

SECTION 13 — CONFIDENTIALITY

13.1 Obligations

Each Party undertakes to keep the other's Confidential Information strictly confidential and not to disclose it to any third party without prior written consent, and to use it solely for the purposes of this Agreement. Each Party shall protect the other's Confidential Information with at least the same degree of care it applies to its own confidential information, and in any event no less than reasonable care.

13.2 Exceptions

The obligations of confidentiality shall not apply to information that: (a) is or becomes publicly available other than through breach of this Agreement; (b) was already in the receiving Party's possession free of any confidentiality obligation; (c) is received from a third party free of any confidentiality obligation; or (d) is required to be disclosed by law, court order, or regulatory authority, provided the disclosing Party gives maximum practicable prior notice to the other. For the avoidance of doubt, production of the Audit Log under Clause 5.12(d) is permitted disclosure.

13.3 Survival

This Section 13 shall survive termination of this Agreement for a period of five (5) years.

SECTION 14 — DATA PROTECTION AND UK GDPR ROLES

14.1 Compliance

Each Party shall comply with its respective obligations under the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018 in connection with any personal data processed in connection with this Agreement.

14.2 Roles of the Parties — Client as Controller, Company as Processor

The Parties acknowledge, agree, and record that, in respect of Operator Data, Operator Documents, Vehicle Data, Compliance Data, Licence Check Recency Data, and Walkaround Records processed through the Platform:

(a) the Client is the Data Controller. The Client alone determines the purposes and means of the processing of Operator Data, Operator Documents, and Compliance Data. This includes, without limitation:

(i) operator identity records and photographic identification;

(ii) driving licence number, entitlement categories, licence expiry date, and driving licence photocard images;

(iii) Licence Check Recency Data, being the Last DVLA Check Date (a timestamp) and the entitlement or CPC expiry date, and nothing further — see Clause 14.2(d)(iii) and Clause 14.2(f);

(iv) tachograph driver card numbers, card expiry dates, and card images, and any driver activity or download data attributable to a named Operator;

(v) camera verification captures, identity-verification photographs, and Walkaround Records, including any photograph or video footage in which an Operator is identifiable;

(vi) training, certification, CPC, and competence records, and any right-to-work documentation where that functionality is enabled by the Client; and

(vii) any other personal data relating to the Client's Operators, employees, Client Admins, or contractors;

(b) the Company is the Data Processor in respect of all such data. The Company processes Operator Data, Operator Documents, Compliance Data, Vehicle Data, Licence Check Recency Data, and Walkaround Records solely on the documented instructions of the Client, for the purpose of providing the Platform and operating the Compliance Module, the Approval Workflow, the Enforcement Matrix, and the Audit Log, and for no other purpose. The Company does not determine the purposes of that processing, does not use it for its own purposes, and does not analyse, interpret, assess, score, or evaluate any Operator on its own account;

(c) the Company's processing of such data is purely technical, infrastructural, and storage in nature. The operation of the Enforcement Matrix — including any Compliance Suspension, Vehicle Lock, or Operator Lock — is an automated function executed on data supplied, inputted, or attested by the Client, or relayed from a Government Data Source at the Client's instruction, in accordance with rules the Client has accepted by entering into this Agreement, and does not constitute the Company determining the purposes of processing or assuming Controller status. The Company's storage of an Operator Document does not constitute review of it — Clauses 5.5(b) and 5.6(c) apply;

(d) the Client warrants and undertakes that it has, and will maintain throughout the Subscription Term:

(i) a valid lawful basis under Article 6 UK GDPR for the processing of all Operator Data and Operator Documents recorded within the Platform;

(ii) where applicable, a valid Article 9 condition and a Schedule 1 Data Protection Act 2018 condition, together with an appropriate policy document, in respect of any special category data it elects to record;

(iii) sole and exclusive responsibility, as Data Controller, for verifying the underlying driving record. The Client acknowledges and agrees that:

(A) the Client alone is responsible for obtaining each Operator's consent and check code as required, for accessing the official DVLA Portal, for reviewing that Operator's physical driving licence record — including any endorsement, penalty point, disqualification, restriction, or entitlement limitation disclosed by it — for determining, documenting, and applying its own fitness-to-drive criteria to that record, for acting upon that determination, and thereafter for updating the last_dvla_check_date within the Compliance Module;

(B) the Company performs no part of that verification. The Company does not access the DVLA Portal, holds and uses no check code, does not retrieve, view, receive, store, assess, interpret, score, or evaluate any driving licence record, and does not determine — and holds no view on — whether any Operator is fit to drive. The Company has no visibility of any offence record, endorsement, penalty point, or disqualification, and no means of acquiring any;

(C) the Company stores the Last DVLA Check Date only — a timestamp recording that a check occurred — together with the entitlement or CPC expiry date. The Platform is not designed to receive, and the Company does not store, any DVLA check code, any pass/fail or other outcome flag, any fitness determination, any offence record, endorsement code, penalty point count, disqualification particular, conviction detail, or offence narrative;

(D) the Enforcement Matrix acts on the age of that timestamp and on nothing else. An Operator Lock arising under Clause 5.13 denotes only that an administrative check is overdue. It is not an adverse finding and permits no inference as to any Operator's driving record, conduct, or fitness; and

(E) accordingly, the Company processes no data relating to criminal convictions or offences within the meaning of Article 10 UK GDPR in connection with driver licence compliance, and the Client shall not cause it to do so;

(iv) all required privacy notices issued to its Operators, covering the collection and processing of driving licence data, licence checking and its outcomes (which outcomes the Client processes outside the Platform), Operator Documents and their storage, tachograph card and activity data, and camera verification and walkaround captures; and

(v) any necessary Data Protection Impact Assessment under Article 35 UK GDPR in respect of camera verification, walkaround capture, tachograph data processing, licence checking, Operator Document storage, and any systematic monitoring of Operators;

(e) nothing in this Agreement shall be construed as making the Company a Controller, joint Controller, or co-Controller of Operator Data, Operator Documents, Vehicle Data, Compliance Data, Licence Check Recency Data, or Walkaround Records; and

(f) Data minimisation — prohibition on recording check codes, outcomes, and offence detail. The Client shall not upload to, enter into, transmit to, or store within the Platform — whether in a structured field, a free-text field, a note, an attachment, a document upload, an image, a screenshot, the Approval Workflow, or otherwise — any DVLA check code, pass/fail or other outcome flag, fitness-to-drive determination, driving offence record, endorsement code, penalty point count, disqualification particular, conviction detail, or offence narrative relating to any Operator. The Platform is designed to hold a date and an entitlement expiry, and nothing more. The Client shall retain all licence check outcomes and assessments within its own systems, outside the Platform. The Client acknowledges that:

(i) any such data recorded in breach of this Clause is recorded without the Company's authority, instruction, or consent, and outside the scope of the processing instructions given under this Agreement;

(ii) the Company may delete any such data without notice upon becoming aware of it, and shall have no liability for doing so; and

(iii) the indemnity at Clause 2.6(i) applies to any regulatory action, data subject claim, or loss arising from the presence of such data within the Platform.

14.3 Company's Processor Obligations

In its capacity as Data Processor under Clause 14.2, the Company shall:

(a) process Operator Data, Operator Documents, and Compliance Data only on the Client's documented instructions, save where required to do so by law, in which case the Company shall inform the Client of that legal requirement before processing unless prohibited from doing so;

(b) ensure that persons authorised to process such data are subject to appropriate confidentiality obligations;

(c) implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, in accordance with Article 32 of the UK GDPR, having regard to the sensitivity of driving licence, tachograph, identity-image, and Operator Document data;

(d) not engage any sub-processor without the Client's general written authorisation, which is hereby given in respect of the sub-processors listed in Schedule 5, provided that the Company shall give the Client 30 days' notice of any intended addition or replacement of a sub-processor and the Client may object on reasonable data protection grounds;

(e) taking into account the nature of the processing, assist the Client by appropriate technical and organisational measures, insofar as reasonably possible, in fulfilling the Client's obligations to respond to data subject rights requests from its Operators;

(f) assist the Client in ensuring compliance with its obligations under Articles 32 to 36 of the UK GDPR, taking into account the nature of processing and the information available to the Company;

(g) notify the Client without undue delay upon becoming aware of a personal data breach affecting Operator Data, Operator Documents, or Compliance Data;

(h) at the Client's election, delete or return all Operator Data, Operator Documents, and Compliance Data at the end of the Subscription Term in accordance with Clause 12.3(e), save where retention is required by law or as provided at Clause 5.12(d) in respect of the Audit Log; and

(i) make available to the Client information reasonably necessary to demonstrate compliance with this Section 14 and allow for and contribute to audits conducted by the Client or an auditor mandated by the Client, subject to reasonable notice, frequency limits, and the Client bearing the Company's reasonable costs of such audit.

14.4 Data Processing Agreement

The Parties shall execute a Data Processing Agreement in the form set out in Schedule 5 (or such other form as agreed in writing), which shall govern the Company's processing of personal data as Data Processor and shall form part of this Agreement. Schedule 5 shall specify the subject matter and duration of processing, the nature and purpose of processing, the types of personal data (including Operator Documents and the last_dvla_check_date field), the categories of data subjects, and the approved sub-processors, as required by Article 28(3) of the UK GDPR. In the event of any conflict between this Section 14 and Schedule 5, Schedule 5 shall prevail.

14.5 Automated Decision-Making — Enforcement Matrix

The Client acknowledges that the Enforcement Matrix executes automated decisions on the Client's data. Where any such decision — in particular an Operator Lock arising from a Stale Check, an expired Client-inputted date, or the absence or revocation of a Client Approval, or a Vehicle Lock affecting an identified Operator's ability to work — may produce legal effects concerning, or similarly significantly affect, a natural person within the meaning of Article 22 UK GDPR:

(a) the Client, as Controller, is solely responsible for identifying whether Article 22 is engaged, for establishing a lawful exception under Article 22(2), and for providing any required safeguards to the affected Operator, including the right to obtain human intervention, to express a point of view, and to contest the decision;

(b) the Company shall, on the Client's documented instruction, provide the Client with the underlying data and the applicable Enforcement Matrix rule relied upon, to enable the Client to conduct any human review it is required to provide. The Client acknowledges that, in respect of an Operator Lock arising from a Stale Check, the underlying data comprises a single timestamp and the applicable rule is a simple comparison against the Check Recency Period, such that the logic is fully intelligible and readily explicable to any affected Operator. The Client further acknowledges that, in respect of any Operator-level restriction arising from a Tier 1B Credential, the Client's own Client Admin has already made a human decision in recording, refusing, or revoking the Client Approval upon which the Enforcement Matrix acts, such that the decision is not solely automated at the point of substance; and

(c) the Company does not, and will not, provide human review of any Enforcement Matrix decision to any Operator directly, that being the Controller's responsibility.

14.6 Operator Claims — Client Responsibility

The Client acknowledges that, as Data Controller of Operator Data and Operator Documents, it bears primary responsibility for any claim, complaint, or regulatory action brought by an Operator in respect of the collection, processing, retention, or disclosure of that Operator's personal data — including driving licence data, licence check outcomes processed outside the Platform, Operator Documents, tachograph card and activity data, and camera verification or walkaround captures — and including any complaint to the Information Commissioner's Office. The indemnities at Clauses 2.6(h) and 2.6(i) apply to any such claim brought against the Company.

14.7 End-User Location Data

The Client acknowledges that the Platform processes real-time GPS location data from drivers and End-User pickup location data for the purposes of ETA calculation and dispatch routing. This processing is described in the Company's Privacy Policy, which the Client shall ensure is brought to the attention of its End-Users where required by applicable law. Where End-User personal data originates from the Towpal Marketplace and is transmitted to the Client via the Towpal Integration, the Client acknowledges that Towpal Ltd is the primary data controller of that data in its consumer-facing capacity, and that the Client assumes data controller obligations in respect of any such personal data from the moment it is received and processed by the Client in connection with the relevant Recovery Service.

SECTION 15 — GENERAL PROVISIONS

15.1 Governing Law and Jurisdiction

This Agreement and any dispute or claim arising out of or in connection with it (including non-contractual disputes) shall be governed by and construed in accordance with the laws of England and Wales. Each Party irrevocably submits to the exclusive jurisdiction of the courts of England and Wales for the resolution of all such disputes.

15.2 Entire Agreement

This Agreement, together with all Schedules and Order Forms executed hereunder, constitutes the entire agreement between the Parties in relation to its subject matter and supersedes all prior agreements, representations, warranties, and understandings — including any pre-contractual representations, forecasts, or projections regarding Towpal Lead volumes or revenue potential, and any statement, demonstration, or marketing material concerning the Compliance Module, the Approval Workflow, the Enforcement Matrix, any warning, notification, or Courtesy Attempt functionality, or any Multi-Year Term. Each Party acknowledges that it has not relied on any representation, warranty, or undertaking not expressly set out in this Agreement.

15.3 Amendments

No amendment to this Agreement shall be valid unless made in writing and signed by authorised representatives of both Parties, save that the Company may update the Schedules — including Schedule 6 (Monitored Compliance Credentials, Compliance Mechanisms, and Declared Data Sources) — on no less than 30 days' written notice. The Company's right to update the Schedules shall not be exercised so as to increase the Locked Fee of a Client on a Multi-Year Term during the currency of that term, contrary to Clause 9.7.

15.4 Waiver

No failure or delay by either Party in exercising any right or remedy shall constitute a waiver of that right or remedy. In particular:

(a) no forbearance by the Company in enforcing a Compliance Suspension, Vehicle Lock, Operator Lock, Performance Warning Notice, or any exclusivity forfeiture provision shall constitute a waiver of its right to enforce the same or any similar provision on any subsequent occasion;

(b) no issuance of any Courtesy Attempt on any occasion shall create any expectation, obligation, duty, or course of dealing requiring the issuance of any Courtesy Attempt on any subsequent occasion; and

(c) no exercise of the right reserved at Clause 5.9(d) on any occasion, and no failure to exercise it, shall create any expectation, obligation, duty, or course of dealing requiring its exercise on any subsequent occasion, or import any duty to detect fraud.

15.5 Severability

If any provision of this Agreement is found by a court of competent jurisdiction to be invalid, unenforceable, or illegal, that provision shall be severed from the Agreement and the remainder shall continue in full force and effect.

15.6 Assignment

The Client may not assign, transfer, or subcontract any of its rights or obligations under this Agreement — including any benefit of Towpal Lead routing or of any Prepaid Territory Fee or Locked Fee — without the prior written consent of the Company. The Company may assign this Agreement to any group company or successor entity without the Client's consent, provided that any such assignee shall be bound by any subsisting Fee Lock.

15.7 Force Majeure

Neither Party shall be in breach of this Agreement for any failure or delay in performance caused by circumstances beyond its reasonable control, including acts of God, floods, fire, civil unrest, or government action, provided it gives prompt written notice and uses reasonable endeavours to mitigate the effect. For the avoidance of doubt, any failure or downtime of the Towpal Marketplace operated by Towpal Ltd, and any unavailability, delay, latency, inaccuracy, interface change, deprecation, suspension, cessation, or withdrawal of the Vehicle Data Aggregator (UK Vehicle Data Ltd) or of any Government Data Source declared in Schedule 6, shall constitute circumstances beyond the Company's reasonable control for the purposes of this Clause 15.7. Force majeure shall not excuse the Client's obligation to maintain current Compliance Credentials or to pay Fees when due.

15.8 Notices

All notices under this Agreement shall be in writing and delivered by email (with read receipt or delivery confirmation) or by first-class recorded post to the addresses set out in the Order Form. Notices shall be deemed received: (a) if by email, on the next business day after sending; (b) if by post, two business days after posting. Automated notifications and Courtesy Attempts issued by the Compliance Module to the Client's registered account contact shall constitute valid written notice for the purposes of Section 5 only, subject always to Clauses 5.8(e) and 5.8(f).

15.9 Survival

The following shall survive termination or expiry of this Agreement for any reason:

(a) Section 2 (Liability Shield, Entity Separation, Aggregate Cap, and Client Indemnity);

(b) Clauses 5.5(f) and 5.6(f) (self-certification and Client Approval indemnities);

(c) Clause 5.6(e) (100% validation liability);

(d) Clauses 5.7(d) and 5.8(e) (Vehicle Data Aggregator / Government Data Source and Courtesy Attempt disclaimers);

(e) Clause 5.9(d) (fraud-response right — no duty to detect);

(f) Clause 5.10 (Zero Liability for Loss of Earnings and Operational Downtime);

(g) Clause 5.12 (Audit Log retention, conclusive-evidence status, and production);

(h) Clause 5.13 (Driver Licence Compliance limitations);

(i) Clause 8.5 (Merchant of Record obligations in respect of transactions processed prior to termination);

(j) Clause 9.8 and Schedule 3 Part D (Prepaid Territory Fee refund treatment and its characterisation);

(k) Section 10 (Intellectual Property);

(l) Section 13 (Confidentiality), for the period stated therein;

(m) Section 14 (Data Protection);

(n) Clause 15.1 (Governing Law and Jurisdiction); and

(o) any accrued payment obligations.

SCHEDULE 1 — ASSIGNED TERRITORY

Forming part of the Agreement

The Client's attention is drawn to Clause 4.3 (No Volume Guarantee), Clause 4.4 (Nature and Limitations of Exclusivity), and Clause 4.7 (Exclusivity Trapdoors).

SCHEDULE 2 — MINIMUM OPERATIONAL VOLUME

Forming part of the Agreement

The Client's attention is drawn to Clause 7.5 — no allowance is made for any period of Compliance Suspension, Vehicle Lock, or Operator Lock.

SCHEDULE 3 — FEES, SUBSCRIPTION TERMS, AND THE MULTI-YEAR PREPAID COMMITMENT

Forming part of the Agreement

Part A — Subscription Term Options

The Client shall elect one of the following in the Order Form. Each option is a genuinely alternative bargain, priced differently, and freely available to the Client.

Note on the two Multi-Year charges. A Multi-Year Term carries two distinct charges: the Prepaid Territory Fee (paid once, in advance, for the territory reservation and Exclusivity element, and governed by the primary-commitment characterisation and refund table in Part D and Clause 9.8) and the ongoing MRR Fee (paid monthly, for Platform access, fixed at the Locked Fee under Clause 9.7 and continuing to fall due throughout the term under Clause 9.3). The refund treatment in Clause 9.8 and Part D applies to the Prepaid Territory Fee; MRR Fees are paid monthly for access actually provided and are not prepaid or refundable save as expressly stated.

Part B — Commercial Terms

Part C — Payment Mechanics

C.1 The Prepaid Territory Fee is payable in full, in cleared funds, in advance, on or before the Effective Date. Instalments require the Company's express written consent (Clause 9.6(c)).

C.2 The Company is under no obligation to activate the Platform, configure the Assigned Territory, grant Exclusivity, or enable Towpal Lead routing until the Prepaid Territory Fee is received in full in cleared funds (Clause 9.6(b)).

C.3 All Fees are exclusive of VAT (Clause 9.10). Stripe processing fees and any Government Data Source charges are third-party pass-through costs outside the Fee Lock (Clause 9.7(b)(iii)).

C.4 Fees continue to fall due in full during any Compliance Suspension, Vehicle Lock, or Operator Lock (Clauses 5.10 and 9.3).

Part D — The Multi-Year Prepaid Commitment: Characterisation of the Bargain

This Part D records the commercial substance of the Multi-Year bargain and is to be read with Clauses 9.5, 9.6, 9.8, and 12.1(b).

D.1 — The bargain. The Prepaid Territory Fee is the price of a committed term of territory reservation and Exclusivity. In electing a Multi-Year Term, the Client commits, as a single indivisible commitment, to a twenty-four or thirty-six month term during which the Company reserves the Assigned Territory to the Client and (where granted) confers Exclusivity, in exchange for payment of the Prepaid Territory Fee in full and in advance and the Client's duration commitment. In return the Client receives a discounted Locked Fee on the ongoing MRR Fee, materially below the Standard Rate available on the Annual Term, together with the price certainty and security of tenure described in Clause 9.5. For the avoidance of doubt, the ongoing MRR Fee for Platform access remains payable monthly throughout the term (Clause 9.3 and Schedule 3 Part A); the Prepaid Territory Fee prepays the territory and Exclusivity element only, and it is that element to which the primary-commitment characterisation in this Part D, and the refund table in Clause 9.8, apply.

D.2 — Primary obligation, not secondary. The Client's obligation to commit for the elected duration, and to pay the Prepaid Territory Fee for it, is a primary contractual obligation and a primary term of the bargain. It is not a secondary obligation. It is not a remedy, sanction, deterrent, or consequence triggered by any breach. It is simply what the Client has agreed to buy, and the price at which the Company has agreed to sell it.

D.3 — The Committed Period. The Committed Period is [12] months from the Effective Date. Where the Client serves notice to terminate for convenience during the Committed Period, no refund of the Unexpired Portion is due, in accordance with Clause 9.8. The Client acknowledges that:

(a) this consequence arises from the Client's own election to terminate, not from any breach by the Client and not as any sanction imposed by the Company. No breach is required for it to operate, and no breach triggers it;

(b) it is the price of the discounted, committed bargain the Client freely chose. The Client has received, and continues to receive, the benefit of a [X]% discount to the Standard Rate and the protection of the Fee Lock at Clause 9.7 in direct consideration for that commitment; and

(c) it applies to a term the Client elected in preference to a genuinely available alternative — the Annual Term, at the higher Standard Rate, with unrestricted convenience termination and pro-rata refund throughout. The Client was not required to elect a Multi-Year Term, and could have obtained flexibility by paying more.

D.4 — Legitimate interest. The Company has a legitimate commercial interest in the performance of the committed term, beyond mere compensation for the Fees themselves, including: (a) withholding the Assigned Territory from the open market for the committed duration, and forgoing the opportunity to licence those postcodes to any other operator during it; (b) forgoing its own pricing flexibility by granting the Fee Lock; (c) committing configuration, onboarding, integration, and territory-reservation resource at the outset of the term; and (d) planning its own capacity, revenue, and territory allocation on the faith of the commitment.

D.5 — Reciprocity. The bargain is not one-sided. Where the Company terminates for convenience, the Client receives a full refund of the Unexpired Portion (Clause 9.8) — the Company bears the entire cost of its own election. Where the Company terminates for cause, the Client nonetheless receives the Unexpired Portion less only the Company's actual, evidenced losses — the Company retains nothing beyond what it can prove. In neither case does the Company profit from termination.

D.6 — Post-Committed Period. After the Committed Period expires, the Client may terminate for convenience on the applicable Termination Notice Period and receives the Unexpired Portion less a [10]% administrative and de-configuration charge, being a genuine pre-estimate of the Company's cost of de-configuring the territory, releasing and re-marketing the postcodes, unwinding the Towpal routing configuration, and administering the exit.

D.7 — Informed election. The Client confirms that: (a) it was offered the Annual Term at the Standard Rate as a genuine alternative; (b) it had the opportunity to take independent legal advice before electing; (c) the discount, the Committed Period, and the refund consequences at Clause 9.8 were disclosed to it before election; and (d) it elected the Multi-Year Term freely, with full knowledge of these terms, in order to obtain the discount and the Fee Lock.

SCHEDULE 4 — WHITE-LABEL TERMS

Forming part of the Agreement where applicable (Clause 3.3)

[Optional. To be completed only where the Company has agreed in writing that the Client may deploy the Platform under its own trading name or branding. No Intellectual Property Rights are conferred on the Client by any such arrangement.]

SCHEDULE 5 — DATA PROCESSING AGREEMENT (ARTICLE 28(3) UK GDPR)

Forming part of the Agreement · Mandatory · Effective on the Effective Date

This Data Processing Agreement ("DPA") is made between the Company and the Client and forms part of, and is governed by, the Agreement. It records the terms on which the Company, as Processor, processes personal data on behalf of the Client, as Controller, in accordance with Article 28 of the UK GDPR and Section 14 of the Agreement.

Terms defined in the Agreement have the same meaning in this DPA. In addition:

"UK GDPR" means the retained EU law version of Regulation (EU) 2016/679 as it forms part of the law of England and Wales by virtue of the European Union (Withdrawal) Act 2018, together with the Data Protection Act 2018 ("DPA 2018");

"Controller", "Processor", "Sub-Processor", "Data Subject", "Personal Data", "Special Category Data", "processing", and "personal data breach" have the meanings given in the UK GDPR;

"Sub-Processor" means any third party engaged by the Company to process Client Personal Data in connection with the provision of the Platform;

"Client Personal Data" means the Personal Data described in Part A that the Company processes on behalf of the Client under the Agreement.

Conflict. In the event of any conflict between the body of the Agreement (including Section 14) and this Schedule 5, this Schedule 5 prevails in respect of the processing of Client Personal Data, in accordance with Clause 14.4.

PART A — DETAILS OF PROCESSING (Article 28(3))

This Part A is the record required by Article 28(3) UK GDPR of the subject matter, duration, nature, purpose, data types, and data subjects of the processing.

A.1 — Roles of the Parties

The Company does not determine the purposes or essential means of the processing of Client Personal Data, does not use it for its own purposes, and does not analyse, assess, score, or evaluate any Data Subject on its own account, consistent with Clauses 14.2(b) and 14.2(e).

A.2 — Subject Matter of the Processing

The provision of the DXDD Recovery Platform to the Client, comprising: dispatch coordination and routing; GPS-based location and mapping; the Compliance Module and its compliance-tracking tools (the "Digital Clipboard" / Approval Workflow); the Enforcement Matrix; the Audit Log; payment facilitation; and, where active, the transmission of Towpal Leads via the Towpal Integration.

A.3 — Nature of the Processing

Collection, recording, organisation, structuring, storage, retrieval, transmission (including transmission to a Service Provider's assigned Operator and, for compliance records, retention as an inert stored record), hosting, back-up, access control, automated rules-based enforcement (the Enforcement Matrix), logging (the Audit Log), and — on expiry or at the Client's election — deletion or return. The processing is technical, infrastructural, and storage in nature. Storage of an Operator Document does not constitute review of it (Clauses 5.5(b), 5.6(c), 14.2(c)).

A.4 — Purpose of the Processing

To provide the Platform and perform the Company's obligations under the Agreement — specifically: (a) dispatch routing of recovery jobs; (b) live location and ETA functionality; (c) operation of the compliance-tracking tools (the Digital Clipboard), by which a Client Admin records and approves the Client's own Operators' documents; (d) operation of the Enforcement Matrix on Client-supplied dates, Client Approvals, timestamps, and relayed Aggregator Data; (e) maintenance of the Audit Log; and (f) facilitation of payment via Stripe Connect. The Company processes for no other purpose.

A.5 — Duration of the Processing

The Term of the Agreement, plus the agreed post-termination retention period — being the period during which the Client may request export under Clause 12.3(e) and, in respect of the Audit Log only, the retention period at Clause 5.12(d) (the Subscription Term plus [6] years) — after which Client Personal Data is deleted or returned at the Client's election in accordance with Section D below, save where retention is required by law.

A.6 — Categories of Data Subject

(a) the Client's Operators (drivers, recovery technicians, and roadside operatives);

(b) the Client's Client Admins and other authorised users of the Client's Platform instance; and

(c) the Client's end-customers (stranded motorists / End-Users) whose job data is processed through the Platform, including any whose request originated as a Towpal Lead.

A.7 — Categories of Personal Data

A.8 — STRICT EXCLUSION: Article 10 Data Prohibited

The Client shall NOT, and the Platform is not designed to, process any Article 10 UK GDPR data (personal data relating to criminal convictions and offences, and related security measures) in connection with driver licence compliance. In particular, and in accordance with Clauses 5.13, 14.2(d)(iii), and 14.2(f), the following are strictly prohibited from being uploaded to, entered into, transmitted to, or stored within the Platform, in any field, note, attachment, image, or screenshot:

❌ any DVLA check code;

❌ any pass/fail or other outcome flag, or fitness-to-drive determination;

❌ any driving offence record, endorsement code, penalty point count, disqualification particular, conviction detail, or offence narrative.

The Platform holds a date and an entitlement expiry, and nothing more. The Company relies on the Client's warranty and the data-minimisation prohibition at Clause 14.2(f); any Article 10 data recorded in breach is processed without the Company's authority or instruction, outside the scope of this DPA, may be deleted by the Company without notice, and is subject to the indemnity at Clause 2.6(i). The Client, as Controller, is solely responsible for its own separate processing of licence-check outcomes outside the Platform.

A.9 — Companies House Verification — Lawful Basis

The onboarding Companies House Verification described at Clause 2.8 processes the corporate-identity particulars at A.7 (including, incidentally, a director's or Client Admin's Personal Data appearing in the public register). In respect of this discrete processing:

(a) the Company acts as Controller, not Processor, this being processing for the Company's own contract-formation and anti-impersonation purposes rather than on the Client's instructions;

(b) the lawful basis is Article 6(1)(f) UK GDPR (legitimate interests) — the Company's legitimate interest in B2B identity verification, verifying the legal identity of its counterparty, and preventing impersonation and fraud in contract formation; and

(c) the processing is limited to the administrative purpose at Clause 2.8(b), involves no assessment of the Client's compliance or fitness, and does not dilute the Section 5 shields (Clause 2.8(d)). It is recorded here for completeness and transparency; it falls outside the Processor relationship that is the primary subject of this DPA.

PART B — APPROVED SUB-PROCESSORS (Article 28(2), 28(4))

B.1 — General Authorisation

The Client gives its general written authorisation under Clause 14.3(d) to the Company's engagement of the Sub-Processors listed at B.2. The Company shall: (a) impose on each Sub-Processor, by written contract, data-protection obligations equivalent to those in this DPA, in accordance with Article 28(4); (b) remain fully liable to the Client for each Sub-Processor's acts and omissions in respect of Client Personal Data; and (c) give the Client [30] days' prior written notice of any intended addition or replacement of a Sub-Processor, during which the Client may object on reasonable data-protection grounds (Clause 14.3(d)).

B.2 — List of Approved Sub-Processors

B.3 — Objection

If the Client reasonably objects to a new or replacement Sub-Processor within the notice period, the Parties shall discuss in good faith. If no resolution is reached, the Client may terminate the affected Platform functionality or the Agreement under Section 12, with the refund treatment at Clause 9.8 applying. Absent objection within the notice period, the Sub-Processor is deemed approved.

PART C — PROCESSOR OBLIGATIONS (Article 28(3)(a)–(h))

The Company shall, in accordance with Article 28(3) and Section 14.3:

(a) Documented instructions — process Client Personal Data only on the Client's documented instructions (which comprise the Agreement, this DPA, and the Client's use and configuration of the Platform), including as to international transfers, unless required to process by law, in which case the Company informs the Client first unless legally prohibited (Article 28(3)(a));

(b) Instruction beyond scope — immediately inform the Client if, in its opinion, an instruction infringes the UK GDPR or other data-protection law;

(c) Confidentiality — ensure that persons authorised to process Client Personal Data are subject to an appropriate duty of confidentiality (Article 28(3)(b));

(d) Security — implement the technical and organisational measures at Part E, appropriate to the risk, in accordance with Article 32 (Article 28(3)(c)), having particular regard to the sensitivity of compliance document images and location data;

(e) Sub-Processors — engage Sub-Processors only in accordance with Part B (Article 28(3)(d), 28(4));

(f) Data-subject rights — taking into account the nature of the processing, assist the Client by appropriate technical and organisational measures, insofar as reasonably possible, to respond to requests from Data Subjects exercising their rights under Chapter III UK GDPR (Article 28(3)(e)), including by providing the underlying data and the applicable Enforcement Matrix rule where an Operator contests an automated restriction (Clause 14.5(b));

(g) Controller assistance — assist the Client in ensuring compliance with Articles 32 to 36 (security, breach notification, DPIAs, and prior consultation), taking into account the nature of the processing and the information available to the Company (Article 28(3)(f));

(h) Breach notification — notify the Client without undue delay upon becoming aware of a personal data breach affecting Client Personal Data, with sufficient information to enable the Client to meet its own Article 33/34 obligations;

(i) Deletion or return — at the Client's election, delete or return all Client Personal Data at the end of provision of the services, per Part D and Article 28(3)(g); and

(j) Audits and information — make available to the Client the information reasonably necessary to demonstrate compliance with Article 28, and allow for and contribute to audits, including inspections, conducted by the Client or a mandated auditor, subject to reasonable notice, frequency limits, confidentiality, and the Client bearing the Company's reasonable costs (Article 28(3)(h)).

PART D — RETURN AND DELETION

D.1 On expiry or termination of the Agreement, the Client has [14] days (Clause 12.3(e)) to request export of its Client Personal Data in a commonly used, machine-readable format.

D.2 After that period, and at the Client's election, the Company shall delete or return all Client Personal Data and delete existing copies, save to the extent retention is required by law.

D.3 By express exception, the Audit Log is retained for the Subscription Term plus [6] years under Clause 5.12(d), and may be produced to a regulator, court, insurer, or enforcement authority on lawful request without the Client's further consent. This retention is a documented instruction of the Client for the purposes of Article 28(3)(g).

D.4 Where a Sub-Processor holds Client Personal Data, the Company shall procure its deletion or return on the same basis.

D.5 The Company may retain Client Personal Data to the minimum extent, and for the minimum period, required by applicable law, and shall protect it and process it only for the purpose of that legal requirement.

D.6 Payment data. Raw card data is never held by the Company (Section 8). Transaction metadata is retained per the Company's and Stripe's respective legal obligations.

PART E — TECHNICAL AND ORGANISATIONAL MEASURES (Article 32)

The Company implements and maintains at least the following, appropriate to the risk:

(a) Encryption — encryption of Client Personal Data in transit (TLS) and at rest, including for stored compliance document images;

(b) Access control — role-based access control, least-privilege access, unique credentials, and multi-factor authentication for administrative access; Client Admins and Operators access only their own Client instance's data;

(c) Tenant separation — logical separation of each Client's data within the multi-tenant Platform;

(d) Audit logging — the append-only, tamper-evident Audit Log (Clause 5.12), recording user identity and timestamp to the second for the actions specified;

(e) Resilience and back-up — regular back-ups, restoration testing, and measures to ensure ongoing confidentiality, integrity, availability, and resilience (Article 32(1)(b), (c));

(f) Data minimisation by design — the Platform is architected not to receive Article 10 data in the licence-check flow (holding only the last_dvla_check_date timestamp and entitlement expiry), giving effect to A.8 and Clause 14.2(f) at the level of system design;

(g) Sub-Processor security — contractual security obligations equivalent to this Part E imposed on each Sub-Processor at Part B; and

(h) Testing — a process for regularly testing, assessing, and evaluating the effectiveness of these measures (Article 32(1)(d)).

PART F — INTERNATIONAL TRANSFERS

F.1 Where the provision of the Platform requires Client Personal Data to be transferred to, or processed in, a country outside the UK — including by the Sub-Processors at Part B whose processing may occur in the United States — such transfer is made only where a valid transfer mechanism is in place: UK adequacy regulations, or the UK International Data Transfer Agreement (IDTA) or the UK Addendum to the EU Standard Contractual Clauses, together with any supplementary measures required following a transfer risk assessment.

F.2 The Company shall make details of the safeguards relied upon available to the Client on request.

F.3 Transfers are a documented instruction of the Client under Part C(a); the Client, as Controller, remains responsible for ensuring its own instructions for transfer are lawful.

PART G — GENERAL

G.1 Liability. The Company's liability under this DPA is subject to the limitations and exclusions in the Agreement, including the aggregate cap at Clause 2.4, save to the extent such limitation is not permitted by the UK GDPR or the DPA 2018.

G.2 Controller warranties. The Client warrants that it has a valid lawful basis and all necessary notices and consents for the processing it instructs (Clauses 5.14, 14.2(d)), and that its instructions comply with data-protection law.

G.3 Term. This DPA takes effect on the Effective Date and continues for as long as the Company processes Client Personal Data.

G.4 Precedence. In the event of conflict with the body of the Agreement in respect of the processing of Client Personal Data, this Schedule 5 prevails (Clause 14.4).

SCHEDULE 6 — MONITORED COMPLIANCE CREDENTIALS, COMPLIANCE MECHANISMS, AND DECLARED DATA SOURCES

Forming part of the Agreement · Updatable by the Company on 30 days' notice under Clauses 5.2(d) and 15.3

Part A — Declared Mechanisms and Data Sources

This Part A is a truthful declaration of the mechanism by which each Compliance Credential is recorded, and the provenance of the data upon which the Enforcement Matrix operates, made for the purposes of Clauses 2.1(d), 5.1(b), 5.1(c), 5.5, 5.6, and 5.7.

A.1 — Tier 1A · Self-Certified Credentials

Mechanism: the Client uploads a document file and inputs an expiry date. The Platform stores the file inert and never reads it. The Enforcement Matrix operates on the inputted date alone, blindly (Clause 5.5).

Effect on expiry (Clause 5.1A): of the credentials below, only the three fleet-level insurances (employers' liability, public liability, goods-in-transit) are Blocking Credentials — their expiry triggers an automated fleet-level Compliance Suspension. All other Tier 1A credentials in this table are flag-only — expiry surfaces an adverse status but does not automatically suspend or lock anything; the Client must act on the flag.

A.2 — Tier 1B · Operator-Level Client-Approved Credentials

Mechanism: a Client Admin views the document within the Approval Workflow, applies the Client's own criteria, records a Client Approval, and inputs an expiry date. The Company never views the document and plays no part in the approval (Clause 5.6).

Effect on expiry (Clause 5.1A): of the credentials below, only Operator licence-check recency (Stale Check) is a Blocking Credential — a stale or absent last_dvla_check_date triggers an automated Operator Lock. All other Tier 1B credentials in this table are flag-only — expiry or a missing approval surfaces an adverse status but does not automatically lock the Operator; revoking approval and standing the Operator down is the Client's act.

A.3 — Tier 2 · Government-Sourced Credentials, Retrieved via the Vehicle Data Aggregator

Mechanism: automated API query by the Platform against the vehicle registration mark recorded by the Client, made to the Vehicle Data Aggregator (UK Vehicle Data Ltd), which in turn sources the data from the relevant Government Data Source. The Company relays "as is"; it does not verify, at either link in the chain (Clause 5.7).

Truthful declaration of the data chain (Clauses 2.1(d)(iii), 5.1(c)(iii), 5.7). The Platform does not query any DVSA or DVLA interface directly. It queries the Vehicle Data Aggregator (UK Vehicle Data Ltd), an independent third-party commercial data aggregator, whose API returns MOT and VED status having itself obtained that data from the Government Data Source. There are two independent third-party links in the chain, neither owned or controlled by the Company.

"As is" reliance and zero-liability declaration (declaratory of, and governed by, Clause 5.7(d)). The Company relies on the Vehicle Data Aggregator and its API strictly on an "as is" and "as available" basis, and accepts zero liability, howsoever arising, for: (i) any downtime, outage, unavailability, latency, delay, throttling, rate limiting, or quota exhaustion of the Vehicle Data Aggregator; (ii) any inaccurate, incomplete, stale, cached, mismatched, corrupted, or erroneous data returned by the Vehicle Data Aggregator, whether the error originated with the aggregator or with the underlying Government Data Source; (iii) any Vehicle Lock applied, or not applied, in consequence of (i) or (ii); and (iv) any act, omission, insolvency, breach, price change, change of terms, suspension, or cessation of the Vehicle Data Aggregator. The Client's obligation to ensure every deployed vehicle holds a current MOT and valid VED is absolute and independent of what the aggregator returns or the Platform relays.

Substitution. The Company may substitute the Vehicle Data Aggregator, add a further aggregator, or revert to direct Government Data Source querying, on 30 days' notice under Clause 5.2(d), by amending this Part A.3. The Clause 5.7(d) disclaimers apply equally to any substitute.

Part B — Self-Certification Declaration (Tier 1A)

B.1 — The mechanism in full. For every Tier 1A Credential the Client (i) uploads a file and (ii) inputs an expiry date. That is the entirety of the process. Nothing else happens.

B.2 — The file is inert. The uploaded file is stored as an inert record for the Client's own convenience and audit purposes. It is never opened, read, examined, parsed, extracted, or looked at by the Company or by the Enforcement Matrix for any purpose whatsoever. The Company does not know what any file contains, whether it is genuine, whether it is legible, whether it relates to the credential claimed, whether it relates to the Client at all, or whether it is a document of any kind.

B.3 — Blind reliance. The Enforcement Matrix operates exclusively upon the Client-inputted expiry date and upon nothing else. The date is applied as fact, automatically, and without verification, question, cross-check, or independent enquiry, and regardless of its truth. The Company has no knowledge of, and no means of discovering, whether any inputted date is true, false, mistaken, mis-keyed, fabricated, or fraudulent.

B.4 — Client warranty. The Client warrants on a continuing basis that every inputted date is true, accurate, and current and corresponds exactly to the expiry of a genuine, subsisting, valid credential actually held; that every uploaded document is genuine, authentic, and unaltered; that it holds every credential it records; and that it will correct any date immediately upon becoming aware of any inaccuracy (Clause 5.5(d)).

B.5 — False entry = material breach + full indemnity. Any false, fabricated, forged, altered, backdated, post-dated, knowingly inaccurate, or recklessly inaccurate entry is a MATERIAL BREACH permitting immediate termination without cure (Clauses 5.5(e), 11.1(h), 11.2), and triggers the full third-party indemnity at Clause 5.5(f) — extending to any claim brought against the Company by any End-User, insurer, regulator, Traffic Commissioner, enforcement authority, motor club, or contracting counterparty who suffers loss in reliance upon, or in consequence of, the Client having been permitted to operate on the strength of that entry.

B.6 — No duty to detect. The Company owes no duty to detect, identify, question, investigate, or act upon any false or inaccurate entry, and none shall be implied from the Compliance Module, the Approval Workflow, the Enforcement Matrix, the Audit Log, any Courtesy Attempt, or the right reserved at Clause 5.9(d) (Clause 5.5(g)).

Part C — Vehicle Registration, Weight Default, and the Tachograph Exempt Toggle

C.1 — Mandatory vehicle fields. Per vehicle, the Client shall record: (a) the vehicle registration mark (upon which all Tier 2 Government Data Source queries depend); (b) make and model; (c) gross vehicle weight in kilograms (upon which the tachograph monitoring default depends); (d) insurance cover designation; (e) any LOLER-monitored lifting asset mounted on the vehicle; and (f) the Tachograph Exempt toggle setting.

C.2 — Tachograph monitoring default by weight.

Recorded GVW	Default	Client may change to
> 3,500kg	Tachograph Applicable — calibration monitored as Tier 1A (flag-only under Clause 5.1A; adverse status surfaced on expiry, no automated lock)	Tachograph Exempt by active declaration (C.3)
≤ 3,500kg	Not monitored — no calibration record required, no Vehicle Lock will arise from calibration	Tachograph Applicable by voluntary opt-in (C.4)

C.3 — The Tachograph Exempt toggle.

Setting	Meaning	Effect on the Enforcement Matrix
Tachograph Applicable (default above 3,500kg)	The Client declares the vehicle is within scope of applicable tachograph requirements	Tachograph Calibration monitored as Tier 1A, flag-only under Clause 5.1A — adverse status surfaced on expiry of the Client-inputted calibration date, no automated vehicle lock; the Client must act on the flag
Tachograph Exempt (active declaration only)	The Client declares, under Clause 5.3(b), that the vehicle falls outside the scope of applicable tachograph requirements	Tachograph Calibration monitoring disapplied for that vehicle only. No Vehicle Lock will arise from the absence or expiry of a calibration record. All other monitoring continues unaffected

C.4 — Exemption is never automatic. Exemption is never applied by the Platform and is never inferred from vehicle weight, class, body type, usage, or any other datum. The Client must positively elect it via the manual dashboard toggle and should, where the Platform provides the field, record a stated ground of exemption and in any event retain its own record of the ground. The Company does not review, assess, verify, question, or advise upon any stated ground. The Client warrants the accuracy of every Declaration and holds sole and exclusive liability for any false Declaration — Clause 5.3(e) applies in full, and the indemnity at Clause 2.6(f) applies.

C.5 — Sub-threshold opt-in. The Client may set the toggle to "Tachograph Applicable" for any vehicle with recorded GVW at or below 3,500kg. The Client acknowledges that a vehicle at or below the threshold may nonetheless fall within scope — including where it forms part of a combination whose aggregate weight exceeds the threshold — and that the default will not monitor such a vehicle unless the Client positively opts in. The Company gives no prompt, warning, or indication that opt-in may be required.

C.6 — Continuing obligation. The Client shall withdraw a Tachograph Exemption Declaration immediately upon the vehicle ceasing to be exempt, whether by reason of a change of vehicle, deployment, combination, or law. The Company does not monitor for, and will not detect, any such change.

C.7 — Audit Log. Every setting, amendment, and withdrawal of the toggle is recorded in the append-only Audit Log per Clause 5.12, capturing the registration mark, the prior and new state, the identity of the individual user account, and the date and time. Where a stated ground of exemption is captured, it is recorded with the entry. The Audit Log cannot be edited, overwritten, suppressed, or deleted by the Client. In respect of the toggle state it records, it is strong evidence of the state of any Declaration at the recorded time, absent manifest error, and is retained for the Subscription Term plus [6] years.

Part D — The Approval Workflow ("Digital Clipboard")

D.1 — Purpose. The Approval Workflow is a record-keeping and administrative convenience made available to the Client for the Client's own internal use, enabling a Client Admin to view, record, approve, reject, revoke, and re-approve the Client's own Operators' documents and record their expiry dates.

D.2 — The Company's absolute non-involvement. The Company never views, opens, reads, examines, or looks at any Operator Document. The Company never reviews, assesses, verifies, or checks any Operator Document or recorded date. The Company never approves, rejects, endorses, clears, or passes any Operator Document or any Operator, and holds no view whatsoever on any of them. The Company does not vet or screen any Operator and is not an employment agency, employment business, vetting service, or screening service. The Company does not select, appoint, authorise, control, supervise, direct, or instruct any Client Admin (Clause 5.6(c)).

D.3 — What "Approve" means. A Client Approval is an attestation by the Client, made by the Client's own representative, in the Client's own account, applying the Client's own criteria. It is not an approval granted by, endorsed by, participated in by, or known to the Company. By recording a Client Approval the Client attests that a competent authorised person actually examined the document; satisfied themselves it is genuine, authentic, unaltered, current, valid, and relates to the correct Operator; that the recorded expiry date is true; that the Client applied its own criteria and judgement; and that the Client has independently satisfied itself that the Operator holds every credential required by law, its insurers, its O-Licence undertakings, and its own contracts, whether or not recorded in the Compliance Module (Clause 5.6(d)).

D.4 — 100% Client liability on approval. Upon a Client Admin recording a Client Approval, the Client — as employer or engager of the Operator, and as Data Controller — assumes ONE HUNDRED PERCENT (100%) of the legal liability for that validation and for every consequence flowing from it. The Company assumes ZERO liability where a Client Admin approves a document that is forged, counterfeit, altered, expired, invalid, revoked, suspended, fraudulent, belongs to another person, or is in any way defective, and ZERO liability for the deployment of any Operator who — notwithstanding a subsisting Client Approval — is disqualified, unlicensed, without entitlement or CPC, without right to work, incompetent, dishonest, impersonating another, or otherwise unfit (Clause 5.6(e)). The full third-party indemnity at Clause 5.6(f) applies.

D.5 — What an approved status means. A green, approved, or unrestricted Operator status means only that a Client Admin clicked a button and typed a date. It means nothing else, and the Client shall not treat it as meaning anything else (Clause 5.6(e)(iv)).

D.6 — Mandatory interface characteristics. For the avoidance of doubt as to the Parties' intentions, and to ensure the Approval Workflow accurately reflects the allocation of responsibility recorded in this Agreement, the interface shall:

(a) attribute every approval to the named Client Admin who recorded it, and display it as such (for example: "Approved by [Client Admin name], [Client entity], [date and time]");

(b) not describe any Operator Document, Operator, or credential as verified, validated, checked, cleared, certified, or approved by the Company, by the Platform, or by DXDD Recovery;

(c) present an express attestation in the terms of Clause 5.6(d) at the point of approval, which the Client Admin must positively acknowledge; and

(d) not represent, imply, or suggest that the Company has seen, reviewed, or formed any view on any Operator Document.

D.7 — Not a checklist of the law. The Approval Workflow records the document types enumerated at Part A.2 and no others. The Company does not represent, and the Client shall not assume, that those document types constitute a complete, sufficient, or current statement of the credentials required for any Operator. The Client's obligations extend beyond what the workflow records (Clauses 5.1(f), 5.6(b)(iii)).

D.8 — Continuing obligation to act. A Client Approval is a point-in-time attestation. The Client shall revoke the approval and remove the Operator by its own action immediately upon becoming aware of any matter rendering the document invalid or the Operator unfit. The Platform will not do this, cannot do this, and must never be relied upon to do this (Clauses 5.6(g), 5.13(e)).

D.9 — Prohibited content. The digital clipboard is for documents evidencing entitlement and qualification. It is not a repository for driving records or offence data. No DVLA check code, outcome flag, fitness determination, offence record, endorsement code, penalty point count, disqualification particular, or conviction detail may be recorded within it, in any field, note, attachment, image, or screenshot (Clauses 5.6(i), 14.2(f)). The indemnity at Clause 2.6(i) applies.

D.10 — Audit Log. Every approval, rejection, revocation, and re-approval is recorded per Clause 5.12 — Operator, document type, Client Admin identity, date and time to the second — and is unalterable and conclusive evidence of who attested to what, and when.

Part E — Courtesy Attempts (All Credentials)

E.1 — Configured intervals. The Platform is configured to attempt to display UI banners and/or issue email notifications at one or more points prior to the applicable expiry date. The number and timing of attempts are at the Company's sole discretion, may differ between credentials and credential tiers, and may consist of a single attempt. No particular interval or sequence is promised.

E.2 — Attempted courtesy behaviour only. This is a description of attempted courtesy automated system behaviour. It is NOT a warranty, undertaking, guarantee, representation, promise, assurance, service level, or contractual obligation. The Company owes NO DUTY TO WARN (Clause 5.8(a)).

E.3 — Warnings derive from the Client's own data. For Tier 1A and Tier 1B, any Courtesy Attempt is calculated from the expiry date the Client itself inputted. A Courtesy Attempt is only ever as accurate as the Client's own data entry. A wrong date produces a wrong warning time, or none at all (Clause 5.8(b)).

E.4 — No guarantee of anything. The Company does not guarantee generation. The Company does not guarantee display. The Company does not guarantee transmission. The Company does not guarantee delivery. The Company does not guarantee receipt. The Company does not guarantee reading — whether at all, at any time, at any interval, by any channel, or to any recipient (Clause 5.8(e)(i)).

E.5 — Blocking applies regardless (Blocking Credentials only). Where the Blocking Function applies (Clause 5.1A(b)), the Compliance Suspension, Vehicle Lock, or Operator Lock operates automatically and unconditionally on expiry, regardless of whether any Courtesy Attempt was generated, displayed, transmitted, delivered, received, opened, read, understood, or acted upon (Clause 5.8(d)). For flag-only credentials, no automated lock applies and the Client must act on the flag.

E.6 — No liability, no defence, no deferral. No failure or absence of any Courtesy Attempt gives rise to any liability, postpones or invalidates any lock, constitutes any breach or duty, provides any defence, or founds any claim (Clause 5.8(e)(iii)).

E.7 — Discontinuable at will. The Company may modify, suspend, degrade, reduce, re-interval, or discontinue Courtesy Attempts entirely, at any time, without notice, consultation, or liability (Clause 5.8(e)(v)).

E.8 — The burden does not move. The burden of monitoring the currency of its own Compliance Credentials rests entirely and exclusively with the Client. The Company has no obligation to warn, and the Client shall not rely on being warned (Clause 5.8(f)).

Part F — Operator Licence Check Recency

F.1 — The only field. last_dvla_check_date — a timestamp. No check code. No pass/fail or other outcome flag. No fitness determination. No offence detail of any kind (Clauses 5.13(a), 14.2(f)).

F.2 — Check Recency Period. 180 days. Variable by the Company on 30 days' notice under Clause 5.2(d).

F.3 — Enforcement.

Condition	Status	Effect
last_dvla_check_date within 6 months	Current	No restriction
last_dvla_check_date older than 180 days	Stale Check	Operator Lock, automatic, zero days
last_dvla_check_date not recorded	Stale Check	Operator Lock, automatic, zero days

F.4 — What the Client must do. The Client alone: obtains the Operator's check code; accesses the official DVLA Portal; reviews the physical driving record; applies its own fitness-to-drive criteria; acts on the outcome; and then records the date. All outcomes are retained in the Client's own systems, outside the Platform.

F.5 — What the Platform does not know. A current date means only that the Client says a check happened within the last 180 days. The Platform has no knowledge of the outcome and is structurally incapable of enforcing upon it. The Enforcement Matrix will NOT lock an Operator the Client has checked and found disqualified — the Client must revoke that Operator's Client Approval and deactivate that Operator by its own action (Clause 5.13(e)).

F.6 — No inference. An Operator Lock under this Part discloses only that an administrative check is overdue. It is not an adverse finding and the Client shall not represent it as one (Clause 5.13(f)).

Part G — Additional or Re-Designated Credentials

[To be completed. Any credential added, removed, re-tiered, or re-sourced under Clause 5.2(d) must be recorded here with its declared mechanism, data source, tier, monitoring granularity, and enforcement effect, and notified to the Client on 30 days' written notice.]

EXECUTION

This Agreement is entered into on the Effective Date as defined in the preamble.

Signed for and on behalf of DX DIGITAL DESIGN (trading as DXDD Recovery):

Signed for and on behalf of the CLIENT:

SCHEDULE STATUS

Open bracketed figures requiring instruction before execution: Clause 5.11(b) [14] days · Clauses 5.11(c) and 11.1(g) [30] days · Clause 5.12(d) [6] years · Clauses 6.2 and 11.1(a) [3] days · Clause 6.3(a) [14] days · Clause 9.8 [10]% · Schedule 3 Part B [12] months Committed Period · Revision Date · Company number · Registered address · Fee figures at Schedule 3 Parts A and B — note the Multi-Year rows now require BOTH a Prepaid Territory Fee ([2YR/3YR PREPAID FEE]) AND a separate monthly Locked MRR ([2YR/3YR LOCKED MONTHLY]); ensure the Order Form itemises both charges consistently with the amended schedule.

Additional items arising from amendment rev-A: confirm the registered company number of UK Vehicle Data Ltd and insert it at the Vehicle Data Aggregator definition · verify that the Company's contract with UK Vehicle Data Ltd permits onward relay of MOT/VED data to Clients on the "as is" basis declared, and does not itself require the Company to give the Client warranties inconsistent with Clause 5.7(d) · confirm the Companies House and UK Vehicle Data Ltd processing activities are entered on the Company's Article 30 record of processing and reflected in Schedule 5 and the Privacy Policy.

— END OF AGREEMENT —