Reference

detik11 Privacy Policy Explained Clearly

Our detik11 Privacy Policy shows how we handle the details connected to your account, wallet status and device access.

Account dataWallet recordsDevice accessCookie choices
detik11 detik11 Privacy Policy Explained Clearly
CONTACT PATHS

Get Privacy Policy Help From Your Account

A clear contact path helps when you want to ask about a record, correct account details or understand a wallet reference. Use the support route linked from your account area and include the phone number or account identifier connected with your request. We check ownership before discussing personal data, so your request reaches the right account rather than exposing details to another person.

Team online

Account data request

Ask us to explain the personal data attached to your account, including phone verification records and recent login details. We may request an account step before releasing private information.

Wallet reference check

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the transaction identifier through support. We compare the reference with account records without requesting your wallet password.

Correction request

Tell us which account detail needs changing and why. We verify the request, update eligible records and explain when a transaction or security record must remain unchanged.

HANDLING DETAILS

How We Apply This Privacy Policy

Privacy choices work best when the handling steps are visible. We separate account details from payment references, use access checks before discussing private records and keep cookie behaviour tied to practical sign-in…

Account records

We use your account identifier, phone verification result and sign-in events to connect requests with the correct account. This helps us investigate access questions without relying on a public display name alone.

Payment references

For DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity, we retain references and status details needed to reconcile deposits or account requests. Wallet credentials stay with the payment provider.

Cookie controls

Cookies can keep a sign-in session connected to the page you opened and remember selected settings. You can manage cookies through your browser, though blocking them may interrupt account access.

Device signals

We may record device type, browser details and security signals when you sign in. These checks help identify unusual access across a mobile path and do not require access to your personal files.

Retention rules

We keep records while they support account operations, payment reconciliation, dispute handling or legal duties. When a record no longer serves one of those purposes, we remove it or reduce its identifying detail.

Your requests

You can ask about access, correction or deletion of eligible personal data through the account support path. We confirm your identity first and explain any record that cannot be removed yet.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the questions we expect before account access, especially around Indonesian wallets, phone verification and mobile sign-in. If your situation is not covered, send the account identifier and a short description through the support path so we can check the relevant record.

It covers personal data linked to your account, phone verification, login activity, device signals, cookies and payment references. It also explains retention, correction requests and how we respond to data questions.

No. We use the payment reference and status needed to match a DANA or QRIS request with your account. Your wallet password and payment credentials remain with the relevant provider.

Phone verification helps connect account access with the correct person and supports security checks. We may use its result when you request account data, change details or ask about a wallet reference.

Yes. Send an access request through the account support path with your account identifier. We verify ownership before sharing eligible records and explain any information restricted by security or legal duties.

Describe the inaccurate detail and the correction you want through support. After confirming account ownership, we review the request, update eligible information and tell you if a transaction record must stay unchanged.

We retain records while they are needed for account operations, payment reconciliation, disputes, security or legal duties. Once those needs end, we remove the data or reduce its identifying detail.

Yes. The same policy applies when you sign in from a phone or desktop. Device type, browser details and security signals may be recorded to support account access and detect unusual sign-ins.