Reference

Your Privacy Policy in Plain Words

Your account data, payment records and device signals are handled through this Privacy Policy before you open the lobby.

Account data useDANA and OVO recordsGoPay and QRIS contextCookie choices

Browse Lobby Read FAQ

What This Policy Covers

mustika78login Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy explains how we collect, use, store and share data linked to your account, wallet checks, lobby activity and support messages. Access to any real account feature depends on local law, and this policy does not change that eligibility position. We keep sign-up details,

1
login records, payment references and cookie signals only for account operation, fraud checks, dispute handling and service contact. When you open an account, we ask for the fields needed to run the wallet and verify access, not extra profile detail that has no clear purpose.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Three Ways To Ask About Privacy

Privacy questions should reach a real support path, not a generic inbox. You can ask us to check account records, correct profile details, explain cookie use…

DATA HANDLING

How We Protect Account Records

Privacy protection starts at the account step. We separate login checks, wallet records, cookie signals and support conversations so each team sees only what is needed for its task.

Registration data

When you join, we collect the details needed to create and protect your account, such as contact fields and login credentials. We use them for access checks, support contact and account recovery only.

Payment references

DANA, OVO, GoPay and QRIS activity creates transaction references that help us match deposits, withdrawals and account disputes. We keep the reference trail separate from game history wherever the workflow allows.

Device signals

We record practical device signals such as browser type, session time and login pattern to spot account takeover attempts. If you switch from mobile to laptop, the system may request extra verification.

Cookie controls

Cookies help keep your session active, remember language choices and measure whether privacy prompts are working. You can clear cookies in your browser, though a fresh login may be needed afterward.

Retention checks

We keep records for account operation, payment tracing, fraud review and legal duties, then remove or anonymise data when the reason no longer applies. Some wallet records must stay longer for dispute handling.

Change requests

You can ask us to correct contact details, explain stored records, or close an account data request through support. We may verify identity first so private records are not released to the wrong person.

Privacy Questions Before You Join

These questions cover the privacy points you may check before creating an account or sending a payment. We focus on the data you give us, the records created by your device and wallet activity, and the ways you can reach us when something needs correction.

We collect the account fields needed to create access, contact you, protect the login and run wallet checks. That can include contact details, login records, device signals and payment references tied to your activity.

We keep payment references so deposits, withdrawals, disputes and account checks can be matched to the correct wallet. The record usually includes rail name, time, status and account link, not your full app balance.

Yes, you can ask support for the account data we hold about you. We may confirm your identity first through your registered contact path so we do not release private records to another person.

Cookies keep your session active, help remember choices and show us whether account pages load correctly. You can clear them through your browser settings, but you may need to log in again afterward.

We share only the details needed to process or trace transactions through DANA, OVO, GoPay, QRIS or related banking channels. We do not share support chat content unless it is needed for a specific dispute.

Contact live chat, email or the account ticket path with the field that needs correction. We may ask for a registered phone, email or recent payment reference before changing data tied to your login.

You can request closure through support. Some records may remain for payment tracing, fraud checks or legal duties where local law permits, but we stop using closed account data for normal lobby access.

Your Privacy Policy in Plain Words

Three Ways To Ask About Privacy

How We Protect Account Records

Registration data

Payment references

Device signals

Cookie controls

Retention checks

Change requests

Privacy Questions Before You Join

01 What data do you collect when I open an account?

02 Why do you keep DANA, OVO, GoPay or QRIS records?

03 Can I ask to see the data linked to my account?

04 How do cookies affect my privacy on the site?

05 Do you share my data with payment partners?

06 How do I correct wrong profile details?

07 Can I request account closure and data removal?

Related Pages