Wallet and blockchain data
Connecting a wallet exposes its public address to the interface. Positions, balances, approvals, and transactions are read from public blockchain infrastructure and are inherently public.
What this preview reads, what remains public, and what still requires production review.
Connecting a wallet exposes its public address to the interface. Positions, balances, approvals, and transactions are read from public blockchain infrastructure and are inherently public.
The preview does not create a username, password, profile, or proprietary offchain balance. The frontend does not ask for a legal name, mailing address, phone number, or payment card.
Hosting, RPC, wallet, and analytics providers may receive technical data such as IP address, browser metadata, request time, chain ID, public wallet address, and requested contract methods under their own policies.
Wallet libraries may use browser storage to remember connection state and preferences. You can clear site data or disconnect the wallet through your browser and wallet controls.
Blockchain transactions cannot be deleted by this interface. Even if a frontend log is removed, transaction calldata, addresses, events, and balances can remain publicly available.
This preview notice is not a substitute for a production privacy policy. Data processors, retention periods, lawful bases, rights procedures, entity details, and contact information must be finalized before launch.