Reference

hk pool asli Privacy Policy for Your Data

Our Privacy Policy explains how hk pool asli handles the data connected with your account, device and wallet activity.

Account dataWallet recordsDevice cookiesPolicy requests
hk pool asli hk pool asli Privacy Policy for Your Data
REQUEST A HAND

Ask Email Support Desk About Your Data

A clear contact path matters when you want to ask what the Privacy Policy means for your own account. We direct requests through the Email Support Desk so our team can identify the relevant account, wallet record or device entry before responding. Include the email or account detail connected with your request, but do not send a password or one-time verification code. Where local law permits, we can explain available access, correction or deletion steps.

Team online

Email Support Desk

Use the Email Support Desk when you want to ask which account data we hold, why a phone verification record appears, or how a Privacy Policy request should be submitted. We may ask for account identifiers so we do not disclose data to the wrong person.

Account access request

If you cannot reach the account connected with a Privacy Policy request, tell us the sign-in detail you used and the last wallet route you selected. We use those points to locate the correct record without asking you to reveal your password or verification code.

Wallet record check

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, attach the transaction reference rather than a full wallet credential. Our support route can then check the matching record and explain what the Privacy Policy allows us to change or retain.

HOW DATA IS HANDLED

Switch On Clearer Account Data Handling

We keep the Privacy Policy practical by linking each data purpose to a real account action. Account creation, phone verification, wallet selection and device sign-in can each create different records, so we…

Account collection

We collect the account details you enter, including the contact point used for sign-in and the phone verification result needed before account access. The Privacy Policy explains why these details are linked to your account and how they help us distinguish one account request from another.

Cookies and devices

Cookies and device signals can help keep a sign-in session working and help us notice unusual access. If you move from a mobile browser to desktop, the policy explains that each device may create separate technical records. Clearing cookies can also remove saved session preferences.

Wallet matching

When you select DANA, OVO, GoPay or QRIS, we retain the references needed to match the wallet action with your account. Bank transfer and virtual account records can carry a bank route and transaction reference. We do not need your wallet password for that matching process.

Account security

We use sign-in details, phone verification and device signals to investigate access that does not look consistent with your account. Never send a password or one-time code through support. The Privacy Policy sets out how these checks support account protection without treating every device change as misuse.

Retention choices

We keep account, support and wallet records only for the period needed for the stated purpose, security checks or a legal requirement that applies where local law permits. A retention request can be sent to the Email Support Desk, which can explain what may be removed and what must remain.

Changes and contact

You can ask us to correct account data, clarify a cookie entry or explain a wallet record through the Email Support Desk. Include the specific item and your account identifier. We check ownership first, then respond under the Privacy Policy and any rule that depends on local law.

Browse Privacy Policy Answers Before Opening

These Privacy Policy answers focus on the searches we hear before an account is opened: what data is collected, how wallet records are matched, what cookies do and how to request a change. The examples use the actual account and payment steps connected with hk pool asli, so you can decide what to share before proceeding. If your question concerns eligibility or access, the answer depends on local law.

It covers account details, phone verification, sign-in and device records, cookies, support messages, and wallet references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account use. It also explains retention, security checks, sharing purposes and how you can request access or correction.

The policy covers the transaction reference, selected route, receipt detail and status needed to match a DANA or QRIS action with your account. We do not ask for your wallet password. OVO, GoPay, bank transfer and virtual account activity follows the same record-matching principle.

Phone verification helps connect account access with the person completing the account step and gives us a security signal when sign-in changes. The Privacy Policy explains how the verification result is stored and used. Do not send the verification code to the Email Support Desk.

Yes, send a correction request through the Email Support Desk with your account identifier and a clear description of the incorrect field. We may confirm ownership before acting. The available result depends on local law, and some wallet or security records may need to remain.

Cookies can keep a mobile sign-in session and selected preferences available, while device signals help us assess unusual access. Clearing browser cookies may remove saved session details and require another sign-in. The Privacy Policy explains these uses without treating cookies as wallet credentials.

We retain wallet references and related account records for the period needed for matching, security, support or a legal requirement where local law permits. The exact result can differ by record type. Ask the Email Support Desk about a specific DANA, QRIS or bank reference.

Use the Email Support Desk for questions about account data, cookies, phone verification, wallet records, retention or a correction request. Include only the details needed to identify your account. Never include a password or one-time code, and ask us to explain any unclear policy wording.