Reference

data hk lotto Privacy Policy for Indonesia

data hk lotto keeps your account path, wallet records and lobby access covered by a clear Privacy Policy, whether you open Live Roulette Prestige or Badminton Malaysia Open…

Account data explainedWallet records clarifiedCookie choices includedLocal access wording
data hk lotto data hk lotto Privacy Policy for Indonesia
CONTACT ROUTES

Privacy questions beside your wallet

A clear contact route helps when your Privacy Policy question concerns a login record, phone verification or wallet status.

Account privacy Ask us to locate the account data linked with your phone verification step. Include your account identifier rather than sending a full wallet statement, and we will explain the next check through the support route.
Wallet records For DANA, OVO, GoPay or QRIS records, share the payment reference and approximate date shown in your receipt. We use that narrow detail to trace status without asking you to repeat unrelated account data.
Correction requests If your name, phone detail or contact record needs correction, contact us from the signed-in account path. We may confirm ownership before changing it, helping keep another person from altering your privacy record.
DATA PRACTICE

Mobile account security and data choices

Our Privacy Policy is designed around the moments that create a record: account opening, phone verification, wallet matching and support contact.

Account collection

We collect the account details needed to create your access path, confirm your phone and respond to requests. When you move from login to the lobby, these records help connect the session to the correct account without asking you to create a second profile.

Cookie controls

Cookies can retain session state, language choices and device preferences on a mobile browser. Our Privacy Policy explains their purpose, while your browser settings provide another way to clear stored cookie data when you no longer want that session record.

Payment matching

A DANA, OVO, GoPay or QRIS reference may be stored with a cashier request so we can match a receipt with its status. Bank transfer and virtual account records are handled for the same narrow account and payment check.

Access protection

Phone verification before account access helps us distinguish the account owner from an unapproved sign-in attempt. We may ask for a matching account detail during a privacy request, and we avoid changing records until that ownership check is complete.

Retention timing

We retain account, support and payment records only for the period needed for the stated account, safety and legal purposes. If you ask why a record remains, our support team can explain its category and whether a local rule affects its removal.

Your requests

You can ask for a copy, correction or removal of personal account data where local law permits. Send the request through the account support path, describe the record clearly, and keep your reply channel available for an ownership check.

Privacy Policy answers for your account

These Privacy Policy answers focus on the records you are most likely to notice while opening an account or checking a wallet status. They cover account access, mobile cookies, payment references, correction requests and local eligibility. If your situation is not listed, contact us through the support path with the smallest useful set of details.

It covers account details, phone verification, cookie records, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account requests. It also explains how we use, retain and respond to requests about those records.

Phone verification helps connect account access with the person who created the account and helps us respond safely to privacy requests. If you ask to change or remove a record, we may use the verified account path to confirm ownership first.

Yes. The Privacy Policy covers payment references and status details created when you use DANA or QRIS, as well as OVO, GoPay, bank transfer and virtual account requests. We use those records to match the correct account and answer payment-status questions.

You can contact us through the signed-in support path and ask which account records are held about you. We may request a matching account detail before responding. The scope and timing of a copy request depends on local law.

Send a correction request through account support, name the field that is wrong, and explain the updated detail. We may confirm your phone or account reference before making the change, so another person cannot alter your record.

Yes. You can clear cookies through your mobile browser settings, although this may sign you out or remove saved session preferences. Our Privacy Policy explains why cookies are used, and support can clarify which session record your request concerns.

Yes. Access, correction and removal requests, along with account eligibility, depends on local law. Where local law permits, contact us from your account path so we can identify the relevant record and explain the available response.