Data minimization
Only information needed for approved account, security, support, compliance, or gameplay operations should be collected once real systems exist.
Privacy Overview
Privacy copy should be specific, minimal, and approved.
This static page describes privacy principles for the prototype. It does not connect registration, payment, KYC, analytics dashboards, or real account systems.
Future account data
Approved account flows may request profile, contact, age, device, security, and gameplay information. The current static page does not process those details.
KYC and compliance
Identity or location verification should be explained clearly before collection. Any final KYC language must match the approved provider and legal process.
Payment information
Payment and withdrawal data should be handled only through approved, secure flows. This prototype does not collect card, bank, wallet, or UPI details.
Player control
Players should have clear routes to review account information, request help, and understand retention rules once real support channels are approved.
Security posture
Final privacy copy should describe realistic safeguards without overstating guarantees. The site should never imply impossible protection or unverified audits.