LOOMIND DATA PROCESSING AGREEMENT Version 1.0 | 31 October 2026 1. PARTIES, ACCEPTANCE AND PRECEDENCE 1.1 AS Standard FZE, business licence 4424152.01, Business Centre, Sharjah Publishing City Free Zone, Sharjah, United Arab Emirates (Provider), operates Loomind. Its contact for this agreement, security incidents, privacy requests and transfer enquiries is hello@athletestandards.com. 1.2 The Merchant is the legal entity identified by its legal name and registered address, including country, in the acceptance record for its Loomind company. Its privacy contact is the verified business contact email in that record until it supplies a replacement in writing. The named representative confirms authority to bind that entity. An individual acting in business must identify themselves as the contracting Merchant rather than invent a company. 1.3 Provider makes this standing offer by publishing this version through Loomind. It becomes binding between Provider and a Merchant when that Merchant's authorised representative expressly accepts it, electronically through the company agreement flow or by a signed written record identifying this version. Provider's publication constitutes its agreement to these terms; a second discretionary countersignature is not required for the core agreement. The acceptance record identifies the parties, representative, verified contact, version, content digest and time. It forms part of this agreement. The parties intend electronic acceptance to have the effect of a signature. A Shopify installation, permission grant, paid plan, store ownership or viewing this document does not by itself record acceptance. 1.4 This agreement supplements the terms governing the Merchant's use of Loomind and controls in a conflict about Merchant Personal Data. An applicable, executed international-transfer instrument takes precedence over this agreement. No other term limits a data subject's rights or a party's liability under that instrument. Mandatory law prevails. Publication of another version does not silently replace an accepted version. Material changes require notice and the Merchant's agreement, except changes taking effect under the mandatory change mechanism of an already executed transfer instrument. 2. ROLES, SCOPE AND INSTRUCTIONS 2.1 Merchant Personal Data means personal information processed by Provider on the Merchant's behalf through Loomind. Personal information includes information relating to an identifiable individual even if a name is absent. The applicable data protection laws determine the meanings of controller, processor, business, service provider and equivalent terms. 2.2 The standard service under this agreement is supplied to the Merchant as controller (or business), with Provider as processor (or service provider). A Merchant acting as a processor for another controller must identify that controller and obtain its authorisation before submitting that controller's data. Provider must agree the resulting subprocessing arrangement in a Transfer Record or other written supplement before that use begins. Merely selecting a company name does not establish the role or supply another controller's authorisation. 2.3 Documented instructions comprise this agreement, its schedules, authorised workspace actions, configured integrations and verified written requests from the Merchant. Shopify access scopes limit access but do not expand these instructions. The Merchant is responsible for its collection and disclosure authority, required notices, lawful basis, rights handling and the instructions it gives. Consent is required only where applicable law requires it; accepting this agreement is not customer consent and is not a substitute for a lawful transfer mechanism. 2.4 Provider will process Merchant Personal Data only on these instructions to deliver, secure, maintain and support the described service. It will inform the Merchant promptly if it considers an instruction unlawful and suspend that instruction while the issue is resolved. Where binding law requires other processing, Provider will notify the Merchant before processing unless the law prohibits notification, restrict the processing to what is required and preserve the protections of any applicable transfer instrument. 2.5 Provider will not sell Merchant Personal Data, disclose it for cross-context behavioural advertising, use it for unrelated marketing, combine it with another customer's personal data for its own unrelated purposes, or train general-purpose AI models on it. It will not retain, use or disclose it outside the parties' business relationship except as authorised by this agreement and applicable law. Provider certifies that it understands and will comply with these restrictions. An optional feature involving a new AI recipient or purpose requires appropriate notice, instructions and contractual safeguards before the additional processing. The service's development conversation is not an authorised destination for Merchant Personal Data under this agreement. 2.6 Provider separately determines the limited purposes of its own account, contract, billing, fraud-prevention and legal-obligation records, as described in its privacy notice. This does not permit Provider to recategorise the Merchant's order or workspace content as its own controller data or evade this agreement. Shopify supplies the source commerce service under its own terms. An independent supplier or collaborator selected by the Merchant receives only the content the Merchant authorises; it is not thereby permitted to receive customer order history. 3. CONFIDENTIALITY AND SECURITY 3.1 Provider will allow access only to authorised people who need it to perform their duties, are bound by confidentiality or a statutory equivalent, and receive appropriate instructions. It will maintain the technical and organisational measures in Schedule B and measures appropriate to the risks of the processing. It will review their effectiveness and will not materially reduce protection during the service. These are contractual measures, not a claim that Loomind holds an independent security certification or that security can be guaranteed. 3.2 The Merchant will maintain appropriate access roles, protect its credentials, use the available security controls and avoid putting unnecessary personal or sensitive information into free-text fields, attachments and collaboration content. Provider remains responsible for its own security obligations. 4. RIGHTS, INCIDENTS AND COOPERATION 4.1 Provider will give the Merchant reasonable and timely assistance with access, correction, deletion, restriction, portability, objection and other applicable rights, taking account of the processing and information available to it. A request received directly will be forwarded to the Merchant or the requester directed to the Merchant, unless a lawful obligation requires another response. Provider will verify authority, avoid unnecessary collection for verification and assist within the applicable deadline. Signed Shopify privacy notifications are handled through the service's privacy workflow; a request requiring review is not treated as done. 4.2 Provider will notify the Merchant without undue delay after becoming aware of a personal-data breach affecting Merchant Personal Data. It will give available information about the incident, affected data and people, likely consequences, containment and remedial steps, a contact and subsequent material updates. It will preserve necessary evidence and cooperate with the Merchant's notifications and remediation. An investigation need not be complete before initial notification. Provider will not notify affected individuals on the Merchant's behalf without instructions unless legally required. 4.3 Provider will assist with relevant security obligations, impact assessments, transfer assessments and regulatory consultations. It will make information needed to demonstrate compliance available and allow and contribute to audits, including inspections, by the Merchant or its independent confidential auditor. The parties will arrange reasonable notice, scope and safeguards for other tenants. Routine reviews may use current documentation first, but this does not eliminate a legally required inspection, incident-driven audit or supervisory-authority access. Any agreed reasonable cost arrangement must not obstruct legally required assistance. 4.4 The Merchant may take reasonable steps to verify that use remains consistent with its instructions and applicable privacy law, and to stop and remediate unauthorised processing. Provider will promptly notify it if Provider can no longer meet applicable obligations. The parties will restrict or suspend affected processing while safeguards are restored; the Merchant may terminate the affected service if compliance cannot be restored. 5. SUBPROCESSORS 5.1 The Merchant gives general written authorisation for the direct subprocessors in Schedule C and their disclosed service-specific subprocessor chains, subject to this clause and the applicable transfer conditions. Provider will bind each subprocessor through written terms imposing the applicable data protection obligations for the delegated processing and remains responsible to the Merchant for performance of its subprocessing obligations. 5.2 Provider will give at least 30 days' prior written notice, including the recipient, location and function, before a new or replacement subprocessor begins processing the Merchant's data. Notice may use the Merchant's privacy contact or an in-product notice accompanied by an alert to that contact. Merely changing an unmonitored web page does not satisfy this commitment. Provider will monitor upstream notices and pass on relevant changes. An upstream supplier's shorter notice does not waive the Merchant's agreed rights: affected processing must be restricted or another lawful solution agreed where necessary. 5.3 The Merchant may object on reasonable data-protection grounds during that notice period. The parties will work in good faith on safeguards or an alternative. If no suitable solution is available before the change, either may end the affected service, with return or deletion under clause 7 and refund of any prepaid unused fees for that affected service. The objection does not authorise continued processing without adequate safeguards. Provider will supply relevant information about its subprocessing agreements when required by law or an executed instrument, with proportionate protection for confidential information. 6. INTERNATIONAL TRANSFERS 6.1 Processing locations and recipient chains are described in Schedule C. Provider is established in the United Arab Emirates. A database in Germany does not itself establish that all processing, support or access stays in the EEA. Provider will make a transfer requiring legal safeguards only when the applicable conditions have been satisfied. The Merchant does not give a blanket waiver of transfer law by accepting this agreement. 6.2 Schedule D is a standing mechanism for completing and entering the appropriate transfer instrument. It does not declare an unknown destination adequate or an unperformed assessment complete. A restricted transfer must not start until the parties have completed the required Transfer Record, established the lawful basis for the transfer, documented any required assessment and put necessary safeguards in place. The core agreement can take effect before that transfer is authorised. Non-affected service functions may continue without authorising the restricted transfer. No ordinary acceptance checkbox overrides this condition. 6.3 Provider will give the Merchant relevant information about processing locations, government-access exposure and safeguards, notify it of material changes and comply with applicable government-request notice, challenge and minimisation duties. Where protection can no longer be ensured, the parties will suspend the affected transfer and follow the applicable instrument's termination, return and deletion requirements. Required reassessments will cover changes to data, parties, destinations, purposes, access arrangements and applicable law. 7. DURATION, RETURN, DELETION AND EVIDENCE 7.1 Processing continues for the service term and the limited periods in Schedule A. On termination or a verified instruction, the Merchant may choose return in an available interoperable format followed by deletion, or deletion without return. Provider will cease ordinary processing and complete return or deletion of active in-scope copies within 30 days, unless a shorter legal deadline applies. It will identify any exception, basis and expected release date and provide completion confirmation on request. If the Merchant gives no choice, Provider will notify it that deletion will follow and allow a reasonable return opportunity within the same period. A newly generated privacy export remains subject to its seven-day availability limit. 7.2 Backups are separated from ordinary use and expire under the applicable provider cycle. Provider will not restore deleted information to normal use. Any restoration must be isolated and reconciled with independently current erasure records before users or automated processing resume. If a provider cannot erase an individual record immediately from a protected backup, Provider will restrict use to recovery, keep the protection in place, and obtain expiry or deletion under the provider contract. Provider will identify the applicable cycle and any known exception on request. Seven days of backup availability is not a promise that every provider copy is irretrievably erased at that moment. 7.3 Installing or uninstalling one Shopify connection does not itself terminate an independent Loomind workspace or erase unrelated stores. Revoked credentials must not be reused. A verified Shopify erasure instruction is acted on subject to necessary checks for a newer installation, other stores and authority; an unresolved check is investigated, not used to retain data without a continuing lawful purpose. 7.4 Where law requires retention, Provider will identify the requirement, retain only the necessary information, isolate it from ordinary use and erase it when that requirement ends. A legal hold must identify its basis, scope, responsible owner and review or end date; an overdue review does not automatically release it. An operational hold cannot override a binding deletion duty. Provider may retain its own minimal contract and compliance evidence under Schedule A only on an applicable lawful basis; this never permits retaining customer orders as proof of a contract. 8. GENERAL 8.1 Notices go to the contacts identified in clause 1 or their notified replacements. The privacy notice is available through Loomind's public Privacy link. The Merchant may obtain the accepted version and its receipt from its company settings or the Provider. Provider will preserve the link between a receipt and the actual terms; publishing a newer document must not rewrite an earlier accepted copy. 8.2 This agreement is governed by Irish law and disputes between the parties are subject to the courts of Ireland, without prejudice to mandatory applicable law, an applicable transfer instrument's rules or a data subject's right to complain to a competent authority or bring proceedings in an available jurisdiction. If a provision is unenforceable, the rest continues so far as legally possible. No exclusion or cap in other service terms overrides mandatory liability or the rights and remedies under an executed transfer instrument. SCHEDULE A — PROCESSING DETAILS AND RETENTION A1. Subject matter and purpose. Loomind is a company workspace for product and collection development, catalogue and variant management, inventory visibility, sourcing, purchasing and sales planning. Processing includes authorised receipt, storage, organisation, calculation, display, correction, export, access control and deletion. It is continuous while the Merchant uses the relevant functions; imports and updates are repeated as instructed or scheduled. A2. People and data. Data subjects are the Merchant's customers whose orders are imported, workspace members, and business contacts intentionally supplied for the service. Order processing uses store/order/product/variant references, dates, quantities, prices or amounts, currency and country codes. Other instructed content includes products, collections, stock, plans, forecasts, supplier details, comments and files. Membership, roles, integration credentials, synchronisation records and privacy-request evidence support operation of these functions. A3. Limits. Order imports do not require customer names, customer email addresses, telephone numbers, street addresses or payment-card details. Order references may still be personal data. The standard service is not intended for special-category, criminal-offence, health or other sensitive personal data, or children's personal data as a distinct dataset. The Merchant must not submit these unless the parties first agree the necessity and additional safeguards. Unexpected inclusion must be reported, restricted and removed or handled under a lawful agreed instruction. A4. Identifiable Shopify orders: a rolling 24 calendar months from the order's creation date, calculated in UTC. Expired order-level information is removed from active workspace data, import snapshots, synchronisation jobs and privacy exports. Write checks and hourly maintenance enforce this boundary. Legacy dates that cannot be parsed require prompt investigation and restricted use while resolved; they are not a perpetual-retention category. For authorised historical planning, older orders may be processed transiently to calculate the permitted aggregates before their identifiable order-level data is discarded. A5. Aggregate planning history: product, variant and market series without order or customer identifiers may remain for the Merchant's instructed planning during the service. They remain company-restricted and subject to this agreement to the extent they are personal data. Removing identifiers is not a universal guarantee against re-identification. Termination and deletion instructions cover these series unless they have become genuinely anonymous under applicable law. A6. Privacy export bundles: seven days from creation. Downloads are denied after expiry and hourly cleanup removes expired bundles. This period does not extend the lifetime of their source information. A7. Completed technical records: successful synchronisation jobs are eligible for deletion 12 months after both completion and last update; processed, allowlisted operational webhook records 12 months after processing; and access-audit records 12 months after their event. A daily cleanup removes eligible records in limited batches. Documented lawful preservation holds are respected. These periods do not permit order-level information to exceed A4. A8. Import snapshots: superseded snapshots are eligible for deletion 30 days after creation; the latest snapshot for each company, store and source remains for the active service. Hourly cleanup respects documented snapshot holds and limited batches. All snapshots remain subject to A4 and clause 7. Unclaimed installation credentials: 30 minutes; expired claims and reads are denied and hourly cleanup removes expired installation records and encrypted credentials. Holds do not extend credential validity. A9. Exceptions to the completed-technical cleanup are governed by this operational schedule, rather than an indefinite exemption: (a) Failed, abandoned and unfinished jobs: review after 30 days without progress; resolve or cancel work no longer needed and delete its payload within the next 30 days. Keep only necessary diagnostic metadata for at most 12 months after resolution, unless a documented incident or legal hold requires more. An active retry does not authorise retaining expired order-level data. (b) Privacy requests and their associated webhook evidence: retain while a request is open and for up to 12 months after resolution to evidence its handling. Remove unnecessary payload and verification material earlier. A specific dispute or legal requirement may justify a documented longer hold. (c) Erasure-prevention records: retain only the minimum store/company/order identifiers needed to prevent prohibited reimport or resurrection. Review necessity at least every 90 days. Delete within 30 days once authorised source access has ended and relevant restorable copies have expired or been reconciled, unless a documented legal obligation requires retention. These records cannot be used to reconstruct the erased customer content. (d) Minimal acceptance evidence: retain the accepted text, version, digest, company identity, representative, verified contact and acceptance time during the service and, where still necessary for contract or claim evidence, for up to six years afterwards. Review necessity annually and remove unnecessary personal identifiers earlier. Six years is a contractual ceiling for this purpose, not a statement that every jurisdiction requires it. A concrete legal obligation or live dispute may require a documented hold. A10. The Provider's privacy operator, reachable at the clause 1 address, owns the manual reviews in A9 and termination requests. Automated cleanup does not replace these reviews. Physical deletion may follow a scheduled job or batch; expired data must not be made available for ordinary use during a backlog. The operator will monitor failures and clear backlogs promptly. Provider backups follow clause 7.2; they are not covered by the active-database job periods above. SCHEDULE B — TECHNICAL AND ORGANISATIONAL MEASURES B1. Separation and authorisation. Company-scoped server authorisation and database access restrictions separate workspaces. Membership status and role control access and changes. Administrative access is limited to operational need. Legal acceptance requires an active company administrator, a verified identity, express acceptance and a declaration of authority; platform administration alone does not sign for a Merchant. B2. Confidentiality and credentials. Network transport uses encrypted connections; managed database and backup encryption is provided by the infrastructure provider. Integration credentials are kept on the server in protected storage rather than exposed in normal client responses. Installation credentials expire as in A8. Personnel access is restricted and subject to confidentiality. This is not a claim of end-to-end encryption against every authorised provider or government. B3. Integrity and minimisation. Shopify webhook signatures and source details are verified. Authorised imports minimise customer fields. Server write guards and retention filters apply to persistent order copies. Privacy exports require company authority and expire. Changes to authorisation, integration and retention logic are subject to testing appropriate to their risk. B4. Availability and recovery. Provider uses the managed database backup service and maintains a recovery procedure. Recovery targets must be isolated from users, outbound integrations, webhooks and automatic jobs. The latest independent erasure evidence is reconciled before return to service. Restore exercises check content integrity and relationships within their documented scope. A scoped exercise is not represented as a complete infrastructure restoration or a guaranteed recovery time. Production is not overwritten for a rehearsal. B5. Accountability. Provider maintains operational access records, privacy-request handling, documented retention and hold reviews, contract versions and incident evidence with restricted access. It verifies relevant provider terms and subprocessor changes and re-examines material changes in risk. Merchant requests and relevant audits can examine these measures without disclosing another merchant's records or live credentials. SCHEDULE C — INITIAL RECIPIENTS AND LOCATIONS C1. Supabase Pte. Ltd., Singapore: managed PostgreSQL database, authentication and related infrastructure. The Loomind project is hosted in Frankfurt, Germany (eu-central-1). Regional database, authentication, storage and backups are distinct from global support, account and operational processing. Supabase Inc., United States, and other relevant providers are in Supabase's service-specific chain. The contractual basis is the Supabase service agreement and its Data Processing Addendum, version 1 of 1 August 2026, including applicable transfer terms: https://supabase.com/legal/customer-resources/data-processing-addendum The provider publishes its current chain through https://supabase.com/legal and location information at: https://supabase.com/legal/privacy-resources/data-residency-and-transfers-faq C2. OpenAI OpCo, LLC, United States, and/or OpenAI Ireland Limited, Ireland, as allocated by the applicable ChatGPT Sites Data Processing Addendum: hosting, maintenance and support of the published Loomind site. The account's contracting entity and the entity processing a category of hosted data may differ under that addendum. Processing and support may be international. The applicable Sites provider contract and its service-specific subprocessor list govern that chain: https://openai.com/policies/chatgpt-sites-data-processing-addendum/ The initial reference is the addendum published 9 July 2026. This authorisation does not extend to unrelated OpenAI products or development conversations. C3. AS Standard FZE operates and may access the service from the UAE. Provider will make the applicable provider identity, processing route and current service-specific downstream list available to the Merchant and record them in a Transfer Record where needed. Merely listing a supplier does not authorise a restricted transfer without clause 6, or mean that every listed downstream supplier receives every data category. No assumption of an EEA-only service or UAE adequacy is made. SCHEDULE D — INTERNATIONAL-TRANSFER INSTRUMENTS D1. Transfer Record and entry into force. Before relying on this schedule for a restricted transfer, the parties will agree a durable Transfer Record identifying: the Merchant and Provider; each role and any underlying controller; the Merchant's establishment, contact and applicable representative; the covered flows, legal regime, destinations and recipients; the selected instrument/module; the competent authority; any additions to Schedules A-C; the assessment reference and necessary supplementary safeguards; and the activation date. The record must be signed or expressly accepted by both parties' authorised representatives and linked to this agreement. Provider's authorised signatory is the person identified in its actual activation record; no signature or assessment is inferred merely from publication. D2. EU instrument. For an EEA-restricted transfer for which Commission Implementing Decision (EU) 2021/914 is an available safeguard, the applicable standard contractual clauses in the Annex to that Decision of 4 June 2021 (SCCs) are incorporated, unchanged except for the permitted selections and appendix information below, into the parties' contract upon the D1 activation. The controlling text is: https://eur-lex.europa.eu/eli/dec_impl/2021/914/oj The parties expressly agree to be bound by it and grant its enforceable third-party-beneficiary rights. Provider will supply and preserve an executed copy comprising the applicable unchanged clauses, these selections, the completed appendices and the parties' actual execution records; a bare web link is not that executed copy. The parties will not represent this Decision as available where its scope does not cover their actual transfer. D3. EU selections. Module Two applies where the Merchant is controller and Provider processor. Module Three applies only where the approved Transfer Record establishes the Merchant as processor and Provider as subprocessor for an identified controller. Only the relevant module and common clauses form the executed instrument. Clause 7 (docking) is included; a new party joins only by the required completed and signed accession. Clause 9(a) uses Option 2, general written authorisation, with a 30-day notice period. The optional independent dispute-resolution wording in clause 11(a) is not selected. Clause 17 uses Option 1 and Irish law. Under clause 18(b), the courts of Ireland are selected. Data-subject forum rights remain. D4. Annex I.A. Data exporter: the Merchant identified in the actual acceptance and Transfer Record; its registered address, named representative and verified privacy contact in those records; activity: operation of its commerce business and use of Loomind for the purposes in Schedule A; role: the selected role in D3. Data importer: AS Standard FZE at the address and contact in clause 1; activity: operation and support of Loomind as described in Schedule A; role: processor or subprocessor as selected. The Transfer Record's actual signatures and date execute Annex I.A for both parties. An exporter subject to GDPR Article 3(2) must identify its Article 27 representative where required, or the applicable exemption. D5. Annex I.B. Data subjects, categories, purpose, operations, frequency and retention are those in Schedule A, limited to the flows actually identified in the Transfer Record. No sensitive-data transfer is authorised by default. The subject matter, nature and duration of subprocessing are the relevant functions in Schedule C during the instructed service and the stated retention periods. The record identifies material additional onward flows and the safeguards applied. D6. Annex I.C. The actual authority is named in the Transfer Record using clause 13: the authority responsible for an EEA-established exporter; otherwise the authority in the Member State of its required Article 27 representative; or, where the exporter is lawfully exempt from that representative requirement, an authority in a Member State where affected data subjects are located. Choosing Irish contract law does not automatically make the Irish authority competent. D7. Annex II is Schedule B together with specific additional safeguards in the Transfer Record. Annex III is not required by the selected general-authorisation option; Schedule C supplies the initial recipient information and clause 5 governs changes. If the parties instead agree specific authorisation in a separate instrument, they must complete the required Annex III before relying on it. D8. Assessment. Before executing an SCC instrument, the parties must have the documented assessment required by clause 14 and reasonable grounds for its warranties, including the actual destination laws, practices, onward transfers and safeguards. A standard assessment may cover materially equivalent flows; it must still fit the Merchant's facts. Provider cooperates in that assessment. No statement in this agreement declares that assessment already complete or changes the unchanged SCC warranties. Clauses 14-16 govern a later inability to comply. Another valid mechanism may be recorded instead where legally available. D9. UK Addendum. For a UK-restricted transfer using the ICO Addendum, the parties incorporate the Addendum to the approved EU SCCs, version B1.0 in force 21 March 2022, on D1 activation, completed as follows: Table 1: the parties, key contacts, signatures and start date are the actual Annex I.A/Transfer Record information described in D4 and D1. Table 2: the approved EU SCCs are those identified in D2, completed with the applicable module and selections in D3; no informal revised SCC version is used. Table 3: Annex I.A is D4 and the Transfer Record; Annex I.B is D5 and Schedule A; Annex II is D7 and Schedule B; the initial general-authorised subprocessors are Schedule C. The actual completed particulars form part of the accepted record. Table 4: both the Exporter and Importer may end the Addendum under section 19 when the Approved Addendum changes. Part 2: Mandatory Clauses of the Approved Addendum, being the template Addendum B.1.0 issued by the ICO and laid before Parliament in accordance with s119A of the Data Protection Act 2018 on 2 February 2022, as it is revised under Section 18 of those Mandatory Clauses. The mandatory provisions are incorporated in full by that reference and control UK interpretation, supervision, law and courts. The approved text and any applicable mandatory revisions form part of the preserved instrument. A required UK transfer risk assessment/data protection test must be completed before transfer. An upstream controller-to-processor instrument is not assumed to authorise a different processor-to-subprocessor route. D10. Swiss adaptation. Where the Transfer Record selects the SCCs for a transfer subject to Swiss law, the parties use the applicable module in D3. For transfers governed exclusively by the Swiss Federal Act on Data Protection (FADP), references to GDPR are read as FADP, the FDPIC is the supervisory authority, and Swiss law and the courts of Switzerland replace D3's law and court selections. Where both FADP and GDPR apply, the GDPR standard, Irish law and Irish courts remain; supervision is parallel: FDPIC for FADP and the D6 authority for GDPR. In either case, references to Member State do not prevent individuals in Switzerland from enforcing their rights in their habitual-residence courts under clause 18(c). These additions do not alter the unamended EU regime for GDPR-covered transfers. D11. Other regimes and alternatives. The parties must identify and comply with any additional applicable cross-border conditions before the affected transfer, including any required local agreement or approval. This agreement does not claim that SCCs universally satisfy every jurisdiction. A later lawful adequacy route or other safeguard may replace a transfer instrument only for covered flows, with a recorded legal basis, notice, preserved historical records and the protection required by the applicable instrument and law. END OF VERSION 1.0