CyberCharge

CyberCharge Privacy Policy

How CyberCharge handles wallet addresses, transaction records, dashboard data, local storage, and third-party service interactions.

Wallet Address Usage

CyberCharge uses connected wallet addresses as the primary user identifier for the front-end MVP experience.

Wallet addresses may be stored to create user records, link allocation records, display dashboard data, and process withdrawal requests.

Transaction Data

The platform may store transaction hashes, payment amounts, payment assets, selected networks, payment status, token contract references, and confirmation timestamps.

Blockchain transactions are public and may remain visible through third-party block explorers even if platform records are later updated.

Dashboard Data

Dashboard records may include allocations, transaction history, reward records, withdrawal requests, payout transaction hashes, and related status changes.

This information is used to help users review platform activity associated with their connected wallet address.

Cookies & Local Storage

CyberCharge may use local storage to remember language preferences and wallet connection state where supported by the user's browser and wallet provider.

Clearing browser storage or using a private browser session may reset preferences and wallet connection state.

Third Party Services

The platform may interact with wallet providers, WalletConnect/Reown, blockchain RPC providers, block explorers, Supabase, Cloudflare, and market data services.

These third-party services may process technical information according to their own privacy practices and policies.

Contact

Questions about privacy, dashboard records, or data handling can be directed to contact@tslcharge.cc.

Users should never send private keys, seed phrases, or wallet recovery information to CyberCharge or any support contact.

These documents are provided for the CyberCharge front-end platform experience and should be reviewed with appropriate professional advice before participating in any infrastructure allocation.