Reference

loketcuanlogin Privacy Policy For Wallet And Account Data

Your account record, phone verification and DANA or QRIS payment status are covered by the loketcuanlogin Privacy Policy.

Account dataWallet recordsDevice choicesCookie controls
loketcuanlogin loketcuanlogin Privacy Policy For Wallet And Account Data
CONTACT PATHS

Where To Ask About Privacy Policy

A privacy question should not get mixed with a game or payment query. Use the support route connected to your account and mention the email or phone number attached to your login.

Account support Open the account support path after login and describe whether your request concerns phone verification, profile data or an unfamiliar sign-in. We use the account record to identify the correct case.
Wallet record query For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, include the receipt reference and date. Never send a wallet PIN, password or full security code with your request.
Rights request Ask for a copy, correction or removal review through the same account support path. We may request account verification before changing data, so another person cannot alter your record.
HANDLING DETAILS

Inside loketcuanlogin Privacy Controls

We treat the Privacy Policy as an operating process, not a footer link. Account access starts with your login and clear phone verification; payment status is kept separate from wallet passwords, while…

Collected account fields

We may handle the contact details you submit for an account, phone verification results, login activity and support messages. These records connect your request to the right account without exposing another account's data.

Cookie choices

Essential cookies can keep login settings and security checks working on your device. Other cookie choices may affect remembered preferences, and you can manage them through your browser controls.

Payment separation

A DANA, OVO, GoPay or QRIS status can be matched with a receipt reference. We do not need your wallet PIN to check that status, and bank transfer records follow the same account-matching purpose.

Device protection

When you move from phone login to the mobile lobby, we may record device and connection signals for security. A changed device can prompt another account check before access continues.

Retention approach

We retain account, payment and support records only while they serve account operation, security, dispute handling or legal duties. When a record is no longer needed, our process removes or separates it.

Change requests

You can ask us to correct an account detail or explain its use through support. We verify the request against your account before making a change, where local law permits.

Privacy Policy Questions Before Access

These Privacy Policy answers focus on the moments that matter before you open an account: phone verification, wallet records, cookies, device changes and requests for correction. If your question concerns a specific receipt or login event, include its date and reference through the account support path so we can respond to the right record.

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

We use phone verification to connect account access with the contact detail you provide and to reduce mistaken or unusual logins. We may ask you to repeat that check after a device change.

No. Our payment record can show a method and receipt status, such as QRIS or DANA, but you should not send us a wallet PIN, password or full security code through support.

Essential cookies can maintain login settings and security checks. Browser controls let you manage other cookie choices, although changing essential settings may affect account access or remembered preferences.

Yes, you can ask through the account support path for a copy, explanation or correction. We first verify that you control the account, and the request depends on local law.

We keep those records while needed for account operation, payment matching, security, dispute handling or legal duties. The period can vary by record type and applicable local requirements.

Contact support through your account path, mention the affected device and approximate time, and change your account password. Do not include wallet credentials or security codes in the message.