Reference

hongkong pools Privacy Policy for Indonesian Accounts

hongkong pools Privacy Policy explains what we collect when you open an account, sign in from a phone, or use DANA and QRIS for account transactions.

Account dataWallet recordsDevice accessCookie choices
hongkong pools hongkong pools Privacy Policy for Indonesian Accounts
CONTACT PATHS

Where To Ask About Your Account Data

A clear contact path helps when you want to ask about a record, correct an account detail or understand a wallet reference.

Account access path If your phone verification record looks wrong, contact our support desk with the account contact used during registration. We use that detail to locate the request and explain the available correction path.
Wallet status path For DANA, OVO, GoPay or QRIS records, share the transaction reference and date rather than private wallet credentials. We can check the stored status and explain which data is retained.
Policy request path To ask for a copy, correction or removal assessment, state the Privacy Policy request clearly through support. We may verify account ownership before changing or releasing personal data.
RECORD HANDLING

Cookies, Devices and Account Records

We keep this Privacy Policy practical by linking each data purpose to an account action.

Account opening

When you open an account, we collect the contact details and phone verification result needed to create and protect that account. We use these details to distinguish your request from an unknown access attempt.

Login device

A mobile browser may provide device and session signals when you sign in. These signals help us identify unusual access and maintain the account path from phone verification to the lobby.

Cookies

Cookies can remember session choices and help pages load as you move between account areas. You can manage cookies through your browser settings, though some account steps may then require another sign-in.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references are used to match a transaction status with the correct account. We do not need your wallet password for that matching step.

Retention

We assess retention by purpose: account security, transaction reconciliation, support handling or a legal requirement. When a record is no longer needed for those purposes, it enters our deletion or restriction process.

Request changes

You can ask to inspect, correct, restrict or remove eligible personal data by contacting support. We first confirm account ownership, then explain the result and any limit that depends on local law.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the searches we hear most often about account records, local wallets, cookies and access requests. If your case involves a specific transaction or phone verification step, include that detail when contacting us so we can assess the correct record.

It covers account details, phone verification, device and session signals, cookies, payment references, support messages, retention and requests to access or change eligible personal data.

No. We use transaction references and status results from DANA or QRIS to match an account record. Do not send a wallet password through support or any account message.

Yes, you can contact support with a clear request for the data connected to your account. We may confirm phone verification or another account detail before releasing a copy.

Send the correction request through our support path and identify the account contact used during registration. We will check the record, confirm ownership and explain the available change.

Retention depends on the purpose, such as transaction matching, account security, support handling or a legal requirement. We assess records for removal or restriction when that purpose ends.

You can adjust cookie settings in your mobile browser. Some session or account steps may then require another sign-in, and certain functions may not retain your page choice.

Yes. The way we handle access, correction, restriction or removal requests depends on local law. Where local law permits, we explain the available route and any applicable limitation.