Reference

Privacy Policy for hmd29 Accounts

The hmd29 Privacy Policy explains how we collect, use and protect the data connected with your account, device and wallet activity.

Account dataWallet checksCookie choicesPolicy requests
hmd29 Privacy Policy for hmd29 Accounts
CONTACT OUR DESK

Privacy Help Along Your Account Path

A clear contact route helps when you need to ask about the Privacy Policy or correct account data.

Policy questions Ask our support desk how the Privacy Policy applies to phone verification, login records, device access or a visit to Live Baccarat Salon. We will explain the relevant handling step and tell you what account detail is needed to locate your request.
Data corrections If your phone number, email or account name is no longer accurate, contact us from the account path and describe the correction. We may verify ownership before changing the record, helping prevent an unknown person from altering your account data.
Wallet records For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account query, send the transaction reference rather than wallet passwords or PINs. We use the reference to check status and keep sensitive payment credentials out of support messages.
DATA CONTROL POINTS

Six Ways We Handle Your Data

The Privacy Policy is practical: it describes what happens at account access, during wallet matching and when you return from a mobile device.

Account creation

We collect the contact and verification data required for your account path, then use it to identify the correct account at login. Phone verification can be requested before account access, and we do not need your wallet PIN to confirm ownership.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference lets us match a wallet event to your account. We use the reference and status response for reconciliation, while payment passwords and PINs remain outside our support request process.

Device signals

We may record browser type, device identifiers, login time and general network signals to protect account access. These signals help us compare a returning mobile session with a new device without reading unrelated files or personal content on your phone.

Cookies

Cookies can remember a session choice, support page operation and show us whether a policy page loads correctly. You can clear or restrict cookies in your browser, although some account steps may ask you to enable necessary session cookies again.

Retention

We keep account, security and transaction records for the period needed to operate the account, investigate disputes or meet applicable legal duties. When a record is no longer needed, we remove it or separate it from direct account identifiers.

Your request

You can contact our support desk to ask what data we hold, request a correction, or ask about deletion where local law permits. Include your account contact and a precise request; we may verify ownership before releasing or changing any record.

Privacy Policy Questions for hmd29

These Privacy Policy answers address the account and wallet questions you may have before opening hmd29. We keep the route direct: identify your account, describe the data request, and provide a transaction reference only when a payment record is involved. Access depends on local law.

It covers account details, phone verification, login and device signals, cookies, lobby activity used for operation, wallet references and retention. It also explains how to contact us about access, correction, deletion or another Privacy Policy request where local law permits.

Phone verification helps us connect you with the correct account and reduce unauthorised access. We record the verification result and related account event, not your phone contents. If access is discussed, it depends on local law and the account checks that apply.

Yes. The Privacy Policy covers the transaction references and status data needed to match DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity with your account. We do not ask support requests to include wallet PINs, passwords or full payment credentials.

Contact our support desk from the account path and state that you want a data access request. Include your account phone or email so we can locate it, then complete any ownership check. We will explain the available response under local law.

You can ask us to correct an inaccurate phone number, email or account name. Send the request through support and identify the record that needs changing. We may verify ownership first, and the available correction route depends on local law.

We retain records while they are needed for account operation, security checks, transaction reconciliation, dispute handling or legal duties. After that period, we remove or anonymise them through our retention process. The exact period can vary with the record and local law.

You can manage cookies through your browser settings and contact our support desk with a specific cookie question. Necessary session cookies may be required for login or account steps. Our Privacy Policy explains their operational purpose and the choices available where local law permits.