Terms of Service

  1. CORPORATE INFORMATION AND REGULATORY DISCLOSURES

    1. The Platform and Services are operated by AI KAT Limited (trading commercially as “Twinnin”), a private limited company incorporated and registered in England and Wales under company number 15040031.
    2. In accordance with the Electronic Commerce (EC Directive) Regulations 2002 and the Companies Act 2006, the corporate and regulatory details for Twinnin are:
      1. Corporate entity: AI KAT Limited;
      2. Email address: mary.maller@twinnin.ai;
      3. Commercial register: Companies House (England and Wales);
      4. Website: twinnin.ai; and
      5. Primary contact for notices: legal@twinnin.ai.
    3. Twinnin is a technology and administrative service provider. As set out in Clause 8, Twinnin is not a law firm, is not authorised or regulated under the Legal Services Act 2007, does not provide legal advice, and does not conduct reserved legal activities.
  2. DEFINITIONS AND INTERPRETATION

    1. In this Agreement (which comprises these Terms of Use and any documents expressly incorporated herein), unless the context otherwise requires, the following capitalised terms shall have the respective meanings assigned to them below:
      1. “Agreement” means these Terms of Use, including all schedules, policies, and operational rules referenced herein, as amended, varied, or supplemented from time to time in accordance with clause 29.
      2. “Affected Party” has the meaning given to it in clause 30.4.
      3. “Applicable Law” means all applicable statutes, statutory instruments, regulations, ordinances, rules, subordinate legislation, common law, and binding regulatory codes in force from time to time within a Covered Jurisdiction.
      4. “AWS KMS” means the Amazon Web Services Key Management Service hardware security module infrastructure used by Twinnin to generate, hold, and apply asymmetric cryptographic signing keys, including the operational key used to execute Smart Contract transactions and sign Verifiable Credentials.
      5. “Badge Tool” means the interactive platform utility and software functionality provided by Twinnin that enables a Twinn to composite a machine-readable quick response (QR) code and hyperlink encoding their Public Verification Page onto an image supplied by the Twinn, as governed by clause 22.
      6. “BIPA” means the Illinois Biometric Information Privacy Act (740 ILCS 14/1 et seq.), as amended from time to time.
      7. “Blockchain” means the Polygon Proof-of-Stake (PoS) public distributed ledger network (or any successor or alternative distributed ledger designated by Twinnin), on which cryptographic proofs, version numbers, and hashes of Credentials are anchored.
      8. “Bound Handle” means an external digital identifier, social media handle, username, or electronic mail address (limited to Instagram, Facebook, LinkedIn, X, TikTok, or electronic mail) that has successfully undergone the verification procedure set out in clause 11, has been approved by Twinnin, and is incorporated into the Defend Credential and rendered on the Public Verification Page.
      9. “Business Day” means a day other than a Saturday, Sunday, or public holiday in England.
      10. “Business Hours” means 9:00 am to 5:00 pm on a Business Day in London, United Kingdom.
      11. “Case Page” means the dedicated, authenticated interface and administrative dashboard accessible by a Twinn within the Platform, displaying the real-time status, timeline, statutory deadlines, evidentiary submission logs, and bilateral communications thread for a specific Takedown Request.
      12. “CCPA/CPRA” means the California Consumer Privacy Act of 2018, as amended by the California Privacy Rights Act of 2020 (California Civil Code § 1798.100 et seq.), and any implementing regulations promulgated thereunder.
      13. “CCRs 2013” means the Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013 (SI 2013/3134), as amended from time to time.
      14. “Cooling-Off Period” means the statutory fourteen (14) day period following contract formation during which a consumer resident in the United Kingdom or the European Economic Area may cancel this Agreement under the CCRs 2013 and applicable consumer protection legislation, subject to the early performance waiver in clause 6.
      15. “Covered Jurisdiction” means the geographic territories within which the Services are made available, comprising: (a) the United Kingdom; (b) the thirty (30) member states of the European Economic Area (comprising the twenty-seven (27) European Union member states together with Iceland, Liechtenstein, and Norway); and (c) any of the fifty (50) states of the United States of America and the District of Columbia.
      16. “CRA 2015” means the Consumer Rights Act 2015, as amended from time to time.
      17. “Data Protection Legislation” means: (a) the UK GDPR; (b) the Data Protection Act 2018; (c) the EU GDPR (to the extent applicable); (d) the Privacy and Electronic Communications (EC Directive) Regulations 2003 (SI 2003/2426); and (e) any other applicable laws, statutes, directives, or regulations relating to the protection of personal data and privacy within a Covered Jurisdiction.
      18. “Declaration” means the formal, versioned objection, opt-out, and assertion of rights executed by the Twinn during onboarding (and re-executed upon subsequent credential updates) under applicable Data Protection Legislation, statutory privacy frameworks, and rights of publicity, as more particularly detailed in clause 4 and clause 12.
      19. “Defend-Admin” means an authorised employee, contractor, or representative of Twinnin assigned to perform identity verifications, handle approval reviews, administrative triaging, and notice dispatch for the Defend Twinn service tier.
      20. “Defend Credential” means the digitally signed, tamper-evident W3C Verifiable Credential issued by Twinnin to the Twinn in compact JSON Web Token (JWT) format, certifying the Twinn’s active objection status, issuance timestamp, declared jurisdiction, and verified Bound Handles, as set out in clause 12.
      21. “Defend Twinn” means the proprietary defensive subscription service tier provided by Twinnin under this Agreement, comprising identity verification, cryptographic declaration anchoring, hosting of the Public Verification Page, provision of the Badge Tool, and the Takedown Service, as described in clause 7.
      22. “Digital Content” has the meaning ascribed to it in section 2(9) of the CRA 2015, encompassing data produced and supplied in digital form by Twinnin under this Agreement.
      23. “Escalation Evidence Pack” means the consolidated digital package and structured dossier compiled by Twinnin following an unsuccessful, refused, or unanswered Takedown Request, comprising transmission logs, timestamped notices, submitted URLs, the confirmed face crop, similarity and explicit content scores, and regulatory complaint templates, as set out in clause 20.
      24. “Feedback” has the meaning given to it in clause 25.5.
      25. “Force Majeure Event” has the meaning given to it in clause 30.1 and clause 30.2.
      26. “EU GDPR” means Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, as amended from time to time.
      27. “Human Verified” means the authenticated status badge displayed on the Public Verification Page, confirming that the Twinn has completed identity verification and biometric liveness screening, and that their profile photograph has been approved by human review.
      28. “Licence Twin” means Twinnin’s commercial likeness licensing platform tier, governed by distinct contractual terms and conditions, under which individuals authorize and license the generation and deployment of their digital replica.
      29. “Likeness” means the biological or synthetic visual representation, facial geometry, physical features, voice recordings, synthetic voice outputs, biometric characteristics, persona, and identifiable personal attributes of a natural person.
      30. “Likeness Score” means the algorithmic similarity metric generated by the client-side facial comparison model, reflecting the mathematical correlation between a facial crop detected within a user-submitted screenshot and the Twinn’s approved reference photograph.
      31. “Non-Consensual Intimate Imagery” or “NCII” means any visual, audio, or synthetic depiction (including sexually explicit deepfakes, nude images, or computer-generated alterations) depicting a natural person engaged in sexually explicit conduct, in a state of nudity, or in an intimate context, produced, published, or disseminated without that person’s express consent.
      32. “NSFW Score” means the automated explicit content classification score generated by the client-side machine learning model executed within the Twinn’s local browser environment, measuring the statistical probability that an uploaded screenshot depicts sexually explicit or intimate content.
      33. “On-Chain Anchor” means the cryptographic transaction record committed to the ConsentRegistry Smart Contract on the Blockchain, consisting of the Twinn’s pseudonymous internal identifier, the cryptographic digest of the Defend Credential, and the sequential version number, as detailed in clause 13.
      34. “Online Safety Act 2023” means the United Kingdom Online Safety Act 2023, and any statutory instruments, codes of practice, or regulations enacted pursuant thereto.
      35. “Platform” means the proprietary software infrastructure, web applications, customer dashboards, APIs, smart contracts, and hosting environments operated by Twinnin at twinnin.ai (and its associated subdomains).
      36. “Privacy Policy” means Twinnin’s privacy policy and notice published on the Platform at twinnin.ai/privacy, as updated from time to time.
      37. “Public Verification Page” means the publicly accessible, read-only webpage hosted on the Platform at twinnin.ai/v/{verification_page_id}, rendering the Twinn’s approved name, verified photograph, Human Verified status, Bound Handles, declaration date, and cryptographic verification parameters, as governed by clause 10.
      38. “Services” means the suite of digital services, content, and tools supplied by Twinnin under the Defend Twinn subscription, as defined in clause 7.
      39. “Smart Contract” means the smart contract suite deployed by Twinnin on the Blockchain to register, update, and manage On-Chain Anchors.
      40. “Stripe” means Stripe Payments UK, Ltd. (or its relevant corporate affiliates), the third-party payment gateway processor through whose payment infrastructure Subscription Fee transactions are processed.
      41. “Subscription Fee” means the recurring subscription fee payable by the Twinn to maintain an active Defend Twinn subscription, as specified during checkout and set out in clause 5.
      42. “Sumsub” means Sum and Substance Ltd (registered in England and Wales under company number 11333792), the external identity verification and biometric authentication service provider engaged by Twinnin.
      43. “TAKE IT DOWN Act” means the United States federal Tools to Address Known Exploitation by Immobilizing Technological Deepfakes on Websites and Networks Act (or any equivalent federal enactment codifying notice-and-takedown obligations for non-consensual intimate imagery).
      44. “Takedown Request” means an administrative complaint and formal notice generated and dispatched by Twinnin acting as the Twinn’s designated agent to an online platform, website host, or AI model provider, requesting the removal, erasure, or de-indexing of content misusing the Twinn’s Likeness, as detailed in clause 15 and clause 19.
      45. “Takedown Service” means the administrative workflow operated by Twinnin, consisting of case intake, on-device analysis, Defend-Admin triage, notice drafting, legal routing, response monitoring, and escalation support, as governed by clauses 15 to 20 (inclusive).
      46. “Twinn” means the verified natural person aged eighteen (18) years or older who has entered into this Agreement, successfully completed identity verification, executed the Declaration, and maintains an active Defend Twinn subscription.
      47. “Twinn Content” has the meaning given to it in clause 25.4.
      48. “Twinnin” means AI KAT Limited, a private limited company incorporated and registered in England and Wales, trading commercially as “Twinnin”.
      49. “twin_uuid” means the unique, randomly generated pseudonymous identifier (UUIDv4) allocated to a Twinn by the Platform, which serves as the core internal identifier in the Defend Credential and is encoded on the Blockchain.
      50. “UK GDPR” has the meaning given to it in section 3(10) (as supplemented by section 205(4)) of the Data Protection Act 2018.
      51. “Verification Page ID” means the unique token embedded in the Uniform Resource Locator (URL) of a Twinn’s Public Verification Page, mapped server-side to the Twinn’s twin_uuid, which controls public routing and access to the page.
      52. “Verifiable Credential” or “VC” means a tamper-evident digital credential conforming to the World Wide Web Consortium (W3C) Verifiable Credentials specification, cryptographically signed by Twinnin as set out in Clause 12.2.
    2. Interpretation. In this Agreement, unless the context otherwise requires:
      1. words importing the singular include the plural and vice versa, and words importing any gender include all genders;
      2. a reference to a person includes a natural person, corporate body, or unincorporated association (whether or not having separate legal personality);
      3. a reference to a party includes its personal representatives, successors, and permitted assigns;
      4. a reference to a statute or statutory provision is a reference to it as amended, extended, consolidated, re-enacted, or replaced from time to time, and includes all subordinate legislation made under that statute or statutory provision;
      5. any words following the terms “including”, “include”, “in particular”, “for example”, or any similar expression shall be construed as illustrative and shall not limit the sense of the words, description, definition, phrase, or term preceding those terms;
      6. a reference to “writing” or “written” includes electronic mail, but excludes text messaging (SMS) and unauthenticated direct messaging on third-party platforms;
      7. headings and clause titles are inserted for ease of reference only and shall not affect the construction, validity, or interpretation of this Agreement;
      8. any reference to an English legal term, concept, or statute shall, in respect of any jurisdiction other than England and Wales, be construed as a reference to the legal concept or term most nearly analogous to it under the applicable laws of that jurisdiction; and
      9. in the event of any conflict, ambiguity, or inconsistency between the main body of these Terms of Use and any schedule, policy, or referenced document, the main body of these Terms of Use shall prevail to the extent of such conflict or inconsistency; and
      10. nothing in this Agreement excludes, restricts, or limits any right, protection, or remedy of the Twinn (including under the CRA 2015, the CCRs 2013, the Data Protection Legislation, or the Unfair Contract Terms Act 1977) that cannot lawfully be excluded, restricted, or limited, and every exclusion or limitation of Twinnin’s liability or obligations in this Agreement takes effect only to the maximum extent permitted by applicable law and subject to this Clause 1.2.10.
  3. ELIGIBILITY, AGE VERIFICATION, AND TERRITORIAL RESTRICTIONS

    1. To be eligible to apply for an account, access the Platform, or subscribe to Defend Twinn, an applicant must be a natural person acting as an individual consumer who satisfies each of the following cumulative criteria at the time of registration and continuously throughout the term of this Agreement:
      1. they must be at least eighteen (18) years of age;
      2. they must be resident within a Covered Jurisdiction, comprising the United Kingdom, any of the thirty (30) member states of the European Economic Area (the twenty-seven (27) European Union member states plus Iceland, Liechtenstein, and Norway), or any of the fifty (50) states of the United States of America or the District of Columbia; and
      3. they must hold a valid, unexpired, government-issued photographic identity document supported by Sumsub and capable of successfully completing the identity verification procedures set out in Clause 4.
    2. Defend Twinn is strictly personal to the individual registering the account. Accounts are limited to one natural person per account. No joint, corporate, minor, parental, guardian, or representative accounts or registrations are permitted under Defend Twinn.
    3. During the initial account registration workflow, the applicant must warrant that they are aged eighteen (18) years or older by completing a self-certification tick-box. Access to and activation of Defend Twinn shall be strictly conditional upon subsequent independent verification of the applicant’s age and date of birth via Sumsub’s government-issued identity documentation screening and biometric liveness checks in accordance with Clause 4.
    4. An applicant must declare their Covered Jurisdiction of residence during registration and notify Twinnin promptly of any relocation. If an applicant or Twinn fails or ceases to satisfy any eligibility criterion in Clause 3.1, relocates outside a Covered Jurisdiction, or provides false, misleading, or unverifiable information, Twinnin shall immediately refuse, suspend, restrict, or terminate their account and access to the Services.
  4. ONBOARDING JOURNEY, IDENTITY VERIFICATION, AND ACCOUNT FORMATION

    1. The onboarding workflow and application process for Defend Twinn comprises the following sequential steps, all of which the applicant must complete to Twinnin’s satisfaction before an account can be approved:
      1. Account Registration: The applicant must supply their legal first and last name and valid electronic mail address, create secure authentication credentials (or authenticate via an approved single sign-on provider), complete electronic mail verification, warrant capacity and age in accordance with Clause 3.3, accept these Terms of Use and the Privacy Policy, and declare their Covered Jurisdiction of residence.
      2. Profile Image Submission: The applicant must upload a profile photograph conforming to the visual standards set out in Clause 9, consisting either of the applicant’s sole unencumbered human face or an acceptable non-human avatar. Uploaded imagery shall be subject to automated content screening; any image flagged for explicit, unlawful, or infringing content shall be deleted immediately, and the applicant shall be subject to a mandatory twenty-four (24) hour submission restriction.
      3. Declaration and Acknowledgements: The applicant must review the full text of the Declaration and provide distinct, explicit consents and affirmative digital acknowledgements evidencing their agreement to: (a) the non-licensable assertion over their Likeness; (b) the operational boundaries and disclaimers governing what Twinnin does not provide; (c) what Twinnin provides under the Services; (d) the applicable Subscription Fee pricing; and (e) the processing of biometric data and identity documentation via Sumsub in accordance with Clause 4.1.4, together with the irreversible recording of the cryptographic digest of the Declaration on the Blockchain as an On-Chain Anchor.
      4. Identity and Liveness Verification: The applicant must complete automated identity verification via Twinnin’s verification partner, Sumsub, consisting of a biometric liveness facial scan and the submission of a valid government-issued photographic identity document. Sumsub processes identity verification documentation as an independent data controller subject to its own terms and privacy policy. Twinnin shall receive and process solely the verification outcome, verified date of birth, and facial reference imagery. To the maximum extent permitted by applicable law, Twinnin excludes liability for third-party verification downtime, latency, technical failures, or provider-side authentication errors.
      5. Defend-Admin Review: Following successful Sumsub screening, a Defend-Admin shall conduct human verification to confirm that the uploaded profile photograph corresponds to the individual authenticated via the biometric liveness scan or otherwise satisfies acceptable avatar criteria. In compliance with Article 22 of Data Protection Legislation, no account approval or rejection is determined solely by automated processing. If an application is not approved, Twinnin shall notify the applicant of the objective grounds for rejection and afford the applicant an opportunity to resubmit compliant imagery.
    2. The onboarding, identity check, and administrative review stages constitute an invitation to treat and a preliminary application only. Twinnin shall not collect payment details, process Subscription Fees, or form a binding contract prior to formal Defend-Admin approval. A legally binding contract for Defend Twinn is formed exclusively when, following express notification of Defend-Admin approval:
      1. the applicant is redirected to a secure Stripe-hosted checkout interface and actively confirms their recurring subscription mandate; and
      2. Stripe confirms the successful initial settlement of the Subscription Fee.
    3. Upon successful settlement under Clause 4.2, the Twinn’s account shall be activated, the initial Defend Credential shall be generated, the On-Chain Anchor shall be committed to the Blockchain, and the Public Verification Page shall go live.
    4. In accordance with data minimisation and storage limitation principles under Data Protection Legislation, any onboarding application that remains incomplete or unapproved due to applicant inaction shall be deleted automatically after twenty-four (24) consecutive hours of inactivity (excluding periods pending Defend-Admin review under Clause 4.1.5). Twinnin shall incur no liability, and no contractual or data retention rights shall accrue, in respect of purged registration attempts.
    5. An applicant may switch their pending onboarding application from Defend Twinn to Licence Twin free of charge at any time prior to the application entering formal Defend-Admin human verification review under Clause 4.1.5. Upon such a switch, completed Sumsub identity verifications shall carry over to the new tier, but the applicant must complete the distinct profile, media, and contractual requirements of Licence Twinn.
  5. SUBSCRIPTION FEES, BILLING CYCLES, AND STRIPE PAYMENT PROCESSING

    1. The Subscription Fee for Defend Twinn is US$4.99 per calendar month across all Covered Jurisdictions. Twinnin does not offer free trials or introductory periods. All Subscription Fees are quoted inclusive of any value added tax or local sales taxes Twinnin is legally required to collect. Any foreign exchange or cross-border charges imposed by the Twinn’s card issuer or bank shall be borne by the Twinn.
    2. Payment processing shall be executed entirely via Stripe through a secure, Stripe-hosted checkout interface. Twinnin does not receive, process, store, or hold payment card numbers or complete sensitive payment credentials on its servers. No Subscription Fee or payment card details shall be requested, collected, or processed prior to formal Defend-Admin approval under Clause 4.1.5.
    3. Upon successful onboarding approval and completion of the checkout workflow under Clause 4.2, the Subscription Fee shall be billed on a recurring monthly basis commencing on the date of initial payment confirmation. Each subsequent payment shall be automatically charged to the Twinn’s designated payment method on the same calendar day of each successive month (or the final day of the relevant month if that calendar day does not occur), unless and until the subscription is cancelled or terminated in accordance with this Agreement.
    4. The Twinn expressly authorises Stripe and Twinnin to store the payment method token and continuously charge the recurring Subscription Fee for each successive billing period (a Continuous Payment Authority) until revoked. The Twinn must maintain valid, unexpired, and sufficient payment details. If a recurring billing charge fails or is declined, Twinnin shall notify the Twinn and may re-attempt the charge via Stripe; if payment remains unresolved following such notice, Twinnin reserves the right to suspend access to the Services, deactivate the Public Verification Page, and pause the processing of Takedown Requests.
    5. The Twinn may cancel their Defend Twinn subscription at any time prior to the commencement of the next billing cycle via the account management dashboard. Following cancellation, access to the Services, maintenance of the Defend Credential, and hosting of the Public Verification Page shall continue until the conclusion of the then-current, paid billing period, at which point the subscription shall terminate without further charge. Except as provided under statutory consumer cancellation rights in Clause 6 or mandatory provisions of the CRA 2015, paid Subscription Fees are non-refundable.
    6. Twinnin may amend the Subscription Fee from time to time. Any change shall be notified to the Twinn by electronic mail at least thirty (30) calendar days before it takes effect, giving the Twinn a clear opportunity to terminate without penalty. Continued use of the Services after the effective date constitutes acceptance of the amended Subscription Fee.
  6. STATUTORY CANCELLATION RIGHTS AND EARLY SUPPLY WAIVERS (CCRS 2013)

    1. If the Twinn enters into this Agreement as a consumer habitually resident within the United Kingdom or the European Economic Area, they have a statutory right under the CCRs 2013 (and corresponding consumer protection laws within the European Economic Area) to cancel this distance contract without giving any reason within the Cooling-Off Period, subject to the early performance requests and waivers set out in this Clause 6.
    2. The statutory Cooling-Off Period expires fourteen (14) calendar days from the day on which the contract is formally concluded in accordance with Clause 4.2.
    3. Defend Twinn comprises the supply of Digital Content (including the generation and issuance of the Defend Credential and the publication of the Public Verification Page) and the performance of Services (including On-Chain Anchor execution on the Blockchain and administrative triage configuration). Pursuant to Regulations 36 and 37 of the CCRs 2013, by proceeding through the Stripe-hosted checkout workflow under Clause 4.2, the Twinn:
      1. makes an express request under Regulation 36(1) for Twinnin to begin the performance of all Services immediately upon contract conclusion, before the expiry of the statutory Cooling-Off Period;
      2. gives express consent under Regulation 37(1)(a) to the supply of Digital Content commencing immediately upon contract conclusion, before the expiry of the statutory Cooling-Off Period; and
      3. expressly acknowledges under Regulation 37(1)(b) that their statutory right to cancel this Agreement in respect of such Digital Content will be lost immediately upon the commencement of its supply.
    4. To the extent that any element of Defend Twinn constitutes Services rather than Digital Content under the CCRs 2013 or the CRA 2015, and the Twinn exercises a valid statutory right to cancel before those Services are fully performed, the Twinn shall, pursuant to Regulation 36(4) of the CCRs 2013, pay Twinnin an amount proportionate to the Services supplied up to the time Twinnin is informed of the cancellation decision, in comparison with the full coverage of the contractual period, and any refund shall be adjusted accordingly. Under Regulation 36(6), the right to cancel Services ceases entirely once the Services are fully performed.
    5. To exercise any statutory right to cancel that has not been extinguished under Clause 6.3, the Twinn must communicate their decision to cancel by an unequivocal statement dispatched to Twinnin by email to legal@twinnin.ai prior to the expiry of the Cooling-Off Period. The Twinn may use the model cancellation text set out below, but its use is not obligatory:
      1. “To AI KAT Limited, trading as Twinnin (email: legal@twinnin.ai): I hereby give notice that I cancel my contract for the supply of the Defend Twinn subscription service, ordered on [insert date]. Name of consumer: [insert name]; Address of consumer: [insert address]; Date: [insert date].”
    6. If the Twinn cancels this Agreement where the statutory right of cancellation has been preserved and not lost under Clause 6.3, Twinnin shall reimburse all qualifying payments received from the Twinn (subject to any lawful statutory deduction under Clause 6.4) within fourteen (14) calendar days following the date on which Twinnin was informed of the cancellation decision. Reimbursement shall be made using the same means of payment as the Twinn used for the initial transaction via Stripe, and Twinnin shall not impose any fee in respect of such reimbursement.
    7. For the avoidance of doubt, the statutory cancellation rights set out in this Clause 6 apply strictly to the initial fourteen (14) day Cooling-Off Period following contract conclusion and do not restrict the Twinn’s separate contractual right to cancel recurring monthly billing cycles at any time pursuant to Clause 5.5.
  7. SCOPE OF SERVICES, SERVICE STANDARDS, AND DIGITAL CONTENT (CRA 2015)

    1. In consideration of the timely payment of the Subscription Fee, Twinnin shall supply the Defend Twinn subscription package to the Twinn, comprising the following core deliverables and features:
      1. the generation, cryptographic signing, and ongoing issuance of the Defend Credential certifying the Twinn’s non-licensable status and active objection under the Declaration;
      2. the submission, publication, and maintenance of the On-Chain Anchor on the Blockchain, anchoring the tamper-evident cryptographic hash of the Defend Credential;
      3. the hosting, deployment, and public serving of the Twinn’s unique, read-only Public Verification Page displaying their Human Verified badge, approved profile image, declaration details, and any verified Bound Handles;
      4. access to the authenticated Platform dashboard, encompassing credential inspection tools, Bound Handle administration, the Case Page interface, and the interactive Badge Tool; and
      5. access to the administrative Takedown Service, under which Twinnin receives user reports, performs Defend-Admin triage, generates and transmits standardised notices to external online platforms, monitors benchmark response windows, and compiles an Escalation Evidence Pack where a platform refuses or ignores a request, strictly subject to the operational boundaries and disclaimers set out in Clause 8 and Clauses 15 to 20 (provided that Twinnin does not warrant or guarantee that any third-party platform will act upon, remove, or restrict content pursuant to such notice).
    2. To the extent that any deliverable supplied under Defend Twinn constitutes Digital Content under the CRA 2015 (including the downloadable Defend Credential, in-browser machine learning runtimes, and machine-readable data rendered on the Public Verification Page), such Digital Content shall:
      1. be of satisfactory quality in accordance with section 34 of the CRA 2015;
      2. be fit for the particular purpose expressly made known by Twinnin in these Terms of Use in accordance with section 35 of the CRA 2015;
      3. match any description supplied by Twinnin in accordance with section 36 of the CRA 2015, subject to Twinnin’s right to modify Digital Content in accordance with section 40 of the CRA 2015 and Clause 29; and
      4. be supplied with the legal right to do so in accordance with section 41 of the CRA 2015.
    3. To the extent that any element of Defend Twinn constitutes a service under Chapter 4 of Part 1 of the CRA 2015 (including Defend-Admin verification, notice dispatch, and case management workflows), Twinnin shall perform such Services with reasonable care and skill in accordance with section 49 of the CRA 2015.
    4. Nothing in this Agreement shall exclude, restrict, or modify any statutory rights or consumer remedies available to the Twinn under the CRA 2015 that cannot be lawfully excluded or limited under English law, including statutory rights to repair, replacement, price reduction, or re-performance where Digital Content or Services fail to conform to the standards set out in Clause 7.2 or Clause 7.3.
  8. EXPRESS SERVICE EXCLUSIONS, LIMITATIONS, AND LEGAL ADVICE DISCLAIMERS (LSA 2007)

    1. The Twinn acknowledges that the Services and Digital Content supplied under Defend Twinn are technical, administrative, and provenance tools, and that Twinnin does not provide legal representation, legal advice, legal opinions, litigation management, or dispute resolution services. Without prejudice to the performance standard in Clause 7.3, the Services are subject to the operational boundaries, exclusions, and statutory disclaimers in this Clause 8.
    2. In accordance with the Legal Services Act 2007, Twinnin is not an authorised legal services provider, is not regulated by the Solicitors Regulation Authority or any approved legal regulator within England and Wales or any other Covered Jurisdiction, and employs no personnel acting as the Twinn’s legal counsel or advocate. No communication, notification template, Escalation Evidence Pack, or guidance provided by Twinnin constitutes legal advice or creates a solicitor-client relationship. The Twinn must consult qualified independent legal counsel for legal analysis, formal representation, or court proceedings.
    3. Twinnin acts solely as an administrative communication and transmission agent in dispatching notices under the Takedown Service, as governed by Clause 14 and Clause 19. Twinnin does not perform any reserved legal activities under the Legal Services Act 2007, including the conduct of litigation or the exercise of rights of audience, nor does it lodge formal proceedings, settle claims, execute compromise agreements, or enforce judicial orders. The transmission of a Takedown Request by Twinnin does not constitute formal service of legal process.
    4. Twinnin does not warrant or guarantee that any third-party online platform, model host, website operator, or individual recipient will acknowledge, process, comply with, or execute any Takedown Request, objection, or erasure notice dispatched on behalf of the Twinn. All compliance and removal decisions remain within the independent discretion, operational governance, and legal assessment of the receiving third party, and, subject to Clause 8.8, Twinnin shall not be liable for the refusal, inaction, delayed handling, or non-compliance of any external platform.
    5. The Twinn expressly acknowledges that Defend Twinn does not operate as an automated technical blocker, content filter, firewall, or active digital rights management barrier. The Services cannot technically prevent third parties from downloading, scraping, harvesting, or processing the Twinn’s Likeness, nor can they intercept external machine learning model training or synthetic generation pipelines.
    6. The Services do not and cannot retroactively purge, erase, retrieve, or expunge synthetic media, digital models, trained neural weights, or AI-generated depictions that already exist, are hosted outside accessible public URL pathways, or were produced prior to the effective date of the Declaration.
    7. Defend Twinn is an opt-out and objection registration service and does not constitute a commercial licensing or revenue-generating arrangement. Twinnin does not market, monetise, or license the Twinn’s Likeness under this Agreement, and no royalties, licensing revenue, commercial fees, or payments shall accrue or be payable to the Twinn in connection with Defend Twinn.
    8. Nothing in this Clause 8 shall exclude, restrict, or limit any liability that cannot lawfully be excluded or restricted under the laws of England and Wales, including under the Consumer Rights Act 2015 or the Unfair Contract Terms Act 1977.
  9. PROFILE IMAGERY STANDARDS, SCREENING, AND ADMINISTRATIVE FACE REQUIREMENTS

    1. All profile imagery submitted by the Twinn for deployment on the Public Verification Page must strictly satisfy one of the following two visual standards:
      1. a clear, unencumbered photographic depiction of the Twinn’s own biological face, containing no other identifiable natural persons, watermarks, or deceptive digital manipulations; or
      2. a non-photorealistic graphic illustration, stylised symbol, or synthetic avatar that cannot reasonably be mistaken for, or misattributed as, a real biological human face.
    2. The Twinn represents and warrants that the Twinn owns or possesses all necessary rights, licences, consents, and permissions to submit and display the profile imagery, and that such imagery does not infringe any third-party intellectual property, privacy, or personality rights. The Twinn grants Twinnin a non-exclusive, royalty-free, worldwide licence to use, store, reproduce, and display such imagery solely for the purposes of operating the Platform, conducting verification workflows, and providing the Services.
    3. All submitted imagery is subjected to initial automated safety and content screening. Any image flagged by automated screening as depicting explicit, sexually suggestive, intimate, hateful, violent, or unlawful content shall be purged immediately, and the Twinn’s profile image upload permissions shall be suspended for a mandatory period of twenty-four (24) hours.
    4. Following automated screening, every profile image is subjected to human verification by a Defend-Admin. Approval of an image under Clause 9.1.1 is strictly conditional upon the Defend-Admin verifying that the facial geometry and features correspond with the reference imagery captured during the biometric liveness check executed under Clause 4.1.4 by Twinnin’s designated identity verification provider, Sumsub. Approval of an avatar under Clause 9.1.2 requires the Defend-Admin to confirm that the depiction complies fully with the non-human avatar standard. In compliance with Article 22 of Data Protection Legislation, no final decision to reject or approve a profile image is determined solely by automated processing.
    5. If a Defend-Admin rejects a submitted profile image, Twinnin shall provide written notification to the Twinn setting out the objective grounds for refusal, and the Twinn shall be afforded a reasonable opportunity to submit compliant replacement imagery via the Platform.
    6. An existing Twinn may request an update to their approved profile image at any time via the Platform. Any replacement image must undergo the automated screening and Defend-Admin verification workflows set out in Clauses 9.3 and 9.4, and the existing approved imagery shall remain displayed on the Public Verification Page until the replacement image is formally approved by a Defend-Admin.
    7. Twinnin reserves the right, upon reasonable prior notice, to update or amend the technical specifications, formatting criteria, and acceptability standards governing profile imagery from time to time, or to remove any previously approved imagery that subsequent review reveals to be non-compliant. The Twinn shall maintain compliant imagery at all times as an ongoing condition of receiving the Services.
    8. Twinnin further reserves the right, where reasonably necessary for administrative triage, case verification, or the assessment of a Takedown Request under Clause 18, to issue a written request requiring the Twinn to supply a mandatory photographic image of the Twinn’s biological face for internal administrative use by a Defend-Admin, irrespective of whether the Twinn has elected to display an avatar on the Public Verification Page. If the Twinn fails to supply a compliant photographic image within a reasonable period following such request, Twinnin reserves the right to suspend or restrict the provision of the Takedown Service or the operation of the Public Verification Page until compliant imagery is provided.
  10. PUBLIC VERIFICATION PAGE AND DYNAMIC IDENTIFIER MANAGEMENT

    1. Subject to Clause 4, Clause 10.5, and any temporary suspension or termination pursuant to this Agreement, Twinnin shall generate, publish, and host a dedicated, publicly accessible, read-only Public Verification Page for the Twinn at a designated URL incorporating the Twinn’s unique Verification Page ID. The Public Verification Page serves as public, tamper-evident verification of the Twinn’s active objection to the unauthorised synthetic use of the Twinn’s Likeness and may be distributed, shared, or linked by the Twinn at the Twinn’s sole discretion.
    2. The Public Verification Page shall publicly render and display the following information:
      1. the Twinn’s approved legal first and last name;
      2. the Twinn’s approved profile photograph or avatar verified pursuant to Clause 9;
      3. the authenticated Human Verified status badge;
      4. an explicit “Not Licensable” declaration indicator, the calendar month and year of initial identity verification, the formal text of the Declaration, and the effective date of execution; and
      5. any active Bound Handles successfully verified under Clause 11.
    3. The Public Verification Page shall include an interactive interface toggle allowing visitors to inspect the underlying cryptographic verification parameters of the Defend Credential, comprising:
      1. the unique credential identifier containing the Twinn’s pseudonymous identifier (twin_uuid);
      2. the active credential version number, issuance timestamp, and cryptographic digest (SHA-256 hash) of the Defend Credential;
      3. an operational hyperlink referencing the confirmed On-Chain Anchor transaction on the Blockchain; and
      4. independent verification instructions enabling any third party, enterprise, or regulatory authority to audit the cryptographic integrity of the Defend Credential and its on-chain registration without relying on Twinnin’s internal systems.
    4. In accordance with Data Protection Legislation and data minimisation principles, the Public Verification Page shall not display or disclose the Twinn’s specific Covered Jurisdiction of residence, residential address, underlying government identity documentation, or raw biometric verification data.
    5. The Public Verification Page is read-only and static, and cannot be altered, edited, or customised by the Twinn or any third party. Any update to the information displayed-including approved profile imagery under Clause 9 or Bound Handles under Clause 11, shall take effect only following the requisite verification workflows and the generation and anchoring of an updated Defend Credential version. Twinnin may unpublish or suspend access to the Public Verification Page immediately where there is reasonable suspicion of identity fraud, breach of this Agreement, or an unresolved legal dispute.
    6. The URL path of the Public Verification Page is governed by the Twinn’s Verification Page ID mapped server-side to the Twinn’s twin_uuid. The Twinn acknowledges and agrees that the Verification Page ID allocated upon account activation is fixed and cannot currently be regenerated, rotated, or modified by the Twinn via the customer dashboard.
    7. In accordance with the CRA 2015 and Clause 29, Twinnin reserves the right to introduce technical enhancements, security updates, and functionality modifications to the Platform from time to time, including functionality enabling a Twinn to regenerate or rotate the Twinn’s Verification Page ID. Where a replacement or rotation of a Verification Page ID is made available and executed, generating a replacement shall immediately and permanently invalidate the preceding Verification Page ID, rendering any previously shared, published, or composited hyperlinks inoperative.
    8. Twinnin shall give reasonable advance notice to the Twinn of any material alteration to the architecture, hosting, or core functionality of the Public Verification Page or Verification Page ID management. If any technical modification materially alters the service description or detrimentally affects the Twinn’s use of the Public Verification Page, the Twinn shall have the right to terminate the subscription pursuant to Clause 5.5 prior to the implementation of the change without incurring any cancellation penalty or fee.
  11. SOCIAL MEDIA HANDLE AND CONTACT VERIFICATION PROCEDURES

    1. Following activation of the Defend Twinn subscription under Clause 4.3, the Twinn may elect to link one or more external digital profiles or communication channels to the Twinn’s account via the authenticated Platform dashboard. Permissible handles and identifiers are strictly limited to the following six supported platforms and contact methods: Instagram, Facebook, LinkedIn, X, TikTok, and electronic mail addresses.
    2. The Twinn represents, warrants, and undertakes that the Twinn is the lawful account holder of, and possesses all requisite rights, title, authority, and control over, every handle, account identifier, and electronic mail address submitted for verification, and shall promptly notify Twinnin and initiate removal under Clause 11.6 if the Twinn ceases to hold or control any Bound Handle. The submission of any identifier belonging to a third party, or any attempt to spoof, misrepresent, or impersonate another natural person or entity, constitutes a material breach of this Agreement, entitling Twinnin immediately to reject the submission, suspend the account, or terminate this Agreement pursuant to Clause 26.
    3. To establish verified ownership of a submitted handle or electronic mail address, the Twinn must successfully complete the applicable verification procedure:
      1. For supported social media platforms (Instagram, Facebook, LinkedIn, X, TikTok), upon submission of the relevant handle via the Platform, the Twinn shall be issued a distinct, pseudorandom 6-digit alphanumeric verification code. The Twinn must transmit this 6-digit code from the external account corresponding to the submitted handle directly to Twinnin’s designated official account on that platform via direct messaging.
      2. For electronic mail addresses, where the submitted address differs from the verified electronic mail address used during initial account registration under Clause 4.1.1, Twinnin shall dispatch a communication containing a unique 6-digit verification code directly to the submitted electronic mail address (rather than displaying the code within the Platform interface). The Twinn must retrieve this code from the inbox and enter it into the authenticated Platform interface to confirm control over the submitted address. Where the submitted electronic mail address is identical to the verified registration address, no secondary verification code dispatch shall be required.
      3. Verification requests are reviewed and reconciled against Twinnin’s administrative records by a Defend-Admin.
    4. A Defend-Admin may, acting reasonably, approve or decline a pending handle request individually or in batches. Twinnin reserves the right to decline or revoke verification of any handle that fails code reconciliation, is associated with abusive or deceptive activity, violates the terms of the underlying third-party platform, or cannot be conclusively validated. If a pending verification request is not completed and approved within thirty (30) calendar days following submission, it shall automatically expire and be deleted outright from the Platform. Where Twinnin revokes an existing Bound Handle under this Clause 11.4, the update procedures set out in Clause 11.6 shall apply mutatis mutandis.
    5. Upon Defend-Admin approval of a submitted handle or electronic mail address, such identifier becomes a Bound Handle. Twinnin shall automatically:
      1. generate an updated version of the Defend Credential incorporating the newly approved Bound Handle in accordance with Clause 12;
      2. anchor the updated cryptographic digest of the Defend Credential on the Blockchain as a sequential On-Chain Anchor pursuant to Clause 13; and
      3. update the Public Verification Page to display the verified Bound Handle publicly alongside the Twinn’s profile.
    6. A Twinn may delete or cancel a pending or rejected handle request at any time via the Platform dashboard without formal confirmation. If a Twinn elects to remove an active, verified Bound Handle, the Twinn must actively re-confirm and execute the full four-point statutory acknowledgement and Declaration set out in Clause 4.1.3, reflecting the narrowed scope of the objection. Following such re-confirmation, Twinnin shall issue an updated Defend Credential version reflecting the excision of the Bound Handle, commit a corresponding On-Chain Anchor to the Blockchain, and remove the identifier from the Public Verification Page.
  12. CRYPTOGRAPHIC CREDENTIAL ISSUANCE AND W3C VERIFIABLE CREDENTIALS

    1. Following formal Defend-Admin approval under Clause 4.1.5 and successful settlement of the initial Subscription Fee under Clause 4.2, Twinnin shall generate, cryptographically sign, and issue the initial Defend Credential to the Twinn as Digital Content.
    2. Every Defend Credential is constructed as a Verifiable Credential conforming to the World Wide Web Consortium (W3C) Verifiable Credentials Data Model 2.0 (JSON-LD format) and serialised as a compact JSON Web Token (JWT). The Defend Credential is cryptographically signed by Twinnin using AWS KMS asymmetric signing infrastructure using the ES256 algorithm (ECDSA P-256) corresponding to the public key published in Twinnin’s decentralised identifier document (did:web:twinnin.ai at twinnin.ai/.well-known/did.json), enabling autonomous verification using standard cryptographic tooling without dependence upon Twinnin’s internal systems.
    3. The Defend Credential comprises:
      1. top-level metadata, including a unique uniform resource name identifier incorporating the Twinn’s twin_uuid and version number (urn:twinnin:credentials:{twinId}:{version}), the issuer decentralised identifier (did:web:twinnin.ai), the timestamp of issuance (validFrom), Polygon transaction hash references to prior anchoring events where applicable (originalAnchor and previousAnchor), and a 256-bit random cryptographic nonce;
      2. the credentialSubject payload, embodying the Twinn’s pseudonymous twin_uuid, active objection status (status: active or withdrawn), the timestamp of the Declaration (declaredAt), the declared Covered Jurisdiction, the formal text and version of the Declaration (declarationText and declarationTextVersion), and any active Bound Handles (boundHandles) verified pursuant to Clause 11; and
      3. the invariant that because Defend Twinn has no minor path, the credential does not contain an is_minor field.
    4. Twinnin warrants that the Defend Credential shall not incorporate, embed, or publicly disclose the Twinn’s legal name, photographic imagery, identity verification documentation, or raw biometric data.
    5. The Defend Credential does not carry a validUntil expiry date or an annual renewal requirement and shall remain valid continuously unless and until the Twinn withdraws the Declaration, the Defend Credential is superseded under Clause 12.6, or this Agreement is terminated or suspended by either party in accordance with its terms.
    6. Any material alteration to the underlying status, scope, or attributes of the objection, including the approval of an added Bound Handle, the excision of an existing Bound Handle under Clause 11.6, the withdrawal or cancellation of the Declaration, or an account transition under Clause 21, shall automatically revoke and invalidate the prior credential and trigger the generation and signing of a newly incremented, sequential version of the Defend Credential.
    7. The issuance of each version of the Defend Credential generates a corresponding 32-byte cryptographic digest of the canonical credential payload, which Twinnin commits to the Blockchain as an On-Chain Anchor in accordance with Clause 13. Stored credential records are maintained as immutable, read-only instances within Twinnin’s database infrastructure and are accessible to the Twinn via the authenticated Platform dashboard.
  13. PUBLIC BLOCKCHAIN ANCHORING AND LEDGER IMMUTABILITY ACKNOWLEDGMENT

    1. Following the issuance of each version of the Defend Credential pursuant to Clause 12, Twinnin shall commit an On-Chain Anchor to the ConsentRegistry Smart Contract deployed on the Polygon PoS Blockchain. Each On-Chain Anchor transaction records exclusively: (a) the Twinn’s pseudonymous twin_uuid encoded as a 32-byte identifier (left-padded bytes32); (b) the cryptographic digest of the canonical Defend Credential; (c) the sequential version number; and (d) where applicable, cryptographic transaction hash references linking to the immediately preceding anchor.
    2. Twinnin warrants that no directly identifying personal data, including the Twinn’s legal name, contact details, residential address, photographic imagery, identity verification documentation, or raw biometric data, shall be transmitted to or recorded on the Blockchain. The substantive text, verified attributes, and declared terms of the Declaration remain off-chain within the signed Defend Credential.
    3. The Twinn expressly acknowledges and agrees that the Blockchain is a decentralised, public, and mathematically immutable distributed ledger. Once an On-Chain Anchor has been confirmed and included within a confirmed block on the Blockchain, the underlying transactional record, block timestamp, version counter, and cryptographic hash cannot be altered, edited, reversed, overwritten, or deleted by any person, including Twinnin, the Twinn, or any third party.
    4. The Twinn acknowledges that because the pseudonymous twin_uuid and cryptographic digest recorded on-chain correspond to the Defend Credential displayed on or verifiable via the Public Verification Page, on-chain records constitute pseudonymous personal data under Data Protection Legislation. The Twinn understands that the public can observe the frequency, sequence, and timestamps of credential updates associated with that pseudonymous identifier, but cannot derive the substantive content of off-chain records directly from the Blockchain.
    5. The Twinn acknowledges that, by virtue of the immutable technical architecture of the Blockchain, physical deletion or alteration of data committed to the Blockchain is impossible. Accordingly, to the maximum extent permitted by Data Protection Legislation, any request to exercise statutory rights of rectification (under Article 16 of the UK GDPR) or erasure (under Article 17 of the UK GDPR), and any withdrawal of the Declaration, modification of Bound Handles, or account closure, shall be given effect exclusively off-chain by: (a) updating Twinnin’s internal databases; (b) issuing and anchoring a superseded Defend Credential version reflecting the updated status; (c) unpublishing or de-indexing the Public Verification Page in accordance with Clause 10; and (d) permanently severing internal linkages between the Twinn’s real-world identity and the twin_uuid, thereby rendering the historical on-chain ledger entries permanently anonymised and mathematically orphaned as an evidentiary audit trail.
    6. Transactions submitted to the Blockchain are signed server-side using AWS KMS. Twinnin shall bear all network transaction fees (paid in native POL tokens) associated with committing On-Chain Anchors during the active subscription. Subject to the performance standard in Clause 7.3 and except to the extent prohibited by applicable law, Twinnin shall not be liable for transient block confirmation delays, peer-to-peer network reorganisations, or distributed network latency inherent to the Blockchain network.
  14. LIMITED AGENCY APPOINTMENT AND ADMINISTRATIVE AUTHORITY FOR NOTICES

    1. By executing the Declaration and maintaining an active Defend Twinn subscription, the Twinn appoints Twinnin as its non-exclusive, limited administrative communications agent, with authority solely to transmit, lodge, and deliver standardised Takedown Requests, objections, erasure notices, opt-out requests, and rights-of-publicity notices arising out of the Declaration to third-party online platforms, web hosts, and technology providers on the Twinn’s behalf.
    2. The scope of authority conferred under Clause 14.1 is strictly limited to administrative notification, evidentiary transmission, and platform liaison within the operational workflows of the Takedown Service. The Twinn expressly acknowledges that such appointment does not constitute a power of attorney, does not authorize Twinnin to enter into legally binding contracts, settlements, releases, or compromises on the Twinn’s behalf, confers no authority to accept service of legal process or contentious counter-notices, and confers no authority to represent the Twinn in any judicial, arbitral, or contentious legal proceedings.
    3. Twinnin acts solely as an administrative intermediary and communication conduit. In accordance with the Legal Services Act 2007, Twinnin does not provide legal representation, legal advice, or litigation services. The limited agency relationship established under this Clause 14 shall not create any solicitor-client relationship, shall exclude all general fiduciary duties save for the duty to act in good faith in the mechanical dispatch of user-initiated notices, and creates no duty to independently verify the Twinn’s underlying rights or guarantee external platform compliance.
    4. In exercising this administrative authority, the Twinn expressly instructs and authorizes Twinnin to disclose to the relevant recipient: (a) the Twinn’s approved legal first and last name; (b) the unique case reference number; (c) the target uniform resource locator (URL) identified in the Twinn’s report; (d) the Twinn’s submitted factual statement; (e) the verified date of the Declaration; and (f) a hyperlink referencing the Twinn’s Public Verification Page.
    5. The limited agency appointment created under this Clause 14 shall endure continuously for the duration of the Twinn’s active Defend Twinn subscription, and shall automatically and immediately terminate upon the withdrawal of the Declaration, the cancellation or termination of this Agreement, or the transition of the account to Licence Twin pursuant to Clause 21.
  15. TAKEDOWN REQUEST SUBMISSION, CASE LOGGING, AND TWINN OBLIGATIONS

    1. The Takedown Service is strictly a self-reporting mechanism accessible exclusively to the authenticated Twinn whose verified identity corresponds to the active Defend Credential. A Twinn must submit reports personally via the Platform dashboard; no third party, representative, agency, or organisation may lodge a report, case, or Takedown Request on a Twinn’s behalf.
    2. To initiate a takedown case, the Twinn must submit an intake report containing the following information:
      1. one or more precise uniform resource locators (URLs) or functional web addresses where the contested material, synthetic media, or unauthorised Likeness is publicly accessible or hosted;
      2. the identity of the target hosting platform, service provider, or website operator;
      3. a detailed, factual written statement specifying the nature of the misuse, including whether the content involves impersonation, non-consensual synthetic generation, harassment, false commercial endorsement, or Non-Consensual Intimate Imagery (NCII); and
      4. any optional evidentiary material, which may comprise screenshot imagery processed on-device in accordance with Clause 16 and, where permissible, Clause 17, provided that the absence of screenshot imagery shall not prevent a report proceeding directly to triage on the basis of the URL, platform identification, and written statement alone.
    3. The Twinn represents, warrants, and undertakes that:
      1. all factual statements, claims, and representations submitted within a report are true, complete, accurate, and made in good faith;
      2. the reported content depicts, mimics, or misuses the Twinn’s own Likeness or identity, and does not relate to third-party individuals or unrelated material;
      3. the Takedown Service shall not be used for vexatious, defamatory, anti-competitive, fraudulent, or abusive purposes, nor to target legitimate parody, fair dealing, or lawfully licensed uses; and
      4. the Twinn shall promptly disclose any relevant context, including any prior consent, historical release, or ongoing commercial arrangement with the hosting entity or creator.
    4. Upon successful transmission of an intake report via the Platform, the submission is logged within Twinnin’s systems, assigned a unique alphanumeric case reference number, and assigned an initial operational status of “PendingTriage”. Twinnin shall automatically generate a dedicated Case Page within the authenticated Platform interface, rendering:
      1. the unique case reference number, submission timestamp, target platform name, and reported URL;
      2. the real-time operational status of the case within the administrative workflow;
      3. the Twinn’s submitted factual statement, alongside the outputs of any on-device image analysis completed pursuant to Clause 16; and
      4. an authenticated, bilateral messaging thread enabling direct administrative communication between the Twinn and the assigned Defend-Admin regarding case progression, evidence requests, and statutory updates.
    5. Throughout the lifecycle of a case, the Twinn shall:
      1. monitor the Case Page and respond promptly to administrative inquiries or requests for supplementary clarification issued by a Defend-Admin;
      2. immediately notify Twinnin via the Case Page messaging thread if the contested content is removed, altered, or relocated, or if the Twinn resolves the matter directly with the hosting platform; and
      3. cooperate in good faith with Twinnin throughout the triage, notice generation, and escalation phases governed by Clauses 18, 19, and 20.
    6. If Twinnin reasonably determines or suspects that a Twinn has submitted false, fraudulent, or materially misleading claims, or has otherwise abused the reporting workflow, Twinnin reserves the right to immediately reject the pending report, close any active Case Page, and suspend or terminate the Twinn’s access to the Takedown Service or the Twinn’s account in accordance with Clause 26.
  16. CLIENT-SIDE AI MODEL EXECUTION, LOCAL IN-BROWSER PROCESSING, AND BIOMETRICS

    1. Where the Twinn elects to submit screenshot imagery in connection with a Takedown Request under Clause 15.2.4, the processing, classification, and analysis of such imagery are executed locally and client-side within the Twinn’s web browser environment. The underlying screenshot image file remains resident on the Twinn’s local hardware and is not transmitted to, hosted on, or ingested by Twinnin’s server infrastructure, subject only to the separate, express upload exception set out in Clause 17.
    2. In implementation of the data protection by design and default requirements under Article 25 of the UK GDPR and the data minimisation principle under Article 5(1)(c) of the UK GDPR, client-side analysis is performed via compiled WebAssembly machine learning models (utilising the tract inference runtime) downloaded transiently to the Twinn’s browser from Twinnin’s cloud storage, comprising: (a) Marqo’s nsfw-image-detection-384 model (exported to ONNX format) for explicit content classification; (b) YuNet for face detection; and (c) SFace for facial feature embedding and likeness comparison. All intermediate candidate facial crops, algorithmic embeddings, and unselected data are automatically purged from temporary browser memory upon completion or cancellation of the session. The local processing pipeline executes sequentially to:
      1. evaluate the screenshot for explicit or intimate material to generate an automated NSFW Score;
      2. detect biological faces within the screenshot, isolate candidate facial crops, and re-run each candidate crop through the explicit-content classifier, automatically discarding any candidate facial crop boundary that clips into explicit content;
      3. perform mathematical facial feature comparisons between surviving candidate crops and the Twinn’s approved reference photograph to calculate a Likeness Score for each detected face; and
      4. present surviving candidate facial crops to the Twinn within the local browser interface to enable the Twinn to confirm which detected face, if any, corresponds to the Twinn’s biological Likeness.
    3. To the extent that the detection, extraction, and algorithmic comparison of facial geometry under Clause 16.2 constitute the processing of Biometric Data or Special Category Data under Article 9 of the UK GDPR, Section 10 of the Data Protection Act 2018, or other mandatory applicable biometrics legislation, the Twinn hereby grants explicit, informed consent to such local processing solely for the purpose of assessing, triaging, and substantiating potential Likeness misuse in support of a Takedown Request. The Twinn may withdraw this consent at any time prior to submission by terminating the browser session, without prejudice to the Twinn’s right to lodge a Takedown Request under Clause 16.5.
    4. Prior to final case transmission, the Twinn is presented with a pre-submission confirmation screen specifying the precise data payload to be transmitted to Twinnin. While the written statement, URL, and target platform remain editable by the Twinn prior to submission, the NSFW Score and confirmed facial crop are system-generated and uneditable. By confirming the submission, the Twinn instructs and authorises Twinnin to receive, process, and retain strictly the following extracted evidentiary outputs:
      1. the generated NSFW Score;
      2. the single cropped image of the specific face confirmed by the Twinn, alongside its corresponding Likeness Score (subject to a secondary automated re-classification check prior to ingestion, whereby any crop that clips into explicit content is dropped);
      3. the Twinn’s written statement, target uniform resource locator (URL), and target platform identification; and
      4. the uneditable system timestamp recording the date and time of intake.
    5. If no facial geometry is detected within the screenshot, or if the Twinn confirms that none of the detected facial crops represent the Twinn’s Likeness, the intake report may proceed to triage on the basis of the URL, target platform, written statement, and NSFW Score alone, without any facial crop or Likeness Score attached. Automated scores, crop thresholds, or model outputs shall not constitute a pre-condition to lodging a case or receiving administrative triage under Clause 18.
    6. Twinnin grants the Twinn a personal, non-exclusive, revocable, non-transferable, royalty-free licence to download and execute the client-side machine learning runtime and model weights within the Twinn’s browser session strictly for the non-commercial purpose of preparing a Takedown Request under this Agreement. Except to the extent permitted by applicable law that cannot be excluded by contract, the Twinn shall not reverse engineer, decompile, extract, distribute, or repurpose such models or software.
    7. While Twinnin supplies Digital Content in accordance with statutory standards under the CRA 2015 and Clause 7.2, the Twinn acknowledges that local model inference is dependent upon the Twinn’s browser configuration, processing hardware, and display drivers. Twinnin does not warrant that client-side machine learning models will operate entirely free of false positives or false negatives, and algorithmic likeness indications are treated as non-dispositive technical indicators corroborated by human triage pursuant to Clause 18.
  17. OPTIONAL UNEDITED CONTEXTUAL EVIDENCE AND CONTENT SAFETY THRESHOLDS

    1. Where the substantive basis of a Takedown Request involves contextual Likeness misuse that cannot be adequately substantiated by an isolated facial crop alone, such as unauthorized commercial endorsements, brand associations, or non-intimate impersonations, the Twinn may elect, as an express and strictly gated exception to the client-side processing architecture set out in Clause 16.1, to upload and transmit the original, unedited full screenshot to Twinnin’s secure server infrastructure.
    2. The transmission of an unedited screenshot under Clause 17.1 is strictly conditional upon the automated NSFW Score generated by the local client-side model under Clause 16.2.1 being equal to or less than 0.20. The Platform interface shall not provide, display, or activate the technical facility to upload an unedited screenshot if the client-side NSFW Score exceeds 0.20. In addition, Twinnin shall enforce this threshold through automated server-side verification upon ingestion, and any transmission that fails to satisfy this threshold shall be rejected and purged immediately without ingestion or review.
    3. Where an unedited screenshot satisfies the dual eligibility thresholds in Clause 17.2 and the Twinn opts to submit it, the Twinn shall be required to review an itemized pre-submission disclosure and provide an affirmative digital confirmation: (a) acknowledging and explicitly consenting to the complete image file being transmitted to, stored on, and processed by Twinnin’s cloud infrastructure as a distinct evidentiary asset solely for administrative triage by a Defend-Admin under Clause 18; and (b) warranting that the Twinn is legally entitled to submit such image file and that doing so does not infringe any third-party privacy, data protection, or intellectual property rights.
    4. A Defend-Admin conducting triage under Clause 18 may, at their sole discretion, permanently delete an uploaded unedited screenshot from Twinnin’s storage systems if the Defend-Admin determines that the content is explicit, inappropriate, or depicts Non-Consensual Intimate Imagery (NCII), notwithstanding any automated score generated under Clause 17.2. In such event, the corresponding Case Page record shall note that an unedited screenshot was submitted and removed, and the underlying Takedown Request shall proceed exclusively upon the basis of the confirmed facial crop, URL, and written statement.
    5. The unedited screenshot permitted under this Clause 17 is utilized strictly for preliminary internal triage under Clause 18 and shall be securely and permanently deleted from Twinnin’s live systems within thirty (30) days of the conclusion of such triage. Except where required by applicable law, a court order of competent jurisdiction, or a binding regulatory directive, Twinnin shall not include, attach, or forward an unedited screenshot to any third-party recipient, nor shall such image form part of an Escalation Evidence Pack compiled under Clause 20.
  18. CASE TRIAGE, HUMAN REVIEW, AND REJECTION PROCEDURES

    1. Following receipt of an intake submission logged under Clause 15, every case is subjected to administrative assessment and human review conducted by a Defend-Admin. Consistent with Data Protection Legislation, no final determination to approve, reject, or legally classify a Takedown Request is made solely by automated processing, and automated metrics (including any NSFW Score or Likeness Score generated under Clause 16) serve as corroborating technical indicators rather than determinative criteria.
    2. During triage, the Defend-Admin assesses the evidentiary submission to determine:
      1. whether the reported material reasonably corresponds to the verified biological identity of the Twinn, evaluated by cross-referencing the confirmed facial crop, written statement, or approved profile reference imagery, or by exercising the administrative verification rights set out in Clause 9.8;
      2. whether a prima facie, viable statutory or contractual legal basis exists within a Covered Jurisdiction to support the dispatch of formal notices under the limited agency authority set out in Clause 14; and
      3. whether the contested material constitutes Non-Consensual Intimate Imagery (NCII). A factual statement affirming the non-consensual intimate nature of the content submitted by an authenticated Twinn shall create a rebuttable presumption of NCII, which the Defend-Admin shall uphold absent manifest fraud, inconsistency, or contrary objective evidence.
    3. If the Defend-Admin is satisfied that the criteria in Clause 18.2 are met, the Defend-Admin shall approve the report, update the operational status on the Case Page to “PendingRequestSent”, and route the case for statutory notice drafting and dispatch pursuant to Clause 19.
    4. If the Defend-Admin determines that the submission lacks sufficient evidence of likeness correspondence, fails to establish a viable legal basis, risks exposing Twinnin to third-party liability, or otherwise falls outside the scope of the Services, the Defend-Admin shall decline to dispatch a notice and update the case status on the Case Page to “PendingNoRequestSent”.
    5. Where a case is assigned “PendingNoRequestSent” status under Clause 18.4, Twinnin shall transmit a written communication to the Twinn via the Case Page messaging thread setting out the objective grounds for refusal. The case shall remain open on the Platform for a period of one (1) month following the date of such notice, during which the Twinn may submit supplementary factual information, clarified statements, or further evidence via the Case Page to address the stated grounds.
    6. If the Twinn supplies supplementary evidence within the one (1) month period specified in Clause 18.5, the Defend-Admin shall re-triage the submission in accordance with Clause 18.2 within a reasonable period. If no response or supplementary evidence is submitted within such one (1) month period, or if the supplementary material remains insufficient to establish a viable basis, the case status shall transition to “NoRequestSent” and the case shall be formally closed without notice dispatch, without prejudice to the Twinn’s right to initiate a distinct report under Clause 15 in respect of different URLs or newly discovered content.
  19. STATUTORY NOTICE GENERATION AND CROSS-JURISDICTIONAL LEGAL ROUTING

    1. Following approval of an intake report by a Defend-Admin under Clause 18.3, Twinnin shall generate and dispatch a formal Takedown Request to the relevant third-party platform, web host, or online intermediary, acting solely as the Twinn’s designated administrative communications agent pursuant to the limited authority granted under Clause 14. Twinnin does not provide formal legal advice, representation, or any guarantee that the recipient platform will remove or restrict the contested material.
    2. Every Takedown Request generated and dispatched by Twinnin shall set out:
      1. the Twinn’s approved legal first and last name;
      2. the unique case reference number allocated pursuant to Clause 15.4;
      3. the target uniform resource locator (URL) or specific online location of the contested content;
      4. the Twinn’s submitted factual statement detailing the nature of the misuse;
      5. the verified execution timestamp of the Declaration, evidencing that the objection predates the creation, distribution, or publication of the contested material; and
      6. an operational hyperlink referencing the Twinn’s Public Verification Page, enabling the receiving entity to verify the underlying Defend Credential and On-Chain Anchor independently.
    3. Twinnin shall determine the appropriate statutory and legal routing for each Takedown Request based on the Twinn’s declared Covered Jurisdiction, the geographic location and legal status of the recipient platform, and whether the case has been classified as Non-Consensual Intimate Imagery (NCII) under Clause 18.2.3, applying the following criteria:
      1. Platform-Specific Channels: where the target platform provides a dedicated machine learning opt-out, biometric data objection, or artificial intelligence content dispute mechanism, Twinnin shall submit the notice through that designated channel, citing the Twinn’s pseudonymous identifier and the execution date of the Declaration;
      2. General European Framework (UK and EEA): where no platform-specific channel exists and the platform is subject to the territorial scope of the UK GDPR or the EU GDPR, Twinnin shall frame the Takedown Request as a formal data subject erasure notice under Article 17 and an objection to processing under Article 21 of the applicable Data Protection Legislation;
      3. United States NCII: where the target platform is subject to United States jurisdiction and the content is classified as Non-Consensual Intimate Imagery (NCII), Twinnin shall dispatch a formal notice under the TAKE IT DOWN Act citing relevant statutory protections, civil tortious non-consensual disclosure, and platform safety enforcement mechanisms;
      4. United Kingdom NCII: where the target platform is subject to United Kingdom jurisdiction and the content is classified as Non-Consensual Intimate Imagery (NCII), Twinnin shall dispatch an intimate image content report under section 100 of the Crime and Policing Act 2026 citing the illegal content duties enforced by Ofcom and relevant criminal offences concerning non-consensual sharing of intimate images;
      5. United States General Misuse: where the target platform is subject to United States jurisdiction and the content involves non-intimate Likeness misuse, commercial misappropriation, or false endorsement, Twinnin shall dispatch a formal right-of-publicity objection notice citing applicable state statutory and common law rights, including consumer privacy protections where applicable; and
      6. Unlisted Platforms: where the recipient platform is not indexed within Twinnin’s internal platform directory, the Defend-Admin shall perform a manual legal classification to establish the governing jurisdiction and applicable regulatory route prior to dispatch.
    4. The Twinn acknowledges and agrees that notices identify contested material exclusively by its URL and descriptive context. Twinnin does not store, host, mirror, or attach copies of the infringing content or synthetic media to any Takedown Request, and the receiving platform remains responsible for accessing, inspecting, and evaluating the material at the specified URL.
    5. Promptly upon the transmission of a notice pursuant to this Clause 19, Twinnin shall update the status of the case on the Case Page to “Submitted”, log the dispatch timestamp, record the relevant response window, and make an administrative copy of the transmitted notice accessible to the Twinn via the Case Page.
  20. PLATFORM RESPONSE TRACKING, BENCHMARK TIMELINES, AND ESCALATION EVIDENCE PACKS

    1. Following the transmission of a Takedown Request under Clause 19, Twinnin shall track the response of the recipient platform or hosting provider through the Case Page against established operational benchmark timelines. The applicable benchmark tracking period commences immediately upon the recorded dispatch timestamp and is determined by the legal classification and governing jurisdiction of the case:
      1. for Takedown Requests concerning Non-Consensual Intimate Imagery (NCII) subject to United Kingdom jurisdiction under section 100 of the Crime and Policing Act 2026 or relevant United States federal legislation under the TAKE IT DOWN Act, Twinnin shall track the request against an expedited benchmark period of forty-eight (48) hours; and
      2. for all other Takedown Requests, including general Likeness objections, right-of-publicity claims, and data subject requests under the UK GDPR or EU GDPR, Twinnin shall track the request against a standard default benchmark period of one (1) calendar month.
    2. The benchmark periods set out in Clause 20.1 serve solely as administrative tracking indicators reflecting statutory response standards and platform performance averages. While Twinnin shall provide tracking services with reasonable care and skill, Twinnin does not control third-party platforms, does not warrant that any platform will respond or comply within such timeframes, and, subject to Clause 7.3, incurs no liability under the CRA 2015 or otherwise for third-party platform delay, non-response, or refusal.
    3. Upon receipt of an external platform response, or upon the expiration of the applicable benchmark period without a substantive reply, Twinnin shall update the status of the case on the Case Page to one of the following terminal or escalation states:
      1. “Removed”, where the platform confirms compliance or the contested content is verified as removed or inaccessible, whereupon the case shall be formally closed;
      2. “Refused”, where the platform communicates an express refusal, rejection, or denial of the Takedown Request; or
      3. “Silent”, where the platform fails to provide an acknowledgment or substantive determination prior to the expiration of the applicable benchmark tracking period.
    4. Where a case transitions to “Refused” (save where the Defend-Admin determines that the platform has provided an objectively valid and conclusive legal justification for non-removal) or “Silent”, Twinnin shall promptly notify the Twinn, the case shall automatically be routed for escalation support, and Twinnin shall generate and deliver an Escalation Evidence Pack to the Twinn via the Case Page.
    5. The Escalation Evidence Pack constitutes a structured evidentiary record compiled in accordance with Data Protection Legislation and the data minimisation principle. It is constructed exclusively from the verified case history, comprising: (a) the submission and dispatch timestamps; (b) the reported uniform resource locator (URL) and target platform identity; (c) the Twinn’s submitted factual statement; (d) the confirmed facial crop and its associated Likeness Score and NSFW Score; (e) transmission records and copies of all formal notices dispatched by Twinnin; (f) records of any correspondence or justifications returned by the platform; and (g) jurisdiction-specific guidance and regulatory complaint templates. In accordance with Clause 17.5, any unedited screenshot uploaded under Clause 17 shall be excluded from the Escalation Evidence Pack.
    6. The regulatory complaint templates and self-help guidance incorporated within the Escalation Evidence Pack are determined by the relevant Covered Jurisdiction and legal classification:
      1. for cases within the United Kingdom involving general data protection or Likeness disputes, guidance and complaint templates for submitting a formal complaint to the Information Commissioner’s Office (ICO);
      2. for cases within the United Kingdom involving Non-Consensual Intimate Imagery (NCII), guidance and complaint templates for submitting an enforcement report to the Office of Communications (Ofcom) pursuant to section 100 of the Crime and Policing Act 2026 or relevant criminal justice authorities;
      3. for cases within the European Economic Area, guidance and complaint templates for lodging a supervisory complaint with the competent national Data Protection Authority (DPA) in the Twinn’s member state of habitual residence;
      4. for cases within the United States involving Non-Consensual Intimate Imagery (NCII), guidance and complaint templates for reporting statutory violations to relevant law enforcement agencies or under the federal TAKE IT DOWN Act; and
      5. for cases within the United States involving general likeness misuse, commercial misappropriation, or false endorsement, the Escalation Evidence Pack serves as the terminal administrative artefact for the Twinn’s independent consideration and private legal recourse.
    7. The Twinn expressly acknowledges that the Escalation Evidence Pack, regulatory complaint templates, and accompanying guidance are provided strictly as informational, administrative record-keeping tools. In accordance with the Legal Services Act 2007 and Clause 8, Twinnin does not provide legal advice, legal representation, or litigation support. Twinnin does not file formal complaints with supervisory authorities, initiate administrative appeals, or commence civil litigation on behalf of the Twinn. Any decision to submit an Escalation Evidence Pack to a regulatory authority, enforcement body, or court of law remains at the sole discretion, initiative, and expense of the Twinn acting independently or through qualified legal counsel.
    8. Twinnin shall maintain the complete digital case record, including all notice logs, scores, confirmed facial crops, and the Escalation Evidence Pack, accessible to the Twinn on the Case Page for a period of six (6) years following the date of case closure, justified under Data Protection Legislation for the establishment, exercise, or defence of legal claims. In the event that a case becomes subject to active litigation or a formal statutory investigation, Twinnin shall place the case record on legal hold, preserving access and suspending routine data deletion schedules until the final resolution of the relevant proceedings.
  21. SWITCHING TIERS BETWEEN DEFEND TWINN AND LICENCE TWIN

    1. The Twinn may elect to transition between the Defend Twinn subscription service tier and the commercial Licence Twin platform tier at any time via the authenticated Platform dashboard, subject to the procedural, financial, and data management terms set out in this Clause 21.
    2. Where an active Twinn transitions from Defend Twinn to Licence Twin:
      1. the Twinn’s verified identity credentials, biometric screening records, and date of birth previously confirmed via Sumsub shall carry over automatically without requiring duplicative government identity document re-verification;
      2. recurring billing of the Subscription Fee shall cease at the conclusion of the then-current monthly billing period, during which the Twinn shall continue to retain access to the Defend Twinn Services pursuant to Clause 5.5, with no pro-rata refund or rebate payable in respect of any unexpired portion of such billing period;
      3. Twinnin shall retain a secure administrative record of the Twinn’s former Defend Twinn subscription for a period of one (1) month following the effective transition date, during which the Twinn may reverse the transition and restore Defend Twinn status without incurring duplicate onboarding or account establishment charges;
      4. the Twinn shall configure their commercial likeness preferences, media assets, dubbing rights, and licensing terms under the governing contractual documentation applicable to Licence Twin; and
      5. upon activation of the commercial licence preferences, Twinnin shall issue an updated Verifiable Credential under the Twinn’s existing twin_uuid, which shall be recorded as an On-Chain Anchor on the Blockchain pursuant to Clause 13, formally replacing and superseding the prior Defend Credential.
    3. Where an active Twinn transitions from Licence Twin to Defend Twinn:
      1. the Twinn’s completed identity verification and liveness records shall carry over to Defend Twinn without requiring repeated Sumsub screening, provided that the Twinn satisfies the territorial residency criteria of a Covered Jurisdiction under Clause 3.1.2;
      2. the Twinn must execute the four-point statutory acknowledgement and Declaration in accordance with Clause 4.1.3, provide valid payment details via Stripe pursuant to Clause 5, and expressly consent to the immediate supply of the Defend Twinn Services, thereby acknowledging that any statutory right of cancellation under the CCRs 2013 is lost once the service has been fully performed (or, in the case of digital content not supplied on a tangible medium, once performance has begun with the consumer’s express consent and acknowledgment of that loss);
      3. recurring billing of the monthly Subscription Fee shall commence immediately upon active checkout confirmation via Stripe, and the initial Defend Credential and On-Chain Anchor shall be committed under the Twinn’s stable twin_uuid; and
      4. all commercial licensing features associated exclusively with Licence Twin, including agency representation links, co-guardian designations, enterprise project allocations, and commercial rate tiers, shall be deactivated from the active account, provided that: (a) any commercial licences or sub-licences legally executed with third parties prior to the transition date shall continue in full force and effect in accordance with their terms; and (b) Twinnin may retain commercial transaction, licensing, and payment records to the extent strictly necessary for statutory tax, accounting, and dispute resolution purposes.
    4. An applicant who has initiated an onboarding application may transition between Defend Twinn and Licence Twin free of charge at any time prior to their application entering formal review by a Defend-Admin under Clause 4.1.5 or the equivalent review stage under Licence Twin. Where an applicant switches tiers prior to such review:
      1. any identity verification steps completed via Sumsub shall be preserved and applied to the alternative tier;
      2. the application workflow shall adjust to collect the requisite imagery, terms, or jurisdictional declarations mandated by the destination tier; and
      3. no binding contract or recurring subscription mandate shall be formed until the applicant receives administrative approval and confirms payment for the selected tier in accordance with Clause 4.2.
    5. Transitioning between tiers does not require routine human review of identity documentation. However, if the Twinn submits a replacement profile photograph or seeks to bind additional handles concurrently with a tier transition, such photograph or handle shall remain subject to the independent verification, screening, and Defend-Admin approval procedures set out in Clause 9 and Clause 11.
    6. Every completed transition between Defend Twinn and Licence Twin constitutes a formal alteration of the Twinn’s legal status and rights assertion, and shall automatically trigger the generation and cryptographic signing of a newly incremented, sequential version of the relevant Verifiable Credential and the recording of a corresponding On-Chain Anchor on the Blockchain.
  22. INTERACTIVE BADGE GENERATION AND TRANSIENT PROCESSING LICENCES

    1. Twinnin grants to the Twinn a personal, non-exclusive, revocable, non-transferable, royalty-free licence for the duration of their active Defend Twinn subscription to access and use the Badge Tool via the Platform dashboard solely for their personal provenance, identity assertion, and verification purposes.
    2. The Badge Tool enables the Twinn to submit an image file to composite a machine-readable quick response (QR) code directly onto such image, linking resolving parties to the Twinn’s Public Verification Page. The Platform interface shall simultaneously display the complete, selectable, and copyable text of the uniform resource locator (URL) corresponding to such Public Verification Page alongside the composited visual output.
    3. The Twinn represents, warrants, and undertakes that:
      1. they own or hold all requisite intellectual property rights, licences, consents, and permissions in and to any photograph or image file uploaded to the Badge Tool;
      2. the submission, processing, and public deployment of such image file does not and shall not infringe, misappropriate, or violate any third-party copyright, trade mark, privacy, publicity, or other proprietary rights; and
      3. no image submitted to the Badge Tool contains any unlawful, defamatory, sexually explicit, abusive, or infringing material, any content depicting Non-Consensual Intimate Imagery (NCII), or any malware, malicious code, or corrupted data.
    4. The Twinn grants to Twinnin and its technical sub-processors a worldwide, non-exclusive, royalty-free, transient licence to ingest, host, reproduce, adapt, and process any uploaded image solely to the extent technically necessary to generate, render, and composite the QR code overlay and return the resulting graphic file to the Twinn’s browser session. In accordance with data minimisation principles under Data Protection Legislation, such processing is strictly ephemeral; Twinnin shall not permanently store, persist, archive, duplicate, or repurpose any source image uploaded to the Badge Tool once transmission of the output is complete or the processing session terminates or fails.
    5. Subject to the statutory standards for Digital Content under the CRA 2015 and Clause 7.2, the Twinn acknowledges that the appearance, contrast, and scannability of a composited QR code depend on the resolution, aspect ratio, colour profile, and compression of the source image. Twinnin does not warrant that the composited code will remain legible or scannable if resized, compressed, distorted, or modified by external platforms, and, to the maximum extent permitted by applicable law (without excluding statutory remedies under the CRA 2015), excludes liability for third-party scanning failures, device incompatibility, or optical capture errors.
  23. DATA PROTECTION, PRIVACY, AND PUBLIC LEDGER ERASURE LIMITATIONS (UK GDPR)

    1. Both parties shall comply with all applicable requirements of the Data Protection Legislation. For the purposes of the Data Protection Legislation, Twinnin operates as an independent Data Controller in respect of personal data processed to administer the Platform, manage accounts, issue Credentials, and provide the Services. The categories of personal data processed, the lawful bases for processing, international transfers, data subject rights, and complaint procedures are set out in the Privacy Policy, and the handling of all personal data is governed by this Clause 23 and the Privacy Policy.
    2. The Twinn acknowledges and agrees that the operation of the Services involves the processing of special category personal data, specifically biometric data within the meaning of Article 9(1) of the UK GDPR and Section 10 of the Data Protection Act 2018. In accordance with Article 9(2)(a) of the UK GDPR, the Twinn provides explicit, informed consent for the processing of biometric data (including facial geometry vectors and reference imagery) solely for the purposes of:
      1. verifying identity, adult capacity, and liveness during onboarding via Sumsub;
      2. conducting Defend-Admin human verification of profile imagery pursuant to Clause 9;
      3. performing client-side Likeness Score analysis in support of Takedown Requests under Clause 16; and
      4. maintaining secure evidentiary audit trails of the Declaration and associated takedown proceedings.
      5. The Twinn may withdraw this consent at any time by notifying Twinnin in writing or closing their account. The Twinn acknowledges that withdrawal of consent shall not affect the lawfulness of processing based on consent before its withdrawal, but will result in the immediate suspension or termination of those Services that strictly require biometric verification.
    3. The Twinn acknowledges that identity verification documentation and liveness data are processed in conjunction with Sumsub. Sumsub acts as an independent data controller in respect of the capture, document authenticity verification, and retention of underlying government-issued identity documents pursuant to its own privacy policies. Twinnin receives and processes strictly limited outputs, comprising the verification outcome, verified date of birth, and facial reference images necessary for Defend-Admin review and administrative triage.
    4. The Twinn expressly acknowledges that On-Chain Anchors committed to the Blockchain contain pseudonymous personal data, specifically the Twinn’s twin_uuid and cryptographic digests (SHA-256 hashes) of the Defend Credential. Due to the immutable, decentralised, and permanent mathematical architecture of the public distributed ledger:
      1. the parties acknowledge that technical immutability precludes the literal modification or deletion of on-chain blocks, and the Twinn agrees that any request to exercise statutory rights of rectification under Article 16 of the UK GDPR or erasure under Article 17 of the UK GDPR, or upon withdrawal or cancellation of the Declaration, shall be satisfied by Twinnin taking all commercially and technically feasible off-chain steps; and
      2. such off-chain measures shall comprise permanently deleting off-chain personal data from live production databases, unpublishing the Public Verification Page, destroying corresponding cryptographic decryption keys where applicable, or issuing an updated credential version reflecting a revoked status, thereby permanently severing the correlation between the Twinn’s real-world identity and the orphaned on-chain hash.
    5. Twinnin implements the technical and organisational security measures described in the Privacy Policy to protect personal data and special category biometric data against unauthorised or unlawful processing, accidental loss, destruction, or damage, including platform-level encryption at rest and in transit, hardware security module key isolation via AWS KMS, and role-based administrative access controls restricting Defend-Admin personnel.
    6. Twinnin shall not transfer personal data outside the United Kingdom except in accordance with Chapter V of the UK GDPR and the international transfer safeguards described in the Privacy Policy.
  24. USER WARRANTIES, ACCEPTABLE USE, AND PROHIBITED CONTENT (ONLINE SAFETY ACT 2023)

    1. The Twinn represents, warrants, and undertakes to Twinnin on a continuing basis throughout the term of this Agreement that:
      1. they possess full legal capacity and competency under the laws of England and Wales and their declared Covered Jurisdiction to enter into, execute, and perform their obligations under this Agreement;
      2. all information, declarations, personal identifiers, contact details, and evidence submitted to Twinnin across the Platform (including during onboarding, handle verification, and takedown reporting) are authentic, accurate, complete, and not misleading in any material respect; and
      3. they shall access and utilise the Platform, the Services, the Badge Tool, and the Digital Content solely in their personal capacity as an individual consumer for lawful purposes, and strictly in compliance with applicable laws, regulations, and the terms of this Agreement.
    2. The Twinn shall not submit, upload, transmit, link, distribute, composite, or otherwise process across or through the Platform (whether via profile images, the Badge Tool, case messaging threads, or intake reports) any material, data, or content that:
      1. constitutes priority illegal content or unlawful material under the Online Safety Act 2023, including any image, text, recording, or representation depicting or promoting child sexual exploitation and abuse (CSAE), suicide or self-harm encouragement, cyberflashing, threats to share intimate images, or extreme violence;
      2. depicts, generates, or disseminates Non-Consensual Intimate Imagery (NCII) of any third party, or any visual depiction of an identifiable individual published without their prior informed consent;
      3. is defamatory, fraudulent, menacing, grossly offensive, obscene, racially or religiously abhorrent, harassing, or calculated to incite hatred, disorder, or violence against any person;
      4. infringes, misappropriates, or breaches the intellectual property rights, database rights, trade secrets, moral rights, privacy rights, publicity rights, or data protection rights of any third party; or
      5. introduces any computer virus, Trojan horse, worm, logic bomb, automated scraping tool, keystroke logger, spyware, or other harmful or malicious code intended or designed to damage, interrupt, intercept, or expropriate the Platform or underlying systems.
    3. The Twinn expressly undertakes that they shall not:
      1. use the Platform or the Takedown Service to lodge fraudulent, vexatious, frivolous, deceptive, bad-faith, or anti-competitive complaints, or mischaracterise legitimate parody, statutory fair dealing, public commentary, or lawfully licensed replicas as actionable misuse;
      2. impersonate any other individual, misrepresent an affiliation with any person or corporate entity, or register, verify, or claim Bound Handles belonging to third parties;
      3. probe, scan, or test the vulnerability of the Platform, the Smart Contract suite, or associated server infrastructure, or circumvent, bypass, or disable any security, content-filtering, rate-limiting, or authentication mechanisms implemented by Twinnin;
      4. sub-license, resell, lease, syndicate, transfer, or commercially exploit access to Defend Twinn, the Case Page, the Badge Tool, or the Defend Credential; or
      5. engage in any conduct that exposes Twinnin, its personnel, its sub-processors, or other users to civil liability, regulatory sanctions, criminal proceedings, or reputational harm.
    4. In accordance with Twinnin’s safety obligations, compliance duties under the Online Safety Act 2023, and statutory duties under English law, Twinnin reserves the right, acting reasonably and without prejudice to any other remedies under Clause 26:
      1. to inspect, screen, and remove any content, metadata, or media uploaded to the Platform that Twinnin reasonably considers to be in breach of this Clause 24;
      2. to suspend, restrict, or revoke the Twinn’s access to the Platform, the Takedown Service, or their account, immediately and without prior notice where reasonably necessary to prevent imminent harm, address legal or regulatory exposure, or protect platform security, or where Twinnin reasonably suspects a material breach of this Clause 24; and
      3. to report any detected, suspected, or confirmed occurrence of child sexual exploitation and abuse (CSAE), severe online harm, or priority illegal content to the National Crime Agency (NCA) or competent statutory law enforcement authorities, and to preserve and disclose relevant evidentiary records, connection logs, and case data to such authorities in accordance with Data Protection Legislation, without incurring liability for any bona fide compliance action taken pursuant to this Clause 24.4.
  25. INTELLECTUAL PROPERTY RIGHTS, MODEL LICENSING, AND BRAND PROTECTION

    1. As between the parties, Twinnin (or its licensors) owns all right, title, and interest, including all intellectual property rights (whether registered or unregistered, and including all applications, renewals, and rights to apply for the same worldwide), in and to: (a) the Platform, Services, Digital Content, software, code, algorithms, APIs, Smart Contracts, database architectures, and user interfaces; (b) all client-side machine learning and artificial intelligence models, weights, classification pipelines, WebAssembly runtimes, and related analytical tools; (c) the trade marks, service marks, logos, brand names, and trade dress of Twinnin, including “Twinnin”, “Defend Twinn”, “Licence Twin”, and “Human Verified”; and (d) all documentation, templates, and Platform-generated outputs.
    2. Subject to the Twinn maintaining an active Defend Twinn subscription and complying with this Agreement, Twinnin grants to the Twinn a personal, non-exclusive, non-transferable, revocable, royalty-free licence for the duration of this Agreement to: (a) access, view, and use the Platform and Digital Content solely for their personal, non-commercial use in managing their objection and receiving the Services; and (b) display and hyperlink to their Public Verification Page and deploy unmodified visual assets generated via the Badge Tool incorporating the “Human Verified” mark, strictly to signify their personal verification and provenance status. This licence terminates immediately upon suspension, cancellation, or termination of the Twinn’s subscription or this Agreement.
    3. Except to the extent expressly permitted by applicable law that cannot be excluded by contract (including section 50B of the Copyright, Designs and Patents Act 1988), the Twinn shall not: (a) copy, modify, adapt, translate, reproduce, distribute, or create derivative works from the Platform, Services, or Digital Content; (b) reverse engineer, decompile, disassemble, decode, extract, or attempt to derive source code, algorithms, training data, or model architectures from any portion of the Platform, including downloadable WebAssembly modules and machine learning weights; (c) sub-license, rent, lease, sell, assign, syndicate, or commercially exploit any software, tool, credential, or output supplied by Twinnin; (d) remove, obscure, or alter any copyright notice, trade mark, digital identifier, or proprietary legend affixed to or contained within the Platform, the Defend Credential, or the Public Verification Page; or (e) use the trade marks, logos, or brand collateral of Twinnin in any manner that suggests commercial affiliation, endorsement, agency representation, or sponsorship without Twinnin’s prior written consent.
    4. The Twinn retains all right, title, and interest, including all intellectual property and personality rights, in and to the profile imagery, reference media, textual descriptions, and factual statements that they supply across the Platform (Twinn Content). Except for the operational, processing, and display licences expressly granted to Twinnin under this Agreement, nothing in this Agreement transfers, licenses, or assigns any ownership, commercialisation rights, or exploitation rights in the Twinn’s Likeness, copyright, or Twinn Content to Twinnin or any third party.
    5. If the Twinn transmits, submits, or provides any feedback, enhancement requests, recommendations, suggestions, or ideas regarding the Platform, Services, models, or operational workflows (Feedback), Twinnin shall be entitled to use, disclose, incorporate, commercialise, and exploit such Feedback without restriction, compensation, credit, or accounting to the Twinn. The Twinn hereby assigns to Twinnin, with full title guarantee, all right, title, and interest in and to any intellectual property rights arising out of such Feedback, waives all moral rights arising under Chapter IV of the Copyright, Designs and Patents Act 1988 (and any equivalent rights worldwide) in such Feedback, and agrees to execute all documents reasonably requested by Twinnin to perfect such assignment.
  26. SUSPENSION, ACCOUNT TERMINATION, AND INACTIVITY PURGING

    1. Twinnin may, without prejudice to any other rights or remedies, immediately suspend, restrict, or throttle the Twinn’s access to the Platform, the Services, the Badge Tool, and the Takedown Service, or unpublish the Public Verification Page, on written notice (or immediately without notice where required by law, regulatory directive, or to prevent imminent harm) if:
      1. the Twinn commits a material breach of this Agreement (including any breach of warranties or acceptable use obligations under Clause 24);
      2. any Subscription Fee remains unpaid, overdue, or subject to a payment dispute, chargeback, or failure via Stripe, and remains unremedied following written notice pursuant to Clause 5.4;
      3. Twinnin reasonably suspects identity fraud, unlawful impersonation, spoofing of a Bound Handle, submission of false or misleading statements in an intake report under Clause 15, or failure to maintain or supply compliant profile or reference imagery under Clause 9; or
      4. Twinnin is required to do so by a court of competent jurisdiction, supervisory authority, statutory regulator (including Ofcom or the Information Commissioner’s Office), or law enforcement agency.
    2. Either party may terminate this Agreement without cause at any time by giving written notice to the other party (or via the self-service cancellation mechanism within the authenticated Platform dashboard), whereupon:
      1. if initiated by the Twinn, such cancellation shall take effect at the conclusion of the then-current monthly billing cycle pursuant to Clause 5.5, with no refund of previously settled Subscription Fees;
      2. if initiated by Twinnin without cause, Twinnin shall give at least thirty (30) calendar days’ advance written notice to the Twinn, and shall refund any pro-rata portion of the prepaid Subscription Fee corresponding to the unexpired remainder of the billing period following the effective termination date; and
      3. on the effective date of such termination, this Agreement shall terminate, subject to the survival provisions in Clause 26.8.
    3. Either party may terminate this Agreement immediately upon written notice to the other party if:
      1. the other party commits a material breach of this Agreement which is incapable of remedy, or, if capable of remedy, fails to remedy such breach within fourteen (14) calendar days of receiving written notice requiring its remedy; or
      2. the other party enters into liquidation, bankruptcy, administration, composition with creditors, or any analogous insolvency proceeding under the laws of any applicable jurisdiction.
    4. Twinnin may additionally terminate this Agreement immediately with written notice to the Twinn if:
      1. the Twinn repeatedly breaches any terms of this Agreement;
      2. the Twinn ceases to satisfy any eligibility criterion under Clause 3.1, including relocating their habitual residence outside a Covered Jurisdiction; or
      3. Twinnin is required to permanently cease providing the Services to the Twinn pursuant to a mandatory order or direction from a court, supervisory body, or law enforcement agency.
    5. In accordance with the principles of data minimisation and storage limitation under Data Protection Legislation, Twinnin implements the following inactivity purging protocols:
      1. any preliminary user account, registration record, and uploaded profile or identity verification material associated with an incomplete or unapproved onboarding application that has remained inactive for twenty-four (24) consecutive hours shall be purged and permanently deleted from the Platform automatically without liability, in accordance with Clause 4.4;
      2. any pending, unverified Bound Handle request that has not been confirmed and approved within thirty (30) calendar days following submission shall automatically expire and be expunged from the Platform pursuant to Clause 11.4; and
      3. following voluntary account closure or termination under this Clause 26, the Twinn’s profile data, personal identifiers, contact details, profile imagery, and active database references shall be deleted or permanently anonymised in accordance with Twinnin’s retention schedules as described in the Privacy Policy, subject to the retention of pseudonymous case audit records under Clause 20.8 and Clause 26.7.
    6. Upon the effective date of termination or account closure for any reason:
      1. all licences granted by Twinnin to the Twinn under this Agreement (including permissions to use the Platform, the Badge Tool, Digital Content, and the “Human Verified” mark under Clause 25.2) shall immediately terminate, and the Twinn shall immediately cease displaying, embedding, or publicly referencing the Badge Tool, Defend Credential, or associated marks on any external platform or profile;
      2. Twinnin’s limited agency mandate under Clause 14 shall immediately cease, and Twinnin shall have no further obligation to process, dispatch, track, or escalate any Takedown Requests or notices (including in-flight requests dispatched prior to termination);
      3. the Twinn’s Public Verification Page shall be unpublished, de-indexed, and permanently rendered inaccessible to the public; and
      4. the active Defend Credential shall be marked as revoked or withdrawn, and Twinnin may, at its operational discretion, commit a final On-Chain Anchor to the Blockchain under the Twinn’s twin_uuid reflecting the revoked status.
    7. On termination of this Agreement, and as provided in Clauses 13.5 and 23.4, historical On-Chain Anchors already committed to the Blockchain cannot be erased, altered, or purged. Twinnin’s sole post-termination obligation in respect of on-chain entries is to execute off-chain decoupling by deleting the associated off-chain identifying personal data, thereby permanently severing real-world correlation with the orphaned On-Chain Anchors.
    8. Termination or expiry of this Agreement, howsoever arising, shall not affect any rights, remedies, obligations, or liabilities of either party that have accrued up to the date of termination. Any provision of this Agreement that expressly or by implication is intended to come into or continue in force on or after termination (including Clause 1, Clause 2, Clause 8, Clause 13, Clause 20.8, Clause 23, Clause 25, Clause 26.6, Clause 26.7, Clause 26.8, Clause 27, Clause 28, Clause 31, and Clause 32) shall remain in full force and effect.
  27. EXCLUSIONS AND LIMITATIONS OF LIABILITY (CRA 2015 COMPLIANT)

    1. Nothing in this Agreement shall limit or exclude Twinnin’s liability for: (a) death or personal injury caused by its negligence; (b) fraud or fraudulent misrepresentation; (c) breach of the terms implied by section 34 (satisfactory quality), section 35 (fitness for purpose), section 36 (as described), or section 41 (right to supply) of the CRA 2015 in relation to Digital Content; (d) breach of the terms implied by section 49 (reasonable care and skill), section 50 (information about the trader or service), section 51 (reasonable price), or section 52 (reasonable time) of the CRA 2015 in relation to Services; (e) compensation for damage to a device or other digital content under section 46 of the CRA 2015; or (f) any other liability which cannot be lawfully limited or excluded under English law, including pursuant to section 57 or section 65 of the CRA 2015.
    2. Subject to Clause 27.1, if Twinnin fails to comply with this Agreement, Twinnin shall be responsible for loss or damage suffered by the Twinn that is a foreseeable result of Twinnin’s breach of this Agreement or Twinnin’s failure to use reasonable care and skill. Loss or damage is foreseeable if either it is obvious that it will happen or if, at the time the contract was made under Clause 4.2, both Twinnin and the Twinn knew it might happen.
    3. Subject to Clause 27.1 and Clause 27.2, Twinnin supplies Defend Twinn, the Platform, the Badge Tool, and Digital Content exclusively for domestic, personal, and private use by individual consumers. If the Twinn uses the Services, the Public Verification Page, or any Digital Content for any commercial, business, trade, or re-sale purpose in breach of this Agreement, Twinnin shall have no liability to the Twinn for any loss of profit, loss of business, business interruption, loss of business opportunity, loss of anticipated savings, or loss of commercial goodwill.
    4. Subject to Clause 27.1, Clause 27.2, and any statutory remedies available under Chapter 3 or Chapter 4 of Part 1 of the CRA 2015, Twinnin’s total aggregate liability to the Twinn arising out of or in connection with this Agreement, whether in contract, tort (including negligence), breach of statutory duty, or otherwise, shall be limited to the greater of: (a) an amount equal to the total Subscription Fees paid by the Twinn to Twinnin under this Agreement in the twelve (12) months immediately preceding the event or series of connected events giving rise to the claim; or (b) fifty pounds sterling (£50).
    5. If defective Digital Content supplied by Twinnin damages a device or digital content belonging to the Twinn as a direct result of Twinnin’s failure to exercise reasonable care and skill, Twinnin shall either repair the damage or pay the Twinn fair and reasonable compensation in accordance with section 46 of the CRA 2015. However, subject to Clause 27.1, Twinnin shall not be liable for damage that could have been avoided by following Twinnin’s advice to apply an update offered free of charge, or for damage caused by the Twinn failing to correctly follow minimum system requirements, browser specifications, or operational instructions communicated by Twinnin.
  28. INDEMNIFICATION AND REGULATORY COMPLIANCE OBLIGATIONS

    1. The Twinn shall comply at all times with all Applicable Law within England and Wales and their declared Covered Jurisdiction, including Data Protection Legislation and the Online Safety Act 2023, in connection with their registration, access to the Platform, and receipt of the Services.
    2. Subject to Clause 28.3, the Twinn shall compensate and indemnify Twinnin (for itself and on trust for its officers, directors, employees, agents, and sub-processors) against all reasonable costs, liabilities, losses, damages, claims, and expenses (including reasonable and documented legal fees, but excluding any statutory fines or penalties to the extent their recovery is prohibited by public policy or applicable law) incurred or suffered by Twinnin arising out of or in connection with:
      1. any material breach by the Twinn of the representations, warranties, or undertakings set out in Clause 11.2, Clause 15.3, Clause 22.3, or Clause 24;
      2. any fraudulent, bad-faith, or knowingly false statements, claims, or evidence submitted by the Twinn in connection with a Takedown Request, Case Page communication, or intake report; or
      3. any third-party claim brought against Twinnin alleging that any photograph, media asset, or content submitted by the Twinn (whether uploaded via the Badge Tool, submitted as profile imagery, or transmitted as an optional unedited screenshot) infringes the intellectual property rights, data protection rights, confidentiality, or privacy rights of any third party.
    3. If the Twinn enters into this Agreement as a consumer, Clause 28.2 shall not constitute an indemnity and the Twinn’s liability shall be limited to direct losses recoverable under general principles of contract law; nor shall Clause 28.2 apply to the extent unfair or unenforceable under the Consumer Rights Act 2015, or to any loss arising from Twinnin’s negligence, fraud, or failure to exercise reasonable care and skill.
    4. If any third party asserts a claim, or if any statutory regulator initiates an inquiry, against Twinnin in respect of which Twinnin may seek recovery under Clause 28.2, Twinnin shall:
      1. give prompt written notice of the claim or inquiry to the Twinn (save where prohibited by applicable law or law enforcement direction);
      2. avoid making any formal admissions or settlements that prejudice the Twinn without prior consultation where reasonably practicable; and
      3. take reasonable steps to mitigate any losses, damages, or liabilities incurred.
  29. PLATFORM MODIFICATIONS, TECHNICAL UPDATES, AND VARIATIONS

    1. Twinnin reserves the right from time to time to update, upgrade, modify, or enhance the Platform, the Services, and the Digital Content, including by applying software patches, security fixes, algorithm revisions, and technical optimizations, or by adjusting the technical functionality and architecture of the Public Verification Page and the management of Verification Page IDs. Twinnin may implement minor technical variations, routine operational enhancements, or bug fixes that do not materially diminish the quality, functionality, or core characteristics of the Services or Digital Content without prior notice to the Twinn.
    2. In accordance with the Consumer Rights Act 2015 and applicable consumer protection legislation, where Twinnin proposes to introduce a modification or technical variation that materially alters the description, functionality, performance, or availability of the Services or Digital Content, or that materially diminishes the Twinn’s control over their Public Verification Page or Verification Page ID, Twinnin shall provide clear written notice of such change to the Twinn by email or via an authenticated notification on the Platform dashboard at least thirty (30) calendar days prior to the effective date of the modification. The thirty (30) calendar days’ prior notice requirement shall not apply where an immediate or accelerated modification is strictly required to address critical security vulnerabilities, urgent legal or regulatory compliance mandates, or emergency operational threats, in which case Twinnin shall give as much prior notice as reasonably practicable.
    3. If any proposed modification under Clause 29.2 is materially detrimental to the Twinn’s access to or use of the Services or Digital Content, the Twinn may terminate this Agreement without penalty or liability at any time prior to the implementation of the change by giving written notice to Twinnin or by cancelling their subscription via the Platform dashboard pursuant to Clause 5.5. Such termination shall take effect on the implementation date of the modification, and Twinnin shall provide a pro-rata refund of any prepaid, unexpired Subscription Fees calculated from the effective date of termination to the end of the current billing period.
    4. Twinnin may amend, revise, or vary the terms of this Agreement from time to time to reflect changes in applicable law, regulatory guidance, technological capabilities, security protocols, or operational infrastructure. Twinnin shall notify the Twinn of any material changes to this Agreement in writing at least thirty (30) calendar days before they become effective. Continued access to or use of the Platform or Services after the effective date of any variation shall constitute acceptance of the amended Agreement; if the Twinn does not agree to the proposed variation, the Twinn may terminate this Agreement without penalty prior to the effective date in accordance with Clause 29.3.
    5. No employee, agent, contractor, or representative of Twinnin (including any Defend-Admin) has the authority to vary, amend, or waive any provision of this Agreement orally or through informal communications. No such statement shall be binding upon Twinnin unless executed in writing by a duly authorised officer of Twinnin.
  30. FORCE MAJEURE AND DISTRIBUTED NETWORK DISRUPTIONS

    1. Neither party shall be in breach of this Agreement nor liable for any delay in performing, or failure to perform, any of its obligations under this Agreement (other than an obligation to make payment of any sums properly due under this Agreement) if such delay or failure results from events, circumstances, or causes beyond its reasonable control (a Force Majeure Event).
    2. A Force Majeure Event includes an act of God, flood, drought, earthquake, or other natural disaster; epidemic or pandemic; terrorist attack, civil war, civil commotion, or riots; war, threat of or preparation for war, or armed conflict; nuclear, chemical, or biological contamination; imposition of sanctions, embargo, or breaking off of diplomatic relations; any law or any action taken by a government or public authority; collapse of buildings, fire, explosion, or accident; interruption or failure of utility service; and general telecommunications carrier failures, widespread internet gateway outages, or distributed denial-of-service (DDoS) attacks directed against core hosting infrastructure.
    3. The Twinn expressly acknowledges that the Services depend upon public distributed ledgers and third-party cryptographic services that operate outside the control of Twinnin. Accordingly, a Force Majeure Event shall further include any of the following distributed network and cryptographic infrastructure disruptions:
      1. any catastrophic failure, network partition, consensus breakdown, persistent validator outage, or chain halt affecting the Blockchain;
      2. any contentious hard fork, chain reorganisation, or state roll-back on the Blockchain that invalidates or delays the confirmation of any On-Chain Anchor or Smart Contract execution;
      3. severe distributed ledger congestion, mempool saturation, or network-wide gas price spikes on the Blockchain that temporarily prevent the timely broadcast or mining of anchoring transactions;
      4. any unexpected disruption, service degradation, or outage affecting external remote procedure call (RPC) routing nodes or JSON-RPC gateway providers utilised to interface with the Blockchain;
      5. any hardware security module failure, key signing latency, or operational unavailability affecting AWS KMS that prevents the automated generation of cryptographic signatures for Verifiable Credentials or transaction payloads; or
      6. any widespread service interruption, security compromise, or technical unavailability experienced by essential third-party identity or payment processors, including Sumsub or Stripe, to the extent such disruption directly prevents the performance of dependent Platform obligations and cannot be mitigated by reasonable commercial failover arrangements.
    4. If a party is affected by a Force Majeure Event (the Affected Party), it shall:
      1. take reasonable steps to notify the other party of the nature and extent of the disruption (which, where Twinnin is the Affected Party, may be given via a Platform notification, service status update, or electronic mail) as soon as reasonably practicable;
      2. use reasonable endeavours to mitigate the effect of the Force Majeure Event on the performance of its obligations and, in the case of Twinnin, restore normal operation of the Services as soon as reasonably practicable; and
      3. upon cessation of the Force Majeure Event, resume performance of its obligations under this Agreement as soon as reasonably practicable, including (where applicable) the submission or resubmission of any queued, delayed, or pending On-Chain Anchors to the Blockchain.
    5. The period of performance for any affected obligation shall be extended by a period equal to the duration of the delay caused by the Force Majeure Event.
    6. If a Force Majeure Event prevents, hinders, or delays the Affected Party’s performance for a continuous period of more than thirty (30) consecutive calendar days, either party may terminate this Agreement immediately by written notice. On such termination, the Twinn shall be entitled to a pro-rata refund of any prepaid, unexpired Subscription Fees for the remainder of the billing period following termination, and neither party shall have further liability to the other, save for rights and liabilities accrued before the Force Majeure Event.
  31. NOTICES, SEVERABILITY, THIRD-PARTY RIGHTS, ENTIRE AGREEMENT, AND WAIVER

    1. Any notice, request, demand, or other formal communication given to a party under or in connection with this Agreement shall be in writing, in the English language, and delivered by hand, pre-paid first-class post or other next working day delivery service, or electronic mail. Notices shall be addressed:
      1. to Twinnin: at AI KAT Limited, First Floor Office, 3 Hornton Place, W8 4LZ, London, United Kingdom, or by electronic mail to legal@twinnin.ai (or to such other physical or electronic address as Twinnin may specify by written notice to the Twinn); and
      2. to the Twinn: at the postal address or electronic mail address associated with the Twinn’s account at the relevant time, or, in respect of operational or administrative updates regarding Takedown Requests, via direct written transmission through the Case Page.
    2. Any notice or formal communication delivered in accordance with Clause 31.1 shall be deemed to have been duly received:
      1. if delivered by hand, at the time of delivery against signature or physical receipt;
      2. if sent by pre-paid first-class post or other next working day delivery service within the United Kingdom, at 9:00 am on the second Business Day following posting;
      3. if sent by pre-paid airmail or international courier to or from an address outside the United Kingdom, at 9:00 am on the fifth Business Day following dispatch; or
      4. if transmitted by electronic mail or posted directly to the Case Page, at the time of transmission or posting (provided that, in the case of electronic mail, no delivery failure or automated bounce notification is received by the sender). If deemed receipt under this Clause 31.2 occurs outside Business Hours, the notice shall be deemed received at 9:00 am on the next following Business Day.
    3. The notice provisions in Clauses 31.1 and 31.2 shall not apply to the service of any proceedings, claims, summonses, or other documents in any legal action or, where applicable, any formal arbitration or judicial dispute resolution proceedings.
    4. Each provision, paragraph, and sub-clause of this Agreement operates separately. If any court of competent jurisdiction or relevant administrative authority determines that any provision, sentence, phrase, or sub-clause of this Agreement is unlawful, invalid, void, or unenforceable, the remaining provisions of this Agreement shall continue in full force and effect.
    5. If any unlawful, invalid, or unenforceable provision would become lawful, valid, and enforceable if some part of it were deleted, such provision shall apply with the minimum deletion necessary to make it lawful, valid, and enforceable. If deletion is not possible, the parties shall negotiate in good faith to agree a replacement provision that, to the greatest extent possible, achieves the intended commercial result of the original provision.
    6. Except as expressly provided in Clause 31.6.1, a person who is not a party to this Agreement shall have no rights under the Contracts (Rights of Third Parties) Act 1999 to enforce or enjoy the benefit of any term of this Agreement:
      1. each officer, director, employee, agent, and technical sub-processor of Twinnin may rely upon and enforce the exclusions, limitations of liability, and protections set out in Clause 27 and Clause 28; and
      2. notwithstanding Clause 31.6.1, the rights of the parties to rescind, vary, amend, or terminate this Agreement in accordance with its terms are not subject to the consent of, or notice to, any third party.
    7. This Agreement, together with any operational policies, credential formats, Declarations, and documents expressly incorporated herein by reference, constitutes the entire agreement between Twinnin and the Twinn regarding its subject matter, and supersedes, cancels, and extinguishes all prior negotiations, draft agreements, commitments, promises, warranties, representations, assurances, and understandings between the parties, whether written or oral, relating to that subject matter.
    8. Each party acknowledges that, in entering into this Agreement, it does not rely on, and shall have no remedies in respect of, any statement, warranty, representation, collateral promise, or assurance (whether made innocently or negligently) that is not expressly set out in this Agreement. Neither party shall have any claim for innocent or negligent misrepresentation or negligent misstatement based upon any statement in this Agreement. Nothing in this Clause 31.8 shall limit or exclude any liability for fraud or fraudulent misrepresentation, nor shall it restrict or exclude any statutory remedies available to a consumer under the CRA 2015.
    9. No failure, delay, or relaxation by a party in exercising any right, power, or remedy provided under this Agreement or by law shall operate as a waiver thereof, nor shall any single or partial exercise of any right, power, or remedy preclude any other or further exercise thereof or the exercise of any other right, power, or remedy. A waiver of any breach of this Agreement shall not constitute a waiver of any subsequent breach and shall be effective only if communicated in writing by the waiving party.
  32. GOVERNING LAW, CONSUMER RIGHTS, AND JURISDICTION (GB-EAW)

    1. This Agreement and any dispute or claim arising out of or in connection with it or its subject matter, formation, or termination (including non-contractual disputes or claims) shall be governed by, and construed in accordance with, the laws of England and Wales.
    2. If the Twinn is a consumer habitually resident in the United Kingdom (outside England and Wales) or in any member state of the European Economic Area, the Twinn also benefits from any mandatory legal provisions that cannot be derogated from by agreement under the laws of their country of habitual residence. Nothing in Clause 32.1 limits or deprives the Twinn of such protections.
    3. Subject to Clause 32.4, each party irrevocably agrees that the courts of England and Wales shall have exclusive jurisdiction to settle any dispute or claim arising out of or in connection with this Agreement or its subject matter, formation, validity, or termination (including non-contractual disputes or claims).
    4. If the Twinn enters into this Agreement as a consumer habitually resident outside England and Wales:
      1. if the Twinn is resident in Scotland, the Twinn may bring proceedings in either the Scottish courts or the courts of England and Wales, and Twinnin may bring proceedings against the Twinn only in the Scottish courts;
      2. if the Twinn is resident in Northern Ireland, the Twinn may bring proceedings in either the Northern Irish courts or the courts of England and Wales, and Twinnin may bring proceedings against the Twinn only in the Northern Irish courts; and
      3. if the Twinn is resident in a member state of the European Economic Area, the Twinn may bring proceedings against Twinnin in either the competent courts of that member state or the courts of England and Wales, and Twinnin may bring proceedings against the Twinn only in the competent courts of the member state in which the Twinn is habitually resident.
  33. EXECUTION AND ELECTRONIC SIGNATURE ACKNOWLEDGEMENT

    1. This Agreement is entered into electronically. By completing the onboarding process, providing affirmative digital confirmation to the Declaration and acknowledgements under Clause 4.1.3, and completing the Stripe checkout workflow under Clause 4.2, the Twinn executes and delivers this Agreement as a legally binding contract.
    2. Twinnin evidences its mutual assent and execution of this Agreement by approving the Twinn’s account via Defend-Admin review under Clause 4.1.5 and issuing the cryptographically signed Defend Credential to the Twinn under Clause 12.

The parties agree that the electronic transmission of assent, including affirmative checkbox clicks, cryptographic key signatures, and digital payment authorisations, satisfies all statutory requirements for writing and execution under the Electronic Communications Act 2000 and Regulation (EU) No 910/2014 (retained UK law). Neither party shall challenge the validity or enforceability of this Agreement on the basis that it was agreed and executed electronically.