Reference

Your detik11 Privacy Policy, In Plain Terms

The detik11 Privacy Policy explains what we collect when you create an account, verify your phone, use DANA or QRIS, and move between the lobby and your wallet.

Account dataWallet activityDevice choicesPrivacy requests
detik11 Your detik11 Privacy Policy, In Plain Terms
PRIVACY SUPPORT

Get Help With A Data Request

A clear contact route matters when a privacy question meets a login or wallet issue.

Account support route Use the support option beside your account area to ask how we handle a…
Payment record check For DANA, OVO, GoPay, QRIS or bank transfer questions, share the payment reference rather…
Access and correction Ask us to provide, correct or remove eligible personal data through the same support…
ACCOUNT SAFETY

What We Do With Your Personal Data

We keep this policy tied to the actions you take rather than collecting details without a reason.

Account details

We use the details you submit for account creation, phone verification and sign-in support. If a field is wrong, tell us through account support and identify the correction clearly so we can review the matching record.

Payment references

A DANA, OVO, GoPay, QRIS, virtual account or bank transfer reference can be stored with a transaction status. This lets us trace a receipt or account action without storing your wallet password.

Device signals

Browser type, device details and sign-in timing may be recorded to recognise an unusual access attempt. These signals support account protection and are not a request for access to unrelated files on your device.

Cookies and sessions

Cookies can keep your session active and remember selected settings on a supported browser. You can manage browser cookie controls, though removing them may require you to sign in again before reaching your account.

Retention choices

We keep personal records only for the account, payment, dispute or legal purpose that requires them. When a record no longer serves that purpose, we remove it or change it so it cannot be linked to you.

Requesting changes

To ask for access, correction or deletion, contact us through the account support route and pass the ownership check. We will explain any limit that depends on local law or an unresolved payment record.

Privacy Policy Answers For Your Account

These Privacy Policy questions focus on the account steps you are most likely to take before using detik11. We address payment references, phone verification, cookies, device signals and requests for access or correction, with the same local-law wording used throughout the policy.

It covers account details, phone verification, sign-in records, browser and device signals, cookies, payment references and support requests. It explains why we use each category, how long records may remain and how you can ask about access or correction.

No. When you use DANA, OVO, GoPay or QRIS, we handle the payment status and reference needed to match the activity to your account. Your wallet password and one-time code should never be sent to our support team.

Phone verification helps connect account access to the person who controls the registered number and gives support a way to identify the correct account. We record the verification result and related account event, not the private contents of your phone.

Cookies can keep a supported browser session active and remember selected settings. You can change cookie controls in your browser, but clearing them may sign you out or require another account check before you reach the lobby.

Yes. Use the account support route, state whether you want access or correction, and identify the relevant account field or payment reference. We may verify ownership first, and the available action depends on local law and any required record.

We retain records for the account, payment, dispute or legal purpose that requires them. When that purpose ends, we remove or anonymise the data where appropriate. A support request can ask which category remains and why it is retained.

Start with the support option connected to your account and describe the privacy issue in plain English. Include your registered phone number and, when relevant, a DANA, QRIS or bank transfer reference; do not include a password or one-time code.