Reference

Privacy Policy for disco388 Accounts

disco388 keeps its Privacy Policy close to the account steps you use for DANA, OVO, GoPay and QRIS.

Account clarityWallet contextMobile access
Browse the lobby Read FAQ
disco388 Privacy Policy for disco388 Accounts
CONTACT ROUTES

Get Privacy Policy Help Without Guesswork

A clear contact route matters when your account record, wallet status or device access does not look right. Our support path is available for Privacy Policy questions, including requests to correct account details, clarify a payment receipt or ask how long a record is retained. Include the phone number linked to your account and the relevant transaction reference, but never send a password or wallet PIN. We use those details to locate the right case while limiting unnecessary disclosure.

Team online

Account data request

Ask us to confirm which account details we hold, including your phone verification status. We may request an account step or matching identifier before discussing the record, so a private request is not disclosed to another person.

Wallet receipt check

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, send the receipt reference through our support path. We compare the payment status with your account record and avoid asking for your wallet PIN.

Correction request

If your name, phone detail or device record needs correction, tell us what appears inaccurate and why. We review the request against the account step used to reach the lobby before changing a stored detail.

DATA PRACTICE

Six Ways We Handle Your Privacy

The Privacy Policy is practical because each account action creates a different data question.

Account details

We use the details you submit during account creation and phone verification to identify your account and respond to requests. We do not need your wallet PIN to answer a Privacy Policy question or check a basic account record.

Device signals

When you open the lobby on a mobile browser or desktop, technical signals such as device type, browser session and security events may be recorded. These signals help us identify unusual access and keep the correct account session active.

Cookie choices

Cookies and similar storage can remember session settings and help pages load in the path you selected. You can manage browser controls on your device, though disabling certain storage may interrupt login, phone verification or the wallet status display.

Payment matching

A DANA, OVO, GoPay or QRIS reference lets us match a payment event to the correct account. For bank transfer and virtual account requests, related references may remain so we can reconcile status questions and payment receipts.

Security checks

We may compare phone verification, session details and account activity when access looks unusual. If you contact us about a locked or unfamiliar session, provide the account identifier requested by support and keep passwords and wallet PINs private.

Retention and changes

We retain records only for the operational, security, dispute or legal reasons described in this Privacy Policy. You can ask what applies to your record, request a correction, or ask about removal where local law permits and no required duty prevents it.

Privacy Policy Answers for disco388

These Privacy Policy answers focus on the searches you may make before opening an account or sending a wallet request. We keep the wording tied to actual steps: phone verification, device access, payment references and support contact. If your question concerns eligibility or access in Indonesia, the answer can depend on local law, so use the contact route shown above when your situation needs a direct response.

It covers account details, phone verification, device and session signals, cookies, support messages, payment references and retention. It applies to activity connected with the lobby, including account access and wallet status checks for DANA, OVO, GoPay, QRIS, bank transfer and virtual account requests.

We use the phone number you submit for account identification and the required verification step before account access. It also helps support locate the correct record when you ask about a Privacy Policy matter. We will not ask you to share a password or wallet PIN.

Yes. The policy covers payment references and status details needed to match DANA or QRIS activity with your account. The same approach applies to OVO, GoPay, bank transfer and virtual account requests. Wallet credentials remain with the relevant payment service.

When you access the lobby from a phone or desktop, we may record device type, browser session, technical events and security signals. These details help maintain the correct login and investigate unusual access. Cookie controls on your device can affect session settings and page continuity.

Yes. Send a correction request through the support path with the inaccurate detail and a reason for the change. We may verify your phone or account identifier before making an update. This process helps prevent another person from changing your account record.

Retention depends on why a record exists, such as account security, payment reconciliation, support handling, dispute review or a legal requirement. You can ask us which retention reason applies to your record. Removal requests are handled where local law permits and no required duty applies.

Use the support contact path connected with your account and describe the request clearly, such as access, correction, retention or deletion. Include the relevant account identifier or payment reference when needed, but do not include a password, wallet PIN or complete security credential.

Related Pages

disco388 Indonesia Basketball IBL Bet Account information About Us Access guide