Reference

dunialoteri88 Privacy Policy for Your Account

The dunialoteri88 Privacy Policy shows what account, device and payment details we collect, why we use them and how you can ask about changes.

Account dataWallet recordsCookie choicesContact requests
dunialoteri88 dunialoteri88 Privacy Policy for Your Account
CONTACT THE POLICY TEAM

Privacy Questions About DANA or QRIS

A clear contact path matters when a wallet record, login event or cookie choice needs explanation.

Account data request Ask which account details we hold by giving your registered phone number and a short description of the record you want checked. We may verify ownership before responding.
Wallet record question For DANA, OVO, GoPay or QRIS questions, share the transaction date and reference shown in your receipt. Do not send a wallet PIN, password or full security code.
Cookie or device help Tell us whether you used an Android or iPhone browser and describe the cookie or login issue. This helps us separate stored settings from account data without guessing.
HOW WE HANDLE DATA

Account Security From Login Through QRIS

Privacy work follows the account path from phone verification to wallet status, so a request can be checked against a real event rather than a vague description.

Collected account data

We may collect your registration details, phone verification result, login activity and support messages. These records help open, secure and maintain your account rather than create unrelated profiles.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a payment to your account. We do not ask for wallet PINs through support.

Cookie controls

Cookies can retain login preferences, security settings and basic browsing choices. You can manage them through your browser settings, although removing some cookies may affect account access.

Login protection

Phone verification and device signals help us identify unusual sign-ins. If a login appears unfamiliar, we may ask for an account step before restoring access or discussing records.

Retention approach

We keep records for as long as needed for the stated purpose, account security, payment checks or legal duties. When a retention need ends, handling follows our internal process.

Change requests

Contact us to request access, correction or deletion of eligible data. Include your registered phone number and request type; we may verify ownership before making a change.

Privacy Policy Answers for Indonesian Accounts

These Privacy Policy answers focus on the questions you may ask before opening an account or when checking a wallet record. They cover collection, cookies, sharing, retention and access requests in practical terms. If your case involves DANA, QRIS, a phone verification step or an Android and iPhone browser, include that detail when contacting us.

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

Phone verification helps connect you to the correct account and helps us examine unusual login activity. We may request this account step before discussing records or changing access details.

Yes. The Privacy Policy covers payment references used to match QRIS, DANA, OVO, GoPay, bank transfer and virtual account activity. We do not need your wallet PIN for that check.

Cookies can remember security settings, login preferences and basic browsing choices. You can manage them in your Android or iPhone browser, though removing necessary cookies may affect account access.

You can contact our support route with your registered phone number and a clear request for access. We may verify account ownership before confirming which eligible records we hold.

You may request correction or deletion of eligible data through support. We assess the request against account security, payment checks and records that applicable rules require us to retain.

We may share necessary data with service or payment partners involved in the stated account task, or when a valid legal request applies. We keep the shared scope tied to that purpose.