Reference

badakslot Privacy Policy For Clear Account Control

The badakslot Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between the mobile lobby and account area.

Account dataWallet recordsCookie choicesPrivacy requests
badakslot badakslot Privacy Policy For Clear Account Control
PRIVACY HELP DESK

Get Help With A Privacy Request

A clear contact path matters when your account record or wallet reference needs attention. Use the support area linked from your account to raise a privacy question, identify the relevant login or transaction, and tell us whether you need access, correction or deletion guidance. We may ask for account details to confirm that the request comes from you.

Team online

Account privacy request

Send the request from the account support path and include your registered phone detail. We use that account step to reduce mistaken disclosures before discussing stored profile or login data.

Wallet record question

For DANA, OVO, GoPay or QRIS records, include the payment reference and date visible in your account. We can use those details to locate the relevant status without asking for your wallet password.

Access and correction

If a phone verification detail, device record or account name appears wrong, tell us what needs changing through the privacy contact path. We may verify identity before applying an update.

DATA HANDLING

What Our Privacy Process Covers

We keep this Privacy Policy practical by connecting each data category to an account action you recognise.

Account creation

When you open an account, we collect the details needed to create and maintain access. Phone verification can be required before account entry, helping us connect the right person with the right record.

Device and session data

Our mobile browser path may record device type, browser signals, login time and session events. These details help us detect unusual access without requiring a separate application on your phone.

Cookie controls

Cookies can remember session choices and help us understand whether a page loads correctly. You can manage available browser cookie controls, although disabling some cookies may affect account access.

Account security

We use login events, phone verification and device signals to protect account access. Never send us your password or wallet PIN; a support request should use the account detail we can verify.

Retention periods

We keep account, payment and security records only for the period needed for the stated purpose, dispute handling and applicable legal duties. When a record is no longer needed, our process addresses its removal.

Your privacy choices

You can ask about stored data, request a correction, question a processing purpose or seek deletion guidance where local law permits. We may request identity confirmation before releasing or changing information.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions you may have before opening an account or contacting us. They cover the records created by login, phone verification, local wallet activity and mobile browsing. If your situation is specific, use the privacy contact path with the account or payment reference you can safely share.

It covers account details, phone verification, login events, device signals, cookies, support requests and payment references created through DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps us confirm account access and reduce mistaken disclosures. It can connect a request to the correct account record, while eligibility and access depends on local law.

Yes. The policy addresses payment references, status and timestamps connected with DANA and QRIS, along with comparable records from OVO, GoPay, bank transfer and virtual account steps.

Where local law permits, you can ask about stored account, device, cookie, support and payment-reference data. Send the request through the account support path so we can verify your identity.

Use the privacy contact path and identify the incorrect phone, account or device detail. We may ask for a verification step before changing the record, especially when wallet activity is involved.

We retain information for the stated account, security, dispute and legal purposes. The period varies by record type, and data is addressed for removal when those purposes no longer require retention.

You can ask for deletion guidance through the support area. We assess the request under applicable rules because some account, transaction or security records may need to remain for a stated legal purpose.