Reference

Privacy Policy For Your hot52 Account

hot52 Privacy Policy explains what we collect when you open an account, sign in from a mobile device, use DANA or QRIS, and contact our support path.

Account clarityWallet recordsPolicy accessIndonesia focus
hot52 Privacy Policy For Your hot52 Account
HELP WITH PRIVACY

Reach Us When A Data Question Stalls

A clear contact route matters when your account details or payment record needs attention.

Account request Ask us to access, correct or explain personal details held for your account. Start from the signed-in support path and provide your linked phone number so we can match the request without asking you to repeat private payment credentials.
Wallet record If a DANA, OVO, GoPay or QRIS record looks incorrect, include its receipt reference and approximate date. We compare the reference with the wallet status attached to your account, then explain which record we can amend and which payment record must remain.
Policy contact For a broader Privacy Policy question, use the policy contact route shown on our site and describe the request in plain English. We may ask for an account verification step before sharing details, especially when the request concerns sign-in history or another person’s information.
DATA HANDLING DETAILS

What You Can Check Before Opening

You should be able to see how a policy works before deciding whether to open an account. We explain the data connected with phone verification, sign-in activity, device behaviour, wallet references and…

Account details

We use your account details to create access, complete the clear phone verification step and respond to requests tied to that account. If a name or phone detail changes, ask us for a correction through support so the account record and wallet status stay aligned.

Device signals

A phone or desktop browser can provide device, browser and sign-in details used to recognise unusual access patterns. We use these signals for account security and troubleshooting, not as a substitute for your own verification. Sign out from shared devices after checking your account.

Cookies

Cookies help keep your session working, remember selected settings and connect a signed-in account with the correct page. Browser controls can restrict cookies, although some account or wallet steps may then need another sign-in or may not work as expected.

Payment records

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we retain references needed to check status, match receipts and resolve account questions. We do not need your wallet password for a support request, so leave that credential out of every message.

Retention choices

We retain account, security and payment records for the period needed to operate the account, resolve disputes and meet applicable obligations. When a record no longer serves one of those purposes, our handling follows the retention process described in the current Privacy Policy.

Request changes

You can ask for a copy, correction or deletion review of personal details through the policy contact route. We verify the requester first, explain any limits caused by required account or payment records, and keep the request history so we can show how it was handled.

Privacy Policy Answers For hot52

These Privacy Policy answers focus on the questions you may search before opening an account or checking a wallet record. We keep each response tied to the actual account steps used on hot52, including phone verification, mobile sign-in, payment references and support requests. If a question concerns eligibility or service availability, the answer remains subject to local law.

It covers account details, phone verification, sign-in and device signals, cookies, support conversations and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It explains why we use those details, retention choices and how you can request access or correction.

We use the phone number linked to your account to complete phone verification, support account access and match a privacy request with the correct record. We may ask you to confirm ownership before discussing private details. Do not send a password or wallet credential when contacting us.

Yes. The Privacy Policy covers references and status details connected with QRIS, DANA, OVO and GoPay, along with bank transfer and virtual account records. We use those references to check a receipt or payment status, while avoiding any need for your wallet password.

You can ask for a copy of personal details held for your account through the policy contact route. We first verify that you control the account, then identify the records covered by the request. Some security or payment records may require a retention-based explanation.

Send a correction request through the signed-in support path or policy contact route, including the linked phone number and the detail that needs changing. We compare the request with your account record, may complete another verification step and confirm what was updated.

We keep account, security and payment information only for the period needed for account operation, safety checks, dispute handling and applicable obligations. The exact period can differ by record type. The current Privacy Policy explains the retention approach and how to ask about a specific record.

You may request a deletion review through the policy contact route. We assess the request against account, security and payment-record duties, explain any information that must remain and remove or restrict details where the applicable rules allow. Service eligibility depends on local law.