Create your affiliate account

TRAFFIC PROVIDER TERMS AND CONDITIONS These Traffic Provider Terms and Conditions (the "Terms") are issued by Four Nine Nine Ltd, a company registered in England and Wales with company number 16389592, of 3 Floor, 86-90 Paul Street, London, United Kingdom EC2E 4NE ("499"). They govern every supply of Traffic to 499 by the supplier identified in an applicable insertion order, order form, campaign confirmation or account registration ("Provider"). 499 and Provider are each a "Party". Acceptance. Provider accepts these Terms by ticking the acceptance box in 499's sign-up or registration form, by signing or electronically accepting an IO that references them, by registering for or using 499's delivery systems, or by delivering any Traffic, whichever occurs first. No signature is required. The individual completing the sign-up form or accepting on Provider's behalf represents and warrants that they are authorised to bind Provider, and Provider is bound accordingly. 499 will maintain a record of each acceptance, including the date, time, account identifier and the version of these Terms accepted, and that record is conclusive evidence of acceptance absent manifest error. These Terms and the applicable IO form the entire agreement for the supply of Traffic and supersede Provider's terms of sale, platform terms, purchase orders and any terms attached to Provider's invoices or correspondence, none of which have effect even if 499 has completed or acknowledged them. 1. DEFINITIONS "Applicable Law" means every law, regulation, binding regulatory rule and enforceable government order applying to a Party's activities under an IO, including advertising, marketing, consumer-protection, privacy, data-security, anti-spam, telemarketing, licensing, sanctions and anti-bribery requirements, and including the FTC Act and state UDAP statutes, CAN-SPAM, the Telephone Consumer Protection Act where messaging channels are used, and state privacy laws. "Billable Click" means a Click for which the billable event stated in the IO occurs on the Platform and which passes the Platform's validity filters, including uniqueness, geography and bot filtering as configured for the campaign, and satisfies the requirements of the IO and these Terms. "Click" means a consumer's visit, click or redirect delivered by Provider through 499's tracking to a destination designated by 499. Where an IO prices another unit (an impression, a session, a qualified visit or a call-through from a number pool), references to a Click include that unit. "Client" means any advertiser, buyer, network or other recipient of campaigns to which 499 directs Traffic, and their permitted downstream recipients. "Client Payment" means 499's actual receipt of cleared, non-refundable, non-reversible funds from a Client in respect of the campaign activity attributable to Provider's Traffic. "Compliance Event" means any of the events listed in Section 8.1. "Business Day" means a day other than Saturday, Sunday or a public holiday in England. "Creative" means every advertisement, banner, ad copy, keyword, search ad, social post, native placement, email, pre-lander, landing page, script or other material used to generate Traffic. "Invalid Traffic" means non-human, bot, emulator, data-centre, proxy-masked or click-farm activity; incentivised, forced, misleading or accidental clicks; cookie stuffing, click flooding, impression laundering, forced redirects, clickjacking, auto-refresh or hidden-frame activity; and any activity designed to simulate genuine consumer interest. "Personal Data" means information relating to an identified or identifiable natural person, including online identifiers, device identifiers, tracking, session and attribution data to the extent they identify a person, and any consumer data fields passed with Traffic, and any equivalent term under Applicable Law. "IO" means an insertion order, order form or written campaign confirmation that identifies the Traffic type, verticals, price and pricing unit, permitted channels and geographies, prohibited channels and practices, Creative approval requirements, tracking, caps and schedule, and any campaign-specific terms, and incorporates these Terms. "Platform" means the tracking and reporting systems operated or designated by 499, including Everflow, TrackDrive, Ringba and any successor system 499 designates in writing. "Source" means a website, application, media account, email list, publisher, sub-affiliate or other originator used to generate Traffic, whether operated by Provider or engaged directly or through any intermediary. "Source ID" means the persistent identifier used to attribute Traffic to a Source or placement. "Traffic" means Clicks and other visitor units supplied under an IO. 2. SCOPE AND CAMPAIGNS 2.1 Roles. Provider supplies Traffic to 499's campaigns. 499 purchases it on its own account. Provider is a supplier and is not an agent, broker, partner or representative of 499 and, except as provided in Section 7.3, has no relationship with, or claim against, any Client. 2.2 Campaigns and tracking. No campaign begins until 499 confirms an IO in writing or in the Platform and issues tracking links, parameters or number pools. Provider will send Traffic only through that tracking, exactly as issued, and will not alter, strip, re-map or chain it through undisclosed redirects. Provider's delivery of Traffic against an IO is acceptance of that IO and of these Terms. There is no minimum volume, purchase commitment, exclusivity or guaranteed run time unless an IO states it expressly. 2.3 Changes, caps and suspension. 499 may prospectively reduce a cap, change targeting, permitted channels, destinations or price on notice, or pause acceptance by operational notice; Provider's continued delivery after notice is acceptance. A stated cap is a maximum and not a commitment, does not roll over, and Traffic delivered above a cap is not billable unless 499 approved the overage in writing before delivery. 499 may prospectively pause or suspend a Source ID, a placement, a campaign or the whole of Provider's delivery on reasonable evidence of a quality, fraud, security, legal, consumer-harm or Client-relationship risk, or on the instruction of a Client, advertising platform or regulator. Provider will stop the affected flow immediately on notice, and Traffic delivered after notice is not billable. 3. TRAFFIC STANDARDS AND PROHIBITED PRACTICES 3.1 Delivery standard. Provider will deliver genuine consumer Traffic in conformity with the IO, from the channels, geographies and placements it permits, and will maintain quality controls sufficient to exclude Invalid Traffic before it reaches 499's tracking. 3.2 Prohibited practices. Provider will not deliver, and will procure that its Sources do not generate, any Traffic that: (a) is Invalid Traffic; (b) is generated using a Creative that has not been approved where the IO requires approval, or that has been materially changed after approval; (c) uses misleading government, benefit, brand, affiliation or endorsement claims, fake news formats, fabricated testimonials or reviews, or implied relationships with a government programme, carrier or insurer that do not exist; (d) bids on, or uses in ad copy, domains or display URLs, the trademarks or brand terms of 499, its Clients or third parties, unless the IO expressly permits it; (e) uses typosquatted, confusingly similar or misleading domains; (f) is generated through adult, piracy, hate, weapons or other content categories prohibited by the IO, or through placements misrepresented to 499; (g) is email traffic that does not comply with CAN-SPAM and equivalent laws, including accurate headers and sender identity, a functioning opt-out honoured within the legal deadline, use only of lists with documented opt-in consent, and suppression-list processing before every send; (h) is SMS or messaging traffic, unless the IO expressly permits it and the consent required for that channel is obtained and documented; (i) is generated through a Source suspended under these Terms; or (j) is otherwise deceptive, fraudulent or unlawful. 3.3 Creative approval and disclosure. Where the IO requires Creative approval, Provider will submit every Creative, pre-lander and email subject line for written approval before launch and before any material change. Provider will operate only disclosed channels and, on request, will identify the placements, accounts, domains and lists behind a Source ID. Approval by 499 does not transfer responsibility: as between the Parties, Provider remains responsible for the accuracy, substantiation, rights clearance and legal compliance of every Creative it or its Sources run. 3.4 Sources, traceability and re-brokering. Provider is fully responsible for every Source, sub-affiliate and intermediary it engages, and for their acts and omissions, as if they were Provider's own. Provider will maintain placement-level traceability through every intermediary to the originating property or list, and will produce that mapping on request under Section 4.3. Provider will not re-broker, resell or source Traffic from an intermediary that has not been disclosed to and approved by 499 in writing. A grouped Source ID is permitted only if Provider maintains the underlying placement-level mapping. 3.5 Source ID discipline. Provider will provide consistent, auditable Source IDs and will not move, relabel, re-number or re-route a suspended or paused Source or placement to a different Source ID, campaign or endpoint to evade a suspension. Doing so is a material breach incapable of cure and permits immediate termination and recoupment under Section 8. 4. COMPLIANCE AND RECORDS 4.1 Provider bears front-end compliance. Provider controls, or is responsible for those who control, the media, Creatives and channels that generate Traffic. Provider is solely responsible for compliance with Applicable Law in respect of the sourcing, generation and delivery of Traffic up to the consumer's arrival at 499's designated destination, including advertising content rules, platform policies binding on its accounts, email and messaging law, and any consumer data collection Provider performs on its own properties and pre-landers. Review, approval, testing, monitoring or feedback by 499 does not transfer any part of that responsibility to 499 and is not a waiver of any term. 4.2 Data collected by Provider. Where Provider collects consumer Personal Data on its own properties or pre-landers in the course of generating Traffic, Provider is the controller of that collection, will provide the notices and obtain the consents Applicable Law requires, and will not represent that 499 collected or instructed the collection. Where the IO provides for consumer data fields to be passed with Traffic: the consent or other lawful basis for each field must be obtained directly from the consumer at the point of origination, must name or clearly describe 499 and its Clients as permitted recipients in the form Applicable Law requires for the intended contact technology, and must not be inherited, purchased, appended or assumed; Provider will retain evidence of that consent, including the source URL, the disclosure and consent language and its version, timestamp, IP address and user agent, and any certificate the IO requires; and Provider will produce that evidence for identified units under, and with the consequences of, Section 4.3. 4.3 Records and production. Provider will retain records of its Creatives as run (including dated captures), placements, accounts, lists, opt-in evidence for email and messaging traffic, and delivery logs, for at least five years after the relevant activity; this survives termination. Provider will produce the records relevant to identified Traffic within two Business Days after a written request. If records for identified Traffic are not produced within five Business Days after a written reminder, that Traffic is not billable, any amount already paid for it is immediately repayable, and 499 may set that amount off under Section 8.4. Failure to retain records that would have been responsive to a claim raises a presumption, in any dispute between the Parties, that the missing records would not have supported Provider's position. 4.4 Security, incidents and consumer requests. Provider will maintain reasonable administrative, technical and physical safeguards appropriate to any Personal Data it handles in connection with an IO, and will notify 499 without undue delay and in any event within twenty-four hours after becoming aware of actual or suspected unauthorised access to, acquisition, loss or disclosure of such Personal Data, without waiting to complete its investigation, and will not notify consumers, Clients or regulators in 499's name without prior written consultation unless legally required. Provider will honour and pass through consent revocation and consumer privacy requests it receives in respect of such Personal Data within the deadline and scope Applicable Law requires, will pass each request that extends to 499's processing to 499 in writing within five Business Days, and will cooperate with 499's own handling of consumer requests passed to it. Each Party acts as an independent controller for the processing purposes it determines unless an IO or data addendum states otherwise. 4.5 Complaints and audit. Provider will pass to 499 without delay any consumer complaint, regulatory contact, platform enforcement action or legal threat relating to Traffic supplied under these Terms. On reasonable written evidence of a material breach, a third-party claim, a regulatory request or a Client demand, 499 may require records reasonably necessary to verify the issue; a formal audit will occur on ten Business Days' notice, no more than once in any twelve-month period absent an ongoing material issue, through 499 or an independent auditor under confidentiality obligations, at 499's cost unless the audit identifies a material breach, in which case Provider bears its reasonable cost. 5. RIGHTS AND DATA 5.1 Attribution data. All tracking data, session data and attribution data generated by Traffic passing through 499's tracking belongs to 499, and 499 may store, use, process, analyse, license and exploit it for any lawful purpose without restriction or further payment, in each case, to the extent such data is Personal Data, within the scope permitted by Applicable Law and the consumer's consent and without limiting any consumer's rights of access, correction, deletion or opt-out. Provider retains no right to condition, restrict or demand deletion of that data, save where required by Applicable Law or a valid consumer request. 5.2 Data fields passed with Traffic. Where an IO provides for consumer data fields to be passed, Provider grants 499, on delivery and as a condition of billability, a perpetual, irrevocable, worldwide, royalty-free, transferable and sublicensable right to use, process, distribute, sell and share those fields for any lawful purpose within the scope of Applicable Law and the consumer's consent. Nothing in this Section treats Personal Data as property or limits a consumer's rights; each Party acts as an independent controller for the purposes it determines unless an IO or data addendum states otherwise. 6. REPORTING, SYSTEM OF RECORD AND BILLABILITY 6.1 System of record. The Platform is the sole and exclusive system of record for clicks, sessions, redirects, validity determinations, billable events, counts and amounts payable. Provider's own tracker, analytics or reporting is for its internal purposes only and has no billing effect. Platform figures are conclusive absent manifest error notified within ten Business Days of the relevant statement with click-level or placement-level evidence; a tracking discrepancy is not itself manifest error, and Provider will not withhold delivery or treat an amount as due on the basis of its own figures. 6.2 Billability. Traffic is billable only if it is a Billable Click. Traffic is not billable if it is Invalid Traffic, fails the Platform's validity filters, falls outside the stated geography, device, channel or schedule targeting, was generated through a practice prohibited by Section 3.2 or a Source suspended under these Terms, or lacks the records required by Section 4.3. 6.3 Reversal and systemic defects. If Traffic is later determined to be non-billable, is rejected, clawed back or refused by a Client or an advertising platform on the basis of a defect or breach described in these Terms or the IO, or is the subject of a Compliance Event, the amount for that Traffic is reversed; if already paid, it is immediately repayable as a debt and may be set off under Section 8.4. An ordinary quality claim by a Client grounds a reversal against Provider only if the Client submitted it within the claim window of the terms governing that Client's purchase (for 499's standard Traffic Buyer Terms and Conditions, five Business Days from the end of the delivery week), measured by the date of the Client's submission and not by the date on which 499 decides it; this limitation does not apply to Invalid Traffic, fraud, Compliance Events, chargebacks, advertising-platform clawbacks evidenced by the platform's determination, or regulatory and legal matters, which may be raised within ninety days after delivery, or without time limit where a regulator or court requires. Where technical or statistically reliable evidence indicates that Invalid Traffic or a prohibited practice affects a wider population from a Source or placement, 499 may extend a reversal to the population reasonably shown to share the defect, and will provide Provider with the basis for that determination. 7. FEES, SELF-BILLING AND PAYMENT 7.1 Fees and self-billing. Fees are stated in the IO; unless it states otherwise, amounts are in United States dollars. 499 will raise self-billed invoices in Provider's name based on Platform figures. Provider agrees to accept those self-billed invoices, will not raise its own invoice for the same supply, and will notify 499 in writing within five Business Days of any change to its legal name, address, bank details, or VAT or tax registration status. Where required, the Parties will execute a self-billing agreement, renewable every twelve months. Provider will provide a valid W-9, W-8BEN-E or equivalent tax certification before the first payment. 7.2 Client Payment is a condition precedent to payment. This Section states an express condition precedent and not a timing mechanism. 499's obligation to pay Provider for Traffic arises only if and when 499 has received Client Payment for the campaign activity attributable to that Traffic. If 499 does not receive Client Payment, no obligation to pay Provider for that Traffic ever arises, and any amount previously accrued in respect of it ceases to be payable. Provider expressly assumes the credit risk of Client non-payment, insolvency, dispute, set-off and chargeback in respect of Traffic it supplies. Provider acknowledges that it has been given the opportunity to take independent legal advice on this Section, that it understands it may never be paid for conforming Traffic if the Client does not pay, and that the price agreed in each IO reflects that allocation of risk. Where 499 receives partial Client Payment, it will apply that payment to the affected providers pro rata by the value of conforming Traffic each supplied to that campaign in the relevant period. 7.3 Collection. 499 will invoice its Clients in the ordinary course and use commercially reasonable efforts to collect. If 499 has not received Client Payment within one hundred and eighty days after the relevant Client invoice date, then on Provider's written request 499 will either continue collection at its own cost or assign to Provider, by written notice of assignment that takes effect as an equitable assignment on service, the right to recover the portion of the Client debt attributable to Provider's Traffic, together with the reasonable supporting records. Where such an assignment is made: Provider pursues the debt at its own cost; 499 will give notice of the assignment to the Client and will join proceedings as a party where joinder is legally required, at Provider's cost; Provider retains recoveries up to the amount that would have been payable to it under Section 7.2 had the Client paid, and accounts to 499 for any excess within ten Business Days of receipt; and Provider will not compromise the debt in a way that releases claims 499 retains without 499's written consent. Provider's sole remedy for non-payment by a Client is under this Section. 7.4 Payment timing, interest and cut-off. A Client Payment is received when the funds have cleared into 499's account, and is treated as non-reversible on the earlier of the date any applicable reversal or chargeback right of the Client's payment method lapses and the date thirty days after clearance with no reversal, chargeback or documented dispute of the payment having been initiated. 499 will allocate Client Payments to campaigns and providers by reference to Platform records; a lump-sum or batch Client Payment covering more than one provider or campaign is allocated across the supply it covers pro rata by value of conforming supply. Once the condition precedent in Section 7.2 is satisfied and the Client Payment is treated as non-reversible, 499 will pay the amount due on the next scheduled payment run stated in the IO and in any event within ten Business Days, less any amounts reversed, held under Section 8.3 or set off under Section 8.4. The agreed contractual rate of interest on amounts payable by 499 is zero, and to the fullest extent permitted by law Provider may not claim statutory interest, fixed compensation or recovery charges under the Late Payment of Commercial Debts (Interest) Act 1998 or equivalent legislation. If and to the extent that exclusion is ineffective, the substitute contractual remedy for late payment, which the Parties agree is a substantial remedy, is simple interest at two percentage points above the Bank of England base rate from the date payment fell due under this Section, in full substitution for the statutory remedies. Provider may not first raise a query in respect of Traffic more than ninety days after its delivery; a later query is waived. 7.5 Taxes, costs and payment security. Fees exclude VAT and similar transaction taxes, payable where properly chargeable; each Party bears its own income taxes, and Provider bears its own bank and currency-conversion charges. If withholding is legally required, 499 may withhold and will provide an official receipt; no gross-up applies. 499 will pay only to the bank account identified in the IO or Provider's signed remittance form, will not act on a change of bank details communicated by email alone, and a change takes effect only after verification by telephone with a previously known authorised contact. 8. RECOUPMENT, HOLDBACK AND SET-OFF 8.1 Compliance Events. A Compliance Event occurs if Provider or any of its Sources: (a) breaches Section 3, 4.1, 4.2, 4.3 or 4.4; (b) delivers Invalid Traffic; (c) fails to produce records within the period in Section 4.3; (d) causes a Client to suspend, cancel, withhold payment on, claw back payment on, or terminate a campaign; (e) causes an advertising platform, carrier, regulator or network to block, flag or take action against 499 or a Client; or (f) commits fraud or wilful misconduct. 8.2 Recoupment. On a Compliance Event, Provider will reimburse 499 for the following amounts, which the Parties agree represent 499's genuine loss and protect 499's legitimate interest in maintaining a shared campaign pool from which other providers must be paid: (a) all amounts already paid to Provider for the affected Traffic; (b) amounts 499 has paid or must pay to other providers on the affected campaign for the affected period, to the extent 499 cannot recover them from the Client because of the Compliance Event; (c) any amount the Client withholds, refuses, claws back or recovers from 499 that is attributable to the Compliance Event; (d) chargebacks, fines, penalties and assessments levied by a Client, advertising platform or regulator; and (e) 499's reasonable investigation, remediation, audit, replacement-supply and external legal costs. Amounts under this Section are not recoverable more than once across its limbs or in duplication of a reversal under Section 6.3, and in aggregate are limited to 499's actual loss and the protection of the legitimate interest this Section records. In respect of affected Traffic for which the condition precedent in Section 7.2 has not been satisfied, no payment obligation accrues; in respect of affected Traffic for which payment has already been made, the amounts described in this Section are repayable by Provider as a debt. 8.3 Holdback. 499 may withhold up to twenty-five per cent of amounts otherwise payable for up to ninety days after payment would otherwise fall due, as security against reversals, Client chargebacks and Compliance Events, releasing the balance at the end of that period. 499 may increase or extend a holdback while an unresolved Compliance Event, regulatory matter, platform enforcement matter or Client dispute affecting Provider's Traffic is outstanding, and will notify Provider of the reason. 8.4 Set-off and recovery costs. 499 may set off any amount owed by Provider under these Terms against any amount owed to Provider under these Terms or any other agreement between the Parties or their affiliates, whether or not then due. Provider has no right of set-off, deduction or retention. Provider will pay 499's reasonable costs of recovering amounts due under this Section, including collection-agency fees, court costs and external legal fees on an indemnity basis, with interest at one per cent per month or the maximum lawful rate if lower, from 499's written demand. 9. WARRANTIES, INDEMNITY AND LIABILITY 9.1 Provider warranties. Provider represents and warrants on a continuing basis, repeated on each delivery, that: (a) the Traffic conforms to the IO and reflects genuine consumer activity; (b) every Creative, placement, channel and list used complies with Applicable Law, the IO and Section 3; (c) it holds all rights, licences and platform authorisations needed to run the media it runs; (d) the records required by Section 4.3 exist, are accurate and are producible; (e) it uses no practice prohibited by Section 3.2; and (f) every Source, sub-affiliate and intermediary in the chain is disclosed and bound by written terms materially supporting these obligations. 9.2 Indemnity. Provider will defend, indemnify and hold harmless 499, its affiliates, its Clients and their officers, directors and employees from all third-party claims, demands, regulatory proceedings, damages, statutory damages, settlements, fines and penalties to the extent legally indemnifiable, and reasonable external legal, investigation and expert fees, arising out of or relating to: (a) the Creatives, placements, channels, lists and practices used to generate Traffic; (b) breach of Section 3, 4 or 9.1; (c) any act or omission of a Source, sub-affiliate or intermediary; (d) infringement of third-party intellectual property or publicity rights by materials Provider or a Source used; or (e) Provider's fraud, gross negligence or wilful misconduct. This applies to pre-litigation demand letters as well as filed proceedings, and is reduced only to the extent a claim is caused by 499's own conduct after the consumer's arrival at 499's destination. 499 will defend and indemnify Provider against third-party claims to the extent caused by 499's own fraud, wilful misconduct or infringement of third-party intellectual property rights in materials 499 supplied. 9.3 Liability. Neither Party is liable for indirect, incidental, special, exemplary, punitive or consequential damages or for lost profit, revenue or goodwill, except for amounts due to third parties under Section 9.2, amounts recoverable under Section 8, or fraud or wilful misconduct. 499's aggregate liability under these Terms and all IOs will not exceed the fees actually paid by 499 to Provider in the three months before the first event giving rise to the claim. Provider's obligations under Sections 4, 8 and 9.2, and its liability for breach of Section 3.2 or 3.5 or for fraud, are uncapped. 499 makes no warranty as to volume, continuation, acceptance rate, payout level or revenue, and forecasts are not commitments. Nothing limits liability for death or personal injury caused by negligence, fraud, or any liability that cannot lawfully be limited. 10. GENERAL 10.1 Term and termination. These Terms apply from Provider's acceptance until terminated by either Party on thirty days' written notice; termination ends active IOs. 499 may terminate or pause any IO immediately on written notice; Provider may terminate an IO on five Business Days' written notice. 499 may suspend immediately under Section 2.3 and may terminate immediately for a material breach incapable of cure, fraud, evasion of a suspension, illegality or Provider's insolvency. Termination does not affect accrued rights or Section 8, and amounts otherwise payable remain subject to Sections 7.2 and 8. Sections 4.3, 4.4, 5, 6, 7, 8, 9 and 10 survive. On termination or suspension Provider will immediately stop using 499's tracking links, number pools, Creatives and marks. 10.2 Confidentiality and non-circumvention. Provider will protect 499's non-public commercial information, including Client identities, destinations, payouts, pricing and campaign specifications, with reasonable care and use it only to perform these Terms, for three years from disclosure (and for Personal Data and trade secrets, as long as law provides). During the term and for twelve months after the last delivery, Provider will not knowingly contract directly or through an intermediary with a Client whose identity it learned through these Terms, for substantially the same traffic flow, to bypass 499, except where a documented pre-existing relationship exists. Provider will not identify 499 or any Client publicly without written consent. 10.3 Governing law and jurisdiction. The laws of England and Wales govern these Terms and each IO. The courts of England and Wales have jurisdiction; that jurisdiction is exclusive as to claims brought by Provider, and 499 may in addition bring proceedings to recover sums due or enforce a judgment in any court where Provider is incorporated, resident or holds assets, Provider waiving any venue objection. 10.4 Miscellaneous. These Terms may be updated by 499 prospectively on fourteen days' written notice; continued delivery after the notice period is acceptance of the update, and the version in force at delivery governs. An update that materially and adversely affects Provider does not apply to Provider if, before the update takes effect, Provider gives notice terminating these Terms and stops delivering; the prior version continues to govern until that termination completes, and accrued rights are unaffected by any update. Provider may not assign, subcontract or charge these Terms or any right to payment without consent; 499 may assign to an affiliate or successor. The Parties are independent contractors. Notices are by email and effective when sent absent an automated failure. If a provision is unenforceable it is modified to the minimum extent necessary, and a rate or period exceeding a legal maximum is reduced to that maximum. No provision is construed against its drafter. The Contracts (Rights of Third Parties) Act 1999 gives non-parties no rights, except a Client indemnified under Section 9.2 may enforce that Section. These Terms may be accepted electronically. Version. These Terms are version 1.0, effective 21 August 2026. The version in force at the time of each acceptance and each delivery governs, as recorded under the Acceptance paragraph above.