Reference

Privacy Policy for Your data hk 4d Account

data hk 4d Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between the lobby and your wallet.

Account recordsWallet detailsDevice controlsPolicy requests
data hk 4d Privacy Policy for Your data hk 4d Account
CONTACT ROUTES

Ask About Your Privacy Policy

A clear contact path helps you act on this Privacy Policy without searching through the lobby.

Account contact Use the support contact linked from your signed-in account to ask for a copy of your personal data, explain a correction, or question how an account record was created. We check the account step first so details are not disclosed to the wrong person.
Wallet query For a privacy question tied to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity, send the transaction reference without sharing a wallet password or full security code. We use the reference to locate the relevant status and explain its data use.
Access concern If a sign-in or device change makes you concerned about personal data, contact the support desk through the account path and describe the device behaviour. We can review session details, help secure access and explain which records may be retained for protection.
HANDLING DETAILS

What Our Privacy Policy Covers

We keep this Privacy Policy practical by linking each data category to an account action you recognise.

Data collection

We collect information you enter during account opening, including contact details and verification responses, along with activity records such as sign-in time, device type and pages requested. We use these details to provide account access and identify unusual behaviour, not to ask for unrelated personal details.

Cookie choices

Cookies and similar browser signals can remember a session, keep a selected language or show whether a page has loaded correctly. You can adjust cookie controls in your browser, although switching them off may require another sign-in or affect parts of the account path.

Account security

A phone verification step helps connect account activity with the person opening the account. We may record failed attempts, device changes and session identifiers to detect misuse. Never send us a password, wallet PIN or complete security code when asking about this policy.

Retention timing

We keep account, support and transaction references for as long as they serve access, dispute handling, security or legal needs. When a record no longer serves one of those purposes, we remove it, anonymise it or restrict it from ordinary account use.

Correction requests

If your phone number, contact detail or another account field is inaccurate, tell us which entry needs attention and why. We may confirm the request through your account before changing it, then keep a short request record so the correction can be traced.

Data questions

You can ask what personal data we hold, why a wallet reference appears, or whether a device signal was used in an access check. Send the request through the account contact route, and we will explain the next verification step before sharing account-specific details.

Privacy Policy Questions For Indonesia

These Privacy Policy answers address the account and wallet questions you may have before using data hk 4d. We keep the wording direct, but a specific request may still require an account check because personal details should go only to the person they describe. Access depends on local law.

It covers account details, phone verification, sign-in activity, device and browser signals, cookies, support messages and transaction references. It explains why we use each category, how we protect access and how you can request a copy, correction or deletion where applicable.

Yes. The Privacy Policy includes references created when you use DANA, QRIS, OVO, GoPay, bank transfer or virtual account routes. We may retain the reference, status, amount and time needed to match account activity, but you should not send wallet passwords or PINs.

Device type, browser details, IP information and session signals help us keep your account secure and investigate unusual sign-ins. For example, a sudden device change may trigger an account check. These signals are handled for access, security and service operation purposes.

Use the support contact connected with your account and state that you are making a Privacy Policy data-access request. Include the account contact detail and the categories you want explained. We verify ownership first, then outline the available records and next steps.

You can ask us to correct an inaccurate phone number, contact detail or other account field through the account support route. Tell us what appears wrong and the replacement detail. We may confirm your identity before changing the record and logging the request.

Retention depends on the purpose of each record. Account and support details may remain while needed for access or dispute handling; transaction references and security logs may remain for operational or legal needs. We remove, anonymise or restrict records when those needs end.

Yes. Account access and eligibility depends on local law. Our Privacy Policy still explains how we handle personal data when you contact us or use an available account path. If you are unsure about access in Indonesia, contact support before sharing extra personal details.