Privacy Policy

This policy covers the Market Calls iOS app, including its wallet, trading and Turbo features, and the Market Calls Android app (see Android and Sign in with Solana), operated by Boole Markets. It is published at calls.boole.markets/privacy. Our public and interactive websites have a separate website privacy policy; marketcalls.app has its own marketing-site policy.

Account, conversation and device information

We process text, token identifiers, public links and microphone audio you submit; account and session identifiers; app installation identifiers, app version and device information; market searches and app interactions; and sign-in and activity timestamps. Sign in with Apple currently requests no name or email scopes and provides a provider identifier. Sign in with Google provides your email address and its verification status, which we store with your account. An email address you voluntarily provide for support is also processed. We do not ask Google for your contacts, calendar or files.

For notifications, we process your push device token, preferences, device time zone, suggested and attempted notifications, Apple's acceptance or error response and notification taps. Apple's acceptance does not prove that a notification was displayed or read.

Security and wallet activity

We process technical request information, including IP addresses and timestamps, and information about wallet setup, deposits, transfers, withdrawals, trades, failed requests, network costs and gas sponsorship. We may associate account, installation, wallet and network signals to detect linked abusive accounts, protect sponsored funds, apply limits and investigate fraud. An IP address can be shared by unrelated people; restrictions or suspected errors can be raised with Support.

How we use information

We use information to authenticate you, provide conversations and market data, display your balances and history, carry out your instructions, reconcile uncertain transactions, prepare and deliver opted-in notifications, measure product use and advertising performance, investigate failures and abuse, and respond to support and privacy requests. Wallet and trading information may be included in the broker's AI context when you use account-aware conversation features, including questions about Turbo positions.

AI and speech providers

Your submitted text, token identifiers, public links, microphone audio and relevant conversation or account context may be processed by OpenRouter and the model providers it routes to, Deepgram, and xAI to transcribe speech, generate responses and speak replies. Their processing is subject to their own service and privacy terms. We do not send private keys or seed phrases as AI context.

Advertising measurement and your tracking choice

The iOS app includes the Meta SDK. It sends app activation/open events and an onboarding-completion event, together with technical app, device and request information, to help measure installs and advertising performance. The SDK is initialized when the app launches; declining the tracking prompt does not mean that all app-event measurement stops. Access to the advertising identifier and tracking across other companies' apps or websites is subject to Apple's App Tracking Transparency permission. You can change that permission in iOS Settings → Privacy & Security → Tracking. Our explicit Meta event calls do not include your conversation text, wallet balances or Turbo orders. See Meta's Privacy Policy.

Android and Sign in with Solana

The Android app processes the conversation and technical information described in this policy. If you sign in with Solana, your wallet signs a sign-in message and we receive its public address, the signed message and its signature. We verify the signature and derive an account identifier from the address. The sign-in account record stores that derived identifier and sign-in timestamps; it does not store the submitted wallet address, message or signature. Sign in with Solana does not provide an email address or authorise a trade or transfer, and we do not receive your wallet's private key or seed phrase. The wallet app and the Solana dApp Store have their own terms and privacy practices.

Android diagnostics about calls and screens carry the app platform, app version and a randomly generated installation identifier, not the device advertising identifier. The app's Delete account and data action also applies to the account created by Solana sign-in, subject to the wallet and retention limits described below.

Trading and wallet information

If you use trading, we hold your public wallet addresses, account-to-wallet mapping and Turnkey sub-organisation identifier; balances and holdings; trade instructions, quotes, fees, status and transaction hashes; deposits, withdrawals and transfers; and position and realised-result history. Optional Auto Buy and copy-trading features add their settings, separate-wallet details and execution records; Auto Buy may also create recorded purchase summaries.

Your main wallet's private key is managed by Turnkey, not stored by our application server. We do not ask you to submit a seed or recovery phrase. Optional delegated features can retain scoped signing credentials as described in the Terms. Signed transactions and authorisation records are different from private keys and may be retained to submit or reconcile an instruction you approved.

Turbo, Cardboard and Paper.trade

Turbo currently connects to Cardboard on Solana and uses real funds. The separate Paper.trade/PaperTrade integration is not currently enabled for Turbo. If another venue is offered, the app must identify it before you authorise its use. A product name containing “paper” does not make live trading simulated.

For Turbo we process the owner wallet and trading-account identifiers; USDC transfers; market, direction, margin and leverage; entry, close and liquidation information; estimated and settled profit or loss; fees and queued claims; and operation identifiers, timestamps, approval/signature records, transaction hashes and diagnostic status. We retain encrypted admission and transaction material where needed to complete or reconcile the exact approved operation. Account and market data are also read from Cardboard and Solana to refresh the interface and prevent duplicate or inconsistent actions.

Cardboard and its relayer receive wallet addresses, authentication/admission proofs and the instructions and signed transactions needed to execute and report your actions. Turnkey processes signing authorisations. Helius and other blockchain node providers receive addresses and transaction or account queries. If Paper.trade is enabled and you choose it, it and its infrastructure would receive the equivalent information needed for that venue. These providers may also receive technical request information. We do not send your Google email address to Cardboard as part of a Turbo trade.

Other trading providers include Jupiter, Relay and, where used, Hyperliquid; market-data providers include DexScreener and other venues queried for token information. Providers have their own terms and privacy practices. You can review the current venue through Cardboard.

Public blockchain records

Wallet addresses and confirmed transactions, including Turbo funding and trading activity, are publicly observable and may link your wallets and activity to one another or to you. Public blockchain records cannot be erased by account deletion or a privacy request. Third-party indexes and venue records are outside our direct control.

Support and operational alerts

Support requests, feedback and content reports are sent to our private Slack workspace for operator review. Operational alerts may include an operation identifier, market, action, leverage, timing and an error category to help resolve a failed or stalled Turbo action. Support messages include a reply address if you supply one. Our server copy of support messages is kept for up to 90 days; Slack retains its copy according to our workspace settings. Do not put passwords, private keys or seed phrases in a support message.

Retention and account deletion

We generally keep conversations, account history, notification suggestions and delivery records for as long as your account exists, with some older material removed earlier. Ordinary live-call audio is processed in transit; recorded features such as Auto Buy summaries are stored separately. Shared items awaiting the iOS app are stored in its shared container and items older than 30 minutes are discarded when it next checks.

Delete account and data in Settings removes account-linked conversation and profile data, including a stored Google email and the account created by Solana sign-in, and requests removal of supported trading-history records. It does not close positions, withdraw funds, cancel an already signed transaction or erase every financial record. Wallet mappings and records needed to recover funds or reconcile unresolved operations can remain. Turbo operation and settlement records are currently kept in a separate ledger and are not automatically erased by the account-deletion flow. Contact us to request review of remaining records; unresolved transactions, security investigations and applicable legal obligations may limit deletion. Backup and third-party copies may remain until removed under their respective retention processes.

Before deleting a trading wallet, close your positions, resolve pending actions and withdraw funds from every venue, including Turbo. Wallet deletion is a separate user-authorised action and is not a substitute for these steps. Deleting the wallet or its access credentials can make remaining funds or claims inaccessible. We cannot remove public blockchain records or recover a lost private key.

Cookies and identifiers

The service uses a secure, HTTP-only session cookie lasting up to 30 days; a private web access gate, where enabled, uses a separate cookie lasting up to 12 hours. The app stores its service session locally. These support authentication, continuity and security. Meta's SDK identifiers and advertising measurement are described separately above.

Processing locations and security

Cloudflare provides edge delivery and security and may process IP addresses, request headers and security signals. Our hosting, AI, signing, analytics and support providers may process information outside your country, including in the United States. Applicable protections and access rules can differ between countries. We use access controls and encryption for sensitive authorisation material, but no network, service or blockchain is risk-free.

Your choices, requests and complaints

You can decline AI processing, control microphone and notification permissions, change the iOS tracking permission and choose not to enable trading. Use Settings for account deletion. To request access, correction or deletion of information, ask about overseas processing or raise a privacy complaint, contact [email protected] or Support. We may need to verify your account ownership. You may also contact the privacy regulator in your jurisdiction where applicable.

Changes and contact

We update this policy as the service changes and identify the revision date above. Material changes may also be notified in the app or through available account channels. Contact Boole Markets at [email protected].