Reference

akun jp slot Privacy Policy

Your DANA, QRIS and account details deserve a clear explanation, so our Privacy Policy sets out what we collect, why we use it and how you can ask…

Clear data purposesWallet detail controlsAccount access requestsCookie choices
akun jp slot akun jp slot Privacy Policy
HELP WITH ACCESS

Privacy Questions Follow Your Account Path

A privacy request should not leave you searching through unrelated pages. We place the support route close to account access and the cashier path, so you can identify the account, wallet reference…

Account data request Use the support route shown after login when you want a copy, correction or explanation of account details. Tell us whether the request concerns phone verification, a device record or a login event, and we will use the account step you identify to locate the relevant entry.
Wallet reference check For DANA, OVO, GoPay or QRIS questions, provide the transaction reference and date rather than private wallet credentials. We can compare the reference with the account record and explain whether a status entry is pending, matched or needs further checking through the cashier path.
Cookie and device help If a phone or browser keeps an old session, contact us through the account support path with the device type and browser action involved. We can explain the related cookie or access record and tell you how to request a change without sharing your password.
ACCOUNT SAFEGUARDS

Six Practical Controls In Our Policy

Privacy works best when each account step has a defined purpose. We separate identity details from payment references where the workflow allows, use device and login signals to detect unusual access, and…

What we collect

We may collect contact details, verification information, login events, device type, browser signals and account activity needed for the requested account service. Payment records normally identify a reference, method and status, such as QRIS or a bank transfer, rather than your private wallet password.

Why each record exists

A phone detail supports account verification, a device signal helps protect a login, and a DANA or GoPay reference helps match a wallet request. We use each category for the stated account, support, payment checking or security purpose instead of collecting unrelated details.

Cookies on your device

Session cookies can keep an account area connected while you move between pages, while preference cookies may remember a language or display choice. Your browser controls whether cookies remain, and support can explain which cookie-related record is involved in a request.

Account protection

Keep your password private and complete phone verification only through the account path. We may compare login timing, device signals and account actions when access appears unusual. If you lose access, support can begin a check without asking you to publish private credentials.

How long records remain

We retain account, payment-reference and support records only for the period needed for the stated purpose, account administration, dispute checking or a legal requirement. A retention question can name the record type and date, allowing us to explain the applicable period.

Changing your details

Ask support to correct an inaccurate phone number, contact detail or account record through the logged-in path. Include the detail that needs changing and why it is incorrect. We may verify account ownership before making a change, especially when wallet status is involved.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers address the account questions you are most likely to have before opening an account or asking for a data change. They cover wallet references, cookies, device access, retention and contact steps without asking you to disclose private credentials. If your situation is not listed, use the support route beside the cashier area and mention the exact record or date you want us to check.

It covers account details, phone verification, login and device signals, game activity linked to your account, cookie use, payment references and support requests. It explains why we use those records, how long they may remain and how you can ask for access, correction or clarification.

No. For DANA, OVO, GoPay and QRIS, we use the payment reference, method and status needed to match an account request. Do not send a wallet password or full credential to support. A receipt date and reference are usually enough for checking.

Use the support route inside your account and state that you want a copy of your personal record. Include the attached phone or contact detail, the date range and any specific category, such as login activity or wallet references. We may verify ownership first.

Yes. The Privacy Policy allows a correction request for inaccurate contact, phone verification or account details. Send the current record, the corrected value and a short reason through the account support path. We may ask for an ownership check before changing details connected with payments.

A new phone or browser can create a separate session and device record. Cookies from the former device do not automatically transfer as account preferences. If an old session remains visible or access behaves unexpectedly, tell support the device type and browser action involved.

Payment references may remain while they are needed for account administration, status matching, dispute checking or a legal requirement. This can include a DANA receipt, QRIS reference, virtual account entry or bank transfer record. Ask support about a specific date and record category for a clearer response.

Account availability and data handling depend on local law, and you should access the service only where local law permits. If you are unsure about eligibility or a local restriction, ask support before opening an account and do not provide verification details until you have made that check.