Reference

Privacy Policy for hoki138 Account Data

Our Privacy Policy explains what we collect when you create an account, verify your phone, sign in from a mobile device, or use wallet options such as DANA…

ACCOUNT DATAWALLET RECORDSDEVICE ACCESSYOUR REQUESTS
hoki138 Privacy Policy for hoki138 Account Data
REQUEST SUPPORT

Contact Routes For Privacy Requests

A clear contact path helps you ask about your personal data without repeating the whole account story. We route privacy questions through the support path connected to your account area, where you can identify the relevant login, wallet reference or device event. Keep your message focused on the request, and we will use the available account record to respond. Access remains where local law permits.

Team online

Account privacy request

Use the support path beside account access to ask which personal records we hold, why a phone verification event appears, or how to request a correction.

Wallet record question

Mention the relevant DANA, OVO, GoPay or QRIS reference when asking about payment-linked data, so we can locate the correct status without broad account searches.

Device access concern

Tell us when a mobile browser, desktop session or unfamiliar login appears in your account history. We can direct the privacy request to the matching security record.

DATA HANDLING

How We Handle Your Account Data

We keep the Privacy Policy practical by linking each data use to an account action you can recognise.

Account creation

When you open an account, we collect the details needed to create your profile and contact you about account access.

Payment matching

A DANA, OVO, GoPay or QRIS reference can be stored with the related account event.

Cookie controls

Cookies and similar browser signals can remember a session, support security checks and preserve page preferences.

Security checks

We examine sign-in time, browser or device signals and phone verification status when access appears unusual.

Retention period

We keep account, support and transaction-linked records only for the period needed for service operations, dispute handling, security checks or…

Changes and deletion

You can ask us to correct, access or remove eligible personal data through the account support path.

Privacy Policy Questions About hoki138

These answers address the searches we receive about the Privacy Policy, account records and Indonesian wallet references. If your situation involves a specific phone number, device session or payment reference, include that context in your request so we can handle the right record. Any access or eligibility decision depends on local law.

The hoki138 Privacy Policy covers account details, phone verification, login events, device signals, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps connect an account access event with the correct account holder. We may retain its status and related time record so we can investigate access questions or security concerns.

We may store the payment status and reference supplied for a DANA or QRIS request, along with the related account event. This helps us reconcile the request without storing details beyond the operational need.

Yes. You can ask about browser, device and session signals linked to your account. Use the support path beside login and mention the approximate time or device so we can locate the record.

Send a correction request through account support and identify the record you believe is inaccurate. We may ask for account or phone verification before changing personal data connected with your profile.

Retention depends on the record and its purpose. Account, support and transaction-linked data may remain for service operations, security checks, dispute handling or legal duties, then be removed when no longer needed.

Use the support route connected to your account area and describe whether your request concerns access, correction, deletion, cookies, a device event or a wallet reference. We will direct it to the relevant record.