Sub-Processor Register
Version 2.1.0 · Last updated: November 2026
This register accompanies the Baysart Privacy Policy and Cookie Policy. It lists the categories of processors that the Privacy Policy names and the purpose for which each receives personal data.
Processor categories
Some processors may process data outside Azerbaijan. Such international transfers are carried out only on the basis of appropriate safeguards.
- Identity Verification Provider — to carry out KYC verification.
- Card Payment Processor — to process card payments.
- Settlement/Liquidity Partner — to execute orders (in anonymized form).
- Infrastructure Providers — for blockchain node/RPC, email, push-notification and analytics services.
- Advertising Platforms — only if you switch on ads measurement, to measure and target our advertising (hashed contact details, account identifier, transaction amounts).
Other providers named in the Privacy Policy
- Analytics provider — receives in-app events and device identifiers unless you turn analytics off in Settings > Privacy.
- Crash-reporting provider — receives crash reports and your account identifier to find and fix stability problems.
- Push, email, monitoring, RPC, pricing, bridge, protocol and settlement providers — receive only the data reasonably required for their function.
Named providers
The providers below are the ones Baysart uses today, grouped by the roles above. Providers in product and protocol roles process data only while that product is enabled for you. We update this register and notify you when a provider is added or replaced.
Identity Verification Provider
- Didit — liveness check and identity-document verification (KYC).
Card Payment Processor
- CibPay — card top-ups, card payouts and saved cards; Baysart never receives the full card number.
Settlement and Liquidity Partners
- Bitfinex — liquidity and treasury for buys and sells, stablecoin reserve custody and price reference (no user identity).
- Li.Fi — swap and bridge routing (no user identity).
- Jupiter — Solana swap routing, token data, lending, perpetual and prediction-market transactions (public wallet address, amounts, transaction data).
- Kraken — request-for-quote venue for tokenized products where enabled (anonymous quote and fill data).
- Chainflip and THORChain — cross-chain swap networks where enabled (public deposit address, amounts, transaction data).
- SunSwap — TRON token conversion where enabled (public transaction data).
Third-party protocols and digital-asset products
These protocols receive your public wallet address, the asset, the amount and on-chain position data.
- Aave — lending: supply, withdraw, borrow and repay.
- Sky — USDS savings vaults.
- Ethena — USDe staking.
- Morpho — curated vaults.
- Kamino — Solana lending.
- xStocks ecosystem and issuer infrastructure — market data and on-chain settlement of tokenized tracker products.
Infrastructure Providers
- Hetzner — application and database hosting in the EU (Germany, Finland).
- Alchemy — EVM node access.
- Blockstream and Baysart's own Bitcoin node — Bitcoin data and transaction broadcast.
- Solana public RPC, TRONGrid, TON Center and public chain gateways — blockchain data and transaction broadcast (public address, transaction data; some TRON and TON reads come directly from the app).
- Public EVM RPC operators (Optimism, Base, Arbitrum, Avalanche, BNB Chain, Polygon, Linea, Plasma, Tempo, Robinhood Chain) — balance reads, normally through Baysart servers; directly from the app only when that proxy is unreachable (the operator then sees your IP address and public wallet address).
- Hyperliquid — perpetuals market and account data where enabled.
- FreeSend — transactional email (one-time codes, notices).
- Firebase Cloud Messaging (Google) — push notifications.
- Firebase Crashlytics (Google) — crash and diagnostic reports.
- Sentry — error and performance monitoring.
- AppsFlyer — install attribution and app analytics (no financial data or wallet addresses; off when you turn analytics off).
- Meta and Google advertising services — conversion measurement, only if you switch on the separate ads-measurement consent (off by default).
- Google Drive app-data storage — your encrypted wallet backup, only if you choose it (neither Baysart nor Google holds the key).
- Chatwoot — customer support conversations.
- Market and FX data providers — public prices and rates (no user data).
No sub-processor receives private keys, recovery phrases, PINs or decryption keys.
Technologies used by the wallet.baysart.com website itself are described in the Cookie Policy, section "This website".
