Public wallet information
When you connect a wallet, Kaverload reads the selected public wallet address, current chain, BOT balance, and configured Kaverload Registry state. Wallet addresses, contract calls, transaction hashes, blocks, and timestamps are public blockchain information.
Information we do not request
Kaverload does not request, receive, or store your seed phrase, private key, keystore, or wallet recovery material. Never provide those credentials to any website or person claiming to represent Kaverload.
Wallet providers
Your injected wallet and, if configured later, WalletConnect or another connection provider operate under their own terms and privacy practices. They may process network, device, or connection information independently of Kaverload.
Local storage
Kaverload stores only non-sensitive pending transaction recovery fields in your browser: transaction hash, wallet address, chain ID, and submission time. These fields let the interface resume receipt checking after a refresh. They are cleared after a confirmed or reverted receipt. Disconnecting the interface does not erase public blockchain records.
Basic analytics and logs
The deployed site may use basic hosting analytics and operational logs to understand aggregate usage and diagnose failures. This release does not use those systems to create a Kaverload identity profile. Hosting, RPC, explorer, and wallet providers may maintain their own logs.
Cookies
Kaverload does not use an application account or advertising cookie in this release. Infrastructure providers may use strictly necessary mechanisms to deliver and protect their services.
Requests and changes
Public blockchain data generally cannot be deleted by Kaverload. Browser-local pending data can be removed through browser storage controls. This policy may change as features and providers change.
No project contact address has been configured. A contact method must be added before formal public launch.