Reference

Privacy Policy for Your detik55 Account

Our Privacy Policy shows how detik55 handles the details connected with your account, including phone verification, wallet status and device access.

Account clarityWallet contextDevice controlsLocal-law access
detik55 Privacy Policy for Your detik55 Account
CONTACT ROUTES

Get Help With a Privacy Request

A clear contact path matters when you want to ask what data we hold or why an account check occurred. Our support route is linked from the account area, so you can send a privacy request without searching through the live lobby. Include your registered phone number, the request type and any relevant receipt reference; do not send a wallet PIN or password. We use those details to locate the correct account and respond within the limits of local law.

Team online

Account access request

Use the account support path when you need a copy of account data, a correction to your phone verification record or clarification about a sign-in event. We may ask you to confirm account ownership before sharing details, so another person cannot obtain your records.

Wallet data question

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, include the payment reference and approximate date. We can check the record attached to your account, while sensitive wallet credentials remain outside our support request process.

Privacy concern

If you believe a device record, cookie setting or account detail is inaccurate, contact us through the same support route and describe the issue. We will review the request, explain any necessary retention and apply changes where local law permits.

DATA HANDLING

What We Do With Account Details

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

Account records

When you open an account, we may store your phone number, verification result, sign-in history and selected account settings. These records help us distinguish your access from an unfamiliar attempt and let support locate the right account when you ask about the Privacy Policy.

Payment references

A DANA, OVO, GoPay or QRIS transaction can create a reference, amount, status and time record connected with your account. Bank transfer and virtual account checks may also show BCA, BRI, Mandiri or BNI as the originating rail, without collecting your banking password.

Device security

Our security checks may record browser type, device identifiers, IP address and sign-in time when you reach the lobby from mobile or desktop. These signals help us investigate a new-device alert and are not used to request access to files, contacts or your wallet PIN.

Cookie choices

Cookies can keep a session active, remember a language or store a security preference. You can adjust cookie controls in your browser settings, although blocking essential cookies may require you to repeat phone verification before account access.

Retention decisions

We retain account, support and payment-reference records only for the period needed for the stated purpose, security checks or legal duties. A request to remove data may be limited where a receipt, dispute or account-security record must remain available.

Changes and questions

You can ask us to correct an account detail, explain a device event or clarify how a record from Fishing War Arcade or BandarQ VIP Table relates to your account activity. We confirm ownership first and respond through the support path where local law permits.

Privacy Policy Answers Before Access

These Privacy Policy answers address the searches we hear most often before account access: what we collect, how wallet references are used, how a mobile device is recognised and how to request a change. We keep the answers tied to detik55 account activity rather than describing unrelated services. If your question concerns eligibility or access in Indonesia, the outcome depends on local law.

The detik55 Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, payment references and support records. It also explains retention, correction requests and contact options. Access depends on local law, and the policy applies when you use a supported browser or device.

No. Our Privacy Policy treats DANA, OVO, GoPay and QRIS as payment references or status records, not as permission to collect your wallet PIN. We may match a receipt or reference with your account, while your wallet credentials stay with the relevant payment service.

Phone verification helps us confirm that the account belongs to you and supports recovery when a sign-in looks unfamiliar. The Privacy Policy covers the verification result and related account record. We may ask for an ownership check before discussing or changing those details.

Open the account support path and ask for a copy of the records connected with your account. Mention your registered phone number and request type, but never include a password or wallet PIN. We verify ownership first and handle the request where local law permits.

When you use a mobile browser, we may record browser type, device signals, IP address and sign-in time for security checks. The Privacy Policy explains that these details can help identify unusual access. We do not use them to request files, contacts or wallet credentials.

You can ask us to correct an inaccurate account detail or request deletion through the privacy support route. We first confirm account ownership. Some payment, dispute or security records may need to remain for a stated period where local law permits.

Cookies may remember a session, language choice or security preference. You can change browser cookie settings, but blocking essential cookies may sign you out or require phone verification again. The Privacy Policy explains which cookie purposes support access and which choices are available.