Reference

hokijp88 Privacy Policy For Your Account

Our Privacy Policy explains what we collect, why we use it and how you can ask about your account data before opening access to the lobby.

Clear data purposesWallet status recordsMobile account accessPolicy request path
hokijp88 hokijp88 Privacy Policy For Your Account
HELP WITH DATA

Privacy Policy Support For Account Questions

A clear contact route helps you resolve a Privacy Policy question without repeating your account story. Start from the support path connected to your hokijp88 account and include the email or phone detail used at registration, plus the subject of your request. We may ask for a receipt reference when your question concerns DANA, OVO, GoPay or QRIS. Do not send a password, one-time code or full wallet credential. Our team can explain a stored record, a correction request or an access question where local law permits.

Team online

Account data request

Use the account support path to ask which registration details we hold and why they are used. Include your registered contact detail so we can locate the correct record without asking you to send a password or one-time code.

Wallet record query

For a DANA, OVO, GoPay or QRIS receipt question, provide the payment reference and approximate date shown in your account. We use that detail to check a wallet status while keeping the request separate from your private wallet credentials.

Correction or access

If a Privacy Policy request concerns an incorrect phone detail, login record or device entry, tell us what needs checking through support. We will explain the next account step and any limits that depend on local law.

DATA PRACTICE

How We Apply This Privacy Policy

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

Account data

We use your registration details to create and maintain your account, connect phone verification and respond to account requests. A change to your registered contact detail may require an account check so we do not disclose private records to the wrong person.

Cookies and sessions

Cookies can keep a login session connected and help us understand which Privacy Policy page brought you to a request. You can manage browser cookie controls, although limiting them may require another login when you return from a mobile device.

Security events

Login time, device type and security events help us investigate unusual access. If your account opens on a new phone, we may request the registered contact detail or phone verification before discussing private account data.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a receipt to the right account. We use the reference for status checking and reconciliation, while wallet passwords and one-time codes remain yours to protect.

Retention choices

We keep account and support records for as long as needed to operate access, resolve a payment query, address a dispute or meet a legal duty. When a record is no longer needed for those purposes, our process removes or de-identifies it.

Your request path

You can ask what data we hold, request a correction or ask how a record is used through the support path. Tell us the account detail involved, and we will explain the available action where local law permits.

Privacy Policy Answers For hokijp88

These Privacy Policy answers address the account and payment questions you may search before opening access. They focus on the records created by login, phone verification, device use and wallet status, rather than describing unrelated lobby features. If your situation is not covered, send the account detail and request through support; eligibility and available actions depend on local law.

The Privacy Policy covers registration details, phone verification, login activity, device records, cookies, support messages and payment references. It explains how we use those records for account access, security, service operation and legal duties, including status checks for DANA, OVO, GoPay and QRIS.

Phone verification connects account access to the contact detail you provided and helps us check that a private request comes from the account holder. If you sign in from another mobile device, this step may be needed before we discuss account data.

Yes. The Privacy Policy covers payment references connected to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use a reference, date or receipt detail to investigate a status question, and we do not need your wallet password or one-time code.

Use the account support path and state that you want to ask about your personal data under the Privacy Policy. Include your registered phone or email detail and the records involved. We may verify account ownership before explaining what can be provided where local law permits.

You can request a correction when a registered contact detail, device entry or other account record appears inaccurate. Tell support what looks wrong and what should be checked. We may ask for phone verification before changing an account record or confirming the result.

We retain records while they are needed for account operation, security checks, payment reconciliation, dispute handling or legal duties. After that need ends, our process removes or de-identifies the record. The exact period can depend on the record type and applicable local law.

Yes. Our Privacy Policy explains that cookies may keep a session connected or measure page activity. You can adjust browser controls, but blocking certain cookies may sign you out or require another login when you return from a phone or desktop device.