Reference

Open detik 11 Privacy Policy Clearly

Our detik 11 Privacy Policy shows what we collect when you create an account, verify your phone, use DANA or QRIS, and move from login to the lobby.

Account dataWallet recordsCookie choicesDevice access
detik 11 Open detik 11 Privacy Policy Clearly
CONTACT WHEN NEEDED

Reach Our Policy Support Path

A clear contact path matters when a name, phone number or wallet status looks incorrect.

Account request Ask us to correct account details through the support path beside the cashier area. Include your registered phone number and the exact field that needs changing, so we can compare the request with your verified account record.
Wallet query For DANA, OVO, GoPay or QRIS records, share the payment reference and date rather than your wallet password. We use that reference to locate the status connected to your account and explain what data is retained.
Access concern If a login alert or device record does not look familiar, contact us from the account help route and change your password after signing in. We can review the access trail and explain the related Privacy Policy step.
HOW RECORDS MOVE

Switch On Clear Account Checks

We handle policy requests as account matters, not as a general lobby enquiry. Your phone verification connects a request to the right account, while session and device signals help us investigate access…

Data collection

We collect the account fields you provide, verification results, payment references and technical events needed for login or support. We do not need access to unrelated files, contacts or messages on your device to handle these steps.

Cookie controls

Cookies can remember a session and your policy choices on the browser you use. Clear them through browser settings when needed; after that, you may need to sign in again before reaching your account area.

Account security

Phone verification is required before account access, and unusual device or session signals may prompt an additional check. Keep your password private, especially when contacting us about DANA, OVO, GoPay or QRIS.

Payment matching

A QRIS, wallet, bank transfer or virtual account reference lets our team match a payment event with your account. We use the reference for status checks and do not request a wallet password as proof.

Retention timing

We keep account, payment and support records for the period needed for service operations, security checks or legal duties. When that period ends, records are deleted or changed so they no longer identify you where practical.

Change requests

You can ask for a correction, access copy or clarification through the support route linked beside your account and cashier area. We verify the request against your registered phone before discussing account-linked data.

Ask About Privacy Policy Access

These Privacy Policy answers cover the account actions you are most likely to take before opening an account or checking a wallet record. We keep the route practical: start with your registered phone, use the policy link in the account area and include a payment reference only when your request concerns DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

It covers account details, phone verification, payment references, cookies, device signals, support records and retention. It also explains how to request access or correction and when local access rules apply. You can open the policy link from your account area before continuing.

We use your phone number to create and verify the correct account, connect policy requests to you and help protect login access. Verification happens before account entry. We do not treat your phone number as permission to read unrelated content on your device.

Yes. The Privacy Policy explains how DANA, OVO, GoPay, QRIS, bank transfer and virtual account references support payment matching and status checks. We use the reference connected to your account and do not ask for your wallet password.

Use the support route beside the account and cashier areas, then provide your registered phone number and a precise request. We verify account ownership before discussing records. For a payment correction, add the relevant QRIS, wallet, bank or virtual account reference.

We may record device type, browser signals, session timing and login events to keep access connected and investigate unusual activity. These signals help with account security on mobile and desktop. They do not provide a reason to collect unrelated files or messages.

We retain account, payment and support records for the period required for operations, security checks and legal duties. After that need ends, we delete or anonymise records where practical. You can contact us if you need the retention reason for a specific record.

Access or eligibility depends on local law. Check the rules that apply to your location before opening an account, then read the Privacy Policy from the account area. If your access or data request is unclear, contact support through the linked account route.