What We Collect And Why
Our policy starts at the account step: when you enter your phone number, email, username, and password, we use that data to create your login, protect access, and connect support replies to the right profile. We also record device type, IP range, browser, session time, cookie
-
1
choices, wallet references, and withdrawal checks, because those entries help us detect duplicate access, resolve payment questions, and keep transaction records aligned. We do not ask for your DANA, OVO, GoPay, or QRIS PIN; payment confirmation comes through the rail’s normal redirect or receipt signal. Access
-
2
to the lobby and payout handling where local law permits may require verification if your account activity changes. We keep privacy requests in the same queue as account cases, so your correction or deletion request is tied to a trackable ticket with date, channel, and outcome.
Service availability depends on jurisdiction. Users are responsible for checking local law before access.