DATA USE · SEPTEMBER 12, 2026
Your lookup.
Your context.
Public address lookups
When you scan an address or open transaction details, Skooby sends the public address or transaction hash to the relevant data provider through its server. Bitcoin uses mempool.space; Ethereum uses BlockCypher. Market data uses CoinGecko. These providers and the hosting platform may process request information under their own policies.
Accounts, trials and subscriptions
Signing in identifies your account through ChatGPT. Skooby stores your account identifier, trial dates, subscription status and Stripe customer and subscription identifiers. Stripe processes billing details in its hosted checkout; Skooby does not collect card numbers. Your Cash App handle is not a substitute for a verified subscription.
Saved follows and AI
Wallet follows are saved in the account database and can be removed from the AI and wallet follows tab. When you request AI analysis, the public address, your question and retrieved provider evidence are sent to the configured AI provider (OpenAI or ChainGPT). OpenAI requests use store=false; ChainGPT requests have chat history disabled. These settings do not eliminate provider operational or abuse-monitoring processing. Daily analysis counts are stored to enforce plan allowances. Avoid entering private or identifying information in a question.
Token research
Token contract and mint lookups go to DEX Screener. Supported EVM contracts are also checked with GoPlus. Reports identify retrieval times and provider coverage.
Additional chain balances
When configured, Crypto APIs receives the selected public EVM address and network for confirmed native-balance lookups. Account usage counts limit provider requests.
Saved preferences
Watchlists and saved casebook addresses use localStorage in your browser. They are not synchronized by Skooby across devices. Removing an item or clearing the browser’s site data removes the local copy. A shared browser profile may expose these preferences to other users of that profile.
Exports and companion tools
CSV exports are created in the browser. Once downloaded, they are managed by you. Skooby’s companion calculators process their inputs locally; their pages explain any links that take you to another service.
Optional wallet payments
Research tools do not require a wallet connection. The separate Wallet Pay page discovers compatible browser wallets and, when you choose to connect, reads the selected public address, chain, balance, code and fee estimates through your wallet provider. Your recipient and amount remain in the page state and are sent to your wallet for preview and payment. A deliberate authorization button requests a native transfer, which requires confirmation in your wallet. Skooby does not receive private keys, recovery phrases or custody of funds. Payment addresses and transaction amounts become public on-chain if you send them.
Casino lab and purchase desk
The free blackjack demo stores only the current game in memory, with no deposits, wagers or prizes. The purchase-fee calculator runs locally; crypto purchasing is not yet open. When enabled, requesting a purchase quote sends the amount, site origin and your originating IP through Skooby’s private session broker to Transak. Skooby stores an account usage count; the broker stores short-lived request nonces, quotas and an encrypted partner token. It does not forward your Skooby account email or identifier. Transak collects the wallet, identity and payment information needed for its hosted purchase flow under its own policies. The downloadable Web3 starter is separate code, not an active Privy or Pinata account integration on Skooby.
Website operations
The application does not include advertising pixels, a mailing-list form, or application-level behavior analytics. Hosting and upstream services may still keep operational logs. External explorer and documentation links take you to sites with their own data practices.
Scope
This page describes the current application’s data flow. It is not a promise of anonymity or a statement that public blockchain data cannot be associated with a person.