Dexter is built to stay clear about what the product sees, what it stores, and what remains under user control.
This policy explains how Dexter handles information when users visit the landing site, read the whitepaper, connect a wallet, join the reward challenge, and interact with the app.
It covers website analytics, product telemetry, support and challenge flows, and operational records used to keep the venue stable.
Dexter collects standard web analytics such as page views, device category, country, referral source, and high-level engagement events. This helps measure product adoption and improve navigation, onboarding, and program performance.
When a wallet is connected, Dexter may process the public wallet address, chain identifier, and app events tied to product usage, such as challenge page opens, challenge access activation, first trades, leaderboard views, referral actions, and feedback submissions.
If a user joins the challenge flow, Dexter may also process program records such as verification status, challenge access state, referral linkage, leaderboard standing, feedback submissions, and the linked airdrop record.
Dexter does not ask for private keys, seed phrases, or wallet secrets. Contract-bound custody and signature flows are designed so sensitive key material remains with the user wallet and does not pass through the site.
Dexter also does not treat wallet activity as private identity data by default. Wallet addresses are public blockchain identifiers, and the app uses them only to provide venue functionality, challenge records, and product analytics.
Dexter uses collected information to operate the product, secure the app, monitor feature adoption, measure funnel performance, prevent abuse, and improve execution, onboarding, season fairness, and support quality.
Analytics and product events also help answer practical questions such as which pages users enter first, which regions drive active trading, where onboarding friction appears, and which challenge paths convert into real trading activity.
Dexter uses analytics tooling, including Google Analytics, to understand how users reach the product and where they drop off. These tools may set cookies or similar identifiers to measure sessions, acquisition source, repeat visits, and product events.
Users can limit or disable cookies through browser settings, though some analytics accuracy may be reduced as a result.
Dexter may rely on infrastructure, analytics, wallet-connectivity, hosting, and security providers to operate the service. These providers may process limited information strictly to deliver the service layer they support.
Dexter does not sell user data. Information may be disclosed where required by law, needed to enforce platform safety, or necessary to protect the product from abuse, fraud, or security incidents.
Dexter keeps operational and analytics records only as long as reasonably necessary to run the service, measure performance, investigate incidents, preserve challenge and airdrop integrity, and meet legal or security obligations.
Dexter uses access controls, monitoring, guarded write paths, and contract-bound settlement design to reduce product risk. No internet service can promise absolute security, but Dexter is built to limit trust assumptions and keep control boundaries visible.
For privacy questions or requests related to this policy, users can reach Dexter through the official X and Telegram channels linked in the site footer.
