Reference

slot aladin Privacy Policy: Your Account Data Path

Clear account and wallet data choices are at the centre of our Privacy Policy.

Account dataWallet recordsCookie choicesMobile access
slot aladin slot aladin Privacy Policy: Your Account Data Path
PRIVACY HELP DESK

Get Privacy Help Near Wallet Status

A direct support path helps when you want to ask about a privacy record rather than a payment result. Use the support route connected to your account, include the phone number on the account and describe the request clearly. If your question concerns a DANA, OVO, GoPay or QRIS reference, share only the relevant receipt details, never a wallet password or verification code.

Team online

Account support route

Send a privacy question through the support path linked to your account. We use your account phone number to locate the right record before responding.

Wallet receipt check

For a DANA, OVO, GoPay or QRIS question, provide the transaction reference and date. We can examine the stored status without asking for your wallet credentials.

Access concern

If a privacy request affects sign-in, tell us the device path you used, such as mobile browser or desktop browser. We will separate access help from data changes.

HOW WE HANDLE RECORDS

Safer Mobile Data For Your Account

We keep the Privacy Policy practical by connecting each data use to an account action you recognise.

Account security

Phone verification is used before account access so we can connect a sign-in to the account you control. Keep your verification code private; support will not request it.

Device signals

We may record browser, device and security-event details when you sign in. These signals help identify unusual access without giving us access to other content on your device.

Cookie controls

Necessary cookies support sign-in and session protection. Where controls are available, you can adjust optional cookies through your browser or the site preference control.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records are used to match payment status. We do not ask for your wallet password or banking login.

Record retention

We retain account, support and payment records only while needed for service operation, security checks or legal duties. When no purpose remains, records are removed or de-identified.

Change requests

To request access, correction or deletion of eligible data, contact support from the account route and describe the record. We may verify account control before making a change.

Privacy Policy Answers Before Account Access

These Privacy Policy answers cover the questions we expect before you open an account or check a wallet status. They explain the data connected to sign-in, cookies, game activity, payment references and support requests, with access handled where local law permits.

It covers account details, phone verification, device and browser signals, cookies, support messages, game activity records and payment references connected with DANA, OVO, GoPay, QRIS or bank transfer.

We use your phone number to create and protect your account, confirm account control before access, connect support requests to the correct record and help identify unusual sign-in activity.

Yes. The policy covers the payment reference, amount status and timing details needed to match DANA or QRIS activity with your account. We do not need your wallet password.

We may collect browser type, device category, session details, approximate connection data and security events. This helps protect access through a mobile or desktop browser without reading unrelated device content.

Necessary cookies support sessions and account protection. Optional cookies can be adjusted through available site controls or your browser settings, subject to the functions required for account access.

You can request access or correction through the support route linked to your account. Include the relevant phone number and record description; we may verify account control before changing the data.

We keep records while they are needed for account operation, security, support or legal duties. After that purpose ends, we remove or de-identify them where the applicable rules allow.