Reference

hot55 Privacy Policy, Clearly Explained

hot55 Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, or use DANA, OVO, GoPay and QRIS.

Account dataCookie choicesWallet recordsAccess requests
hot55 hot55 Privacy Policy, Clearly Explained
CONTACT ROUTES

Request Privacy Help From Support

A clear contact route matters when you want to ask about personal data rather than a wallet balance. We direct privacy questions through the support path attached to your hot55 account, so our team can match the request with your verified account details. You can refer to a login concern, a cookie choice or a payment record without sending unnecessary documents. When access or eligibility is discussed, our response remains subject to local law.

Team online

Account support path

Open the support area after signing in and state that your request concerns the Privacy Policy. Include the account contact detail you used during verification, but do not send a wallet password or full payment credential.

Wallet record question

For a DANA, OVO, GoPay or QRIS record, share the date, reference shown in your account and the wallet name. We use those details to locate the event while limiting the request to the relevant transaction record.

Access or correction

Ask support to view or correct eligible account data through the same account route. We may ask for a verification step before discussing personal details, which helps prevent another person from receiving your account data.

DATA PRACTICE

Explore How We Handle Your Data

We keep this policy practical by connecting each data use to an account action you can recognise.

Account details

When you open an account, we use the submitted contact details and phone verification status to establish which account is yours. If you change a phone number, we may request another check before updating the record or discussing related data.

Device and browser

A mobile browser or desktop session can provide technical signals such as browser type, operating system and sign-in time. We use these signals to identify unusual access around the lobby, not to read unrelated files or messages on your device.

Cookies and settings

Cookies can keep a session working, remember selected settings and help us understand whether a page request completed. You can manage available cookie controls in your browser; disabling some cookies may require you to sign in again.

Wallet activity

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account event may leave an account reference, amount status and time record. We retain only what is needed for reconciliation, account safety, support handling and applicable legal duties.

Security checks

Phone verification and sign-in checks help us separate your account from an unauthorised attempt. We may pause a data request until the check is complete, especially when it concerns wallet history or access from a new device.

Retention and changes

We keep records for as long as needed for the stated service purpose, account protection or a legal duty, then assess whether they can be removed. You can ask about correction, access or an eligible deletion through support.

Browse Privacy Policy Answers

These Privacy Policy answers cover the searches we hear most often before an account is opened. We explain the practical path for account data, cookies, devices and local wallet records, including what to provide when you contact us. If your situation is not listed, use the signed-in support route and describe the specific record or account step you want us to check.

The hot55 Privacy Policy covers account details, phone verification, device and browser signals, cookies, support requests and records linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security checks and requests to access or correct eligible data.

Phone verification helps us connect an account request with the person who controls its contact detail. It also protects Privacy Policy requests involving wallet history or sign-in activity. We may repeat the check before changing account data or discussing records tied to your account.

Yes. When you use a mobile browser to sign in or open a lobby page, we may receive technical details such as browser type, operating system and session time. We use those signals for access, security and troubleshooting, rather than to inspect unrelated content on your device.

We may keep the wallet name, account reference, status and time connected with a DANA or QRIS instruction so we can reconcile the account event and answer support questions. We do not need your wallet password for a Privacy Policy request or a status check.

You can request a correction through the signed-in support path. Tell us which account detail is wrong and provide the verified contact detail used at account creation. We may ask for an additional identity check before making a change to protect the account.

Open support from your account and identify the data category you want us to check, such as phone verification, cookie settings or a GoPay record. We will assess the request under applicable law and may limit disclosure where another person’s data or a legal duty is involved.

We retain each record only while it supports the stated account purpose, security, support handling or an applicable legal duty. Wallet references and sign-in events can therefore have different periods. Ask support about a category, and we will explain the available retention position.