Reference

dunialoterry88 Privacy Policy: Your Data Path

Our Privacy Policy explains what we collect when you open an account, verify your phone and enter the lobby from a mobile browser or desktop.

Clear collection rulesWallet data contextRequest paths included
dunialoterry88 dunialoterry88 Privacy Policy: Your Data Path
CONTACT YOUR WAY

Privacy Questions Before Account Access

A clear contact route matters when a Privacy Policy question concerns your login, phone verification or wallet record.

Account support path Use the support route attached to your account for Privacy Policy questions about registration…
Wallet status query For DANA, OVO, GoPay or QRIS records, tell us the wallet name, date and…
Correction request If your name, phone detail or contact record needs changing, state the old and…
HOW WE HANDLE DATA

Rocket Crash Records and Account Security

The Privacy Policy sets boundaries around the records created while you use the account, from a mobile login to a Rocket Crash lobby visit or a wallet status…

Account details

We collect details you submit during account opening and phone verification so we can connect your login, account status and…

Device signals

A mobile browser or desktop session may create access signals such as device and connection details.

Cookies

Cookies can remember session choices and help the account page load the right status.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records can be linked to a transaction reference, amount status and…

Retention controls

We retain records for the period needed for account operation, security checks, dispute handling and applicable duties.

Your request

You can ask which personal details we hold, request a correction or ask about deletion through account support.

Privacy Policy Questions for DANA Accounts

These Privacy Policy answers focus on the account steps people usually ask about before opening access from Indonesia. We explain wallet references, mobile sessions, phone verification and requests in direct language, so you know what to include when contacting us. Where a request depends on identity or local requirements, we will explain the next account step.

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

Yes. It explains that we may use a wallet name, transaction reference and status to match a DANA or QRIS event with your account and answer a receipt question.

Phone verification helps connect account access to the person opening it and supports security checks. We may use that step before changing personal details or responding to a data request.

Cookies can preserve a mobile or desktop session and remember account-page settings. You can adjust browser controls, but blocking cookies may interrupt sign-in, verification or displayed wallet status.

Yes. Send the correction through account support with the relevant old and new detail. We may confirm your phone or another account step before applying the change.

You can ask about deletion through the account support path. We first check the request and explain whether certain records must remain for security, account handling or applicable duties.

Yes. Account eligibility and access depends on local law. Our Privacy Policy still explains the data process for supported Indonesia access, while a request may require an additional local check.