Reference

Privacy Policy For Your hot15 Account

Our Privacy Policy explains what we collect when you open a hot15 account, use the lobby, or check DANA and QRIS wallet status.

Account dataCookie choicesWallet recordsAccess requests
hot15 Privacy Policy For Your hot15 Account
PRIVACY CONTACT

Get Help With Your Data Request

A clear contact route matters when you need to understand or change personal data held with your account.

Account access If you cannot sign in, tell our account support route that the request concerns your Privacy Policy rights. We first confirm the account contact detail, then explain what data can be accessed or changed without asking for your wallet password or full payment credentials.
Wallet record check For a DANA, OVO, GoPay, or QRIS record, send the transaction reference shown in your account rather than a wallet PIN. We use that reference to locate the matching status and keep payment evidence separate from sensitive wallet authentication data.
Correction request When your phone number or account detail needs correction, provide the existing value and the replacement value through our support path. We may request phone verification before changing the record, which helps prevent another person from taking control of your account.
DATA PRACTICES

What We Do With Privacy Choices

We keep the Privacy Policy practical by tying each data use to an account action you can recognise.

Data collected

We collect the contact details you enter during account creation, phone verification results, sign-in timestamps, device and browser signals, support correspondence, and payment references. Selecting Live Baccarat Table or Sportsbook Odds Board may also create service-use records needed to keep the requested session operating.

Cookie controls

Cookies and similar device storage can keep your login state, language choice, and security checks consistent between pages. You can manage available cookie settings in your browser or device. Disabling some storage may require you to repeat account verification during a later visit.

Account security

We use phone verification, sign-in records, and device signals to detect unusual account access. If a new device opens the iOS App Install path or the mobile website, we may request an extra account check before showing private account or wallet status.

Payment separation

DANA, OVO, GoPay, QRIS, bank transfer, and virtual account records are handled as transaction references and statuses. We use them to match activity to your account and investigate a receipt question; we do not ask you to send a wallet PIN or banking password.

Retention timing

We keep personal data while it supports account operation, security checks, support handling, or a legal record that must be retained. When a record no longer has one of those purposes, we remove it, anonymise it, or restrict access according to the applicable retention requirement.

Your request route

You can ask for a copy of account data, correction of an inaccurate phone detail, clarification about cookies, or deletion where local law permits. Send the request through our account support route with enough context for us to identify the account without exposing another person’s records.

Privacy Policy Questions About hot15

These Privacy Policy answers address the account and device questions you are most likely to have before opening hot15. We explain the records connected to login, wallet status, cookies, and support so you can decide what to share and how to request a change. If your case concerns a specific account, use the contact route above and include only the identifying detail needed for us to locate it.

The hot15 Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, support messages, and payment references. It applies when you use the website or the iOS App Install path where available. Access depends on local law, and we explain any account-specific restriction before handling your request.

No. Our Privacy Policy distinguishes wallet credentials from transaction records. For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity, we use a payment reference and status to match the account action. Never send us a wallet PIN, banking password, or full authentication code in a support request.

Send a Privacy Policy request through the account support route and identify the account contact detail you used. Ask clearly for a copy of your personal data. We may require phone verification or another ownership check before releasing records, so another person cannot obtain your account or payment history.

Yes, you can ask us to correct an inaccurate phone number or contact detail. State the existing value and the replacement value in your request. Because phone verification controls account access, we may pause the change until ownership is confirmed. We will explain the result where local law permits.

Cookies and similar storage can keep your login state, selected language, and security checks available as you move between pages. You can manage them through your browser or device settings. Our Privacy Policy explains that disabling required storage may make you repeat verification or prevent certain account functions.

We retain personal data while it is needed for account operation, security review, support handling, or a record required by applicable rules. Payment references such as a QRIS status may remain for reconciliation. When the purpose ends, we remove, anonymise, or restrict the record under our retention process.

Use the account support route and label your message as a Privacy Policy request. Include your account contact detail, the right you want to exercise, and a relevant reference only when needed. We can address access, correction, cookie questions, retention, or deletion where local law permits.