FortiSwap — AML & Sanctions Statement
Effective date: 2026-10-16 Version: 3.3 Operator: FortiBlox Labs LLC Contact: support@fortiblox.com Canonical URL: https://app.fortiblox.com/aml
1. Purpose and posture
This statement describes the anti-money-laundering ("AML") and sanctions posture of FortiSwap, the non-custodial decentralised-exchange ("DEX") aggregator and self-custody wallet interface operated by FortiBlox Labs LLC ("we", "us", or "our") as the web application at app.fortiblox.com (the "Web App"), the FortiSwap Android app (the "Android App"), and the FortiSwap browser extension (the "Extension") (together, the "Interface"). It is intended to be read alongside — and is incorporated by reference into — our Terms of Service and Privacy Policy.
This is a statement of compliance posture, not a representation that FortiSwap is a registered money-services business ("MSB"), a money transmitter, a custodian, an exchange, or a licensed financial-services provider — because it is none of those things. FortiSwap is a software tool that helps you construct unsigned on-chain transactions that you sign with your own self-custodial wallet; once signed, a transaction is broadcast by your wallet or, at your direction, relayed unchanged by the Interface's servers to the network.
2. Why FortiSwap is not the KYC/AML-obligated party for swaps
The AML and money-transmission obligations that attach to a custodial exchange or a fiat money-services business arise from taking custody of customer funds and holding or transmitting fiat. FortiSwap does neither for swaps:
- Non-custodial. FortiSwap never receives, holds, or transmits your fiat currency for swaps; never receives or holds your tokens or other digital assets in a wallet or account whose private key FortiBlox holds; and never holds or can recover your private keys. Every swap is signed by you, in your own wallet, and is broadcast by your wallet or, at your direction, relayed unchanged by the Interface's servers — a relay that cannot alter the signed transaction or move your funds. The only places your assets leave your wallet without going straight to a third-party protocol are the on-chain order escrow and the X1ID gift escrow described below, each held by an on-chain program, not by any FortiBlox key.
- No accounts, no fiat rails for swaps. FortiSwap creates no FortiSwap username or password and operates no fiat payment path of its own for swaps. It reads public on-chain state to compute routes and assembles unsigned transactions. The limited records the Interface keeps (for example in connection with an optional sign-in, an Android App or Extension installation, or a fiat order) are described in the Privacy Policy.
- Not a counterparty. FortiSwap does not act as the counterparty to any swap and does not operate an order book or matching engine. Your swap executes on-chain against independent third-party liquidity protocols (on X1, currently XDEX and Degen; on the Arc network, Circle App Kit, described below).
- On-chain orders on X1 use program-controlled escrow. When you place an on-chain limit or other conditional order on X1, the transaction you sign moves the order's input tokens into an escrow token account controlled by FortiBlox's on-chain order program (not by a private key). As described in Section 3 of the Terms of Service, escrowed tokens can leave only back to your wallet (including when you cancel, which you can do at any time) or in a fill that must deliver to your wallet at least the minimum output your order sets. Orders are filled against third-party liquidity by an automated keeper operated by FortiBlox (or by anyone else who meets the program's on-chain conditions), not matched against other users' orders. No fiat is involved, and FortiSwap performs no KYC for orders.
- Circle App Kit on Arc is wallet-to-wallet. In the Web App, the Interface offers the Arc network (Circle's blockchain) on Arc mainnet, with live money, for swaps between USDC and EURC only, settled through Circle App Kit: FortiSwap's server requests a swap plan from Circle under FortiBlox's API key; Circle builds and signs the plan; you sign a permit or approval and one transaction in your own wallet; and Circle's swap adapter contract settles the output directly to your own wallet. FortiSwap's server only requests the plan, checks it against what you reviewed, and forwards it; you sign in your own wallet, FortiSwap holds nothing in transit, no fiat is involved, and FortiSwap performs no KYC. As at the effective date the Interface does not offer Arc testnet, FortiBlox's own Arc router (the "Aggregator route"), Circle StableFX, its own CCTP transfer feature, or limit orders on Arc.
- Sign-in / wallet infrastructure is not a KYC gate. FortiSwap's optional sign-in and embedded-wallet infrastructure is provided by Privy (privy.io). In the Web App you may sign in by email one-time passcode, passkey, wallet, or a social provider (Google, X, Discord, GitHub, or Telegram); in the Android App, by a phone (SMS) one-time passcode; and in the Extension, by email or a social provider (Google, X, GitHub, or Discord). Signing in is optional for swaps and the cross-chain bridge, which work with a connected wallet alone, and required to start a fiat on-ramp or off-ramp session. In the Android App and the Extension you may instead create or import a self-custody wallet whose keys are generated and kept on your device, without Privy. Privy authenticates you and can provision a user-owned, non-custodial embedded wallet; it is an authentication and signing service, not a KYC/AML programme for swaps. FortiSwap does not take custody of, or hold the keys to, any wallet Privy provisions, and signing in through Privy does not create a KYC relationship with FortiSwap. The only identity verification associated with FortiSwap is the KYC that each Fiat Provider (Stripe, Coinbase, Transak, or MoonPay) performs for its own fiat on-ramp or off-ramp (Section 3).
- Cross-chain bridge routes are wallet-to-wallet. FortiSwap's optional cross-chain bridge, offered in the Web App, quotes routes from independent Bridge Route Providers — Rango, MoonPay Trade (operated by Swaps XYZ Ltd, a MoonPay company), deBridge, Allbridge, Squid, Houdini Swap, ChangeNOW, and THORChain (a THORChain route may be shown for price comparison and is executable only where the Interface offers a transaction to sign for it) — and the Solana ↔ X1 leg settles through the X1 Warp bridge, which we do not operate. Every leg the Interface constructs is a transaction you sign from your own wallet. For a deposit-address route (a route that starts on Bitcoin, Litecoin, Dogecoin, TRON, or PulseChain, or delivers to a Bitcoin, Litecoin, or Dogecoin address), the Bridge Route Provider issues a deposit address and you send the funds yourself, from your own wallet, directly to that provider. In every case no fiat is involved, FortiSwap takes custody of nothing in transit, and FortiSwap performs no KYC. A Bridge Route Provider may apply its own wallet screening and regional restrictions and may decline to quote; the Interface then shows fewer routes.
- Private (confidential) balances on X1. For supported Token-2022 tokens on X1, the Interface lets you move tokens into and out of a confidential balance and send them privately, using the X1 network's Token-2022 confidential-transfer extension. Each step is a transaction you sign in your own wallet; the keys that decrypt a confidential balance are derived on your device and never sent to us. As a result, FortiSwap cannot see the amount of a confidential balance or of a private transfer. What remains visible on-chain is: the sending and receiving accounts, the token, and the fact and time of each transaction; the amounts moved into or out of a confidential balance; and, where a token's issuer has configured an auditor key for that token, the amounts are decryptable by that issuer's auditor (not by FortiSwap). The address screening and activity limit FortiSwap applies to these operations are described in Section 4.
- X1ID, including gifts, is a FortiBlox service. X1ID (x1id.io), the @name registry on X1, is operated by FortiBlox; it is not a third-party protocol. Each X1ID registration, gift, claim, or refund made through the Interface is a transaction you sign in your own wallet, paid in XNT on-chain under the rules of the X1ID registry program; no fiat is involved, and FortiSwap performs no KYC for it. Creating a gift moves the gifted @name's price in XNT into a gift account controlled by FortiBlox's X1ID registry program (not by any private key). As described in Section 3 of the Terms of Service, that XNT can leave only in a claim before the gift expires, which registers the @name to the recipient wallet the gift names and pays the registration fee to X1ID, or in a refund to the sender's wallet, which only the sender can sign, once the gift has expired or the @name has been registered by someone else.
Because FortiSwap is not the custodial or fiat-handling party for swaps, it is not the entity that carries the customer-identification (KYC) obligation for on-chain swaps. It does not, and has no obligation to, operate a KYC identity-verification programme for the swap Interface.
3. The fiat on-ramp and off-ramp — KYC/AML is performed by the Fiat Providers
FortiSwap surfaces, in the Web App, an optional fiat on-ramp that lets users buy USDC with a card or bank payment and an optional fiat off-ramp that lets users sell USDC for fiat paid to their own account, each operated by an independent Fiat Provider — currently Stripe (Crypto Onramp), Coinbase, Transak, and MoonPay. As at the effective date, these features are not available in the Android App or the Extension. In those flows:
- The Fiat Provider (or its regulated partner) is the licensed party. The Fiat Provider is the party that sells the crypto (on-ramp) or buys the crypto and pays out the fiat (off-ramp), processes the fiat payment or payout, and performs all identity verification (KYC), anti-money-laundering checks, payment-fraud controls, and sanctions screening required for the transaction, under its own licences, terms, and privacy policy. MoonPay is the merchant of record for purchases and sales made through its widget and performs its own KYC, AML, fraud, and sanctions checks inside that widget.
- FortiSwap merely provides access. A user must sign in through Privy before an on-ramp or off-ramp session is created; that sign-in is authentication only and is not KYC (Section 2). FortiSwap surfaces each provider's hosted widget or checkout; it does not sell or buy crypto, does not process payments or payouts, and does not receive the user's card, bank, payout, or identity-document data. The one exception is Coinbase's guest checkout (available in the United States without a Coinbase account), where the phone number and email address the user enters for Coinbase to verify are relayed by FortiSwap's server to Coinbase with the order and are not stored by FortiSwap. FortiSwap performs no KYC for the on-ramp or off-ramp — that is each provider's programme, not ours — and does not store the outcome of a provider's identity check.
- Non-custodial in both directions. Crypto a user buys is delivered by the Fiat Provider as USDC on Solana directly to a wallet address the user controls; the user then bridges it to X1 in a separate transaction they sign. Crypto a user sells is sent by the user, from their own wallet, directly to the deposit address the Fiat Provider issues, and the fiat proceeds are paid by the provider directly to the user. FortiSwap does not receive fiat on any user's behalf and does not hold the crypto at any point. For a MoonPay cash-out, the deposit must reach MoonPay within 48 hours or MoonPay fails the transaction and FortiSwap will not build the transfer; a cash-out MoonPay fails after a valid deposit is refunded by MoonPay to the user's own wallet.
Accordingly, FortiSwap does not re-perform, duplicate, override, or gate a Fiat Provider's KYC/AML decisions, and does not hold the identity records a Fiat Provider collects. Any request for on-ramp or off-ramp KYC records must be directed to the relevant Fiat Provider, which is the record-holder.
Circle is the regulated party for its own products. Where the Interface offers the Arc network, Circle — the issuer of the USDC and EURC stablecoins and the provider of Circle App Kit, Circle StableFX, and CCTP — operates those products under its own licences, registrations, and compliance programmes, and FortiSwap uses them as a developer under Circle's developer terms. Circle is not a Fiat Provider: no Circle venue on the Interface involves fiat, and none involves identity verification of the user by FortiSwap. As at the effective date the only Circle product the Interface offers is Circle App Kit, on Arc mainnet. Circle StableFX is an institutional venue that Circle gates on its own know-your-business ("KYB") onboarding of the institution that trades; the Interface does not offer StableFX (an earlier integration was limited to Circle's sandbox on Arc testnet and is no longer exposed), and FortiBlox has not completed Circle's production onboarding — nothing in this statement is a representation that StableFX is available for live funds. The Interface does not offer its own CCTP transfer feature; some routes quoted by a Bridge Route Provider may use CCTP internally. Any compliance determination Circle makes for a Circle product (including declining to serve a wallet or a region) is Circle's, and FortiSwap does not re-perform or override it. FortiSwap remains, for every Circle product, the non-custodial interface: it requests the plan or quote, shows it to you, and you sign in your own wallet.
4. FortiSwap's own sanctions posture
While FortiSwap is not the fiat-side compliance party, we maintain an interface-level sanctions posture as a matter of responsible operation:
- No dealing with sanctioned persons. We do not intend to make the Interface available to, and prohibit its use by, any person or entity that is identified on, or is owned or controlled by or acting on behalf of a person identified on, a sanctions list — including the U.S. Department of the Treasury Office of Foreign Assets Control ("OFAC") Specially Designated Nationals and Blocked Persons ("SDN") List, and the consolidated sanctions programmes of the European Union, the United Kingdom, and the United Nations.
- Sanctioned jurisdictions blocked at the interface. We do not target, market, or make the Interface available to residents of jurisdictions subject to comprehensive U.S. sanctions — as at the effective date: Cuba, Iran, North Korea, Syria, and the Crimea, Donetsk, and Luhansk regions of Ukraine — or to residents of Russia, from which the Interface is also blocked. The country-code-blockable jurisdictions among these (Cuba, Iran, North Korea, Syria, and Russia) are enumerated in the
EXCLUDED_COUNTRIEScontrol in the Interface source (src/lib/geoblock.ts, applied bysrc/middleware.ts), which short-circuits Web App page requests from those jurisdictions — identified by Cloudflare'scf-ipcountrycountry signal — to a/region-not-supportedpage. Our servers apply the same list to the Android App and the Extension: they refuse to open or honour an Android App or Extension session for a request originating in those jurisdictions. We also apply country-based access restrictions toapp.fortiblox.comat our network edge, in addition to the application-level block. The sub-national sanctioned regions of Ukraine (Crimea, Donetsk, Luhansk) cannot be targeted by a country code without over-blocking all of Ukraine and are addressed by the user sanctions self-certification. - Additional restricted jurisdictions. As described in Section 5 of the Terms of Service, the Interface is also not offered to residents of jurisdictions that impose a comprehensive local prohibition on cryptoasset use (currently the People's Republic of China, Bangladesh, Bolivia, Egypt, Morocco, Nepal, the Republic of Türkiye in respect of payments, and Belarus); these are enumerated in the same
EXCLUDED_COUNTRIEScontrol and enforced in the same way, including at our network edge. So that they can be read, the Terms of Service, the Privacy Policy, this statement, and the data-deletion page remain reachable from these eight jurisdictions (but not from Cuba, Iran, North Korea, Syria, or Russia); being able to read them does not authorise use of the Interface. Residents of the United Kingdom may use the Web App and the Extension for swapping, bridging, and on-chain orders; the Android App is not offered in the United Kingdom (theMOBILE_EXCLUDED_COUNTRIEScontrol in the Interface source, default: the United Kingdom), and the fiat on-ramp and off-ramp (card or bank buying and selling through a Fiat Provider) are not offered to United Kingdom residents (theRAMP_EXCLUDED_COUNTRIEScontrol in the Interface source, default: the United Kingdom), in each case pending completion of the applicable U.K. financial-promotions pathway (a regulatory limitation, distinct from sanctions). - User self-certification. By using the Interface, you self-certify that you are not a sanctioned person, are not located in a sanctioned or restricted jurisdiction (including Russia and Belarus), and are not using a wallet subject to a sanctions designation, as set out in the Terms of Service.
- Address screening for private (confidential) balance operations. Before the Interface's server constructs a transaction that sets up, funds, applies, withdraws from, or privately transfers a confidential balance (Section 2), it checks: (a) that the request's country, where Cloudflare has identified it, is not in
EXCLUDED_COUNTRIES; (b) that neither your wallet address nor, for a private transfer, the recipient's address is on a list of the Solana-format digital-currency addresses published on the OFAC SDN List, taken from the SDN List as published on the date recorded in the Interface source (a snapshot, not a live feed); and (c) that your wallet has not exceeded a per-wallet limit on how many such transactions the Interface will construct in a rolling one-hour period. If any check fails, the Interface declines to construct the transaction. To apply the limit we keep, for up to 30 days, a record of each such transaction the Interface constructs (wallet address, token, operation, time, and — for moves into or out of a confidential balance — the public amount; no amount is recorded for a private transfer), as described in the Privacy Policy. These checks apply only to confidential-balance operations; as at the effective date FortiSwap does not screen wallet addresses for swaps, bridge routes, on-chain orders, or Arc swaps, and does not use a third-party blockchain-analytics or wallet-risk-scoring service. - On-ramp and off-ramp sanctions screening is the Fiat Provider's. For a fiat purchase or cash-out, sanctions screening of the payer or payee and the payment is performed by the Fiat Provider (Stripe, Coinbase, Transak, or MoonPay) as part of its licensed programme, in addition to the interface-level jurisdiction block above. For cross-chain bridge routes, each Bridge Route Provider may apply its own wallet screening and regional restrictions before quoting. For Circle App Kit on Arc, any wallet or regional screening Circle performs for its own products is Circle's, in addition to the interface-level jurisdiction block.
- Applies regardless of network. The interface-level jurisdiction block, the restricted-jurisdiction list, and the user sanctions self-certification apply identically whether you transact on X1 or on the Arc network: the Web App page block operates before any network, venue, or wallet is chosen, so Circle App Kit on Arc is not offered through the Web App to a request identified as coming from a blocked region. That Arc mainnet involves live money does not change this posture.
- Applies regardless of how you connect. The interface-level jurisdiction block and the user sanctions self-certification apply to every user, whether you connect an external wallet directly, sign in through Privy (optional for swaps and the bridge, required for the on-ramp and off-ramp) and use an embedded wallet, or use a self-custody wallet in the Android App or the Extension. The Web App page block operates before any wallet-connection or sign-in step, and the Android App and Extension session refusal operates before a session is opened.
5. Prohibited use
You must not use the Interface to launder proceeds of criminal activity, to finance terrorism, to evade sanctions, to commit tax evasion or fraud, or for any activity that is illegal in your jurisdiction. Use of the Interface for any such purpose is a material breach of the Terms of Service.
6. Right to restrict access
We reserve the right, at our discretion and to the extent technically possible for a non-custodial interface, to restrict or refuse access to the Interface — including by blocking a region, a network origin, or the display of the Interface to a given request — where we reasonably believe that access would violate sanctions law, the eligibility or prohibited-use terms of the Terms of Service, or applicable law. Because FortiSwap is non-custodial, it cannot freeze, seize, or move the assets in any user's wallet; any restriction operates at the level of access to the Interface, not custody of funds. Tokens escrowed for an open on-chain order on X1, and XNT escrowed for an X1ID gift, can leave escrow only in the ways described in Section 3 of the Terms of Service, including back to you when you cancel an order or refund an expired gift.
7. Cooperation and referrals
FortiSwap is not the licensed MSB for any transaction and does not itself file suspicious-activity reports. Where required by applicable law, or where we receive a valid legal request, we will cooperate with competent authorities in respect of the limited data we hold (as described in the Privacy Policy). Matters concerning a fiat on-ramp purchase or off-ramp cash-out — including the customer's KYC file and any suspicious-activity determination for that purchase — are the responsibility of the relevant Fiat Provider (Stripe, Coinbase, Transak, or MoonPay) as the licensed party and should be directed to that provider. Matters concerning a Circle product used on Arc (such as Circle App Kit) are Circle's, as the provider of that product, and should be directed to Circle.
8. Amendments
We may amend this statement to reflect changes in law, in the networks the Interface supports, in the third-party protocols the Interface routes across (including a Circle product being offered or withdrawn), in the fiat on-ramp / off-ramp providers, in the bridge route providers, in the sign-in / wallet-infrastructure provider, in the surfaces through which the Interface is offered, or in our operational posture. Material changes will be posted at app.fortiblox.com/aml with a revised effective date and a change-log entry.
9. Contact
Questions about this statement may be sent to support@fortiblox.com. For security-vulnerability disclosures, please use security@fortiblox.com.
Change log
| Date | Version | Summary |
|---|---|---|
| 2026-07-30 | 1.0 | Initial published version. AML & Sanctions Statement for FortiSwap, the non-custodial DEX aggregator operated by FortiBlox Labs LLC. Establishes that FortiSwap is not an MSB / money transmitter / custodian / exchange and carries no swap-side KYC obligation because it is non-custodial and handles no fiat for swaps; that all KYC/AML, payment processing, and sanctions screening for the Stripe Crypto Onramp (buy-side USDC only, no off-ramp) are performed by Stripe or its regulated partner, not by FortiSwap; FortiSwap's own interface-level sanctions posture (no dealing with SDN/sanctioned persons; OFAC-sanctioned and other restricted jurisdictions blocked at the edge and application layer via EXCLUDED_COUNTRIES); prohibited-use terms; and the reserved right to restrict access. |
| 2026-07-31 | 2.0 | Privy sign-in / embedded-wallet clarification. Section 2 clarifies that FortiSwap's optional sign-in and embedded-wallet infrastructure is provided by Privy as an authentication/signing service — not a KYC/AML programme for swaps; signing in via Privy does not create a KYC relationship with FortiSwap, and FortiSwap holds no keys to any Privy-provisioned wallet. Section 4 adds that the interface-level jurisdiction block and user sanctions self-certification apply regardless of how the user connects (external wallet or Privy embedded wallet), and operate before any wallet/sign-in step. Existing non-custodial / no-swap-KYC posture, Stripe-performs-onramp-KYC framing, and OFAC/edge geoblock unchanged and not contradicted. No license numbers, registration IDs, or physical address asserted. |
| 2026-08-22 | 3.0 | All Fiat Providers (Stripe, Coinbase, Transak, MoonPay), the off-ramp, and the cross-chain bridge (Rango, MoonPay Trade) disclosed. Section 3 rewritten from "Stripe, buy-side only" to "KYC/AML is performed by the Fiat Providers" in both directions; MoonPay named as merchant of record performing its own KYC/AML/fraud/sanctions checks in its widget, with the 48-hour cash-out deposit window and refund-to-own-wallet behaviour; non-custodial settlement (USDC on Solana, separate user-signed Warp step to X1) stated. Section 2 adds that cross-chain bridge routes from Rango and MoonPay Trade (Swaps XYZ Ltd, a MoonPay company) are wallet-to-wallet, user-signed, fiat-free, and carry no FortiSwap KYC, with provider-side wallet screening. Section 4, 7, and 8 generalised from Stripe to the Fiat Providers and Bridge Route Providers. Superseded the v1.0 "buy-side only / no off-ramp" statement. OFAC/edge geoblock and non-custodial / no-swap-KYC posture unchanged. |
| 2026-08-22 | 3.1 | Sign-in requirement stated precisely. Sections 2, 3, and 4 now state that Privy sign-in (email one-time passcode, passkey, or Google / X / Discord / GitHub / Telegram) is optional for swaps and the cross-chain bridge but required before an on-ramp or off-ramp session is created, and that it remains authentication only — not KYC, which stays with the Fiat Provider. No renumbering. |
| 2026-09-11 | 3.2 | Arc network and Circle (App Kit, StableFX, CCTP) disclosed. Section 2 adds that swaps on the Arc network (Circle's blockchain, testnet only, no live money) settle wallet-to-wallet through the Arc pools, Circle App Kit (Circle-built plan, Circle's contract, user-signed), Circle StableFX (Circle's sandbox only; user-funded FxEscrow under Permit2; PvP settlement by Circle and its makers; FortiSwap not a party), or CCTP (burn/mint from and to the user's own address, Circle attests) — no custody, no fiat, no FortiSwap KYC. Section 3 adds a paragraph naming Circle as the regulated party for its own products (issuer of USDC/EURC; App Kit/StableFX/CCTP under Circle's own licences and developer terms; not a Fiat Provider), states that StableFX production would require Circle's KYB onboarding of FortiBlox, which has not occurred, and that Circle's compliance determinations are Circle's. Section 4 adds that the interface-level jurisdiction block applies identically on X1 and Arc, before any network or venue is chosen, and that Circle's own screening is additional. Sections 7 and 8 reference Circle and supported networks. Stray trailing markup after the "Last updated" line (present since an earlier revision and rendered as literal text at the foot of the page) removed. No renumbering; non-custodial / no-swap-KYC / no-MSB posture unchanged. |
| 2026-10-16 | 3.3 | Accuracy amendment: the statement brought in line with what the Interface does today and with Terms of Service 5.7 and Privacy Policy 5.0. Surfaces: Section 1 now covers the Web App, the Android App, and the Extension; broadcast "by your wallet or, at your direction, relayed unchanged by the Interface's servers". Arc: the "testnet only, no live money" and StableFX "sandbox only" statements (Sections 2, 3, 4, 8) are replaced — the Web App offers Arc mainnet with live money, USDC ↔ EURC only, through Circle App Kit; Arc testnet, the Aggregator route, Circle StableFX, the Interface's own CCTP feature, and Arc limit orders are stated as not offered. Custody: Section 2 carves out, and describes, the program-controlled escrow of open X1 on-chain orders and the FortiBlox-operated keeper, and the program-controlled escrow of X1ID gifts (claim for the named recipient, or refund to the sender); Section 6 "cannot freeze, seize, or move" now refers to assets in a user's wallet, with a pointer to the order and gift escrow rules. Providers: the Bridge Route Providers are now all named (Rango, MoonPay Trade, deBridge, Allbridge, Squid, Houdini Swap, ChangeNOW, THORChain — THORChain for comparison unless signable), with the deposit-address route model; provider screening stated as "may". Coinbase guest checkout's relay (not storage) of phone and email disclosed; fiat flows stated as Web App only. Sign-in: Privy methods stated per surface; on-device self-custody wallets in the Android App and Extension. New factual descriptions: private (confidential) balances on X1 and what remains visible (accounts, token, timing, deposit/withdraw amounts; auditor key per issuer; FortiSwap cannot see confidential amounts); X1ID (including gifts) as a FortiBlox service. Sanctions controls: EXCLUDED_COUNTRIES location corrected (src/lib/geoblock.ts, applied by src/middleware.ts), Web App page block, server-side Android App and Extension session refusal, and network-edge restrictions stated; Russia separated from the comprehensive-sanctions list and stated as also blocked; self-certification now names Russia and Belarus; Android App not offered in the United Kingdom; legal and data-deletion pages reachable from the eight local-restriction jurisdictions; the address screening (geo, OFAC SDN-listed Solana-format addresses, per-wallet hourly activity limit with a record kept up to 30 days) applied to confidential-balance operations only is described, together with the fact that swaps, bridge routes, orders, and Arc swaps are not address-screened and no blockchain-analytics service is used. Other: Section 7 "non-identifying technical data" replaced by "the limited data we hold"; Sections 7 and 8 Circle references updated. No renumbering; no new compliance programme, reporting obligation, or legal term. |
Last updated: 2026-10-16
