Reference

hot50i Privacy Policy: Your Data, Clearly Handled

Our Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and browse titles such as Live Blackjack Table or Color Game Live.

Clear data purposesWallet-aware handlingPhone verificationIndonesia access
hot50i hot50i Privacy Policy: Your Data, Clearly Handled
HELP CHANNELS

Get Privacy Help Through Account Chat

A direct support path helps you ask about a data record without sending sensitive wallet credentials through an open channel. Start from the account support form or account chat, include your registered phone number and the relevant transaction reference, and we will use those details to locate the request. Our stated support window is 09:00–22:00 WIB, including requests about cookies, phone verification, payment matching or access where local law permits.

Team online

Account support form

Use the signed-in support form for a copy request, correction request or question about the personal details attached to your hot50i account. Add the transaction reference if your question concerns DANA, OVO, GoPay, QRIS or a bank transfer.

Account chat

Account chat is suited to access questions when your phone verification is pending or a wallet status looks unfamiliar. We may ask for an account identifier, but we will not ask you to disclose a wallet password or full payment PIN.

Receipt status path

Keep your QRIS receipt, virtual account reference or bank transfer record when contacting us. That reference lets our team separate a payment-status question from a broader Privacy Policy request and respond within the 09:00–22:00 WIB support window.

DATA CONTROLS

Six Controls Around Your Account Data

We handle privacy through practical account controls rather than broad promises. The lobby may open on a mobile browser, while a desktop session can show a wider account area; the same account…

Data collection

We collect details you provide during account creation, including your phone number and verification status, plus information created when you request support. Browsing a title such as Aviator Fast Round may also create device and session records used to keep the account path working.

Cookie choices

Cookies and similar browser storage can remember a session, preserve a selected language or connect a return visit to the correct account path. You can clear them through your browser settings, although clearing session storage may require phone verification again.

Account security

Phone verification helps connect account access to the registered number, while device and session checks can flag an unusual sign-in. If access to your account changes unexpectedly, use account chat rather than sending a password or wallet PIN in a message.

Payment matching

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account payments, we use transaction references and status information to match the payment with your account. We keep the payment record needed for reconciliation without requesting your private wallet password.

Retention periods

We retain account, support and payment records only for the period needed for the stated purpose, account safety, dispute handling or a legal duty. When a record is no longer needed, our handling process removes it or separates it from direct account identification where practical.

Change requests

You can ask us to correct inaccurate profile details, explain a data use, provide available account records or clarify a retention reason. Send the request through the signed-in support form, and include the phone number connected to your account so we can confirm ownership.

Privacy Policy Questions Before Account Access

These answers address the privacy questions we expect before phone verification or a first wallet transaction. They focus on the records created by an account, the way payment references are handled, the role of cookies and the route for asking us to change or explain personal data. Access depends on local law.

It covers personal details you submit, phone verification, device and session records, cookies, support conversations and payment references connected with your account. It also explains why we use each category, how retention works and how you can request access, correction or clarification where local law permits.

No. Our payment workflow uses transaction references and status details to match DANA or QRIS activity with your account. We do not need your wallet password or payment PIN to record a deposit, investigate a receipt or answer a status question.

Phone verification links account access to the number you provide and helps us distinguish an authorised sign-in from an unusual session. We may retain the verification result and related security record for account protection, support and any applicable legal duty.

Cookies can keep a browser session active, remember a language choice and help route you back to the correct account area. You can remove them in your browser settings. After removal, the site may ask you to verify your phone again before account access.

Yes. Use the signed-in support form and ask for the personal data connected to your account, its purpose or its retention reason. Include your registered phone number and a clear request. We may confirm account ownership before releasing account-specific records.

Send a correction request through account chat or the support form, explaining which profile detail is inaccurate. A phone number, name field or payment reference may require an ownership check. We will assess the request under applicable local requirements and update records where appropriate.

We keep records for the time needed to match payments, protect account access, answer disputes, provide support or meet a legal duty. The period can differ by record type. You may ask us why a particular DANA, bank transfer or support record remains stored.