Reference

rtp slot Privacy Policy: Your Account Data Path

Our rtp slot Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, or connect DANA, OVO, GoPay and QRIS.

Account clarityWallet recordsCookie choicesRequest access
rtp slot rtp slot Privacy Policy: Your Account Data Path
CONTACT ROUTES

Three Ways To Ask About Your Data

A clear contact route helps you act on this Privacy Policy without searching through unrelated account screens.

Account message Send a request through the support route connected to your account.
Wallet query For OVO, GoPay, bank transfer or virtual account records, include the reference and date…
Access request Ask us to locate, correct or explain personal details held under your account.
SIX DATA CONTROLS

Six Practical Controls For Your Account Data

We keep this policy practical by tying each data use to an account action you can recognise.

Account creation

We use the details you enter to create your account, send essential account messages and complete the phone verification step before access. You can ask us which fields remain attached to your profile.

Wallet matching

DANA, OVO, GoPay and QRIS references help us match a payment status to your account. We keep the reference needed for checking, rather than requesting your wallet PIN or private login.

Device signals

A mobile browser or desktop browser may provide session, language, screen and sign-in details. We use these signals to spot unusual access and help explain why a page did not load.

Cookie settings

Cookies can retain your session and remember selected settings. You can adjust cookie controls in your browser; disabling some cookies may require another login before opening the lobby.

Retention checks

We retain account and wallet records for the period needed to operate the account, resolve disputes and meet applicable duties. You can ask why a particular record is still held.

Correction requests

If your phone detail, contact field or account record is wrong, contact us through the account support path. We may verify ownership before changing information linked to Mobile Legends or Super Bingo activity.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers focus on the steps you are most likely to take before opening or using an account. They explain access requests, wallet references, cookies, device records and corrections in plain terms. Where a request involves eligibility or account access, the outcome depends on local law and applies where local law permits.

It covers account details, phone verification, sign-in events, browser data, cookies and wallet references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

We use the phone verification step to confirm that the account request belongs to you and to protect access. Ask through support if the stored contact detail needs correction.

Yes. The Privacy Policy covers technical details from your mobile or desktop browser, such as session events and device settings, when those details help maintain access or investigate an account issue.

Use the support contact inside your account and ask for an access request. Include your account identifier and the record involved; we may verify ownership before sharing private details.

Yes. Tell us which contact, phone or account field is inaccurate and provide the relevant account step. We will assess the request and may ask for verification before making a change.

We keep transaction references, status and timestamps needed to match DANA or QRIS activity to your account. We do not need your wallet PIN or full authentication code for that check.

Contact us through the account support route and name the cookie setting or record-retention question. We will explain the relevant use, subject to applicable law and account verification.