FortiSwap — Privacy Policy
Effective date: 2026-11-06 Version: 5.3 Operator: FortiBlox Labs LLC Contact: support@fortiblox.com Canonical URL: https://app.fortiblox.com/privacy
1. Summary
FortiBlox Labs LLC ("we", "us", or "our") operates FortiSwap, a non-custodial decentralised-exchange aggregator and self-custody wallet interface, available as:
- the web app at
app.fortiblox.com(the "Web App"); - the FortiSwap Android app (the "Android App"); and
- the FortiSwap browser extension (the "Extension"),
together the "Interface". This Privacy Policy describes the data we process when you use any of them.
The short version:
- Your keys never leave your device. FortiSwap is self-custodial: your private keys and seed phrase are created and kept on your device (or, for a Privy embedded wallet, in Privy's key infrastructure under your control). Our servers never receive, hold, or can recover your keys or seed phrase, and we never hold your funds in a wallet or account whose key we hold. The only exceptions are tokens you place in an on-chain order on X1 and XNT you put into an X1ID gift: these sit in an escrow account controlled by our on-chain program (not by any key) until they are released under that program's rules, as described in our Terms of Service.
- No FortiSwap username or password. Swaps and bridging work with a connected wallet alone. An optional sign-in powered by Privy (required for the fiat on-ramp and off-ramp) is handled by Privy under its own privacy policy (Section 6).
- We do keep a limited set of technical records, described in Section 4: request logs (kept up to one month), rate-limit records (which can contain your IP address for up to one day), a pseudonymous record for each Android App or Extension installation, a record of which policy versions you accepted, push-notification registrations, the status of fiat-provider orders, and a 30-day compliance record of private-balance transactions. Where you sign in with Privy, some of these records are linked to your Privy user identifier and the wallet addresses linked to it.
- We do not sell your data, run advertising, or send marketing email. The Web App uses Cloudflare Web Analytics, a cookieless, aggregate page-view measurement (Section 8); the Android App and the Extension contain no analytics.
- You can ask us to delete your data at https://app.fortiblox.com/delete-account or from inside the Android App (Section 11).
Most of what makes a swap work is public blockchain data that exists independently of us (Section 3).
This Policy is incorporated by reference into our Terms of Service and should be read together with our AML & Sanctions Statement.
2. What we do not collect
We do not collect, and do not ask you for:
- Your wallet's private keys or seed phrase. These never leave your device (or your Privy embedded wallet), and we have no ability to see or recover them. When you import a wallet in the Android App or Extension, the seed phrase is processed only on your device; only public addresses derived from it are sent to us (Section 4.6).
- Government-issued identification, date of birth, biometric identifiers, proof of address, source-of-funds evidence, or politically-exposed-person data. We do not perform KYC. Fiat Providers do, under their own policies (Section 5).
- Card numbers, bank account or payout details. These go directly to the Fiat Provider.
- A FortiSwap password. Sign-in is passwordless and handled by Privy.
- Advertising identifiers, device contacts, photos or media, location, the list of other apps on your device, or your device's model or OS version. The Android App requests these permissions: internet and network-state access; biometric/fingerprint unlock; permission to show notifications; permission to restart notification checks after your phone restarts; the camera, only when you scan a QR code (images are processed on your device and never stored or sent); and nearby-device (Bluetooth) access, only if you choose to connect a Ledger hardware wallet. We do not request your location, contacts, photos or media. The Extension requests no access to your browsing history, tabs, cookies or page content (Section 4.5).
We do receive a name and email address only when you choose to give them to us: by writing to support or using the support form (Section 4.8), by submitting a data-deletion request (Section 11), by requesting a developer API key (Section 4.9), or — relayed to Coinbase and not stored by us — in the Coinbase guest checkout (Section 5).
3. What is inherently public (and not ours to control)
- Your wallet addresses and on-chain activity are public. When you broadcast a transaction, your address, the tokens and amounts (except amounts kept confidential in a private balance on X1), and the transaction are recorded on the relevant public blockchain — X1, Solana, Arc, or any other network you use through a bridge. Anyone can inspect this with a block explorer, independently of the Interface.
- Transactions are irreversible. We cannot delete, alter, or reverse anything recorded on a blockchain.
- We index public on-chain data about swaps and orders routed through FortiSwap (transaction signature, wallet address, tokens, amounts) to show transaction feeds, order history, and volume statistics. This is a copy of public data; deleting our copy does not remove it from the blockchain.
4. What we collect and why
4.1 Overview by surface
| Data | Web App | Android App | Extension | Purpose | Retention |
|---|---|---|---|---|---|
| IP address (transient) | ✓ | ✓ | ✓ | Security, rate limiting, geographic restriction, forwarding to some providers (Section 5) | Not written to our request logs; stored as a rate-limit key for up to 1 day |
| Country (derived from IP by Cloudflare) | Used, not stored | Stored with installation record | Stored with installation record | Geographic restriction (Terms of Service) | Web: not stored. App/Extension: see Section 9 |
| Request logs (request ID, route, method, status, latency, installation ID where applicable) | ✓ | ✓ | ✓ | Operations, debugging, abuse prevention | Up to 1 month |
| Installation ID (random UUID) and installation public key | — | ✓ | ✓ | Authenticating the app/extension to our servers | See Section 9 |
| Google Play Integrity verdict (device/app/licensing labels → device tier) and app version code | — | ✓ | — | Abuse and fraud prevention | See Section 9 |
| Extension ID and version | — | — | ✓ | Authenticating the Extension | See Section 9 |
| Hashed refresh tokens | — | ✓ | ✓ | Keeping you signed in | 7-day lifetime, purged 30 days after expiry |
| Consent records (policy versions, timestamp) | Browser only | ✓ | — | Proof of acceptance of Terms / Privacy / AML | See Section 9 |
| Privy user identifier + linked wallet addresses | Where you sign in | Where you sign in | Where you sign in | Linking installations, notifications, X1ID links and ramp orders to your sign-in | See Section 9 |
| Public addresses derived from an imported seed (up to 22) | — | ✓ | ✓ | Finding which of your accounts have activity | Not stored (short in-memory cache) |
| Transactions submitted for a security scan (+ requesting site's origin) | ✓ | — (checked on-device) | ✓ | Warning you before you sign | Not stored |
| Transactions you build or send (addresses, amounts, signed transaction) | ✓ | ✓ | ✓ | Building and broadcasting your transaction | Not stored by us beyond request logs (route only); public once broadcast |
| Compliance records for private (confidential) balance transactions (wallet, token, operation, time; public amount for moves into or out of a private balance) | ✓ | ✓ | ✓ | Sanctions screening and the hourly limit (Section 4.3) | 30 days |
| Push-notification registration (Web: browser push subscription; Android: Firebase installation ID, notification settings, watched addresses) | ✓ (signed-in) | ✓ (if you allow notifications) | — | Notifications you enable | Until you turn notifications off, the registration stops working, or you ask us to delete it |
| Fiat-provider order status | ✓ | — (Buy/Sell not yet available) | — | Showing order status | Up to 400 days |
| Support messages | ✓ | Via email | Via email | Answering you | See Section 9 |
| On-device storage (encrypted keys, accounts, settings, address book, connected sites) | Browser local storage (no keys) | ✓ | ✓ | Running the wallet on your device | Until you clear it or uninstall; never sent to us |
4.2 Edge and server logs
The Interface is served behind Cloudflare, which terminates TLS and processes standard request metadata — including your IP address, an approximate country derived from it (cf-ipcountry), user-agent, the requested address, and timestamps — for delivery, security, abuse mitigation, and to enforce the geographic restrictions in our Terms of Service. Cloudflare's processing is additionally governed by Cloudflare's own privacy terms.
Our application writes one log line per API request containing a request ID, the route called (e.g. "POST /api/quote", not the full URL), method, status, latency, an access tier, and — for the Android App or Extension — the installation ID and device tier. These request logs do not contain your IP address, user-agent, or wallet address. When the compliance check for a private-balance transaction refuses a request (Section 4.3), we log the refusal with your wallet address, the reason, and — depending on the reason — your country, the recipient address, the matching sanctions-list entry, or your transaction count for the hour. Some events in the Android App and Extension sign-in flow additionally log the installation ID, app/extension version, and country. A small number of lookup endpoints take a wallet address in the request address, which Cloudflare handles when delivering the request.
If the Web App crashes in your browser, it sends a short error report (error message, the first lines of the stack trace, the page path, and your browser's user-agent), which we write to the same logs. Browsers may also send us Content-Security-Policy violation reports (page and blocked-resource URLs).
Our server logs, including these refusal records, are kept in our server's system journal (journald) for up to one month, after which they are deleted automatically.
4.3 Rate limiting and abuse prevention
To protect the service we count requests per IP address, per installation ID, per Privy user, and — for transaction submission — per wallet address. Most counters exist only in server memory and disappear within minutes. Some are written to a shared database table that contains the raw IP address, wallet address, or installation ID and is automatically deleted after one day. Private (confidential) balances. Before our server builds a transaction that sets up, funds, applies, withdraws from, or privately sends from a private balance on X1, it checks your country, checks your wallet (and, for a private transfer, the recipient's address) against a list of sanctioned addresses, and checks that your wallet has not exceeded a limit on how many such transactions we build per hour (by default 30). For that limit we record each such transaction we build: your wallet address, the token, the type of operation, the time and, for a move into or out of a private balance, the amount (which is public on-chain anyway). We do not record the amount of a private transfer and cannot see it. These records are kept for up to 30 days and are described in our AML & Sanctions Statement.
4.4 Android App: installation and device integrity
When you first open the Android App it creates, on your device:
- a random installation ID (UUID), and
- an installation key pair in the Android Keystore (StrongBox where available). The private key never leaves the device; the public key is sent to us. Every subsequent request is signed with this key. The Keystore's attestation certificate chain is not sent to us.
To protect against tampered apps and automated abuse, the Android App asks Google Play Integrity for a verdict, which our server sends to Google to decode. We store the resulting device-recognition, app-recognition and app-licensing labels and a derived device tier — not the raw token. Google processes the Play Integrity request under Google's terms and privacy policy.
We also store with your installation record: the app version code, your country (from Cloudflare's IP-derived signal), timestamps, and — only if you sign in with Privy — your Privy user identifier and the wallet addresses linked to your Privy account. We do not store your IP address in the installation record. We do not collect your device model, OS version, or advertising ID.
The Android App receives a 15-minute access token and a 7-day refresh token. We store only a hash of the refresh token; hashed tokens are purged 30 days after they expire. Logging out marks the installation as revoked; it does not by itself erase the record — use Section 11 for that.
What else the Android App sends us. To send tokens, it sends the sender and recipient addresses and amount so our server can build the transaction, and then the transaction you signed so our server can broadcast it. It also reads token lists, prices and market data, and (on wallet import) performs the address scan in Section 4.6. Transactions requested by dApps are checked on your device; the Android App does not send them to our scan service.
The Android App contains no analytics, no crash-reporting, and no advertising SDKs. Its third-party components are Privy (sign-in), Google Play Integrity, Google Firebase Cloud Messaging with the Firebase Installations component it requires (used only to deliver the notifications you allow — Section 4.10; no Firebase Analytics or Crashlytics), Trust Wallet Core (on-device key derivation and signing), and standard Android networking and storage libraries. It does not offer Houdini, ChangeNOW, THORChain, Shield, or cross-chain bridges, and Buy/Sell is not yet available in the Android App.
4.5 Browser Extension: installation
When you install the Extension it generates an installation key pair in your browser (the private key stays in the browser) and registers the public key, a random installation ID, the extension ID and version, and your country with our server. If you sign in with Privy, your Privy user identifier and linked wallet addresses are added. We do not store your IP address in this record. Session tokens work as for the Android App (15-minute access tokens; 7-day refresh tokens stored only as a hash).
On your device. Your recovery phrase and private keys are encrypted with a key derived from your wallet password and kept in the browser's extension storage, together with your account list (public addresses), settings, address book, the sites you have connected, and caches. A short-lived unlock key is kept in session storage until the wallet locks or the browser closes. None of this is sent to us.
What the Extension sends to app.fortiblox.com: public wallet addresses (balances, X1ID names, address history, recipient checks); transactions you create or sign (to build, check and broadcast them); for a signing request from a website, the transaction and that site's origin for the safety scan (Section 4.7); the installation ID, key and session tokens; the extension version; and downloads of our signed phishing list, configuration and token images.
Permissions. The Extension requests storage, alarms, idle, sidePanel, offscreen (to host the Privy sign-in frame) and identity (social sign-in via Privy), and host access only to app.fortiblox.com. It injects a wallet-provider script into web pages so sites can find the wallet; that script does not read page content, cookies or form fields. Each site connection and each signature needs your approval. It does not request tabs, history, cookies, web-request, bookmarks, downloads, notifications or clipboard access.
Directly to others. For some networks (for example the X1 public node, the public Solana node, and public Base, Optimism and Arbitrum nodes) the Extension sends reads and transactions directly to public RPC endpoints, whose operators see your IP address and the addresses and transactions involved. Websites you connect to receive only the one public address you choose and the results of requests you approve. If you use a "FortiSwap account", Privy's sign-in and embedded-wallet frames (auth.privy.io, privy.fortiblox.com) run inside the Extension.
Collectible pictures. Collectible (NFT) pictures shown in the Extension are loaded through our own image service (app.fortiblox.com), so the websites that host the pictures do not see your wallet address or IP address. We do not store the pictures on our servers or link them to you; Cloudflare may keep a cached copy of a picture for up to 7 days to deliver it faster.
FortiSwap Link. If you choose to move a wallet between the FortiSwap Android App and the Extension, the two devices exchange the wallet data through a temporary relay on app.fortiblox.com. The data is encrypted on one device with a key that only the two devices share, so the relay carries only unreadable data. A session lasts at most 10 minutes and is kept only in server memory, and the relay does not receive your recovery phrase in readable form. Nothing is sent unless you start pairing on both devices.
Optional auto-approve. If you turn on auto-approve in the Extension, the limits, the list of trusted sites and a log of what was approved are stored on your device only. Each approved request is still checked by the safety scan described in Section 4.7.
Chrome Web Store Limited Use. The use of information received from the Chrome Web Store APIs and from the Extension will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. We use the data described in this Policy only to provide and improve the wallet's single purpose, we do not sell it, we do not use or transfer it for unrelated purposes, and we do not use it to determine creditworthiness or for lending.
The Extension contains no analytics, usage tracking, or crash-reporting.
4.6 Wallet import: active-address scan
When you import an existing wallet from a seed phrase in the Android App or Extension, the app derives candidate public addresses on your device — for up to four wallet layouts, and up to 100 accounts per layout when you ask it to look further — and sends them to our server in batches of at most 22, which asks X1 and Solana RPC providers (Section 8) whether each has any balance or transaction history, so that the app can show the accounts you actually use. The seed phrase is never sent. In the Android App, the "total across accounts" figure is calculated by reading the portfolio (Section 4.5's balance lookups) of each account you hold. The addresses are sent in the request body (not the URL), are not stored or logged by us, and are cached in server memory for at most 10 minutes. Because these addresses are sent together, a recipient could infer they belong to the same person; the RPC providers we use may log the queries under their own policies.
4.7 Transaction security scan
Before you sign a transaction requested by a third-party site or dApp, the Web App and the Extension send that unsigned transaction, the requesting site's origin, and optionally your signing address to our server, which simulates it against an X1 or Solana RPC node and checks the site against phishing lists held on our server. No third-party scanning vendor is used. The transaction and origin are not stored. The Android App (version 1) performs its checks on your device and does not use this service.
4.8 Support requests
If you contact us via the support form in the Web App, we receive your name, email address, the category and subject, your message, an optional transaction hash and network, an optional screenshot (up to 5 MB), the page you sent it from, and your browser's user-agent. The form is delivered by email through our mail provider (mxroute) to the relevant FortiBlox mailbox, and an automatic confirmation is emailed back to you. The form is not stored in our databases. If you email support@fortiblox.com directly, we receive whatever you send. We use this only to respond to you.
The form has a "Subscribe to product updates" checkbox. Your choice is recorded only as a yes/no line in the email we receive with your message; it is not added to any mailing list, and we do not send marketing email.
4.9 Developer API keys (developers only)
If you request a FortiSwap developer API key, we store your project name, website, contact email, use case, optional Telegram/Discord handle, fee wallet (partner tier), and a salted hash of your IP address (never the IP itself). The form is protected by Cloudflare Turnstile. For API-key and pay-per-request (x402) traffic we keep usage records (key ID, paying wallet, route, status, token pair, amounts) for 400 days, and records of x402 payments (payer, recipient, transaction) as described in Section 9.
4.10 Notifications
Web App: if you are signed in and enable notifications, your browser gives us a push subscription (an endpoint URL at your browser vendor's push service plus encryption keys), which we store with your Privy user identifier, the wallet addresses you watch, and any price alerts you set. Notifications are delivered through your browser vendor's push service (for example Google, Mozilla, Apple or Microsoft). You can turn notifications off in the Interface or your browser.
Android App: notifications are optional and need your permission. If you allow them, the app registers with Google Firebase Cloud Messaging (FCM), which gives it a Firebase installation ID, and sends our server that ID, your installation ID, your notification settings (which notification categories you want: swaps, orders, recurring buys, bridges, Buy/Sell, price alerts, incoming transfers — a category only produces notifications where the app offers that feature) and up to 10 wallet addresses to watch. If you are signed in with Privy, the registration is also linked to your Privy user identifier, so it shares the watched wallets and price alerts of your Web App notifications. When you ask to be told how a swap or bridge ends, the app also sends that transaction's signature (swap) or the destination address and token (bridge).
To decide what to notify you about, our server reads public chain data for the addresses you watch (for example, incoming transfers, order fills, recurring-buy steps and swap results) through the RPC providers in Section 8; it never needs your keys. Notifications are delivered through Google's FCM service: Google, as our service provider, processes the Firebase installation ID and the standard data its FCM and Firebase Installations services need to deliver to your device, and receives each notification's content — its title and text (for example a token, an amount or a trading pair) and references the app uses to open the right screen (such as a transaction signature, token address or order ID). Google processes this under its own terms and privacy policy.
You can turn notifications off in the app's settings or in Android's system settings at any time. Turning them off in the app, signing out of the app, or Settings → Delete my data (Section 11) removes the registration from our servers; if you are not signed in with Privy, signing out and Delete my data also remove the wallets and price alerts watched for that installation (wallets and alerts you set while signed in with Privy stay with your Privy sign-in for your other devices). If we end a session for your security (for example when a sign-in token is reused), the registration is removed too. A registration Google reports as no longer valid (for example after you uninstall the app) is removed automatically the next time we try to notify it.
4.11 Referrals and X1 rewards
If you open a referral link, the Web App creates a random visitor ID in your browser and sends it, with the referrer's code, to our server. We do not link it to your wallet. A referrer's code is derived from the referrer's wallet address.
After a confirmed swap in the Web App, our server reports your wallet address, the transaction signature, and the swap's tokens and amounts to X1 Core (core.x1.xyz), a separate X1-ecosystem rewards programme that awards XP. The Interface does not currently offer a setting to turn this reporting off.
4.12 X1ID handles
X1ID (x1id.io), the @name registry on X1, is a FortiBlox service, not a third party. If you look up, register, or link an X1ID handle, the wallet address and handle are sent to the X1ID service (api.x1id.io); to show your X1ID gifts, our server sends your wallet address or the gifted name to the X1ID indexer (query.x1id.io). To link a handle to your sign-in, our server sends the X1ID service your wallet address and a message signed by your wallet, and stores the link (Privy user identifier, address, handle). Handle records, gifts and their public profile fields are on-chain and public.
5. Fiat on-ramp and off-ramp, bridges and other third-party venues — data flow
5.1 Fiat Providers
FortiSwap surfaces optional buy/sell flows operated by independent Fiat Providers — currently Coinbase, Stripe (Crypto Onramp), Transak, and MoonPay — in the Web App. In the Web App, fiat flows require a Privy sign-in. In the Android App you can buy and sell through the Fiat Providers (Coinbase, MoonPay, Stripe, Transak) from the Buy and Sell screens, either signed in with Privy or, for a wallet kept only on your device, with your app installation; in that case the pseudonymous customer reference is a keyed hash of your installation ID, and you prove that you control the receiving wallet with a signature. Your payment and identity data go directly to the Fiat Provider; we receive only the order status and the references described in this Section 5.1. The Extension has no fiat flows.
- The Fiat Provider collects your payment, payout, and identity data directly, under its own privacy policy and terms; your data relationship for a purchase or cash-out is with that provider.
- What our server sends the provider: your wallet address, the asset, network and amount, and a pseudonymous customer reference (a keyed hash of your Privy user identifier — not your email). In addition: Coinbase, Stripe, and Transak receive your IP address from our server (their fraud and eligibility checks require it); MoonPay receives only a keyed hash of your IP address.
- Coinbase guest checkout (US, Apple Pay / Google Pay). If you buy without a Coinbase account, you enter your phone number and email address, which Coinbase verifies. Our server relays them to Coinbase with your order; we do not store or log them. Your browser keeps the Coinbase verification references for the browser session only.
- What we receive back: the order identifier, status, amounts, network and asset, wallet or deposit address, settlement transaction hash, and a bounded failure code. We keep this against the pseudonymous reference for up to 400 days (MoonPay cash-out deposit records: 60 days) so we can show you the status and, for a cash-out, build the deposit transfer. We do not store identity-verification outcomes.
- Settlement is on Solana; moving funds between Solana and X1 is a separate transaction you sign through the X1 Warp bridge.
Spritz (bill pay) is not currently offered.
5.2 Cross-chain bridges and swap venues
Where you use cross-chain routes, our server sends the Bridge Route Provider the route parameters — tokens, amounts, slippage and, where the provider needs them, your source and destination addresses — and receives quotes and an unsigned transaction or deposit address. We may register your transaction hash with the provider to track delivery. Providers may screen addresses and decline to quote. Currently:
- Web App: Rango, MoonPay Trade (Swaps XYZ Ltd, a MoonPay company), Squid, deBridge, Allbridge, Relay (Uneven Labs, Inc.), LI.FI, Houdini Swap, ChangeNOW, and THORChain (quotes via Liquify), plus the X1 Warp bridge. For swaps on one chain, Jupiter (Solana), 0x (EVM), LI.FI, and Rango receive the same route parameters, including your wallet address when you request a swap. Houdini additionally receives your IP address and browser user-agent from our server.
- Relay: when a route you choose uses Relay, Relay receives your source and destination addresses, the tokens and amounts, and the transaction details. Relay may also collect on-chain data about those addresses, including completed transactions and token holdings, and may screen them; if it flags an address, it can refuse, delay or block the transfer. The route review tells you before you sign. Relay's use of this data is described in its Terms and Privacy Policy.
- Android App: no cross-chain bridges in version 1. When added, only deBridge and the X1 Warp bridge are planned; this Policy will be updated first. Houdini, ChangeNOW and THORChain are not available on Android.
- Extension: no cross-chain bridge providers; the Extension's swaps and sends go through FortiSwap's own API (Section 4.5).
The Interface keeps in-flight transfers in your browser's local storage so you can resume tracking them.
5.3 Circle on Arc
In the Web App, the Interface offers the Arc network (Circle's blockchain) for swaps between USDC and EURC settled through Circle App Kit. Each such swap is requested by our server under FortiBlox's API key. Circle receives your wallet address, tokens, amounts, and slippage setting from our server's IP address, not yours. The Interface does not offer Circle StableFX or its own CCTP transfer feature; some bridge routes may use CCTP internally (Section 5.2). No identity data is sent. Arc RPC endpoints your browser or wallet uses — some operated by Circle — see your IP address. Signed Arc limit orders (your EVM address and the signed order), where that feature has been offered, are stored on our server so they can be filled (retention: Section 9).
5.4 Provider privacy policies
Each provider's own privacy policy governs what it collects and keeps. Please review it before using the feature. We are not responsible for providers' privacy practices.
6. Sign-in and embedded wallets (Privy)
FortiSwap uses Privy (privy.io) for optional sign-in and embedded wallets.
- Sign-in is optional. In the Android App and Extension you can instead create or import a self-custody wallet whose keys stay on your device; Privy is not involved.
- Web App sign-in methods: email one-time passcode, passkey, wallet, or a social provider — Google, X, Discord, GitHub, or Telegram. The Web App does not offer SMS sign-in.
- Android App sign-in: an on-device self-custody wallet, or Privy with a phone (SMS) one-time passcode — your phone number is processed by Privy. Sign-in and embedded-wallet operations in the Android App run through Privy's SDK, including Privy's own in-app web view of
auth.privy.io; Privy processes that data under its privacy policy. The Android App's own code shows no in-app web view: our legal pages, the deletion page and similar links open in your browser. - Extension ("FortiSwap account") sign-in: email, or a social provider — Google, X, GitHub, or Discord (via the browser's sign-in window).
- What Privy processes. Your email address or phone number, the basic profile your social provider returns, or your passkey authentication — processed by Privy directly under its own policy (privy.io/privacy-policy).
- Embedded wallets are user-owned and non-custodial. If you have no wallet, Privy can create a Solana (and, where enabled, an Ethereum) wallet for you. Its key is held in Privy's secure infrastructure under your control; FortiSwap never receives, holds, or can recover it. We configure no session signers or delegated actions.
- What we receive and keep. When you sign in, our server verifies Privy's access token and learns your Privy user identifier and the wallet addresses linked to your Privy account. We store the Privy user identifier with your Android App or Extension installation record, consent records, web-push subscription, and X1ID link (Section 4). For fiat orders we use a keyed hash of it instead (Section 5.1). We do not store your email address, phone number, or social profile from Privy. (This corrects version 4.2, which said we keep only the hashed reference.)
7. Cookies and local storage
Web App. We set no cookies of our own. Privy sets cookies and local storage to keep you signed in, and our server reads Privy's session cookie to verify you. Cloudflare may set strictly necessary security cookies. A Fiat Provider's widget may set its own cookies.
The Web App uses your browser's local storage for things like: theme, your acceptance of the legal documents, last-used and recent wallets, your address book, selected network, swap settings, favourite and recent tokens, price alerts, notification state, in-flight bridge and cash-out transfers, onboarding hints, and the random referral visitor ID. It uses session storage for the Coinbase guest-checkout verification references. This data stays in your browser — we cannot see it — and you can clear it at any time in your browser settings.
Android App / Extension. Your encrypted keys, accounts, settings, address book, connected sites and installation ID are stored on your device or in your browser profile (Section 4.5). The Extension sets no cookies. Uninstalling removes this local data; it does not delete our server-side records (Section 11).
8. Third parties (processors and independent providers)
- Cloudflare — content delivery, TLS, DDoS/WAF protection, geographic signal, Turnstile (developer form), and Cloudflare Web Analytics on the Web App.
- Cloudflare Web Analytics — what it measures: when you load a Web App page, a Cloudflare script records the page path, the referring page, your browser and device type, your country (from the network), and page-load performance timings. Cloudflare states that it does not use cookies or local storage for this, does not fingerprint visitors, and does not use the data to track individuals across sites. We receive aggregate statistics only (for example page views per page and per country), never per-visitor records.
- Cloudflare Web Analytics — what we exclude: the Web App loads it itself and never runs it on a page whose address contains a wallet address (the pool holder pages,
/pool/<pool>/holders/<wallet>) or on the key-export pages, and it does not report in-app page changes, so those addresses are not sent to Cloudflare. - Cloudflare Web Analytics — where it runs: it runs only on the Web App; the Android App and the Extension do not run it. Cloudflare's own handling is described in its privacy policy (https://www.cloudflare.com/privacypolicy/).
- Privy — sign-in and embedded wallets (Section 6).
- Google — Play Integrity verdicts for the Android App (Section 4.4); Google Play distributes the app.
- RPC and data providers — X1 RPC nodes (including
rpc.mainnet.x1.xyzand FortiBlox-operated nodes), Helius and Alchemy (Solana and EVM), GoldRush / Covalent (multichain portfolio), TronGrid, Sui, TON Center and public EVM RPC endpoints. When our server calls them they receive the wallet addresses being looked up and the transactions you broadcast, from our server's IP address. Where the Extension calls a public RPC node directly (Section 4.5), that operator also sees your IP address. - Fiat Providers — Coinbase, Stripe, Transak, MoonPay (Section 5.1).
- Bridge Route Providers and venues — Rango, MoonPay Trade (Swaps XYZ Ltd), Squid, deBridge, Allbridge, Relay (Uneven Labs, Inc.), LI.FI, Jupiter, 0x, Houdini Swap, ChangeNOW, THORChain/Liquify, X1 Warp (Section 5.2).
- Circle — Circle App Kit on Arc (Section 5.3).
- X1 Core — XP rewards reporting (Section 4.11).
- mxroute — email delivery for support and deletion requests (Sections 4.8 and 11).
- Browser push services — delivery of web notifications (Section 4.10).
- Google Firebase Cloud Messaging and Firebase Installations — delivery of Android App notifications, as our service provider: the Firebase installation ID and the notification content (Section 4.10).
- Liquidity protocols — XDEX, Degen and other on-chain programs; your interaction with them is public and direct.
- Your wallet provider — holds your keys and signs your transactions.
Our servers run on Oracle Cloud Infrastructure in the United States (us-ashburn-1, Virginia); Cloudflare's edge network is global. We do not sell personal data, and we do not share it for advertising.
9. Retention
Where a record has no fixed expiry below, it is kept until you ask us to delete it (see Section 11, Deleting your data) or until we no longer need it for the purpose described in this Policy.
| Data | Retention |
|---|---|
| Our server request logs | Up to 1 month |
| Rate-limit records containing IP / wallet / installation ID | 1 day |
| Compliance records for private-balance transactions (wallet, token, operation, time, public amount) | 30 days |
| Compliance refusal log lines (wallet, reason, country / recipient / matching list entry) | Up to 1 month, with our server logs |
| Hashed refresh tokens | 30 days after expiry (7-day tokens) |
| Android App notification delivery records | 30 days |
| Transfers an installation asked to be notified about | 7 days |
| Android App / Extension installation records (installation ID, public key, integrity labels, version, country, Privy ID, wallets) | Until you ask us to delete them or until we no longer need them for the purpose described |
| Consent records | Until you ask us to delete them or until we no longer need them for the purpose described |
| Web-push subscriptions, watched wallets, price alerts | Until you unsubscribe, or until you ask us to delete them |
| Android App push registrations (Firebase installation ID, installation ID, notification settings, watched addresses) | Until you turn notifications off, sign out or delete your data in the app, Google reports the token as no longer valid, or you ask us to delete them |
| Incoming-transfer scan position per watched address (last transaction checked) | 30 days after the address is last checked |
| X1ID links | Until you unlink, or until you ask us to delete them |
| Fiat-provider order status (pseudonymous) | 400 days; MoonPay cash-out deposits 60 days |
| Indexed public swap and order data | 14 to 180 days for most tables; router volume statistics and the limit-order book have no fixed expiry (public on-chain data) |
| Signed Arc limit orders | Until you ask us to delete them or until we no longer need them for the purpose described |
| Referral visitor IDs | Until you ask us to delete them or until we no longer need them for the purpose described |
| Developer API-key requests and keys; x402 payment records | Until you ask us to delete them or until we no longer need them for the purpose described |
| Developer API usage records | 400 days |
| Support and deletion-request emails | Until you ask us to delete them or until we no longer need them for the purpose described |
| Data held by Cloudflare, Privy, Google, Fiat Providers, bridge providers, Circle, X1 Core, RPC providers | Under each provider's own schedule |
| Public blockchain data | Permanent; outside our control |
10. Your choices and rights
You always control your keys (which never leave your device) and whether you transact (nothing happens until you sign). You can stop using the Interface at any time, revoke notification permission, log out, clear your browser storage, or uninstall the Android App or Extension.
You can ask us to access, correct, or delete personal data we hold about you. Because most of our records are keyed to an installation ID, a Privy user identifier, or a wallet address rather than to your name, we may ask you to prove control of the relevant installation, sign-in, or wallet before acting on a request.
To make a request, use the deletion options in Section 11 or email support@fortiblox.com. We respond to requests sent to support@fortiblox.com as soon as we can.
For data held by a third party — a Fiat Provider, Bridge Route Provider, Circle, Google, or Privy — contact that party, which is responsible for it. X1ID is our own service: send requests about it to us. We cannot alter or erase anything recorded on a public blockchain.
11. Deleting your data
Android App: open Settings → Delete my data. This deletes, on our servers, the installation's record (replaced by a deleted-installation marker holding only the random installation ID, its public key and a "deleted" flag — no device verdict, wallet, Privy identifier or country — so the ID is never reused), revokes its sign-in sessions, and deletes the consent records made from that installation and its push registration. The installation cannot be used again; reinstalling registers a new one. Records linked to your Privy sign-in elsewhere (other installations, X1ID links, web-push subscriptions) are not removed by this option; ask for them with the form below or by email.
Web App, Extension, or if you no longer have the app: submit a request at https://app.fortiblox.com/delete-account. The form asks for your contact email and, optionally, the wallet addresses and Android installation ID concerned and any details. It is sent to our support mailbox; we reply to the email you give and may ask you to confirm that the wallet or installation is yours before we act. You can also email support@fortiblox.com.
Your Privy account. Our server cannot delete a Privy account automatically today. When you ask — with the in-app option while signed in, with the form, or by email — our support team deletes the account in Privy. Deleting your Privy account permanently deletes any Privy embedded wallet created for it: export its private key (or move your funds) first. Self-custody wallets created or imported on your device are not affected by deleting server data.
What deletion does not cover:
- Server logs and rate-limit records are not individually deleted; they expire automatically (up to 1 month and 1 day respectively), as do revoked refresh-token hashes (30 days after expiry), notification delivery records (30 days) and transfers you asked to be notified about (7 days).
- Pseudonymous fiat-order records expire after 400 days (MoonPay cash-out deposit records: 60 days).
- Data held by third parties (Section 8) and public blockchain data.
- Your wallet and funds. Deleting your data does not affect your on-device wallet. Make sure you have your seed phrase backed up before uninstalling — we cannot recover it.
12. International transfers
We are based in the United States, and our servers run in the United States (Section 8). Our providers — including Cloudflare, Privy, Google, Coinbase, Stripe, Transak, MoonPay, Circle, Alchemy, Helius and Covalent — operate in other countries too. If you use the Interface from outside the United States, your data will be processed in the United States and in other countries where our providers operate.
13. Children
FortiSwap is not intended for children. The Interface is not directed at, and must not be used by, persons under eighteen (18) years of age (or the age of majority where you live, if higher), consistent with our Terms of Service. We do not knowingly collect data from children. If you believe a child has used the Interface, contact support@fortiblox.com.
14. Security
Installation keys stay on your device; refresh tokens are stored only as hashes; requests from the Android App and Extension are signed; connections are encrypted with TLS; access to our databases is restricted. No system is perfectly secure. Please report vulnerabilities to security@fortiblox.com.
15. Changes to this Policy
We may update this Policy to reflect changes in the Interface or in applicable law. Material changes will be posted at app.fortiblox.com/privacy with a revised effective date and a change-log entry. When a new version takes effect, the Web App asks you to accept it the next time you sign in, and the Android App asks you to accept it before you continue.
16. Contact
- Operator: FortiBlox Labs LLC
- Email (questions, privacy and data requests):
support@fortiblox.com - Security:
security@fortiblox.com - Data deletion: https://app.fortiblox.com/delete-account
- Governing law: as set out in our Terms of Service (State of Wyoming, USA).
Change log
| Date | Version | Summary |
|---|---|---|
| 2026-07-24 | 1.0 | Initial published version. Privacy Policy for the non-custodial DEX aggregator at app.fortiblox.com. Documented the no-account, no-PII, no-KYC, no-fiat posture; the public nature of wallet-address and on-chain data; Cloudflare edge/security logs and the cf-ipcountry geographic signal; minimal application request data; third-party protocol reliance; minimal retention; and user rights. |
| 2026-07-30 | 2.0 | FortiSwap rebrand + Stripe Crypto Onramp data flow. Product presented as FortiSwap, operated by FortiBlox Labs LLC. New Section 4 documents the on-ramp data flow: Stripe collects and processes the user's payment and identity (KYC) data directly under Stripe's own privacy policy, and FortiSwap does not receive it; buy-side only, no off-ramp/payout data flow. Contact email updated to support@fortiblox.com. Stripe added to the third-parties list; retention and rights sections note that on-ramp data is held by and exercised against Stripe. No account, no PII, no KYC, non-custodial posture preserved. |
| 2026-07-31 | 3.0 | Privy sign-in + embedded-wallet data flow disclosed. New Section 5 documents the optional Privy-powered sign-in: email one-time-passcode, passkey, or social sign-in (Google, X, Discord, GitHub, Telegram) data is collected and processed by Privy directly under Privy's own privacy policy; for users without a wallet, Privy provisions a user-owned, non-custodial embedded wallet whose key FortiSwap never holds or can recover (no session signers, no delegated actions, no custodial mode); FortiSwap receives only the public wallet address and authorised transactions. External-wallet connection does not involve Privy. Summary, Section 2 (email carve-out), Cookies, Third-parties list, Retention, and Rights updated for Privy; downstream sections renumbered (old 5–12 → 6–13). Scope covers the login methods actually implemented: email, passkey, social (Google, X, Discord, GitHub, Telegram), and external wallet. |
| 2026-08-22 | 4.0 | All Fiat Providers (Stripe, Coinbase, Transak, MoonPay), the off-ramp, and the cross-chain bridge (Rango, MoonPay Trade) disclosed. Section 4 rewritten from "Stripe, buy-side only" to the Fiat-Provider data flow in both directions: the provider collects payment, payout, and identity data directly under its own privacy policy; FortiSwap receives only transaction identifier/status/amounts/settlement hash/wallet address and a bounded failure code, kept against a pseudonymous keyed-hash reference derived from sign-in; identity-check outcomes are not stored. MoonPay disclosed as merchant of record, with the keyed IP-address hash included in the signed MoonPay widget link (MoonPay's IP-matching requirement; no clear-text IP sent by us). Settlement on Solana with the Solana ↔ X1 leg a separate user-signed Warp step. New bullet for the cross-chain bridge: Rango and MoonPay Trade (Swaps XYZ Ltd, a MoonPay company) receive wallet addresses and route parameters only; transaction hash may be registered for delivery tracking; in-flight transfers recorded in browser local storage. Summary, Section 2 (no-accounts sentence qualified by the pseudonymous transaction record), Section 6, Cookies, Third-parties list, Retention, and Rights updated accordingly. No renumbering. Superseded the v2.0 "buy-side only / no off-ramp" statement. |
| 2026-08-22 | 4.1 | Sign-in methods and requirement stated consistently. Section 5 corrected from "email or Google" to the implemented set — email one-time passcode, passkey, or a social provider (Google, X, Discord, GitHub, Telegram) — with external wallets connected directly outside Privy; Summary, Section 5, Section 8, and Section 10 now state that sign-in is optional for swaps and the cross-chain bridge but required for the fiat on-ramp and off-ramp (sessions and provider quotes are minted only for a signed-in user and keyed to the Section 4 keyed-hash reference; no FortiSwap account is created; we keep the reference, not the Privy identifier or email). No renumbering. |
| 2026-09-11 | 4.2 | Arc network and Circle (App Kit, StableFX, CCTP) data flow disclosed. Section 4 retitled to include "Circle products on Arc" and gains a bullet: where the Interface offers Arc (Circle's blockchain, testnet only), a swap settled through Circle App Kit or (sandbox only) Circle StableFX, or a USDC transfer through CCTP, is requested by our server under FortiBlox's API key and sends Circle only the wallet address, token addresses, amounts, and slippage setting (for CCTP, the burn transaction hash) from our server's IP address; Circle may log requests; no identity data is involved; Circle's privacy policy governs Circle's use; in-flight CCTP transfers are kept in browser local storage; StableFX production would require FortiBlox's own institutional onboarding with Circle, which has not occurred. Summary, Section 3 (Arc as a public testnet), Section 6 (request data forwarded to Circle), Section 8 (new Circle third party; X1 and Arc RPC providers; Arc pools), Section 9 (Circle retention), and Section 10 (rights against Circle) updated. 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. |
| 2026-10-16 | 5.0 | Rewritten to match what the code actually collects, and extended to the Android App and the browser extension. New per-surface data table (Web / Android / Extension) and Section 4 subsections for: request logs (no IP/UA/wallet in our access log; up to 1 month), rate-limit records (raw IP/wallet/installation ID, 1 day), Android installation ID + Keystore public key + Google Play Integrity verdicts + version + country, extension installation records, hashed refresh tokens, consent records, the seed-derived active-address scan (up to 22 public addresses, not stored), the transaction security scan (Web App + Extension; not stored, no vendor; Android checks on-device), Android permissions and SDKs (no FCM/analytics/crash/ads; Keystore attestation chain not sent; SMS-OTP Privy sign-in; no bridges or Buy/Sell in version 1), Extension permissions, on-device storage and direct public-RPC calls, support form (name/email via mxroute; the "subscribe" checkbox is recorded with the message only — no marketing email), developer API-key form, web push, referral visitor IDs, X1 Core XP reporting (wallet, signature, tokens and amounts; no opt-out setting), and X1ID. Corrected v4.2 statements that we collect no email, keep no per-user records beyond ramp status, keep only a hashed Privy reference (the Privy user identifier is stored with installation, consent, push and X1ID records), use no tracking (Cloudflare Web Analytics now disclosed, configured to exclude wallet-address pages, Web App only), that logs age out under the provider's practices (now a stated retention table; records without a fixed expiry are kept until deletion is requested or they are no longer needed), and that Arc is offered as a testnet only. Disclosed raw-IP forwarding to Coinbase, Stripe, Transak and Houdini, and the Coinbase guest-checkout phone/email relay. Added bridge providers Squid, deBridge, Allbridge, Houdini, ChangeNOW, THORChain; RPC/data providers Helius, Alchemy, GoldRush; Google, mxroute, X1 Core; server hosting (Oracle Cloud Infrastructure, us-ashburn-1, United States). New sections: Deleting your data (https://app.fortiblox.com/delete-account and Settings → Delete my data in the Android App; Privy account deletion through support; embedded-wallet warning), International transfers, Security. Sections renumbered (old 4→5, 5→6, 6→4.2, 11→13, 12→15, 13→16; new 4, 11, 12, 14). Aligned with Terms of Service 5.7 and the AML & Sanctions Statement 3.3: the compliance record for private-balance transactions is described accurately (one record per transaction built, an hourly limit of 30 by default, kept up to 30 days; the public amount only for moves into or out of a private balance, none for private transfers), and compliance refusal log lines (wallet, reason, country / recipient / matching list entry; up to 1 month) are disclosed; the custody statement carries the on-chain order and X1ID gift escrow carve-outs; X1ID is described as a FortiBlox service rather than a third party; Circle StableFX and the Interface's own CCTP feature are stated as not offered. |
| 2026-10-17 | 5.1 | Android App notifications disclosed. The Android App now offers optional push notifications through Google Firebase Cloud Messaging. Section 4.10 describes what the app sends when you allow them (Firebase installation ID, installation ID, notification categories, up to 10 watched addresses, the Privy link when signed in, and swap/bridge references you ask to track), the public chain reads our server makes for watched addresses, what Google processes as our service provider (the Firebase installation ID and each notification's content), and how they stop (turning them off, signing out, or deleting your data). The per-surface table, the Android SDK list (Section 4.4; it previously said the app contains no Firebase Cloud Messaging; it now names FCM and Firebase Installations, still with no analytics, crash-reporting or advertising SDKs), the third-party list (Section 8) and the retention table (Section 9: Android push registrations; incoming-transfer scan position, 30 days) are updated to match. No other change. |
| 2026-10-25 | 5.2 | Extension and Android App updates. A1: the Extension's direct public-RPC calls now name the public Solana node (Section 4.5). A2: Extension collectible (NFT) pictures load through our image service; we do not store them, and Cloudflare may cache a copy for up to 7 days (Section 4.5). A3: FortiSwap Link wallet transfer between the Android App and the Extension through an encrypted, memory-only relay (sessions at most 10 minutes) (Section 4.5). A4: optional auto-approve settings and log stay on your device; approved requests are still safety-scanned (Section 4.5). A5: Chrome Web Store User Data Policy / Limited Use statement (Section 4.5). B1: Android App permissions updated — notification restart after reboot, camera only for QR scanning (processed on device), and nearby-device (Bluetooth) only for a Ledger; no location (Section 2). B2: Buy/Sell in the Android App through Coinbase, MoonPay, Stripe and Transak, with a Privy sign-in or the app installation as the identity (Section 5.1). B3: the seed-derived scan covers up to four wallet layouts, up to 100 accounts each on request, in batches of at most 22 addresses; the Android "total across accounts" reads each account's portfolio (Section 4.6). |
| 2026-11-06 | 5.3 | Relay, LI.FI, Jupiter and 0x named as route providers. Section 5.2 now lists what these providers receive and describes Relay's on-chain data collection and address screening. Section 8 updated to match. |
Last updated: 2026-11-06
To delete data associated with FortiSwap, see Delete your data.
