Reference

Open big winner apk Privacy Policy

big winner apk Privacy Policy explains what happens to your account, device and payment details when you move from login to Live Roulette Wheel, Majapahit Empire Reels or…

Clear data categoriesWallet-use contextRequest path
big winner apk Open big winner apk Privacy Policy
CONTACT ROUTES

Switch to the right privacy contact path

A clear contact route helps when a phone verification record, wallet reference or device session needs checking. We keep privacy requests separate from game questions, so your message can identify the account detail that needs attention without exposing a full wallet credential. Start from the account help area and include your registered phone number only through the secure form, where local law permits.

Team online

Account help area

Use the privacy option beside account assistance when your phone verification record, login detail or stored contact information needs correction. We ask for the registered account reference so we can locate the right record without requesting your DANA, OVO, GoPay or QRIS password.

Wallet record check

If a payment reference looks unfamiliar, send the receipt number and date through the account help path rather than posting wallet credentials in a message. We can compare the reference with the account ledger and explain what was stored for DANA, QRIS or bank transfer activity.

Privacy request

For a copy, correction or removal request, name the account field concerned and use the privacy contact shown after login. We may ask for an account step or phone verification to confirm identity before changing records, with handling subject to local law.

DATA SAFEGUARDS

Browse our data handling safeguards

We handle privacy as an account process, not as a single notice shown at the end of registration.

Account details

We use your phone number and verification result to connect the account step with the person requesting access. Login credentials are used for authentication, while profile fields are handled for account administration. We do not need your DANA, OVO or GoPay password to identify your account.

Device sessions

Your mobile browser or desktop session can produce technical records such as login time, device type and security events. These records help us identify unusual access and troubleshoot a stalled lobby path without treating every device signal as a personal profile.

Cookie controls

Cookies and similar browser storage can keep a session connected and remember basic access settings. You can adjust browser controls or clear stored data, although clearing cookies may require you to complete phone verification again before account access continues.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can help us reconcile an account event. We use the reference, amount record and status detail needed for that check, rather than collecting a wallet password or unrelated wallet content.

Retention steps

We keep account, security and payment-reference records for the operational or legal period explained by this policy. When a retention period ends, records are deleted or separated from direct account access where our process and local law allow that action.

Change requests

You can request a copy, correction or deletion of eligible personal details through the privacy contact in the account help area. We verify the requester first, record the request, and explain any field that must remain for security, payment reconciliation or legal reasons.

Check Privacy Policy answers before opening

These Privacy Policy answers address the searches we hear most often before an account is opened. We explain the data connected with login, device use and local wallets in plain English, while keeping account eligibility tied to where local law permits. If your situation is not covered, the privacy contact in your account help area is the next step.

It covers account details, phone verification, login activity, device and browser records, cookies, payment references, security events and retention. It also explains how to request a copy, correction or deletion. The policy applies when you access the service where local law permits.

No. Our Privacy Policy describes payment references and status details used to match an account event, not your DANA or QRIS password. The same approach applies to OVO, GoPay, bank transfer and virtual account activity. Send receipts only through the secure account help path.

Yes, you can request a copy of eligible account data through the privacy contact in the account help area. We first confirm that you control the account, then identify the records available for release. Some security or legal records may require continued retention.

Use the privacy request route after login and describe the phone verification field that needs correction. We may ask you to complete an account step before changing it. This protects the account from an unauthorised edit and keeps the correction linked to the right record.

Yes. The Privacy Policy explains that cookies or browser storage can keep a mobile session connected and remember basic access settings. You can clear them in your browser, but doing so may end the session and require phone verification when you return.

We retain account, security and payment-reference records for the operational or legal period described in the policy. The period can differ by record type. When permitted, we delete or separate information from direct account access after that period ends.

Open the account help area and choose the privacy contact route. Include the account reference, the record concerned and the action requested, such as access or correction. Do not include a wallet password. Eligibility and handling depend on local law.