Reference

Your Data Use Before Account Access

Your account, wallet and device details are handled so we can run logins, lobby access and payment checks without asking for more than we need.

Account dataDANA and OVOGoPay and QRISDevice checks
cakrabola Your Data Use Before Account Access
CONTACT ROUTES

Fast Privacy Help From Our Team

Privacy questions should reach the team that can check account records, not a generic inbox.

Live chat Use live chat when you are signed in and need a quick privacy check…
Email privacy desk Send privacy requests by email when you need a written answer about stored data…
WhatsApp support WhatsApp helps when you cannot reach your account page but still need to flag…
HANDLING PRACTICE

How We Protect Payment And Login Data

We treat privacy as daily account handling, not a footer promise. The wallet, login page and game lobby each create different records, so we separate payment references from…

Account setup

When you join, we collect the details needed to create your profile, verify contact access and connect your wallet.

Payment records

DANA, OVO, GoPay and QRIS activity creates timestamps, reference codes and status marks.

Device sessions

We log device type, browser version, IP address and sign-in timing to help detect account takeover attempts.

Cookies

Cookies help keep you signed in, remember language and keep security checks consistent across lobby pages.

Retention timing

We keep account and wallet records only as long as needed for service, dispute handling, security checks and legal duties.

Change requests

You can ask us to correct profile details, update contact data or explain a stored account record.

Privacy Questions Before You Join

These answers focus on the privacy choices you are likely to check before creating an account or using the wallet. They explain what we collect, why we need it and how you can contact us if something on your record needs attention. For access and eligibility questions, the answer depends on local law.

We collect contact details, login credentials, account settings and payment references needed to create your profile. We also record session data such as device type and IP address so we can protect access and trace support cases.

Payment rails create reference codes, timestamps and status marks that connect your wallet activity to your account. We use those records to match deposits, check withdrawals and answer payment questions without exposing more data than needed.

We share limited data with payment processors, hosting partners, security tools and support systems that help run the account flow. Those services receive only the records needed for their task, such as transaction status or login security signals.

Contact live chat, email or WhatsApp with your registered phone or email and the detail that needs correction. We verify the request first, then update the profile field or explain why a record must stay unchanged.

We may store device model, browser type, IP address, session time and failed login attempts. This helps us identify unusual access, protect your wallet and keep your account available when you switch phones or browsers.

Yes. Send a privacy request through email or signed-in chat and include your account ID or registered contact. We will verify your identity, then explain the main account, wallet, device and support records linked to you.

We keep records for the period needed to operate your account, handle disputes, meet legal duties and protect the wallet. When records are no longer needed, we delete them or restrict access according to our internal retention process.