Reference

Your account data stays explainable

Account data, payment checks and device sessions sit under one privacy policy before you open an account, so you know how we handle DANA, OVO, GoPay and QRIS…

DANA privacy checksOVO receipt recordsGoPay account matchingQRIS payment logsCookie controls
sar288 Your account data stays explainable
PRIVACY HELP

Reach us about your privacy choices

Privacy requests should reach the team that can trace account logs without exposing extra data.

In-lobby chat Daily 09:00-23:00 WIB, in-lobby chat lets you ask what data sits on your account…
WhatsApp privacy queue Use the WhatsApp contact shown after login for identity checks, data correction requests and…
Account request form From Account, open Profile, then Privacy Request to ask for access, correction or deletion.
CONTROL CENTER

How we protect and adjust data

Your privacy settings work beside account security, not behind it. We separate payment references from game activity where practical, limit staff access by role and keep audit logs…

Data we collect

We collect registration data, contact details, payment references, device signals and lobby activity tied to your account.

Payment privacy

DANA, OVO, GoPay and QRIS records are stored as transaction references, status codes and timestamps.

Cookie controls

Cookies help keep you logged in, remember language choice and detect repeated failed access.

Retention periods

We keep account and payment records only for operational, safety and dispute handling needs.

Access protection

Staff access is limited by task, and sensitive account actions leave audit records.

Correction requests

If your phone number, display name or payment label is wrong, send a request from the logged-in account.

Privacy questions before you join

Before you open an account, you deserve clear answers about what we collect, why we keep it and how you can ask for changes. These privacy answers focus on account setup, payments, cookies, device sessions and contact paths for Indonesia. If a request involves wallet records, we may need extra identity checks before we release or change anything.

We ask for details needed to create and protect your account, such as username, phone contact, login credentials and payment labels. Extra checks may apply when a withdrawal or profile change needs identity matching.

We keep payment references, timestamps and status messages so wallet movements can be matched to your account. These records help us answer failed deposit questions, withdrawal checks and privacy requests tied to transactions.

Yes. Open Account, choose Security, then Active Sessions to see recent device access. If you see a phone or browser you do not recognize, contact chat and change your password right away.

Cookies remember login state, language choice and basic session details on your phone browser. You can clear them in your browser settings, but you may need to log in again and confirm security prompts.

Log in first, open Profile, then use Privacy Request or contact chat from the same account. We compare your request with registered phone, login history and payment labels before changing stored details.

You can send a deletion request through the account form or privacy queue. Some payment and security records may be kept for operational or dispute handling needs before they are removed or reduced.

Only staff assigned to account, payment or security tasks can handle the related request. We limit access by role, and sensitive actions may be recorded in audit logs for follow-up checks.