Reference

Open with bighoki Privacy Policy

bighoki Privacy Policy explains how we collect, use, protect, and remove account data when you access Speed Blackjack or Lucky Neko and connect DANA or QRIS.

Account dataWallet detailsCookie choicesRequest support
bighoki Open with bighoki Privacy Policy
CONTACT ROUTE

Contact us about Privacy Policy access

A clear contact route matters when you want to ask about your Privacy Policy rights or the data attached to your account. We ask you to contact us from the same account where possible, so we can check identity without requesting a wallet password or a full payment credential. If you are in Jakarta or elsewhere in Indonesia, include the account step or device path that caused the concern, such as phone verification, a QRIS status screen, or a browser session. Access depends on local law, and our team can explain which requests we can process.

Team online

Account privacy request

Use the support route connected to your bighoki account to ask for a copy, correction, or deletion of eligible personal data. Include your account identifier so we can locate the right record.

Wallet data question

If DANA, OVO, GoPay, or QRIS appears in a privacy question, tell us the transaction status and date without sending your wallet PIN. We can check the account-side record safely.

Access concern

For a privacy concern after phone verification or a new-device login, describe the browser or phone path and the message shown. We use those details to route your request correctly.

SECURITY PRACTICE

See how Privacy Policy guides data care

We apply the Privacy Policy through ordinary account controls rather than asking you to rely on broad promises.

Collection

We collect account details you submit, phone verification results, login events, device signals, and wallet status needed to connect DANA, QRIS, or other supported payment records to your account.

Use

The Privacy Policy permits data use for account access, security checks, support replies, payment reconciliation, and legal duties. We do not need your wallet PIN to answer an account-side question.

Cookies

Cookies and similar browser storage can keep essential sessions working and remember selected privacy settings. You can manage browser controls, though changing them may affect login or lobby access.

Account security

Phone verification and sign-in checks help protect your account when you move between a phone and desktop browser. Never share a password, verification code, or wallet credential in support contact.

Retention

We retain account, security, and payment-status records only while an operational, dispute, security, or legal reason applies. The policy explains the factors used when storage is no longer needed.

Changes and requests

You can ask about access, correction, deletion, or an objection through the account support route. We may verify that you control the account before changing or releasing personal data.

Browse bighoki Privacy Policy questions

These Privacy Policy answers cover the searches we hear most often before an account is opened or a wallet is connected. They explain what data may relate to Speed Blackjack, Fishing God, DANA, QRIS, phone verification, and mobile browser access. If your situation is not listed, use the account support route and describe the exact request you want to make. Our response and any available action depend on local law.

It covers account details, phone verification, login and device events, cookies, support records, and payment status connected with DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account.

Phone verification helps connect you to the correct account and supports sign-in security. We may use the result to investigate access concerns, but you should not send verification codes through support contact.

Yes. When you use a phone browser to access the lobby, we may process session, device, and cookie data needed for page operation, security checks, and your recorded privacy choices.

You can ask through the account support route for access to eligible personal data. We may first confirm account control, and the available response depends on local law and the type of record requested.

You may request correction or deletion of eligible data through support. Some account, security, payment-status, or legal records may need to remain for the period explained in the Privacy Policy.

Do not send a wallet password or PIN to us. Our account-side records may show payment status or a reference needed for reconciliation, but wallet credentials should remain with your wallet provider.

Open the account support path and state whether you want access, correction, deletion, or an explanation. Include the relevant account step, such as QRIS status or a new-device login, without sharing secret credentials.