This page describes the current ChainCheck product flow. Operator identity, jurisdiction and final commercial terms must be completed before public paid launch.
01What ChainCheck processes
ChainCheck uses the public wallet address you submit or connect, the selected blockchain network, public on-chain transaction data returned by configured providers, and your interface language. Private keys and seed phrases are never requested by ChainCheck.
02Wallet connections
Wallet connections are handled through compatible browser wallets or WalletConnect. A connected session can later be used for a separate Sign / Approve flow. Your wallet displays the exact request before you confirm it. Wallet providers and WalletConnect may process connection metadata under their own policies.
03On-chain data and reports
Recent transaction history can be loaded from configured public blockchain providers such as explorer APIs or TronGrid. On-chain activity is presented separately from any demo risk layer. If labelled AML intelligence is not connected, sanctions, mixer and similar sections must not be interpreted as live screening results.
04Service records and payments
The service may create short-lived server records required for wallet verification, report access and payment flows. Subscription checkout can include a payment address/QR option and a wallet-based authorization flow. Final retention periods, billing processors and payment monitoring must be documented by the operator before production billing is enabled.
05Cookies and local state
The aml_locale cookie stores the selected interface language. Session storage can temporarily cache recent on-chain results to avoid unnecessary repeated requests during the current browser session. Browser and wallet storage can be cleared using their respective controls.
Clear data labels and clear wallet prompts are part of the product.