Reference

Privacy Policy For Your detik288 Account

detik288 explains how we collect, use and protect the account details connected with your lobby access and local wallet activity.

Account dataWallet recordsCookie choicesPrivacy requests
detik288 Privacy Policy For Your detik288 Account
HELP WITH DATA

Privacy Support Beside Account Help

A clear support path matters when a privacy request is tied to a login, wallet status or account record. We route privacy questions through the account help area so you can identify the relevant account step without sending sensitive credentials in an open message. If your question concerns DANA, QRIS, a bank transfer or a virtual account reference, include the date and transaction reference where available. We then use the smallest practical set of details to locate the matter and respond.

Team online

Account help route

Open the account help area for a Privacy Policy question, identify the email or phone detail connected with your account, and describe the request plainly. We may ask for a verification step before discussing account-specific data, but we will not ask for your password.

Wallet record request

For a DANA, OVO, GoPay or QRIS record, provide the relevant reference and date rather than a wallet password or full security code. This helps us locate the correct event while limiting the personal data included in your support request.

Access issue path

If a phone verification step blocks account access, mention the device and browser path you used, such as mobile Chrome or desktop web. We can separate a privacy question from a login issue and direct the request to the right account check.

DATA HANDLING

What We Do With Your Account Data

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

Account creation

When you open an account, we use the submitted contact details and phone verification result to create the account path you requested. The same records help us respond when you ask about access, a profile detail or a previous support conversation.

Cookies and devices

Cookies and device signals can remember a session, browser setting or security event. On mobile, clearing site data in your browser can remove local session storage and require another login; it does not automatically erase account records held on our systems.

Wallet matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may be used to match a payment question with the correct account event. We aim to avoid collecting complete wallet credentials when a reference is enough to investigate.

Account security

We use phone verification and sign-in details to help protect account access. If a login appears unusual, we may request an additional account check before discussing personal data or changing details connected with the profile.

Retention choices

We retain records for as long as they are needed for the account service, security checks, dispute handling or a legal duty that applies to us. You can ask which category concerns you and request deletion or restriction where the applicable rule allows it.

Changing your details

If your phone or contact detail is inaccurate, use the account help route and state what needs correction. We may verify your identity before making a change, because altering an account record without a check could expose your wallet or login history.

Privacy Policy Questions About detik288

These answers address the privacy searches we expect before you open an account or return to the lobby. They cover the data connected with phone verification, cookies, local wallet references, device access and requests to change or remove personal details. If your situation is specific, use the account help path and mention the relevant record without sharing a password.

The Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains how to ask about access, correction, retention or removal of your data.

Phone verification helps connect the account with the person requesting access and supports checks when login details or profile data change. We may ask for another verification step before discussing account-specific records, and we do not need your password to handle a Privacy Policy request.

Yes. Our policy explains how we use a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference to locate an account event or answer a support request. The wallet or bank may apply its own separate privacy terms to data held on its side.

Cookies can help retain a browser session and selected site settings. If you clear cookies or mobile browser storage, you may need to log in again. Clearing local storage does not by itself remove account records, payment references or support history held in our systems.

You can use the account help route to ask what personal data category concerns you or to correct an inaccurate phone or contact detail. We may verify the request before responding, and the available action depends on the rule that applies to your account and location.

We keep data only while it supports the account service, security checks, payment queries, dispute handling or a legal duty that applies. Retention can differ by record type. Ask through account help for the category and reason connected with a particular record.

Start in the account help area and describe whether your request concerns access, correction, cookies, deletion or a wallet reference. Include the relevant date or reference when useful, but never send a password, full security code or unnecessary financial credentials.