Reference

holiganbet Privacy Policy For Your Account

holiganbet Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between the lobby and cashier.

Account dataCookie choicesPayment recordsRequest changes
Explore our lobby Read FAQ
holiganbet holiganbet Privacy Policy For Your Account
HELP WITH PRIVACY

Three Ways To Ask About Your Data

A clear contact route matters when your account record needs attention. Use the support path connected to your account when you want to ask why a phone check is needed, query a DANA receipt, or request a correction to your details. Include the email or phone linked to your account and a short description, but do not send a password or one-time code. We use the details you provide to locate the request and respond about this Privacy Policy.

Team online

Account support

Open the signed-in support path for a privacy question about your name, phone verification or login record. We can use the account identifier you provide to locate the relevant record without asking you to disclose a password or one-time code.

Payment record help

If a DANA, OVO, GoPay or QRIS reference appears in your account history, send the transaction reference through the support route. We use it to identify the record under discussion and explain its handling under the Privacy Policy.

Data change request

Ask us to correct account details or clarify a retention question through the available contact path. State the requested change clearly, use your linked contact detail, and we will assess the request against account security and local legal requirements.

DATA PRACTICES

How We Handle Account Records

We apply the Privacy Policy to the practical moments you recognise: creating an account, confirming a phone number, signing in from a mobile device, and checking a wallet record.

Account creation

When you open an account, we collect the details needed to create your profile and establish a contact route. Phone verification happens before account access, so we can connect the verified number with the correct account record.

Phone verification

The phone check confirms that the contact detail used for your account belongs to you. We retain the result and related security record for the period needed to protect access, handle disputes and meet applicable legal duties.

Device signals

Your browser or mobile device may provide sign-in signals such as device type, session details and approximate network data. We use these signals to spot unusual account activity, not to replace the account checks required for a data request.

Cookies

Cookies can remember session settings and help pages load in the way you selected. You can manage cookie controls in your browser, although disabling some cookies may affect sign-in continuity or the way policy choices are saved.

Payment records

A bank transfer, virtual account, DANA, OVO, GoPay or QRIS reference may be stored with account activity. These records help us reconcile a cashier entry, investigate a disputed receipt and answer questions about how payment data is used.

Retention requests

We keep records only for operational, security or legal reasons described in the Privacy Policy. To ask about deletion, correction or retention, contact us from your linked account route so we can verify the request safely.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the searches we hear around account creation, local wallets, device access and data requests. If your question concerns a record that is not covered here, use the account support path and quote the relevant section. We will assess your request using the current policy and the rule that access depends on local law.

It covers account details, phone verification, sign-in activity, device signals, cookies, payment references and support messages. It also explains why we use each category, how long records may remain, and how you can ask for a correction or other data action.

Phone verification links a contact detail to the correct account before access. The result helps protect your account and lets us assess a privacy request safely. We do not need your password or one-time code when you contact support about the policy.

Yes. A DANA or QRIS transaction can create a reference, amount and status connected with your account activity. We use that record to reconcile the cashier entry, investigate a receipt question and explain payment-data handling under the current Privacy Policy.

Yes. It describes cookies used for sessions and saved choices, along with device signals that can help identify unusual sign-ins. Your browser controls cookies, while disabling some settings may change how login continuity or policy preferences work on mobile.

Use the support path linked to your account and state which detail should be corrected. Include the linked email or phone, but never send a password or one-time code. We verify the request before changing a record or explaining why a restriction applies.

You can ask about retention through account support. The period depends on the record, its security purpose and applicable legal duties. Payment references, phone-check results and support messages may not follow the same timetable, so we assess each request separately.

Access and eligibility depend on local law. The Privacy Policy explains data handling when the service is available to you, but it does not change local requirements. Check your local position before opening an account and contact support if a policy clause needs clarification.

Related Pages

holiganbet Indonesia Tennis Grand Slam Access guide Live Roulette Prestige About Us