$TICKET Privacy Policy
Draft public privacy placeholder. Last updated: pre-launch.
1. Information the product may process
$TICKET may process public wallet addresses, token balances, eligibility status, reward history, payout transaction hashes, free-entry submissions, X account identifiers, X handles, submitted post URLs or IDs, campaign verification status, timestamps, and abuse-prevention signals.
2. Wallets
Wallet connection should be read-only unless a specific transaction flow is clearly shown. The product should not ask for seed phrases or private keys. Users may be offered a manual wallet-address entry option if they prefer not to connect a wallet.
3. X account data
If a user connects X, $TICKET may use OAuth or another approved flow to verify account identity and qualifying campaign posts. The system may check whether a submitted post remains public through draw verification. $TICKET should not ask for X passwords.
4. Public proof records
Reward-cycle transparency may require publishing wallet addresses, eligibility counts, excluded wallet reasons, selected wallets, payout transactions, snapshot hashes, randomness/proof data, and reserve/pool information.
5. Service providers
The product may use infrastructure providers for hosting, RPC/indexing, analytics, authentication, X verification, databases, proof dashboards, and payout automation.
6. Retention
Some records may be retained to verify eligibility, prevent duplicate free-entry claims, audit reward events, and publish proof history.
7. User choices
Users may choose not to connect a wallet and may use a manual wallet-address option if offered. Users may choose not to connect X, though X connection may be required for X-based free entries.
8. Contact
Launch contact information will be published before live rewards begin.