Reference

Privacy Policy For Your Account

yummy 138 slot Privacy Policy tells you what we collect when you open an account, use DANA or QRIS, and move between the mobile lobby and account area.

Clear data purposesWallet record contextPhone access checksIndonesia account path
Explore Our Lobby Read FAQ
yummy 138 slot Privacy Policy For Your Account
CONTACT ROUTES

Get Privacy Help Through Your Account

A privacy question should have a clear route, so we keep contact tied to the account area rather than asking you to post personal details publicly. You can ask about a phone verification record, a DANA receipt, a QRIS status reference or the device used for a login. Include only the details needed to locate the request, and remove wallet passwords or one-time codes. If you are in Semarang or elsewhere in Indonesia, the same account contact path applies where local law permits.

Team online

Account message

Send a privacy request from the account contact path and state whether you need access, correction or removal of a particular record. We use the account details already on file to locate the request without asking you to place sensitive wallet credentials in a message.

Wallet reference

For a DANA, OVO, GoPay or QRIS question, provide the transaction reference and approximate account action, not your wallet password. This lets us trace a payment status record while limiting the personal details included in the privacy conversation.

Login assistance

If phone verification or a device sign-in blocks your privacy request, tell us the account phone number and device type through the account help route. Never send a one-time code. We can use the access record to separate a login issue from a data request.

DATA PRACTICES

What We Do With Account Details

Privacy starts with keeping each record connected to a stated account purpose. We use login and phone verification details to maintain access, payment references to reconcile wallet status, and device signals to…

Account data

We may hold the details you enter for an account, including contact data and phone verification status. These fields support sign-in and account messages. We use them for the purpose described here, rather than requesting unrelated personal details during a normal lobby visit.

Cookies

Cookies can keep your session active and remember basic browser choices when you move from the login screen to the lobby. You can manage cookie settings in your browser. Blocking some cookies may require you to repeat an account step or sign in again.

Wallet records

A wallet reference can show that a DANA, OVO, GoPay or QRIS action reached a particular account status. We use the reference for reconciliation and support checks. The record does not require us to collect your wallet password or payment PIN.

Account protection

Login time, device type and phone verification can help us identify an unusual access attempt. If the mobile path looks different from your usual account activity, we may ask for an account step before access continues. Keep one-time codes private and do not share them with support.

Retention

We retain account and payment records only for the period needed for the stated account, support and legal purposes. The period can differ by record type and applicable rule. A request about a specific DANA receipt or login record helps us locate the relevant retention detail.

Your request

You can contact us to ask what personal data is connected with your account, request a correction or ask whether deletion is available. Include the account phone number and a precise record description. Where local law permits, we respond through the account contact path after confirming the request.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions that arise when you create an account, check a wallet reference or return to the lobby from a phone. We keep each answer practical so you know what to send, what we may retain and how access depends on local law. If your situation is not covered, use the account contact route without sharing a wallet password or one-time code.

It covers account details, phone verification, login activity, device signals, cookies, payment references and privacy messages. For DANA, OVO, GoPay and QRIS, we may use a transaction reference to match an account action with its status. The policy applies to the website and account path.

Phone verification helps us connect the account to the correct sign-in step and investigate an access problem. We may retain its status and related account record for account protection and support. We do not ask you to send a verification code in a privacy message.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS actions, including a status check when a cashier step stalls. We do not need your wallet password or payment PIN. Send only the reference needed to locate the account record.

Use the account contact path and say whether you want access to a record or a correction. Add your account phone number and describe the relevant login, cookie or payment reference. Where local law permits, we confirm the request through the account before responding.

You can ask whether deletion is available for a particular account record or for the account itself. Some records may need to remain for a stated account, support or legal purpose. Tell us which record you mean, and we will handle the request where local law permits.

The policy includes device type, login activity and cookies used when you move from phone verification to the mobile lobby. These details can help identify an unusual sign-in. Your device does not give us access to your DANA, OVO, GoPay or QRIS password.

Yes. Requests for access, correction or deletion depend on local law and the record involved. We use the account contact path to confirm the requester, then explain what can be provided. Access to the service itself is also available where local law permits.

Related Pages

yummy 138 slot Indonesia Dice Duel Mobile Play Basketball IBL Bet Access guide FAQ