Reference

dunialottrey88 Privacy Policy for Your Account

Our Privacy Policy explains what account, device and wallet data we use when you open an account and move through the lobby.

Account dataWallet recordsCookie choicesAccess requests
dunialottrey88 dunialottrey88 Privacy Policy for Your Account
CONTACT PATHS

Privacy Questions Near Your Cashier Path

A clear support route helps when you need a copy of your data or a correction to an account record.

Account data request Use the signed-in support route to ask what account data we hold. Include your phone number and request scope so we can match the request to the correct account.
Wallet status query For DANA, OVO, GoPay or QRIS records, add the payment reference and date. We can then check the stored status without requesting your wallet password or private wallet login.
Correction path If your phone, name or payment reference is inaccurate, contact support from your account. We may ask for an account step that confirms you control the request before changing the record.
HANDLING YOUR DATA

Privacy Controls From Login to Retention

We handle privacy through practical account steps rather than broad promises. Sign-in checks, cookie controls and payment matching each serve a defined purpose, while retention depends on the record and the legal…

Account collection

We collect details you enter during account opening, including your phone number, plus sign-in events needed to connect access with the right account. Phone verification takes place before account access.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us identify a cashier event. We use status, amount and time details rather than your wallet password.

Cookie controls

Cookies can keep your mobile browser connected to an account session and remember technical choices. You can adjust browser cookie settings, though some sign-in steps may then need repeating.

Device signals

Browser type, IP address, device signals and sign-in time help us spot unusual account access. These signals also help separate a normal mobile session from a login that needs checking.

Retention periods

We keep account, support and payment records only for the period needed for their stated purpose or a legal requirement. When retention ends, we remove or de-identify the relevant record.

Your requests

You can ask for access, correction or deletion of eligible data through signed-in support. We confirm account control first and apply the result where local law permits.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening an account. Each answer points to a practical step, from changing cookie settings on mobile to sending a data request through the signed-in support route, with access depending on local law.

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

Phone verification connects account access to the person making the request and helps reduce mistaken access. We may use that account step before handling a data copy or correction request.

Yes. We may store a DANA or QRIS reference, amount, status and time to reconcile the cashier record. We do not need your wallet password to check that status.

Sign in, open the support route shown in your account and state that you want an account data copy. Add your phone number and the specific record range you want checked.

You can request a correction or deletion through signed-in support. We confirm that you control the account, identify any record affected and apply the request where local law permits.

Cookies can keep a mobile browser session connected and retain technical choices. If you block them, sign-in or account preferences may need repeating, while essential access steps can still depend on browser settings.

Retention varies by the payment, support or account record and the reason it must remain available. We remove or de-identify data when its stated purpose and legal need have ended.