Reference

389sport Privacy Policy For Your Account

389sport Privacy Policy explains what we collect when you open an account, sign in, use DANA or QRIS, and move between casino, sports and live table areas.

Account clarityWallet recordsCookie choicesAccess requests
389sport 389sport Privacy Policy For Your Account
CONTACT ROUTES

Get Help With A Privacy Request

A clear request route helps us deal with an account question without exposing your details to the wrong person. Use the support path linked beside your account area and include the email or phone detail attached to your profile, the issue you want checked, and any relevant payment reference. We may ask for an account step before changing personal data.

Team online

Account access request

Ask us to confirm what account details are connected with your sign-in. We may verify the phone or email on file before discussing records or making a change.

Wallet record question

For DANA, OVO, GoPay or QRIS references, send the date and account-linked payment reference. We use those details to locate the correct record without requesting your wallet password.

Cookie choice help

If a mobile browser keeps a setting you did not expect, tell us the device path and browser behaviour. We can explain the available cookie controls and the effect on sign-in.

DATA CONTROLS

Aviator Access And Data Controls

We handle this policy area through identifiable account steps rather than broad promises. Sign-in checks, wallet references and device activity are kept separate from the content needed to show a casino, sports…

Account details

We may use your phone or email, verification status and sign-in history to recognise the account you asked to access. These details help us separate your records from another account.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can connect an account action with a payment record. We do not need your wallet password for that match.

Device signals

Browser type, device path and session timing can help us spot an unusual sign-in. On mobile, these signals may be used when you move from verification to a lobby page.

Cookie settings

Cookies can keep a session and remember a setting, but they do not replace your account verification. You can manage available browser choices, although some sign-in functions may then need another step.

Retention choices

We retain records only for the account, security, payment matching or legal purpose described in the policy. When a retention reason ends, handling follows the applicable deletion or restriction process.

Correction requests

To request a correction, send the account detail that appears wrong and the change you seek. We check ownership first, then explain whether the record can be amended under local requirements.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the account, wallet and device questions you may have before opening access. We keep the wording tied to the actual steps used on 389sport, including verification, payment matching, cookie settings and requests made from Semarang, Makassar or another Indonesian location.

It covers account details, verification, sign-in activity, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

We use the phone or email attached to your account to complete an access check, send account-related messages and match a privacy request with the correct record before making changes.

The policy describes payment references used to match an account action with DANA, QRIS and other supported rails. We do not need your wallet password for that matching step.

Cookies can retain a session or a selected setting while you move from sign-in to a lobby page. Browser controls may remove them, but another account step could then be required.

Yes. Send the detail you believe is wrong and explain the requested correction through the account support path. We first check that you control the related phone or email.

Retention depends on the account, security, payment matching or legal purpose described in the Privacy Policy. When that purpose ends, the applicable deletion or restriction process is considered.

Yes, requests and eligibility depend on local law. Where local law permits, we explain the available access, correction, restriction or deletion route after confirming the account details.