Reference

Open the holywin88 Privacy Policy Clearly

Our holywin88 Privacy Policy explains what we collect when you create an account, sign in, browse Live Football Odds or open Madame Destiny, and connect a local wallet.

Account data explainedWallet records clarifiedAccess requests supported
holywin88 Open the holywin88 Privacy Policy Clearly
CONTACT THE TEAM

Ask About Privacy Policy Access

A clear contact route helps when a phone check, wallet reference, or stored account detail needs explanation.

Account access Ask through the signed-in support chat when your phone verification, login record, or account profile needs correction. We may request an account detail before discussing personal data, so another person cannot use a simple wallet reference to obtain your records.
Wallet reference For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account query, share the transaction reference rather than a wallet password or full security code. We use the reference to find the relevant record while limiting unnecessary payment details.
Privacy request Send a correction, access, deletion, or processing question through our available support path. Tell us which account detail or cookie concern you mean, and we will explain the next verification step before changing or disclosing anything.
HANDLING YOUR DATA

Check How holywin88 Handles Your Data

Our Privacy Policy is applied through practical account controls rather than broad promises. We separate login details from payment references where the workflow allows, limit internal access to records needed for a…

Account records

When you open an account, we collect the details needed for login and phone verification. Your chosen account path may later connect activity from Live Football Odds, E-Sports Arena, or Super Bingo, so we can answer an access or security question accurately.

Payment references

A wallet or bank record is handled as a transaction reference, not as permission to view your wider financial account. DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri, and BNI details are used only where needed to match your submitted payment step.

Cookies and devices

Cookies can remember sign-in state, language choice, and the page needed to return to your account. On a phone browser, device signals may help detect a changed session; clearing cookies can require phone verification again before access continues.

Account security

We use phone verification and session checks to reduce unauthorised account access. Never send a password or security code in support chat. If a sign-in looks unfamiliar, tell us through the account support path so we can review the relevant access record.

Retention period

We keep personal and payment records for the period needed to operate the account, resolve a transaction question, protect access, or meet a legal requirement. When a reason ends, we remove or anonymise the record under our retention process.

Change requests

You can request access, correction, deletion, or an explanation of processing through support chat. Identify the account detail concerned, complete the verification step we provide, and tell us whether the request concerns cookies, login data, or a payment reference.

Find Privacy Policy Answers Before Opening

These Privacy Policy answers cover the questions we expect before you create an account or connect an Indonesian wallet. They explain the records behind phone verification, mobile browser access, payment references, cookies, and requests for account data. If your case is unusual, use the support route described above and avoid sending passwords or security codes.

It covers account and phone-verification details, device and cookie signals, support messages, game-session records, and payment references from DANA, OVO, GoPay, QRIS, bank transfer, or virtual account steps. It also explains retention, security checks, and how you can request access or correction.

Phone verification connects the person opening the account with the login record and helps reduce mistaken access to personal data. We may ask you to complete it again after cookies are cleared, a mobile browser session changes, or an account request needs identity confirmation.

Yes. The Privacy Policy covers the payment reference created when you use DANA or QRIS, as well as OVO, GoPay, bank transfer, or virtual account steps. We use that reference to reconcile the account action and answer a payment-status question without requesting your wallet password.

Use the support chat available after sign-in and state that you want an account-data access request. Tell us whether you need login details, cookie-related records, game-session data, or a payment reference. We will confirm the account step before preparing a response.

You can ask for correction or deletion through our support path. Describe the specific record, such as an outdated phone detail or an unnecessary cookie concern, and complete the verification step. Any request is handled where local law permits and may be limited by legal retention needs.

We keep payment references for as long as they are needed to match a transaction, resolve a dispute, protect the account, or meet a legal requirement. This can include DANA, OVO, GoPay, QRIS, bank transfer, and virtual account records; later, data is removed or anonymised.

Do not send your password or security code in chat. Sign out where possible, complete phone verification when prompted, and contact support with the account detail and approximate time of the unusual session. We will use the relevant access record to explain the next security step.