Reference

hexa188 Privacy Policy: Your Data Path

Clear account, wallet and device rules are at the centre of the hexa188 Privacy Policy.

Account collectionWallet recordsMobile cookiesAccess requests
hexa188 hexa188 Privacy Policy: Your Data Path
CONTACT PATH

Where to Ask About Account Privacy

A clear contact route matters when your account record or wallet status needs explanation. Start from the support link beside the signed-in account and include the phone number linked to your profile, the relevant date and the payment reference shown for DANA, OVO, GoPay or QRIS. We use those details to locate the right record without asking you to send a password.

Team online

Account access

If phone verification or a sign-in check blocks your policy request, contact support from the account path and describe the screen message. We can check the access record without requesting your password.

Wallet reference

For a DANA, OVO, GoPay or QRIS question, include the receipt reference and status shown beside the cashier record. This gives our team a focused way to match payment data.

Change request

To ask for a correction, access copy or deletion assessment, use the same support route and identify the account phone number. We may ask for verification before changing personal data.

SECURITY RECORD

How Device and Wallet Data Stay Controlled

We keep this policy practical by tying each data action to an account step you can recognise.

Account details

We use the contact details you submit to create your account, send account-related messages and respond to policy requests. If a detail changes, your request can be checked against phone verification.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account entries are kept as matching references. We use status and transaction identifiers rather than asking for wallet passwords or full login secrets.

Cookies

Cookies can keep an account path working and help us understand essential security events. Your mobile browser settings provide a place to clear or restrict cookies, although some account functions may then need checking again.

Device signals

Browser type, device characteristics and security signals may be recorded when you sign in. These checks help identify unusual account access and are assessed alongside the phone verification step.

Retention

We keep personal records only while they support account administration, payment matching, security checks or a legal duty. When a record no longer serves those purposes, we assess removal or restricted storage.

Your requests

You can ask what personal data we hold, request a correction, question a processing purpose or ask for deletion assessment. Send the request through account support so we can verify ownership first.

Privacy Policy Answers for hexa188 Accounts

These Privacy Policy answers address the checks you are most likely to make before opening an account or contacting us. We cover collection, cookies, wallet references, phone verification, access requests and the local-law wording that applies to Indonesian access.

It covers account details, phone verification, payment references, cookies, device security signals, retention and requests to access, correct or assess deletion of personal data connected with your account.

Phone verification helps connect an account request to the correct account holder and supports security checks. It can also help us locate the right record when you ask about Privacy Policy handling.

No. We use transaction references and status details for DANA, OVO, GoPay and QRIS matching. Your wallet password is not needed for us to identify a cashier record or answer a policy request.

We may record browser type, device characteristics, IP-related security signals and cookie settings when you access your account. These details help identify unusual access and support account protection.

Use the support link beside your signed-in account and state that you want a data access request under the Privacy Policy. Include your linked phone number, then complete any ownership check we request.

Yes. Send the correction through account support, identify the field that needs changing and provide the accurate value. We may compare your request with phone verification before making an update.

Our handling is described for Indonesian access, but account access and eligibility depends on local law. If a local requirement changes, the policy link connected to your account shows the applicable wording.