Privacy Policy
Version 3 — current wallet, cloud and USDC beta · 15 October 2026
This notice describes the current Hero Stars game and its optional wallet/cloud services. Guest play remains free. The beta supports real Solana Mainnet USDC purchases when the server enables payments; these are not Devnet test payments.
Guest play and device storage
The game stores your nickname, heroes, Power Levels, Account XP, Coins, Hero Credits, Gems, chest inventory, Season Pass progress, language and device settings. Android uses local preferences. Web uses browser storage and IndexedDB for saves and caching. Clearing app or site data removes the guest save; it is not automatically backed up to Hero Stars servers. Downloaded game content may also be cached locally.
Wallet sign-in and cloud profile
If you connect a wallet, its public Solana address identifies your cloud account. The backend stores account creation and login times, display name, language, selected and owned heroes, Power Levels, XP, balances, inventory, Season Pass progress, claims and entitlements. It stores match identifiers, mode, hero, start/completion times and reported results used to validate rewards, as well as economic action identifiers and their results. These records support account recovery, synchronized progression and duplicate-reward prevention; the match-reward service does not record a video or a continuous movement history.
Authentication uses a wallet-signed challenge, valid for two minutes and usable once. The backend stores the challenge and a hash of the session token. A game session expires after 30 minutes; the client bearer token is held in memory. Expiry stops authorization, but does not itself delete database records. Disconnecting clears the game session and requests server revocation when reachable. The separate guest save is not merged with cloud balances.
On Android, Hero Stars opens Phantom using wallet links and receives encrypted callbacks; Web uses the connected wallet provider. Connecting or signing in is separate from approving a payment. Hero Stars never asks for or stores your wallet recovery phrase or wallet private key. Android stores the app's own wallet-transport/session state and pending callback data using Android Keystore-backed encryption. These app transport keys are not your wallet's signing keys. A bounded guest import is optional and allowed once per wallet; local paid entitlements are not imported.
USDC purchases and public blockchain data
When you buy Gems or another offered digital product, the backend records an order identifier, your public wallet address, the selected product and its reward terms, network, token mint, recipient, amount, reference, status and timestamps. It keeps prepared and signed transaction data as needed by the current payment/recovery flow, plus the public transaction signature and fulfillment result. A signed transaction can be broadcast to execute the specific payment you approved; it is not your private key or permission for an arbitrary new payment.
Pending order identifiers, transaction signatures and signed transaction data may also be saved on-device to resume an interrupted payment. Successful recovery/fulfillment clears the relevant pending client proof. The server verifies the transaction and finalized on-chain result before granting the purchase. Processed transaction records and atomic order fulfillment prevent the same payment from being credited twice.
Solana records, including public addresses, token transfers, transaction signatures and an order-reference memo, are public and cannot be erased by deleting a Hero Stars account. The off-chain order links this public payment to your game account. Your external wallet and Solana RPC services process the information needed to sign, broadcast and query the transaction under their own policies.
Service providers and technical records
Vercel hosts the website, Web game and API. The backend uses Supabase PostgreSQL for cloud accounts, profiles and payment/security records; wallet authentication is handled by the Hero Stars backend. Cloudflare R2 delivers remotely downloaded update content and APK files. These delivery services receive network requests and may process IP addresses, request metadata and operational logs. Solana RPC services receive public blockchain queries and approved transactions.
The API uses a hash of the request IP address and wallet/account rate-limit identifiers to limit abuse. Security and payment diagnostics include stage/error codes, order identifiers, message hashes, mismatch field names, public transaction signatures, confirmation and credit status. The current compact diagnostic logger does not log raw signed transactions, wallet secrets or full request bodies; operational transaction data described above is stored separately for payment handling. No advertising or behavioral analytics system was added by these wallet/cloud services.
Provider information: Vercel, Supabase, Cloudflare and Phantom.
Retention and deletion
The current service has no configured automatic fixed-period purge for cloud profile, order, security or anti-replay records. The two-minute challenge, 30-minute session and 20-minute payment-order validity windows are authorization/payment validity limits, not promises of physical deletion. Provider log and backup retention is separate; this notice does not promise a verified fixed deletion period for those copies.
In Settings → Wallet & Cloud Account, account deletion requires a fresh wallet signature. It removes the account, cloud profile, balances, claims, sessions, account-linked match/economy/order records, authentication challenges and wallet-linked audit records from the active database. Minimal anti-replay records remain: processed public transaction signatures/order identifiers and a stable SHA-256 wallet migration receipt. A known public address can be matched to its hash, so this receipt is pseudonymous, not anonymous. IP-derived technical rate-limit records and provider logs are not necessarily removed by account deletion. Public blockchain records remain.
Local guest saves and device settings remain separate. Use Android app-storage settings or browser site-data controls to remove them. Your operating system may keep a backup according to its settings. Account deletion does not delete your external wallet or undo an approved blockchain transfer.
Requests and contact
For access, correction, deletion or questions, contact Sup_rivalcrest@outlook.fr. Provide only the information needed to identify the issue, such as a public order or transaction reference; never send a recovery phrase, private key or session token. This notice describes the audited implementation. Publisher review of applicable legal obligations, retention limits and provider arrangements remains necessary; this technical update is not a certification of legal compliance.