Reference

Open detik55 Privacy Policy Before Account Access

detik55 Privacy Policy explains how we handle your account details, wallet references and mobile-browser signals before you enter the lobby.

Account dataWallet referencesCookie choicesMobile access
detik55 Open detik55 Privacy Policy Before Account Access
POLICY HELP PATH

Check Privacy Help Through Your Account

A clear support route helps when you cannot identify a wallet record or need to ask about personal data. From your account support path, include the registered contact detail, transaction reference and the specific Privacy Policy question. We use those details to locate the relevant record while limiting unnecessary disclosure.

Team online

Account privacy request

Ask us to explain a data field, confirm its purpose or correct an account detail through the support path attached to your account. Please avoid sending wallet PINs or full payment credentials.

Wallet record check

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, provide the payment reference and date. We can compare the record without requiring your private wallet password.

Policy change request

If you want a correction, restriction or removal request assessed, state the account step involved and the data concerned. We may ask for account verification before making a change.

HANDLING DETAILS

Explore Security Rules Beside Wallet Status

Privacy work follows the same account steps you see when signing in, checking wallet status or opening a mobile lobby.

Data we handle

We may handle your contact details, account credentials, verification results, sign-in events, device signals and transaction references. The Privacy Policy connects each data type to a stated account, security or payment purpose.

Cookies and sessions

Cookies and similar browser storage help keep your session connected while you move from login to wallet status or the lobby. You can adjust browser controls, although some account steps may then need repeating.

Account security

We use sign-in records, device signals and phone verification steps to identify unusual account activity. Keep your password and verification code private; our support route will not need your wallet PIN.

Retention periods

We retain account and payment records for the period needed for account administration, dispute handling, security checks or legal duties. When a record is no longer needed, our process moves toward removal or anonymisation.

Who handles requests

Our account support team receives Privacy Policy questions and routes them to the staff responsible for data handling. We may verify your account before discussing personal records or accepting a removal request.

Requesting changes

You can ask us to correct account data, explain its use or assess deletion where applicable. Include the registered contact detail and requested change so we can respond to the correct account.

Find Privacy Policy Answers Before Opening

These Privacy Policy answers address the account, device and payment questions we expect from Indonesian customers. If your situation involves DANA, OVO, GoPay, QRIS or a bank reference, use the account support route with the relevant transaction detail.

It covers account details, phone verification, sign-in events, mobile-browser signals, cookies, payment references and retention. It also explains request paths, provider handling and changes to your privacy choices.

We use account data to create access, confirm phone verification, protect sign-ins, connect wallet status and respond to support requests. We aim to collect only what each stated purpose requires.

Yes. The policy covers references, amounts, status and timestamps connected with DANA, OVO, GoPay and QRIS. It does not require us to collect your private wallet PIN for reconciliation.

Browser and device signals help keep your session connected and identify unusual sign-in patterns. They can also support troubleshooting when the mobile path from login to wallet status does not behave as expected.

You can ask for a correction through the account support path. State the registered contact detail, the field needing change and the reason; we may verify account ownership before updating the record.

Retention depends on the record and its purpose. Account, payment and security records may remain for administration, disputes or legal duties, then move toward removal or anonymisation when no longer needed.

Yes. Access and eligibility depends on local law, and our data handling applies where local law permits. If a legal rule affects a request, we will explain the relevant limitation through account support.