Abstract Migration Hub TOS

Migration Hub Terms of Service
Last updated: October 6, 2026 Effective date: October 6, 2026

These Migration Terms govern the Covered Services identified in Section 1.1, including the Migration Hub provided by Cube, Inc. to help users move supported assets from the Abstract blockchain as it winds down. They replace earlier Cube terms as described in Section 1.4. Read the migration provisions in Section 5, the deadlines and discontinuation provisions in Section 8, Section 17 on dispute resolution, and the Privacy Policy embedded below before accepting.

IMPORTANT NOTICE: PLEASE READ THESE MIGRATION TERMS CAREFULLY. THEY AFFECT YOUR LEGAL RIGHTS. SECTION 17 PROVIDES FOR BINDING INDIVIDUAL ARBITRATION AND A WAIVER OF CLASS PROCEEDINGS, SUBJECT TO STATED EXCEPTIONS AND MANDATORY LOCAL LAW. WHERE ARBITRATION APPLIES, YOU AND THE RELEVANT CUBE PARTY WAIVE A COURT TRIAL AND JURY TRIAL. YOU MAY OPT OUT OF THE NEW ARBITRATION AGREEMENT AND CLASS WAIVER WITHIN 30 DAYS AFTER FIRST ACCEPTING THIS VERSION, AS PROVIDED IN SECTION 17.8. SECTION 5.8 CONTAINS A LIMITED WAIVER FOR YOUR MIGRATION ACTIVITY THROUGH THE MIGRATION HUB. SECTION 8.6 ADDRESSES LOSSES FROM MISSED EXIT STEPS. SECTIONS 12 AND 13 CONTAIN WARRANTY DISCLAIMERS, SERVICE LIABILITY EXCLUSIONS, AND LIABILITY LIMITS. SECTION 13.5 REQUIRES CLAIMS TO BE COMMENCED WITHIN ONE YEAR WHERE PERMITTED BY LAW, SUBJECT TO ITS STATED EXCEPTIONS AND TOLLING. MANDATORY RIGHTS UNDER APPLICABLE LAW ARE PRESERVED.

Essential Terms Summary
This summary highlights key provisions. Read the full Migration Terms and the Privacy Policy embedded below, which control if there is any conflict. Nothing in this summary limits rights that cannot lawfully be limited.

The service. Cube operates the Migration Hub to assist users during the wind-down of Abstract. The Migration Hub supports only the assets and routes displayed in the Migration Hub.
Your options. You may use the Migration Hub or an available alternative exit route. The Migration Hub displays eligibility, fees, and route-specific instructions. Access to transfer assets left on Abstract through the discontinued services will end permanently on the Service Discontinuation Date for the Abstract blockchain. Section 8.5 addresses withdrawals already initiated.
Exit deadlines. Start each exit before its initiation deadline and complete every required step before its completion deadline. These may be earlier than the applicable Service Discontinuation Date. A submitted transaction is not necessarily a completed transfer.
Wallets and bridging. You authorize transactions using your wallet. Check the destination chain, compatible receiving wallet, token, amount, and fees. Transfers can be delayed, fail, or become irreversible. Recovery is not guaranteed.
Fees and liability. The Cube Parties charge no Migration Hub usage fee. Network and provider fees may apply. Section 5.8 contains a limited waiver for your Hub migration activity. Section 8.6 addresses missed exit steps. Sections 12 and 13 contain warranty disclaimers, service liability exclusions, and liability limits, subject to applicable law. Section 13.5 requires claims to be commenced within one year where permitted by law, subject to its stated exceptions and tolling.
Disputes. Section 17 applies to all users who validly accept these Migration Terms, regardless of residence or location, subject to mandatory law. It includes an arbitration opt-out and a small-claims exception. Section 18 preserves applicable mandatory consumer protections.
Privacy. The Privacy Policy explains Migration Hub data use, sharing, retention, public blockchain records, and applicable privacy rights. Accepting these terms is not blanket consent to optional data processing.
1. About These Migration Terms
1.1 Parties and roles. These Migration Hub Terms of Service, including the accompanying Privacy Policy embedded below (the "Migration Terms"), are a binding contract between you and Cube, Inc., a Delaware corporation ("Cube," "we," "us," "our"). They govern your relationship with Cube concerning the Abstract blockchain ("Abstract"), the Abstract Global Wallet and related account features, the Abstract Portal at https://abs.xyz, the bridge interface at https://bridge.abs.xyz, related websites, interfaces, software development kits ("SDKs"), and tools provided by Cube, participation programs and account activity records administered by Cube (including XP, points, streaks, and badges), the Migration Hub, and related information, support, operational communications, recordkeeping, migration, wind-down, or discontinuation (the "Covered Services"). Cube operates the Migration Hub at the official address identified in Section 21. Certain protocol upgrade and security functions are exercised through the Abstract Protocol Security Council, subject to the applicable governance arrangements and technical requirements. The Abstract Foundation, a Cayman Islands foundation company (the "Foundation"), and the Security Council Participants defined in Section 1.2 are separate from Cube and are not parties to this contract. Cube is responsible for its own obligations under these Migration Terms. Identifying an entity or person as a Cube Party does not make it responsible for another party's obligations, establish an agency relationship, or give Cube control over its powers. Implementation of the wind-down remains subject to the applicable governance arrangements and dependencies on technology providers. Section 1.4 governs replacement of prior agreements, including the limits on replacing another entity's agreements.

1.2 Protected parties. "Cube Parties" means Cube; the Foundation; the current and former members of the Abstract Protocol Security Council and the current and former trustees, enforcers, authorized representatives, and multisignature signatories under its trust and related governance arrangements (the "Security Council Participants"); their respective current and former affiliates, directors, officers, employees, contractors, and agents; and their respective successors and permitted assigns. Each is covered only in connection with its relevant role in the Covered Services, including their development, marketing, administration, governance, security, operation, participation programs, migration, and wind-down. Security Council Participants are covered individually and collectively as the Security Council, in their relevant personal or representative capacities, including claims based on their Council, trustee, enforcer, or signing functions. To the extent permitted by applicable law, these protections also apply where a claim seeks recourse to the property of a relevant trust on the basis of a covered participant’s liability. An independent technology provider is also covered to the extent it performs or performed services on behalf of Cube or the Foundation in a relevant role. These protections do not extend to a provider's independent services or obligations outside its covered role merely because it is a Security Council Participant or its technology interacts with Abstract.

1.3 Scope and acceptance. You accept these Migration Terms, including the limited migration waiver in Section 5.8, the provisions concerning missed exit steps in Section 8.6, and the arbitration and class-action waiver in Section 17, and acknowledge the embedded Privacy Policy by selecting the single, initially unchecked agreement checkbox and confirming acceptance through the process made available on the existing abs.xyz Portal or the Migration Hub. That process identifies and clearly links these Migration Hub Terms of Service. Acceptance of the separate Abstract Portal Terms of Service does not itself accept this agreement. Acceptance does not require a migration transaction. Once validly accepted, these Migration Terms govern the Covered Services within their stated scope; Section 5.8 applies only to your actual or attempted use of the Migration Hub's migration functions after acceptance. Viewing public information, holding assets, connecting a wallet, or signing a transaction does not by itself accept these Migration Terms. Public wind-down information remains available without acceptance. In exchange for your acceptance and commitments under these Migration Terms, Cube grants the license in Section 11 and undertakes its express obligations, including the recordkeeping commitment in Section 7.3, the information and support commitment in Section 8.4, and its reciprocal dispute-resolution commitments. If you act for an entity, you represent that you have authority to bind it; "you" then refers to that entity.

1.4 Replacement of prior terms and policies. Upon your affirmative acceptance, these Migration Terms supersede and replace, to the fullest extent permitted by applicable law, prior terms of service, user agreements, wallet terms, participation and rewards terms, policies, and other agreements or understandings between you and Cube concerning your relationship with Cube in connection with the Covered Services after acceptance, including their wind-down or discontinuation. Subject to Section 17.8, this replacement applies notwithstanding a prior provision stating that it survives termination. These Migration Terms become the sole governing agreement between you and Cube within that scope after acceptance. Later acceptance or use of an earlier or separate Cube service agreement does not reinstate it within that scope unless a valid amendment expressly provides otherwise under Section 15.2. Supersession does not release a claim based on conduct before acceptance, extinguish an accrued obligation, revive a time-barred claim, or waive an available defense. Claims based on earlier conduct remain subject to applicable law and the substantive terms, if any, governing that conduct, whether the claims accrue before or after acceptance. Section 17 governs dispute procedure, subject to the preservation of previously applicable procedures under Section 17.8, including their existing temporal limits and effective opt-outs. A prior provision remains relevant only to determine an earlier claim or accrued matter, or as mandatory law requires; it does not continue as a separate agreement governing your subsequent relationship with Cube within that scope.

The embedded Privacy Policy replaces earlier Cube privacy policies and notices for processing within its scope from its stated effective date, subject to applicable notice and consent requirements. It governs subsequent processing, including processing of previously collected information to the extent lawful. Replacement does not itself supply consent for a new use or disclosure, revoke an existing privacy choice, or eliminate a binding privacy commitment or restriction that applicable law requires us to honor. These Migration Terms do not replace an agreement with an independent third party or another entity unless that entity joins in, or validly authorizes, its replacement. Replacement does not extend service availability beyond the periods published under Section 8. The XP recordkeeping commitment in Section 7.3 continues any corresponding commitment that arose upon your earlier valid acceptance of the Abstract Portal Terms of Service; replacement does not cancel it, restart its period, or create a duplicate benefit.

2. Operational Information
2.1 Operational information. The initial mandatory exit guidelines are identified in Section 8.2. Operational notices and route instructions about the wind-down, including initiation and completion deadlines, supported assets and routes, network and provider dependencies, service availability, guidance on pending and failed transactions, official links, and support arrangements, are published primarily through the official social media accounts and other designated communication channels identified in Section 21 (the "Official Channels"). Information may also appear on the Migration Hub, but not every update will be reproduced there or on every Official Channel. Monitor the Official Channels while planning and completing your exit. Operational information may be updated as the wind-down proceeds; Sections 8 and 15 govern changes. Published deadlines and supported route procedures supply the operational details for Sections 5 and 8 and are subject to their conditions and change procedures. These Migration Terms control any conflict concerning contractual rights or obligations; an operational update does not amend those rights or obligations outside Section 15. Before authorizing a transaction, also review the route and transaction details shown in the Migration Hub. We will make each effective version of these Migration Terms available for download and retain copies of material operational notices and route disclosures under Section 16.

2.2 Changes. Changes to dates and service availability are subject to Section 8. Other material changes to contractual rights require notice and acceptance under Section 15.

3. Available Choices
You decide whether and how to move your assets. You may use the Migration Hub, use an alternative route available for your wallet and assets, or leave assets on Abstract. Leaving assets on Abstract carries the access risks in Section 8. Availability, cost, eligibility, and completion steps differ by route. Do not assume that a route supports every asset, wallet, or location. The bridge interface at https://bridge.abs.xyz is separate from the Migration Hub and may have different supported routes, fees, and availability. Use of that interface does not itself accept these Migration Terms. The Abstract Portal Terms of Service apply to that interface to the extent validly agreed, unless replaced by your valid acceptance of these Migration Terms under Section 1.4. Independent providers' terms continue to govern their separate services.

We do not impose a separate charge or forfeiture merely because you decline the Migration Terms. Declining does not extend a deadline or guarantee another route's availability. Independent alternative routes described through the Official Channels do not require acceptance of these Migration Terms, although separate wallet or provider terms may apply. No Cube Party obtains ownership of your assets because you decline to migrate or miss a deadline. Acceptance alone does not trigger the migration waiver in Section 5.8. If you use the Migration Hub and later choose another route, that waiver remains applicable only to your earlier Hub migration activity within its stated scope. Section 8.6 applies to accepting users whether they use the Migration Hub, use another route, or do not migrate. We will not withhold assets or an exit process that we are legally obliged to provide solely to obtain acceptance of a liability waiver.

4. Eligibility and Compliance
4.1 Eligibility and authority. If applicable law requires a parent or legal guardian to accept these Migration Terms on your behalf, that person must do so with the authority required by law before you use a feature requiring acceptance. Acceptance on another person's behalf is effective only to the extent permitted by applicable law. You must own the assets you instruct the Migration Hub to move or have lawful authority to act for their owner. Controlling a wallet does not authorize you to dispose of another person's assets or waive that person's rights. A waiver on behalf of a minor or another person is effective only with the legal authority and any approval required by applicable law; parental or guardian status alone does not establish that authority.

4.2 Legal restrictions. You may use the Covered Services only where lawful. You represent that your use and the requested transaction do not violate sanctions, export controls, or other laws applicable to you, the relevant Cube Parties, or the relevant provider. You must not use the Covered Services for a prohibited person or entity, including an entity blocked by applicable ownership or control rules, or to evade a legally applicable restriction. Additional provider or territorial restrictions are identified on the Migration Hub before you select a route.

4.3 Screening and review. The relevant Cube Parties and providers may screen addresses and transactions, request information reasonably necessary for legal compliance or fraud prevention, and restrict or decline a transaction where reasonably required. Restrictions on the interface are distinct from control of assets or a legal requirement to block property. Treatment of any blocked property or rejected transaction is governed by applicable law. Contact Cube at the legal notices and compliance review email in Section 21 if you believe a restriction is incorrect. Review does not guarantee approval or suspend a deadline; Section 8 addresses service interruptions.

5. Migration and Third Party Services
5.1 Supported routes and assets. The Migration Hub supports only the assets, token contract addresses, origin and destination chains, and routes displayed as supported on the Migration Hub before authorization. Tokens with the same name or symbol may be different assets. A route may deliver a different representation of an asset or include a conversion, as disclosed before authorization. Support for a token does not constitute an endorsement of its issuer, value, or redeemability. The assets, balances, and positions displayed in the Migration Hub are not necessarily a complete inventory of your holdings across accounts, wallets, or applications. Review your other holdings and positions before the applicable exit deadlines; an asset’s absence from the Migration Hub does not establish that you have no balance or that no action is needed.

5.2 Assets requiring other action. NFTs, unsupported tokens, staked or locked assets, liquidity positions, collateral, escrow, and assets held through an application may require action outside the Migration Hub and may be subject to third-party restrictions. Migration options for these assets depend on applicable network, issuer, and provider support. The Migration Hub does not automatically close positions or discharge liabilities. Review the asset-specific options and limitations published through the Official Channels and any route disclosures shown before authorization, and follow the instructions of the relevant application or issuer before the applicable deadlines.

5.3 Your authorization. You choose the route and destination and authorize the approvals, signatures, and transactions shown to you. Assets do not move merely because you connect a wallet or accept these Migration Terms. A migration applies only to the assets and amounts covered by your authorized transaction. It does not set up automatic forwarding or migrate later receipts. Stop directing deposits, exchange withdrawals, recurring payments, and other transfers to Abstract in time to complete any required exit steps before the applicable deadlines. Approvals may grant a smart contract permission to spend specified assets; review their scope. Subject to the disclosed route mechanics, providers may relay or execute the transaction you authorize. The Cube Parties do not exercise investment discretion over your assets.

5.4 Providers. The Covered Services depend on protocol developers, sequencers, validators, authentication and wallet providers, bridges, swap and liquidity providers, networks, hosting, and other infrastructure and technology providers. The Migration Hub identifies the providers and their separate terms relevant to your route before authorization. Cube supplies the interface; independent providers may supply or execute other parts of the transaction. No Cube Party guarantees an independent provider's continued availability, liquidity, solvency, security, performance, or ability to complete, reverse, refund, or recover a transaction. Selecting, integrating, identifying, or making a provider or route available does not itself make a Cube Party its guarantor or assume that provider's independent obligations. Route availability does not endorse an asset or promise the best available price.

Subject to Sections 13.3 and 18.2, the Cube Parties are not liable to the extent a loss is caused by an independent provider's acts, omissions, outages, restrictions, withdrawal of service, or failure to perform its separate obligations. This provider allocation does not itself excuse a Cube Party's breach of its own express obligations or a duty that cannot lawfully be excluded. Any resulting claim remains subject to the independently applicable waiver in Section 5.8, exclusions in Section 12, and limitations in Section 13, within their respective scopes. Providers may impose their own restrictions and procedures; their terms do not amend your agreement with Cube. A provider failure is not automatically an event excusing a Cube Party's performance; Section 20.2 governs qualifying events outside reasonable control. Section 8.4 governs Cube's response to interrupted exits.

5.5 Quotes and fees. The Cube Parties charge no Migration Hub usage fee. This fee treatment applies to the Migration Hub; separate interfaces may have different disclosed fees. Network and provider charges are distinct from a Migration Hub usage fee. Network, bridge, liquidity, conversion, and other provider charges may apply. Before authorization, the interface will display the estimated fees, expected destination asset and amount, and any applicable minimum received, slippage tolerance, or quote expiry. Estimates may change before execution, and a quote may expire or be replaced before you authorize a transaction. No quoted conversion or displayed balance guarantees continued liquidity, redemption, market value, or execution outside the parameters you authorize. Transactions execute under the parameters you authorize, which may permit a range of outcomes. Fees may be incurred on failed transactions and may not be refundable. Do not proceed if you do not understand the displayed parameters.

5.6 Destination and finality. Verify the destination chain, receiving address, receiving wallet's compatibility, token, amount, and approval details. An Abstract smart-contract wallet address may not be usable or controlled by you on another chain. Do not reuse that address as a destination unless the route expressly supports it and you have confirmed control. A transaction may become irreversible after submission or finalization. The Cube Parties cannot guarantee reversal or recovery, and receipt by an unintended address or on an unsupported chain may result in permanent loss.

5.7 Completion and failed transactions. Source-chain confirmation may not complete a cross-chain transfer. Routes may require additional confirmations, waiting periods, destination claims, or fees. Check the route's status and completion instructions. Do not retry a pending or uncertain transaction until you have checked its status through the official tools or support channel. A retry may create another transaction and additional fees. Instructions published through the Official Channels explain the treatment of pending, failed, refundable, and claimable transfers for each supported route. Submission before a deadline does not guarantee completion; Section 8.4 describes Cube's response to interrupted exits.

5.8 Migration-related claims. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, BY USING OR ATTEMPTING TO USE THE MIGRATION HUB'S MIGRATION FUNCTIONS AFTER ACCEPTING THESE MIGRATION TERMS, YOU WAIVE CLAIMS AGAINST THE CUBE PARTIES ARISING DIRECTLY FROM THEIR PROVISION OF THOSE FUNCTIONS OR DIRECTLY RELATED MIGRATION INSTRUCTIONS AND SUPPORT, INCLUDING LOSS, DELAY, ERROR, OR FAILURE CAUSED BY THEIR OWN ORDINARY NEGLIGENCE. This waiver applies only to each Cube Party's relevant role in your migration activity through the Migration Hub, including transaction preparation, authorization, routing, processing, and completion. Successful completion is not required. Merely accepting these Migration Terms, viewing information or balances, or connecting a wallet does not constitute actual or attempted use of a migration function for this waiver. The waiver does not release claims based on conduct before acceptance, participation or rewards programs, general governance or the decision to discontinue Abstract, activities through a route used independently of the Migration Hub, or assets you do not attempt to migrate through the Migration Hub. Section 8.6 separately addresses missed exit steps.

This waiver does not cover fraud, fraudulent misrepresentation, gross negligence, willful misconduct, breach of an express obligation under these Migration Terms, or a claim, liability, or remedy that applicable law does not permit to be waived. It does not transfer ownership of your assets. A claim outside this waiver remains subject to other independently applicable disclaimers, liability limits, and dispute provisions only to the extent lawful; an exception to this waiver does not itself create an exception to Section 13.

6. Wallet Access and Security
6.1 Wallet functions. The Migration Hub is designed to let you authorize transactions from your wallet without depositing assets into an account maintained by Cube. Assets may interact with third-party smart contracts or liquidity arrangements as part of the route you select. Wallet authentication, signing, recovery, and transaction processing depend on the wallet architecture and relevant providers. Operational notices published through the Official Channels describe material changes to those dependencies during the wind-down, subject to Section 8. Non-custodial design does not mean that the interface, network, or an issuer cannot restrict access or that every asset is recoverable.

6.2 Your security responsibilities. Keep your authentication credentials and signing devices secure, review delegated permissions, and use the supported recovery and export processes before they cease to be available. Support personnel acting for the Cube Parties will not ask you to disclose a seed phrase, private key, or recovery secret. Use the official Migration Hub address identified in Section 21 and verified service links published through the Official Channels. Notify support promptly of suspected compromise.

6.3 Relationship. These Migration Terms and the provision of the Covered Services do not create an investment-advisory, brokerage, fiduciary, agency, partnership, joint-venture, or trust relationship between you and a Cube Party. To the fullest extent permitted by applicable law, no Cube Party assumes or owes fiduciary duties to you in providing the Covered Services, and any such duties that might otherwise be implied are disclaimed and excluded. This provision does not exclude a duty that cannot lawfully be excluded or limited, or an express undertaking in these Migration Terms.

7. Participation and Rewards
7.1 Scope of migration. The Migration Hub provides migration tools and related support within the scope and availability periods described in these Migration Terms. Using it does not enroll you in a new participation or rewards program or create an entitlement to a reward for migrating assets.

7.2 Participation and rewards. The migration services do not include tokens, airdrops, distributions, profit shares, rewards, or redemption of XP, points, streaks, or badges. Any program operated by another platform is subject to that platform's terms. Section 1.4 governs the treatment of earlier agreements and claims. Section 7.3 describes Cube's limited XP recordkeeping commitment.

7.3 XP record retention. On your valid acceptance of these Migration Terms, Cube commits to retain the existing XP information associated with your account through the existing recordkeeping process, including an offchain record of that information and its association with your account until six calendar months after the Service Discontinuation Date for the Abstract blockchain. You become entitled to this commitment when you validly accept, whether or not you initiate or complete a migration, use the Migration Hub or another route, or leave assets on Abstract. Cube will maintain the retained record in a reasonably retrievable form. Preserving this record allows your past participation to remain documented and may be useful if an independent project chooses to recognize that participation under its own program. Any sharing or verification would be subject to applicable law, the Privacy Policy, and appropriate arrangements. No Cube Party promises that any third party will receive access to the record, offer a program, or grant eligibility, rewards, or other benefits.

The commitment concerns record retention only; it does not require continued display of XP, access through a portal or other user interface, or continued blockchain or migration operations, and does not create a right to a token, airdrop, reward, or redemption of XP. Cube may fulfill this commitment through a recordkeeping provider acting on Cube's behalf, without reducing the commitment or relieving Cube of its obligations. Closure of the chain, termination of access, or replacement of these Migration Terms does not shorten the retention period. Cube may delete the record earlier only to the extent required by applicable law, a valid deletion request that Cube is required to honor, or a binding privacy commitment concerning previously collected information. Retention after the stated period, if any, is governed by the Privacy Policy and applicable law. If you previously became entitled to this commitment under the Abstract Portal Terms of Service, this Section carries forward that same commitment and period; repeated acceptance does not restart the period or create a duplicate benefit.

8. Deadlines and Service Closure
8.1 Discontinuation dates and exit deadlines. The "Service Discontinuation Date" for a Covered Service is the date on which that service is permanently discontinued as part of the wind-down. For the Abstract blockchain, it is the date on which normal transaction processing permanently ends. A temporary interruption is not a Service Discontinuation Date. Different services may have different Service Discontinuation Dates; the wind-down does not require a particular sequence or intermediate operating phase. Restrictions on deposits or new activity, each route's initiation deadline, and any completion or claim deadline may precede the relevant Service Discontinuation Date. Dates and times are announced through the Official Channels, with the applicable time zone identified, subject to this Section. Do not treat a Service Discontinuation Date as the deadline for every required exit step.

8.2 Mandatory exit guidelines and updates. The Migration Hub, these Migration Terms, and the wind-down announcements published through the Official Channels on October 6, 2026 together set out the initial mandatory exit guidelines, including applicable deadlines, supported routes, and required exit steps. Cube may update deadlines, exit windows, supported routes, and required steps, subject to applicable law. Any extension of the Service Discontinuation Date for the Abstract blockchain is subject to the agreement of the relevant infrastructure providers. Operational updates may be published through the Official Channels and may also appear on the Migration Hub; not every update will appear in every location. Cube will provide any notice, including direct notice, required by applicable law. Keep your contact details current and monitor the Official Channels while your exit is pending. Operational updates do not independently amend these Migration Terms; changes to these Migration Terms remain subject to Section 15.

8.3 Urgent restrictions. A security incident, binding legal requirement, or critical failure or withdrawal of necessary third-party infrastructure may require an earlier restriction or interruption. We will limit such action to what is reasonably necessary. Notice is governed by Section 8.2; information about an incident may be subject to legal and security constraints. Any change to contractual liability or dispute provisions remains subject to Section 15.

8.4 Wind-down information and interrupted exits. During the support availability periods published through the Official Channels, Cube will use commercially reasonable efforts to provide available information about supported routes, required exit steps, and transaction status through the support contact in Section 21 and to coordinate with relevant providers concerning reported migration problems. This commitment is available to accepting users whether or not they initiate or complete a migration. If a Migration Hub interruption materially prevents exits during a published window, Cube will assess a practicable extension or alternative supported process with the relevant providers and, where necessary, Security Council Participants. Any extension, recovery, refund, or completion process depends on technical feasibility and applicable law; none is guaranteed unless expressly stated. This Section does not require a Cube Party to process an unlawful transaction, continue unsafe operation, guarantee a provider's response or performance, or fund recovery or reimbursement. These Migration Terms do not themselves oblige any provider or Security Council Participant to provide an extension or alternative process.

8.5 Service discontinuation. Normal transaction processing on Abstract ends on the Service Discontinuation Date for the Abstract blockchain. Migration Hub functions and other Covered Services may end on their respective Service Discontinuation Dates, as announced through the Official Channels. WHEN NORMAL TRANSACTION PROCESSING ENDS, ACCESS TO TRANSFER ASSETS REMAINING ON ABSTRACT THROUGH THE DISCONTINUED SERVICES WILL END PERMANENTLY. COMPLETE THE REQUIRED EXIT STEPS BEFORE THE APPLICABLE DEADLINES. A withdrawal initiated before a deadline may still require destination-chain steps under its route’s terms. Any supported completion process continuing after chain discontinuation is subject to its disclosed terms and deadline; its availability does not provide a means to initiate a new withdrawal of assets left on Abstract. No post-discontinuation recovery process is promised. A balance remaining visible in an explorer does not establish that the asset can still be transferred or recovered.

8.6 Discontinuation and residual assets. You are responsible for identifying your assets and completing all required available exit steps before the applicable deadlines communicated in accordance with these Migration Terms and applicable law. SUBJECT TO SECTIONS 13.3 AND 18.2 AND THE EXPRESS OBLIGATIONS IN THESE MIGRATION TERMS, THE CUBE PARTIES ARE NOT LIABLE FOR LOSSES ATTRIBUTABLE TO YOUR FAILURE TO COMPLETE AVAILABLE REQUIRED EXIT STEPS BY THOSE DEADLINES, INCLUDING RESULTING LOSS OF ACCESS FOLLOWING DISCONTINUATION. This includes overlooking assets or wallets, failing to complete an available withdrawal or destination-chain claim step, or directing additional assets to Abstract after the applicable deadline. It applies whether you use the Migration Hub, use another route, or do not migrate.

A provider interruption, unavailable route, locked position, or other inability to complete an exit is not by itself treated as your failure to act; Sections 5.2, 5.4, 8.4, 12, 13, and 20.2 address those circumstances within their respective scopes. No exclusion in this Section excuses a Cube Party's breach of an express obligation or overrides required notices or nonwaivable rights. Any claim not excluded remains subject to the other independently applicable limitations in these Migration Terms to the extent lawful.

Discontinuation carried out in accordance with these Migration Terms does not itself entitle you to compensation, reimbursement, replacement services, or rewards. Unless expressly undertaken or required by law, no Cube Party must recover, replace, or reimburse unmigrated assets, maintain infrastructure indefinitely, create a recovery mechanism, or redeem third-party assets. Do not rely on a future recovery option. Discontinuation does not itself transfer title to a Cube Party, authorize retention or disposal of your assets, determine an asset's legal value, or extinguish independent rights against an issuer or other person.

8.7 Records and support. Save any transaction and cost-basis information you need using available tools before the applicable availability deadlines published through the Official Channels. Those channels identify the availability periods for any supported explorer, export tools, wallet access dependencies, and migration support. Access to a public record or third-party service may end independently. A Cube Party's retention of records for legal purposes does not itself promise continuing access through a user interface.

9. Risks and Information
9.1 Technology and asset risks. Using the Migration Hub involves risks including software defects, exploits, compromised credentials, incorrect inputs, network congestion, transaction ordering, outages, forks, bridge or liquidity failures, token restrictions, depegging, and regulatory changes. Transfers can take longer than expected or fail. Network and provider dependencies may affect whether you can complete an exit. Review the route disclosures and allow time for each required step.

9.2 Decisions and advice. You make your own decisions about whether, when, and how to hold, transfer, convert, or otherwise deal with assets. Information, tools, quotes, and communications provided by a Cube Party through or in connection with the Covered Services, the Official Channels, or support are for general information and to explain available operations. They are not investment, financial, legal, tax, accounting, or other professional advice, or a recommendation concerning the suitability, purchase, sale, holding, or conversion of an asset. You do not rely on a Cube Party as your adviser and are responsible for assessing your circumstances and obtaining independent professional advice as appropriate. Transfers and conversions may have tax consequences. No Cube Party promises a particular asset value, exchange rate, tax treatment, or market outcome. This Section does not limit express obligations under these Migration Terms, responsibility for operational information as provided in these Migration Terms, or a duty that cannot lawfully be excluded, and does not prevent you from following official operational instructions.

9.3 Effect of acknowledgment. These risk disclosures describe potential outcomes and allocate responsibility as expressly stated in these Migration Terms. Acknowledgment of a risk does not itself release a claim. Section 5.8 states the limited migration waiver; Section 8.6 addresses missed exit steps; and Sections 12 and 13 provide separate disclaimers, service liability exclusions, and liability limits. Express obligations remain enforceable, subject to independently applicable lawful limitations, and nonwaivable rights remain preserved.

10. Acceptable Use and Access Restrictions
You must not use the Covered Services to violate applicable law, misappropriate assets, evade sanctions or screening, impersonate another person, exploit a vulnerability, disrupt the service, or collect nonpublic personal data without authorization. You must not bypass access controls or use automated requests in a manner that materially impairs the service. This does not prohibit ordinary access to public blockchain data, lawful criticism, or good-faith reporting through an authorized security channel.

The relevant Cube Parties may restrict access to the services and interfaces they provide where reasonably necessary to address a material violation, security risk, fraud, or legal requirement. Where practicable and lawful, the Cube Party imposing a restriction will explain it and provide a review channel. An interface restriction does not itself transfer or forfeit your assets. Effects on pending transfers or published exit windows are addressed under Section 8. The relevant Cube Party may not be able to give advance notice where doing so would compromise security or compliance.

11. Intellectual Property
The Cube Parties and their respective licensors retain their rights in the Covered Services' software, design, branding, and content. Subject to these Migration Terms and to the extent Cube is authorized to do so, Cube grants you a limited, non-exclusive, non-transferable license to use the Covered Services for their authorized functions during their respective availability periods. Applicable open-source licenses govern open-source components. Restrictions and termination of this license are subject to Sections 8 and 10.

You retain your rights in your assets and information. You grant the relevant Cube Parties and providers only the permissions necessary to process information you submit, display requested records, and carry out authorized operations through the Covered Services, subject to applicable privacy requirements. This license does not transfer asset ownership or authorize unrelated commercial use of your personal information.

12. Warranty Disclaimers and Service Liability Exclusions
12.1 Warranty disclaimers. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, AND EXCEPT FOR EXPRESS COMMITMENTS IN THESE MIGRATION TERMS, THE COVERED SERVICES ARE PROVIDED "AS IS" AND "AS AVAILABLE." THE CUBE PARTIES DISCLAIM ALL WARRANTIES, WHETHER EXPRESS, IMPLIED, OR STATUTORY, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, AND WARRANTIES ARISING FROM A COURSE OF DEALING, COURSE OF PERFORMANCE, OR USAGE OF TRADE. THEY DO NOT WARRANT UNINTERRUPTED, ERROR-FREE, OR SECURE OPERATION; THE ACCURACY, COMPLETENESS, RELIABILITY, OR TIMELINESS OF INFORMATION; CORRECTION OF EVERY DEFECT; FREEDOM FROM MALICIOUS CODE; OR SUCCESSFUL OR TIMELY COMPLETION OF A TRANSACTION. Information or communications from a Cube Party do not create an additional warranty or guarantee unless expressly agreed under these Migration Terms. Nothing in this Section excludes an express obligation under these Migration Terms or a statutory guarantee, remedy, or warranty that cannot lawfully be excluded. Sections 13.3 and 18.2 govern mandatory exceptions and consumer protections.

12.2 Security. SUBJECT TO SECTION 12.6, SECTIONS 13.3 AND 18.2, AND EXCEPT FOR BREACH OF AN EXPRESS OBLIGATION UNDER THESE MIGRATION TERMS, NO CUBE PARTY IS LIABLE FOR LOSS ARISING OUT OF A SECURITY BREACH, UNAUTHORIZED ACCESS OR ACTIVITY, CYBERATTACK, PHISHING, MALICIOUS CODE, COMPROMISED DEVICE OR CREDENTIAL, SMART-CONTRACT VULNERABILITY, OR LOSS, CORRUPTION, OR UNAUTHORIZED DISCLOSURE OF DATA IN CONNECTION WITH THE SERVICES IDENTIFIED IN SECTION 12.6. THIS EXCLUSION INCLUDES LOSS CAUSED IN WHOLE OR IN PART BY A CUBE PARTY'S OWN ORDINARY NEGLIGENCE, TO THE FULLEST EXTENT PERMITTED BY APPLICABLE LAW. No Cube Party guarantees the prevention of every security incident or recovery of an affected asset. Section 6.2 addresses your security responsibilities.

12.3 Wallets and transactions. SUBJECT TO SECTION 12.6, SECTIONS 13.3 AND 18.2, AND EXCEPT FOR BREACH OF AN EXPRESS OBLIGATION UNDER THESE MIGRATION TERMS, NO CUBE PARTY IS LIABLE FOR LOSS ARISING OUT OF YOUR USE OF A BLOCKCHAIN NETWORK, DIGITAL ASSET WALLET, OR OTHER ELECTRONIC WALLET IN CONNECTION WITH THE SERVICES IDENTIFIED IN SECTION 12.6, INCLUDING INCORRECT TRANSACTION INSTRUCTIONS, AN INCOMPATIBLE OR UNCONTROLLED RECEIVING ADDRESS, LOST OR COMPROMISED CREDENTIALS OR SIGNING DEVICES, CORRUPTED WALLET FILES, SERVER FAILURE OR DATA LOSS, OR A DELAYED, FAILED, DUPLICATED, MISDIRECTED, OR IRREVERSIBLE TRANSACTION. THIS EXCLUSION INCLUDES LOSS CAUSED IN WHOLE OR IN PART BY A CUBE PARTY'S OWN ORDINARY NEGLIGENCE, TO THE FULLEST EXTENT PERMITTED BY APPLICABLE LAW. Review the chain, token, amount, receiving address, approvals, and required completion steps before authorizing a transaction.

12.4 Networks and providers. SUBJECT TO SECTION 12.6, SECTIONS 13.3 AND 18.2, AND EXCEPT FOR BREACH OF AN EXPRESS OBLIGATION UNDER THESE MIGRATION TERMS, NO CUBE PARTY IS LIABLE FOR LOSS ARISING OUT OF THE OPERATION, FAILURE, OR FEATURES OF A BLOCKCHAIN NETWORK OR WALLET IN CONNECTION WITH THE SERVICES IDENTIFIED IN SECTION 12.6, INCLUDING CONGESTION, FORKS, CONSENSUS OR NODE FAILURES, UNAVAILABLE AUTHENTICATION, PROTOCOL OR SMART-CONTRACT VULNERABILITIES, INCORRECT OR DELAYED THIRD-PARTY DATA, CHANGES IN ASSET VALUE, OR A DEVELOPER'S OR PROVIDER'S DELAY OR FAILURE TO REPORT AN ISSUE. THIS EXCLUSION INCLUDES LOSS CAUSED IN WHOLE OR IN PART BY A CUBE PARTY'S OWN ORDINARY NEGLIGENCE, TO THE FULLEST EXTENT PERMITTED BY APPLICABLE LAW. A displayed balance, quote, transaction status, or route does not guarantee value, liquidity, completion, transferability, or recovery. Sections 5.4 and 20.2 provide additional allocations of responsibility within their respective scopes.

12.5 Access and availability. SUBJECT TO SECTION 12.6, SECTIONS 13.3 AND 18.2, AND EXCEPT FOR BREACH OF AN EXPRESS OBLIGATION UNDER THESE MIGRATION TERMS, NO CUBE PARTY IS LIABLE FOR LOSS OR HARM ARISING OUT OF YOUR INABILITY TO ACCESS OR USE THE SERVICES IDENTIFIED IN SECTION 12.6, INCLUDING INTERRUPTION, RESTRICTION, SUSPENSION, DISCONTINUATION, OR LOSS OF ACCESS TO A FEATURE, WALLET, NETWORK, OR ASSET. THIS EXCLUSION INCLUDES LOSS CAUSED IN WHOLE OR IN PART BY A CUBE PARTY'S OWN ORDINARY NEGLIGENCE, TO THE FULLEST EXTENT PERMITTED BY APPLICABLE LAW. No Cube Party is liable solely because such a service or feature is discontinued, restricted, or unavailable in accordance with these Migration Terms. No Cube Party undertakes to maintain a discontinued or unsupported feature or create an alternative service or recovery process except as expressly agreed or required by applicable law. Section 8 governs wind-down arrangements and express commitments.

12.6 Scope and independent application. Sections 12.2 through 12.5 apply to the operation, use, security, and availability of the Abstract Portal, Abstract Global Wallet, bridge interface at https://bridge.abs.xyz, and related interfaces and tools other than the Migration Hub, after your acceptance. Claims arising directly from your actual or attempted use of the Migration Hub's migration functions or directly related migration instructions and support are governed by Section 5.8; Sections 12.2 through 12.5 do not expand that waiver. Those exclusions do not release claims based on earlier conduct and do not extend to participation or rewards programs, general governance, or the decision to discontinue Abstract. Sections 8.6 and 13 apply independently within their stated scopes. A claim not excluded, including a claim for breach of an express obligation, remains subject to Section 13. Section 1.4 governs the treatment of earlier conduct.

13. Limitation of Liability
13.1 Aggregate cap. SUBJECT TO SECTION 13.3, THE TOTAL AGGREGATE LIABILITY OF ALL CUBE PARTIES TO YOU, COLLECTIVELY, FOR CLAIMS ARISING OUT OF OR RELATING TO THESE MIGRATION TERMS OR THE COVERED SERVICES GOVERNED BY THEM WILL NOT EXCEED THE GREATER OF US$100 OR THE FEES YOU PAID DIRECTLY TO THE CUBE PARTIES FOR THOSE SERVICES DURING THE 12 MONTHS BEFORE THE FIRST EVENT GIVING RISE TO THE CLAIMS. NETWORK AND THIRD-PARTY FEES ARE NOT FEES PAID TO THE CUBE PARTIES. This is one aggregate limit for those claims across transactions, accounts, wallets, Cube Parties, and legal theories, including claims concerning authorized or attempted transactions, asset losses, service interruption, data loss, and loss of access. It is not a separate limit per transaction, wallet, defendant, or legal theory. Subject to Section 13.3, this limit applies to contract, tort (including ordinary or gross negligence), and other theories to the extent permitted by applicable law.

13.2 Excluded damages. SUBJECT TO SECTION 13.3, NO CUBE PARTY WILL BE LIABLE FOR INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL, EXEMPLARY, OR PUNITIVE DAMAGES, LOST PROFITS, REVENUE, BUSINESS OPPORTUNITIES, GOODWILL, ANTICIPATED SAVINGS, OR SPECULATIVE FUTURE REWARDS, EVEN IF ADVISED OF THEIR POSSIBILITY. The cap in Section 13.1 applies to recoverable direct losses, including asset losses, where lawful.

13.3 Exceptions. Nothing in these Migration Terms prospectively excludes or limits liability for fraud, fraudulent misrepresentation, willful misconduct, death or personal injury caused by negligence where such limitation is prohibited, or any other liability or remedy that cannot lawfully be excluded or limited. The cap and damages exclusions in this Section do not apply to liability or remedies preserved by the preceding sentence. Subject to those exceptions, Sections 13.1 and 13.2 apply to claims alleging gross negligence only to the extent applicable law permits the particular limitation. No provision restricts regulatory reporting or relief that applicable law makes nonwaivable.

13.4 Application. These provisions allocate risk for the Covered Services, including the Migration Hub supplied without a Cube Party usage fee; they are not insurance, a reimbursement commitment, or an admission of liability. Where lawful, amounts recovered for the same loss, including returned assets or provider refunds, reduce compensatory damages so there is no double recovery. This does not assign claims or override a mandatory rule on damages. The cap and damages exclusions apply independently to the extent lawful, including to claims outside the migration waiver in Section 5.8, the missed-exit exclusion in Section 8.6, or the service exclusions in Section 12. An exception to any of those provisions does not itself disapply this Section. Express contractual obligations remain enforceable; independently lawful caps and damages exclusions apply to resulting claims unless expressly stated otherwise. Asset ownership does not itself create a right to uncapped damages or authorize a Cube Party to retain property belonging to you. Unenforceability of one waiver, cap, or exclusion does not displace another independently enforceable limitation. These provisions remain subject to Section 1.4 and do not retrospectively alter the substantive treatment of earlier conduct.

13.5 Time to bring claims. TO THE EXTENT PERMITTED BY APPLICABLE LAW, YOU AND EACH CUBE PARTY MUST COMMENCE ANY CLAIM ARISING OUT OF OR RELATING TO THE COVERED SERVICES OR THESE MIGRATION TERMS WITHIN ONE YEAR AFTER THE CLAIM ACCRUES; OTHERWISE, THE CLAIM IS PERMANENTLY BARRED. A claim is commenced by filing an arbitration demand or court proceeding in the appropriate forum. Applicable accrual rules, legally required tolling, and the tolling during informal resolution under Section 17.2 remain effective. The one-year period does not apply to claims for fraud, fraudulent misrepresentation, or willful misconduct; to death or personal-injury claims where such a restriction is prohibited; or wherever applicable law prohibits shortening the statutory period, including where Florida Statutes Section 95.03 applies. The applicable statutory period then governs. For other claims, including claims alleging gross negligence, the one-year period applies only where contractual shortening is lawful. This provision applies whether a claim proceeds in court or arbitration and remains effective if you opt out of Section 17. A Cube Party invoking it accepts its reciprocal application. This Section does not shorten the period applicable to a claim based on conduct before your acceptance. Section 1.4 governs the treatment of earlier conduct and accrued matters. This Section does not extend an otherwise applicable limitation or claim-presentation period, revive a barred claim, or displace a claims bar validly established under applicable law.

14. Third Party Claims
To the extent permitted by applicable law, you will indemnify and hold harmless the Cube Parties against third-party claims, resulting losses and liabilities, and reasonable, documented defense costs to the extent caused by your material breach of these Migration Terms, unlawful conduct, infringement or misappropriation of a third party's rights, negligence, or misuse of the Covered Services. You will reimburse covered defense costs as reasonably incurred, subject to proportionate allocation and adjustment to reflect the responsibility finally determined or agreed. This obligation does not apply to your own good-faith claim against a Cube Party or to the extent a claim results from a Cube Party's breach, negligence, or other misconduct.

The party seeking indemnification must promptly notify you, provide reasonable information, and use commercially reasonable efforts to mitigate costs, without limiting any duty to mitigate under applicable law. Delay in notice reduces the obligation only to the extent it materially prejudices the defense. That party may control the defense with qualified counsel; you will reasonably cooperate and may participate at your expense, subject to applicable conflict-of-interest requirements. No settlement may impose an admission, nonmonetary obligation, or payment on you without your consent, which will not be unreasonably withheld. This Section does not authorize recovery prohibited by consumer law or duplicate recovery of the same expense.

15. Changes and Termination
15.1 Services. The relevant Cube Parties may maintain, update, restrict, or discontinue features of the Covered Services that they provide in accordance with Sections 8 and 10 and the applicable operational notices. Changes affecting published exit opportunities are subject to Section 8. Feature changes or termination do not cancel the recordkeeping commitment in Section 7.3 or excuse the express obligations in Section 8.4. Ending access does not automatically cancel a submitted blockchain transaction or eliminate a provider's pending completion process.

15.2 Terms. Cube may update these Migration Terms. Cube will identify the revised version and effective date and provide conspicuous notice of material changes through the Covered Services or the Official Channels, with direct notice where required by applicable law. Material changes require affirmative acceptance before further use of the affected features and apply prospectively. They do not govern a transaction already authorized or retrospectively alter a claim based on earlier conduct without a separate valid agreement and any procedure required by law, and do not revoke an effective arbitration opt-out. A changed date, posting, continued use, or expiration of a deadline does not by itself establish acceptance of material changes. If you decline, the relevant Cube Parties may restrict the affected features they provide subject to express obligations, Section 8, and mandatory law; public wind-down information remains available. Available alternative routes and deadlines remain as described through the Official Channels, subject to Section 8. Operational updates, including a factual correction or extension of an exit deadline, do not by themselves require new contractual assent.

16. Privacy and Records
The Privacy Policy embedded below explains the personal information processed for the Covered Services, including authentication, wallet connections, transaction routing, account activity information, compliance, support, and agreement records, and describes recipients, retention, and applicable rights. It forms part of this document and is presented with these Migration Terms before information is collected. The single acceptance process in Section 1.3 includes acknowledgment of the Privacy Policy. It does not supply a specific privacy consent that applicable law requires separately. Processing requiring such consent will not occur unless the required consent is obtained.

We may retain the exact versions of these Migration Terms, operational notices and route disclosures, and the Privacy Policy presented to you; the acceptance screen and checkbox wording; acceptance timestamp; account or wallet association; relevant transaction records; and notices or opt-outs, as described in the Privacy Policy and as permitted or required by law. Contractual acceptance is separate from any transaction signature. We will retain dated document versions so that the applicable terms and disclosures can be identified. Retention for legal, compliance, or dispute purposes is distinct from public explorer or Migration Hub availability.

17. Dispute Resolution for All Users
17.1 Scope. This Section applies to all users who validly accept these Migration Terms, regardless of residence, nationality, location, or whether they use the Migration Hub, subject to Sections 17.8 and 18.2 and other mandatory law. "Dispute" means any dispute between you and a Cube Party arising out of or relating to the Covered Services, these Migration Terms, the Migration Hub, operational notices and route instructions published through the Official Channels, the wind-down of Abstract, or the formation, interpretation, performance, validity, or enforcement of these Migration Terms. A Dispute may arise in contract, tort, statute, or otherwise, and includes a dispute concerning Section 5.8 or 8.6. Claims based on conduct before your first valid acceptance of this version are "Earlier Claims," whether those claims accrue before or after acceptance. Section 17.8 preserves previously valid dispute-procedure provisions applicable to Earlier Claims; to the extent no preserved earlier provision governs, this Section applies, subject to its opt-out and mandatory law. Applying a dispute procedure does not release an existing claim or alter its substantive treatment under Section 1.4. This Section does not extend to an unrelated transaction or relationship merely because a Cube Party is involved, and applies only within the scope permitted by mandatory consumer law. A Cube Party invoking this Section accepts its reciprocal obligations for the Dispute, including its applicable payment obligations under Section 17.5.

17.2 Informal resolution. Before initiating arbitration, the claimant will send a written notice with their name, contact details, relevant account or wallet, a brief statement of the facts, and relief sought. Notices under this Section to a Cube Party must be sent to Cube at the dispute address stated in Section 21; a Cube Party will use your last available contact address. Do not include private keys or recovery secrets. The parties will try in good faith to resolve the Dispute for 30 days after receipt. Applicable limitation periods are tolled from receipt until that period ends. Either party may file sooner if necessary to preserve a nonwaivable right or seek relief allowed under Section 17.4. This procedure does not limit a small-claims filing or contact with a regulator.

17.3 Individual arbitration. Except as provided below, you and the relevant Cube Party agree to resolve a Dispute through binding individual arbitration before one neutral arbitrator administered by the American Arbitration Association ("AAA"), including through its international division, the International Centre for Dispute Resolution ("ICDR"), where designated by AAA. FOR DISPUTES REQUIRED TO BE ARBITRATED UNDER THIS SECTION, YOU AND THE RELEVANT CUBE PARTY WAIVE THE RIGHT TO A TRIAL BEFORE A JUDGE OR JURY. The Federal Arbitration Act governs the arbitration agreement to the extent applicable, subject to mandatory law. The AAA Consumer Arbitration Rules and consumer fee schedule apply to consumer disputes, including international consumer disputes. The AAA Commercial Arbitration Rules apply to domestic nonconsumer disputes; the ICDR International Arbitration Rules apply to international nonconsumer disputes. The applicable rules in effect when the demand is filed govern, subject to nonwaivable rights. Rules and forms are available at https://www.adr.org/rules-forms-and-fees/consumer/ and https://www.adr.org/rules-forms-and-fees/international/. If the administrator requires a different set of rules for an international consumer case, the consumer protections and cost allocations in this Section continue to apply. The arbitrator may award the individual relief available in court, subject to lawful contractual limitations, and will provide a reasoned written award.

On a party's request, the arbitrator may enter appropriate protective orders for trade secrets, security-sensitive information, personal information, and other confidential material disclosed in the proceeding. This does not prohibit lawful reporting or cooperation with a regulator, disclosures required by law, obtaining professional advice, or disclosure reasonably necessary to pursue or defend a claim or enforce an award, subject to applicable protective orders.

17.4 Exceptions and decision maker. Either party may bring an eligible individual claim in small-claims court. Either may seek temporary judicial relief needed to preserve the status quo pending arbitration without waiving arbitration, or seek injunctive or other equitable relief in a court with jurisdiction for infringement or misappropriation of intellectual property rights. Nothing prevents a report to or participation in a proceeding before a government agency. A court decides whether an agreement to arbitrate was formed, whether an opt-out is effective, which of conflicting agreements governs, and whether the class waiver or public-injunction provisions are enforceable. Subject to those exceptions and applicable law, the arbitrator decides the scope and enforceability of this arbitration agreement. Statutory exclusions from compelled arbitration remain applicable.

17.5 Location, language, and costs. A consumer may elect a documents-only or remote hearing where permitted by the applicable rules; any required in-person hearing will be at a reasonably convenient location in the consumer's country of habitual residence, unless the consumer agrees otherwise after the Dispute arises. The legal seat of arbitration is Miami, Miami-Dade County, Florida, United States, unless mandatory law or applicable consumer rules require otherwise or the parties agree otherwise. A hearing location does not itself change the legal seat. Nonconsumer hearings will be at the seat unless otherwise agreed. Proceedings will be in English, subject to any accommodation required by applicable law or directed by the administrator or arbitrator to ensure a fair opportunity to participate. A consumer initiating arbitration pays no more than the applicable AAA consumer filing fee, subject to waivers; the relevant Cube Party pays any additional amount necessary to avoid prohibitive costs or comply with mandatory law, and the remaining administrative fees and arbitrator compensation required of the business. A Cube Party initiating arbitration against a consumer pays all administrative fees and arbitrator compensation. A Cube Party invoking this Section accepts its applicable payment obligations. The applicable rules and law govern allocation of required business-side fees among multiple Cube Parties; the allocation does not require duplicate payment or increase the consumer's permitted share. Except as required by applicable law, Cube does not undertake another Cube Party's payment obligations solely because that person is a protected beneficiary. Nonconsumer arbitration fees and arbitrator compensation are allocated under the applicable rules and law. Other fees and any award of attorneys' fees are governed by applicable rules and law. No provision removes a nonwaivable right to recover fees or requires costs that would make this agreement unenforceable.

17.6 Class waiver and coordinated filings. SUBJECT TO SECTIONS 17.1 AND 17.8 AND TO THE FULLEST EXTENT PERMITTED BY APPLICABLE LAW, YOU AND EACH RELEVANT CUBE PARTY AGREE THAT EVERY DISPUTE WILL BE BROUGHT AND RESOLVED SOLELY ON AN INDIVIDUAL BASIS, WHETHER IN ARBITRATION OR COURT. EACH WAIVES THE RIGHT TO BRING, MAINTAIN, PARTICIPATE IN, OR SEEK RELIEF THROUGH A CLASS, COLLECTIVE, OR REPRESENTATIVE ACTION OR ARBITRATION AS A REPRESENTATIVE, CLASS MEMBER, OR OTHERWISE. No arbitrator has authority to conduct a class, collective, or representative arbitration or to determine the claims of persons who are not parties to the individual arbitration. Claims of different users may not be joined or consolidated for a determination on the merits without the express written agreement of all affected parties. Except for nonwaivable public injunctive relief preserved below, relief may be awarded only to the individual party seeking it and only to the extent necessary to resolve that party's individual claim. This waiver applies independently of whether a particular Dispute must be arbitrated, subject to an effective opt-out under Section 17.8. It does not restrict government enforcement, regulatory reporting or cooperation, or relief or participation rights that applicable law makes nonwaivable. Section 17.7 governs public injunctive relief and an unenforceable waiver. Coordinated individual demands remain subject to the applicable AAA Mass Arbitration Supplementary Rules and fee schedules. Administrative coordination does not authorize class arbitration, consolidate merits without the affected parties' written consent, or bind a claimant to another claimant's merits record or award.

17.7 Public relief and severability. If applicable law prevents arbitration of a request for public injunctive relief, that request may proceed in a competent court while arbitrable issues proceed individually. A court may stay claims only as permitted by applicable law. If any provision of this Section is unenforceable, it is severed to the extent permitted and the remainder continues. If the class waiver cannot be enforced for a particular claim or remedy, that claim or remedy will proceed in court, not class arbitration. Nothing requires dismissal of an otherwise valid claim merely because AAA is unavailable. If AAA cannot administer for reasons unrelated to a Cube Party's noncompliance, the parties may agree on another administrator or seek appointment under the Federal Arbitration Act; mandatory consumer standards must be preserved. If administration fails because a Cube Party does not comply with AAA requirements or pay required fees, you may pursue the Dispute in court as permitted by applicable rules and law.

17.8 Opt-out and earlier agreements. You may opt out of the new arbitration agreement and class waiver in this Section by emailing written notice to [email protected] within 30 days after first affirmatively accepting this version of these Migration Terms. Include your name, account email or relevant wallet address, a contact address, and a clear statement that you opt out. A timely and otherwise valid notice does not depend on an acknowledgment. Opting out does not affect Migration Hub eligibility or other terms, including Sections 5.8, 8.6, and 13.5 within their respective scopes.

Your acceptance of, or opt-out from, this Section does not replace or extinguish previously valid arbitration, class-waiver, or other dispute-procedure provisions applicable to Earlier Claims immediately before your acceptance, including provisions preserved for earlier conduct under the Abstract Portal Terms of Service. Those provisions remain effective only within their original lawful scope, including their existing temporal limits and any previously effective opt-out. This preservation does not create an agreement that was not validly formed, expand an earlier provision, or revive a provision that previously expired or was validly terminated or superseded. To the extent no preserved earlier provision governs an Earlier Claim, this Section applies, subject to a timely opt-out and mandatory law.

For claims based on conduct after acceptance, this Section replaces earlier dispute-procedure provisions within its scope, subject to prior effective opt-outs and mandatory law; opting out does not revive those superseded provisions. Section 18 governs permitted court proceedings to the extent no preserved earlier provision governs. A later amendment does not revoke an effective opt-out. Material changes require notice and affirmative acceptance under Section 15.2 and any additional procedure required by applicable law.

17.9 Time to bring claims. Section 13.5 governs the time to commence a claim, including its one-year contractual deadline where lawful, exceptions, and tolling. A timely notice under Section 17.2 tolls the applicable period as stated there; notice alone does not commence an arbitration or court proceeding.

18. Governing Law and Mandatory Rights
18.1 Law and courts. Subject to the Federal Arbitration Act and Section 18.2, Delaware law governs these Migration Terms, without applying conflict-of-law rules that would select another jurisdiction's law. Subject to Sections 17 and 18.2, disputes governed by these Migration Terms that are not arbitrated will be brought in the state courts located in Miami, Miami-Dade County, Florida, or the United States District Court for the Southern District of Florida, Miami Division, and each party consents to personal jurisdiction there. Small-claims proceedings permitted by Section 17 may be brought in a court with appropriate jurisdiction.

18.2 Mandatory consumer protections. If you use the Covered Services as a consumer, nothing in these Migration Terms deprives you of protections, guarantees, remedies, or access to courts that cannot be waived under applicable law, including mandatory protections of your habitual residence where applicable. A foreign-law or forum provision applies only to the extent lawful. If applicable law permits you to bring proceedings in your home courts notwithstanding an arbitration agreement, you may do so; if it requires proceedings against you there, the relevant Cube Party will comply. Arbitration, class waivers, liability waivers, disclaimers, limitations, indemnities, and changes to terms operate subject to those protections. Mandatory privacy rights are also preserved as described in the Privacy Policy.

19. Entire Agreement and Continuing Provisions
19.1 Entire agreement and replacement. These Migration Terms, including the embedded Privacy Policy, constitute the entire agreement between you and Cube concerning the Covered Services and supersede prior agreements and understandings as provided in Section 1.4. The Privacy Policy is the controlling privacy notice within its scope and describes our data practices and applicable rights; it does not constitute blanket consent or waive mandatory privacy remedies. Linked operational guides explain use of the service and do not expand contractual scope. Independent provider terms govern that provider's separate service and are not agreements between you and Cube. This integration provision does not itself exclude liability for fraud or fraudulent misrepresentation, or release claims based on earlier conduct.

19.2 Scope of commitments. Cube's contractual commitments for the Covered Services from your acceptance onward are those stated in these Migration Terms. Operational notices published through the Official Channels provide the operational details contemplated by these Migration Terms. General descriptions, promotional materials, forecasts, and statements of intention do not add a contractual commitment to continue a service, maintain an asset's value, or provide a reward. This Section does not itself excuse inaccurate operational information or noncompliance with a notice required by applicable law. Any resulting claim remains subject to Sections 5.8, 8.6, 12, and 13 within their respective scopes, including the exceptions in Section 13.3. Section 1.4 governs the treatment of earlier conduct.

19.3 Priority. Mandatory law controls. Subject to it, the Privacy Policy governs the privacy disclosures and processing commitments it describes. The body of these Migration Terms otherwise controls legal conflicts. An update is effective only under Sections 8 and 15 or, for privacy disclosures, the Privacy Policy's changes provision. A quote specifies the authorized transaction parameters under Section 5.5; it does not change the legal terms.

19.4 Survival. Sections 1.2 and 1.4, 5.4 and 5.8, 6.3, 7.2 and 7.3, 8.4, 8.6 and 8.7, 9.2, and 11 through 20 survive to the extent necessary to give effect to their stated scopes, including accrued payment, dispute, recordkeeping, and enforcement obligations. The Privacy Policy continues to apply to personal information retained within its scope. Survival does not expand a waiver or exclusion, extend an operational service or support period, enlarge the recordkeeping commitment in Section 7.3, or authorize retention beyond applicable law and the Privacy Policy.

20. General Provisions
20.1 Assignment. You may not transfer this contract without Cube's consent, except as required by law. Cube may assign it to an affiliate or in connection with a merger, reorganization, or transfer of the relevant business, on notice, provided the successor assumes Cube's obligations and the transfer does not reduce your mandatory rights. Assignment does not retrospectively relieve liability already incurred.

20.2 Force majeure. Subject to Sections 13.3 and 18.2, no Cube Party is liable for a delay, interruption, degradation, unavailability, or failure of performance to the extent caused by an event or circumstance beyond that party's reasonable control, whether or not foreseeable. Covered events include natural disasters, severe weather, fire, epidemic or pandemic; war, terrorism, civil unrest, strikes, or other labor disruption; governmental or regulatory action, sanctions, embargoes, court orders, or changes in law; failures or shortages of power, telecommunications, internet, cloud, hosting, or other infrastructure; cyberattacks, denial-of-service attacks, malicious code, or unauthorized third-party interference; blockchain congestion, forks, consensus failures, protocol vulnerabilities, or network attacks; and failures, interruptions, withdrawals of service, or unavailability of independent technology providers, sequencers, validators, bridges, wallets, exchanges, or other dependencies. Each listed event qualifies only to the extent beyond the affected Cube Party's reasonable control. A failure of an affiliate or contractor does not qualify merely because performance was delegated.

The affected Cube Party may suspend or restrict the affected performance, and its time for performance is extended for the duration of the event and the time reasonably needed for safe restoration, subject to Section 8 and mandatory law. It will use commercially reasonable efforts to mitigate the effects. Those efforts do not require it to compromise security, violate law, settle a labor dispute, challenge governmental action, or obtain replacement services at materially disproportionate cost. It will provide any notice required by applicable law. If continued performance becomes unlawful or cannot reasonably be restored, the affected services may be discontinued under Section 8.

This Section does not excuse an accrued payment obligation, shorten or cancel the XP record-retention commitment in Section 7.3, transfer ownership of user assets, or displace a nonwaivable right or duty. The planned wind-down, a party's own shortage of funds, or a mere decline in profitability is not itself a force-majeure event. Discontinuation of the chain or a user-facing service does not itself excuse the offchain recordkeeping commitment in Section 7.3. An otherwise qualifying event affecting implementation of the wind-down remains covered. Any change to a user action deadline remains subject to Section 8 and applicable law; an extension of a Cube Party's performance time does not itself extend a blockchain or third-party deadline.

20.3 Severability and waiver. Except as specifically provided in Section 17, an unenforceable provision is severed to the extent necessary and lawful, and the rest remains effective. A failure to enforce a provision is not a waiver. A waiver of one breach does not waive another. These provisions do not require a court to rewrite an unlawful term.

20.4 Beneficiaries. The Cube Parties are intended third-party beneficiaries of Sections 1.1 and 1.2, 4.3, 5.3, 5.4, 5.6, 5.8, 6.3, 7.2, 8.6, 8.7, 9.2, 10 through 15, 17, 18, 19.2, 20.2 through 20.4, and 20.6 only to the extent those provisions apply to their relevant conduct and capacities identified in Section 1.2. A beneficiary enforcing Section 17 accepts its reciprocal obligations, including its applicable payment obligations under Section 17.5, subject to its opt-out provisions, the preservation of Earlier Claims procedures under Section 17.8, and mandatory law. The Foundation and Security Council Participants may enforce the protections applicable to their capacities under Section 1.2 although they are not contracting parties. These rights do not make a beneficiary a contracting service provider or enlarge the user's obligations beyond these Migration Terms. Their beneficiary status does not expand Section 5.8 beyond the user's Hub migration activity, Section 8.6 beyond its stated scope, or Sections 12.2 through 12.5 beyond Section 12.6. There are no other intended third-party beneficiaries. These provisions do not impose liability on you for acts of another user.

20.5 Notices. Notices may be provided electronically to your contact address or through the Official Channels, subject to any specific delivery requirement in these Migration Terms or applicable law. Operational notices are governed by Section 8; notices of changes to these Migration Terms are governed by Section 15. Your acceptance permits electronic delivery to the extent lawful, but does not replace any separate electronic-consent procedure required by applicable law. The designated dispute and opt-out addresses must remain available for notices concerning surviving rights.

20.6 Efforts standard. Where these Migration Terms expressly require a Cube Party to use "commercially reasonable efforts," this means efforts reasonably proportionate to the stated task, assessed objectively in light of its scope and duration, the stage of the wind-down, technical feasibility, security and legal requirements, dependencies outside that party's control, and the cost and operational burden of the available measures. The standard does not require a guaranteed outcome, guaranteed independent-provider performance, materially disproportionate expenditure, or development or continued operation of services beyond an express commitment. It does not qualify an obligation that is not expressly subject to that standard or excuse a Cube Party's own breach. Required notices, the XP record-retention commitment in Section 7.3, and duties that cannot lawfully be limited remain unaffected.

21. Contact
Cube, Inc.
Migration support: https://discord.gg/abstractchain
Legal notices, disputes, and compliance review: [email protected]
Arbitration opt-outs: [email protected]
Privacy requests: [email protected]
Official Migration Hub: https://migrate.abs.xyz
Official Channels: @Abstract_Eco and @AbstractChain (on X.com). Discord available at: https://discord.gg/abstractchain. Wind-down updates are published primarily through these channels. A replacement or additional channel will be identified through an existing Official Channel; verify the source before following a migration link.

Abstract and Migration Hub Privacy Policy
Last updated and effective date: As stated at the beginning of these Migration Terms.

1. Who We Are and What This Policy Covers
This Privacy Policy explains how Cube, Inc., a Delaware corporation ("Cube," "we," "us," "our"), handles personal information in connection with the Abstract blockchain ("Abstract"), the Abstract Global Wallet and related account features, the Abstract Portal at https://abs.xyz, the bridge interface at https://bridge.abs.xyz, related websites, interfaces, software development kits ("SDKs"), and tools provided by Cube, participation programs and account activity records administered by Cube (including XP, points, streaks, and badges), the Migration Hub, and related information, support, operational communications, recordkeeping, migration, wind-down, or discontinuation (the "Covered Services"). This policy forms part of the same document as the Migration Hub Terms of Service and may be read independently. References to sections of this Privacy Policy refer to its separately numbered sections below. It replaces earlier Cube privacy policies and notices for the Covered Services from its effective date, subject to the qualifications below. Our contact information appears in Section 12 of this Privacy Policy. Where applicable data-protection law uses that term, Cube is a controller for processing whose purposes and means it determines. The Abstract Foundation is a separate Cayman Islands foundation company. Each entity's data-protection role depends on its actual processing activities; inclusion as a protected party under the Migration Terms does not determine that role.

This policy covers information collected through the Covered Services and existing information retained or used for their operation, migration, support, compliance, wind-down, and other purposes described here. It is the current controlling Cube privacy notice for that processing. Earlier notices do not continue as separate governing policies, but prior collection circumstances, binding commitments, choices, and applicable law may restrict how previously collected information can be used. We will obtain any notice, consent, or other authorization required before a changed use or disclosure. Independent wallets, bridges, networks, applications, and other entities may have their own policies for their separate processing; Cube does not replace those policies without authority. We will identify relevant providers and links before their use. Acknowledging this policy through the single acceptance process does not supply a specific privacy consent that applicable law requires separately.

2. Information We Collect and Its Sources
Account and contact information. Information you or an authorized authentication provider supply, such as an email address, account identifier, connected wallet address, authentication status, and wallet or account associations needed to use a feature. We do not need your seed phrase, private key, or recovery secret for support; do not send them to us.

Transactions and activity. Source and destination wallet addresses, transaction hashes, networks, assets and amounts, route and quote details, fees, transaction status, and relevant service usage, historical transaction activity, and account activity records, such as points, streaks, and badges where recorded for your account. Sources may include you, public blockchains, explorers, existing Abstract records lawfully available to us, and relevant providers. Public availability does not mean information is never personal information. Linking a wallet to an account or another wallet can make activity identifiable.

XP information. XP information recorded through the existing account process and associated account identifiers. Sources include existing Abstract account records and the providers supporting that process. We process this information to administer the existing account records and fulfill the recordkeeping commitment in Section 7.3 of the Migration Terms or the corresponding commitment in the Abstract Portal Terms of Service, as applicable. We retain the record in a reasonably retrievable form to preserve information about past participation. Its possible use for verification or recognition by an independent project is subject to Sections 3 and 4 below. Retention is described in Section 7 of this Privacy Policy.

Device and usage information. IP address, approximate location inferred from it, browser and device information, request times, pages or features used, errors, security events, and cookie or similar identifiers where deployed. Hosting, security, and analytics providers may collect this information for us. Section 6 of this Privacy Policy explains tracking choices.

Compliance and support information. Requests, correspondence, documents you choose to submit, investigation records, and screening results obtained from public records or compliance providers. Where needed and lawful for a particular compliance check, we may request additional identity or residency information and explain the requirement.

Agreement and preference records. Versions of notices and terms presented, acceptance wording and timestamps, account or wallet associations, consent and withdrawal records, privacy choices, opt-outs, and communications needed to demonstrate what was agreed or disclosed. We receive information directly from you, automatically through the Covered Services, and from the sources identified above. We do not require information unrelated to the stated purposes.

3. Why We Use Information
We use information to authenticate users; operate, support, secure, and wind down the functions we provide in connection with the Covered Services; show available routes and relevant balances; prepare and route authorized transactions; monitor and troubleshoot transfers; answer support requests; communicate operational deadlines and service changes; detect fraud, abuse, security incidents, and prohibited transactions; meet applicable legal obligations; administer existing account and activity records where needed for those purposes; maintain agreement and preference records; and establish, exercise, or defend legal claims. A service notice is distinct from optional promotional messaging. We may also use retained XP information to respond to an appropriately authorized verification request relating to a program independently offered by another project, subject to the conditions in Section 4 below. No such program or use is guaranteed.

Where a legal basis is required, we rely on performance of a contract or steps you request before contracting only for processing objectively necessary to provide the requested service; applicable legal obligations for processing required by law; and legitimate interests, where recognized and subject to the required balancing of rights, for proportionate security, fraud prevention, service administration, and legal-claims handling. We rely on consent where required, including for optional tracking or marketing. We will explain the relevant basis for additional processing at collection. A foreign-law obligation is not automatically a legal-obligation basis under European or UK law. We do not treat a purpose as necessary merely because it is described in the Migration Terms.

Where processing depends on consent, you may withdraw it through the relevant control or by contacting us; withdrawal does not affect prior lawful processing. Declining optional processing will not prevent access to unrelated core functions. If information is necessary to provide a requested feature or satisfy a legal requirement and you do not provide it, that feature may be unavailable; we will explain the requirement and consequences.

4. When We Disclose Information
We disclose information as reasonably necessary to hosting, security, authentication, wallet, bridge, transaction, analytics, compliance, communications, and support providers for the stated purposes; to the Foundation or relevant affiliates for their actual, disclosed administrative or other functions connected with the Covered Services; and to professional advisers and insurers for appropriate business or legal purposes. Providers acting on our behalf are subject to applicable contractual restrictions and safeguards. A provider acting as a separate controller is responsible for its own disclosed processing; that does not remove our responsibility for our own disclosures.

We may disclose information to comply with a binding legal requirement or lawful process; investigate fraud or security incidents; protect lawful rights, property, or safety; or establish, exercise, or defend claims, subject to applicable law and proportionality. We may disclose relevant information during a proposed or completed business transfer, reorganization, or wind-down subject to appropriate confidentiality and safeguards; a recipient remains subject to applicable law and any required notice or consent for changed uses. These provisions do not authorize unrestricted transfers of user information.

A recordkeeping provider may store and administer retained XP records on Cube's behalf, subject to applicable contractual restrictions and safeguards. Such custody does not by itself authorize the provider to use the records for its own program. If an independent project later proposes to recognize past participation, we may consider limited verification or disclosure of relevant XP information and associated account or wallet identifiers under separate arrangements. Before sharing, we will tell affected users who will receive what information and why, establish an applicable lawful basis, and obtain any consent required by law. An independent project using information for its own program is responsible for its separate processing and program terms. Accepting the Terms does not authorize unrestricted disclosure or replace consent that must be obtained separately.

Public blockchain disclosures are addressed separately below.

5. Public Blockchain Records
When you authorize an onchain transaction, wallet addresses, transaction details, and other submitted data may become publicly accessible, be copied by others, and persist on networks outside our control. Connecting an account to a wallet or associating wallets may reveal relationships between them. Do not put confidential or unnecessary personal information into an onchain field.

We generally cannot change or erase a confirmed record on an independently operated public blockchain or copies held by others. This technical limitation does not eliminate our duties concerning information we control, including offchain account associations, support records, and hosted data. We will assess a rights request on its facts and explain any legally permitted limitation. Ending Migration Hub or explorer access does not remove publicly replicated blockchain records.

6. Cookies, Analytics, and Marketing Choices
Cookies and similar technologies may be used for authentication, security, preferences, and service operation. Nonessential analytics or advertising technologies, if used, will be identified and enabled only with the choice or consent required by applicable law. You may use the available privacy controls for the relevant Covered Service and relevant browser controls; disabling essential storage may affect a requested feature. We will honor legally recognized opt-out preference signals where applicable.

We will seek any consent required for promotional messages and provide an effective unsubscribe mechanism. Operational notices may still be sent where lawful.

7. Retention, Wind-Down, and Security
We retain personal information only for as long as reasonably necessary for the disclosed purposes, taking account of service availability, transaction completion, support needs, applicable limitation periods, legal retention duties, and properly scoped preservation obligations. We do not retain every category indefinitely merely because a dispute is possible. Access is limited according to role, and we use reasonable technical and organizational measures appropriate to the information and risks. No system can guarantee absolute security.

Account associations and migration records are retained while needed for requested features, pending transactions, and related support, then deleted or de-identified unless a defined legal or other disclosed need remains. For a user entitled to the XP recordkeeping commitment under the Migration Terms or Abstract Portal Terms of Service, Cube retains the existing XP record and associated account identifiers offchain until six calendar months after the Service Discontinuation Date for the Abstract blockchain, subject to a valid deletion request that Cube is required to honor or earlier deletion required by applicable law or a binding privacy commitment. The same retention period applies whichever agreement was accepted first; accepting both does not restart it. Record retention does not promise continued display or user-interface access. After that period, XP information is deleted or de-identified unless a defined legal or other disclosed need requires further retention. Support and screening records are retained for resolution and applicable compliance or claims requirements. Security logs are retained for a period proportionate to investigating and preventing incidents. Terms, notice, consent, and opt-out records may be retained for the relevant enforcement or claims period, with periodic review. Public versions of documents can be retained without publishing user identities.

Discontinuation of the Migration Hub or Abstract blockchain does not automatically require deletion of every record or justify keeping every record indefinitely. Where deletion is appropriate, we delete or de-identify information, subject to lawful, limited preservation and backup cycles. Backup data awaiting deletion remains protected and restricted from ordinary use. Privacy requests remain available through Section 12 of this Privacy Policy after service closure.

8. International Processing
Cube is based in the United States, and the Foundation is organized in the Cayman Islands. Information may be processed where the relevant personnel and providers operate. Those jurisdictions may have different data-protection laws.

Where required, we will use a lawful transfer mechanism and appropriate safeguards before a restricted transfer, such as an applicable adequacy decision, approved standard contractual clauses and supplementary measures, or the appropriate UK transfer instrument. Any reliance on a consent or other exception will meet the applicable conditions. For other jurisdictions, we will comply with applicable comparable-protection, notice, consent, localization, or transfer requirements. Use the contact details in Section 12 of this Privacy Policy to request information about the safeguards applicable to your information and a copy where required, with necessary confidential information redacted.

9. Your Rights and Requests
Depending on applicable law and our processing, you may have rights to know or access personal information and obtain a copy; correct inaccurate information; request deletion; obtain portability; restrict or object to processing, including certain processing based on legitimate interests; withdraw consent; opt out of sale, sharing, targeted advertising, or certain profiling; limit qualifying uses of sensitive information; and appeal a refusal where an appeal right applies. These rights are subject to applicable conditions and exceptions. We will explain a refusal or limitation and available review or complaint options where required.

Submit a request to [email protected]. We may request information reasonably necessary to verify identity, wallet control where relevant, or an authorized agent's authority, using a method proportionate to the request. Do not send private keys or recovery secrets. We will respond within the applicable legal period and explain any permitted extension. We will not unlawfully discriminate or retaliate against you for exercising privacy rights. You may complain to the competent data-protection authority or other regulator. Where provided by law, you may appeal by contacting [email protected].

10. Children
Some users may be minors. We handle personal information relating to minors in accordance with applicable law. Where a particular collection, use, or disclosure requires verified parental consent, we will obtain that consent before the processing occurs, unless a lawful exception applies. Acceptance of the Migration Terms does not replace that consent. A parent or guardian may contact us using the details in Section 12 of this Privacy Policy about a child's information or applicable access, deletion, or consent rights. If we learn that information has been collected without consent required by law, we will take the legally required corrective action.

11. Changes to This Policy
We will date each version and provide notice of material changes through the Official Channels identified in Section 21 of the Migration Terms and through direct communications where required by law or otherwise appropriate and available before the changes take effect or as otherwise required by law. We will provide any required notice at or before collection and obtain consent where a new purpose or disclosure requires it. A posted update, continued use, or contractual acceptance does not override an earlier binding privacy commitment or supply consent that applicable law requires us to obtain separately. Dated versions of this document, including this Privacy Policy, will remain available through the same page as these Migration Terms.

12. Privacy Contact and Post-Closure Requests
Cube, Inc.
Privacy requests and questions: [email protected]
Appeals, where applicable: [email protected]
Post-closure privacy contact: [email protected]

We will maintain a functioning privacy contact for as long as we retain personal information subject to continuing obligations, and provide notice of a material contact or responsible-entity change where required. The Migration Terms' arbitration and liability provisions do not waive privacy rights or regulatory remedies that cannot lawfully be waived.