← Back to trading

Your privacy.

We use first-party analytics to understand visits and improve Purple Hands and Yellowhands. A random ID stored in this browser tab groups page views and simple actions. It expires when the tab session ends. Traffic records are retained for 90 days.

We record the brand, public page path (without query strings or fragments), approximate device size, country when supplied by our host, and referring website domain. We do not store IP addresses, full referrer URLs, page query strings, form inputs, signatures or private keys in our first-party analytics database.

Verified public wallet addresses and public transaction data are stored separately for operational reporting: deposits, trades, balances and fees. Detailed financial records are retained for authorized administrators. The public leaderboard displays wallet addresses, closed-trade counts and aggregate realized net P&L for verified trades opened through the current brand. It excludes wallet balances, deposit records, open positions and browsing data. Traffic opt-out does not disable transaction reconciliation.

Traffic collection honors Global Privacy Control and Do Not Track. You can also turn it off for this browser on this domain:

Operational diagnostics

On the owned exchange, we retain unsampled backend request records, transaction attempts and onchain financial events for troubleshooting. Browser action diagnostics use a random tab ID and attempt ID, public wallet/transaction identifiers when available, action stages and bounded error categories. Funding diagnostics record asset lookup, quotes, wallet confirmation, bridge submission, arrival checks and loading funds, with elapsed time and a journey identifier that can persist in this browser for up to 24 hours. Browser reports are unverified and may be incomplete when offline or blocked. Raw browser, HTTP and executor-error diagnostics retain 30 days; financial transaction records persist. These records are visible only to authorized administrators and are never sent to Google or Clarity. No signing payloads, authentication tokens, private keys, email addresses or raw form contents are collected. Operational diagnostics are separate from optional traffic analytics.

Email login & embedded wallets

Privy provides email verification, account recovery and an embedded EVM wallet. Your email and login verification are handled by Privy. Use the same login to return to your wallet on either brand. Existing extension-wallet balances remain separate; creating an embedded wallet does not transfer them.

We do not send email addresses, login codes, authentication tokens or private keys to our analytics. Optional external analytics stops before Privy loads. Privy privacy policy.

Pilot invitation requests

You may submit your email address and a wallet address verified by a message signature. Older requests may also contain optional names, notes or Telegram handles. With your consent, we send those details to the pilot reviewer’s private Telegram chat. We keep contact details in our request database for 30 days; Telegram messages follow the reviewer’s chat retention settings. Wallet address, request decision and review audit remain operational records. We do not send application details or signatures to analytics. Approval requires a separate onchain guardian confirmation.

You may optionally connect Telegram using a private, one-time link after applying. Pressing Start in @yellowhandsbot links your Telegram user ID, chat ID and username (if present) to your request. We use this connection for decision updates and two-way messages with the team. Send /stop to remove this contact connection; it does not cancel your application. Connections expire 30 days after the application. Undelivered message text is held for up to 7 days and removed from our queue after delivery. Telegram keeps delivered messages according to its settings. Private links expire after 20 minutes and are not sent to analytics.

Telegram support

You can contact @yellowhandsbot before applying or signing in. Messages, screenshots and other supported attachments you send are forwarded to the team’s private admin chat. The owner can reply through the bot. Telegram user/chat IDs and message references are used for delivery; support queues retain references for up to 7 days and reply mappings for 30 days. Files stay on Telegram and are not downloaded to our servers. Send /stop to stop forwarding and notifications; /start support reconnects support. A minimal disconnected-chat record remains to honor this preference. Delivered messages follow Telegram’s retention settings. Do not send secrets or login codes.

Optional Google Analytics & Clarity

With your permission, Google Analytics measures visits on both brands and Microsoft Clarity provides heatmaps and replay of the public page. These providers process browser/device, interaction and network data and may set analytics cookies. Advertising storage and personalization are disabled. The private command center is excluded.

External analytics stops when you open a dialog, connect a wallet or open the public leaderboard, and account text is masked. We do not deliberately send wallet addresses, transaction hashes, balances, signatures or trading keys to these services. The built-in financial command center works independently.

These optional scripts load only after you allow analytics, and remain off when your browser sends Global Privacy Control or Do Not Track. Preferences apply separately to this browser on each domain. Disabling traffic analytics above also disables these services. A running replay stays stopped until a new page load.

Google privacy · Microsoft privacy