Reference

game8jp Privacy Policy, Made Clear

game8jp Privacy Policy explains how we handle your account, phone verification, wallet references and device access when you use our Indonesia lobby.

Account dataWallet referencesCookie choicesSecurity controls
game8jp game8jp Privacy Policy, Made Clear
CONTACT YOUR WAY

Privacy Questions Reach the Right Desk

A clear contact route helps when your account record, cookie choice or wallet reference needs attention. Start from the account help path and include the email or phone detail linked to your profile, plus the subject of your request. Our support desk can direct privacy matters separately from a stalled DANA, OVO, GoPay or QRIS status check. Do not send a password, one-time code or full payment credential in a message. We may ask for an account step to confirm that the request comes from you.

Team online

Account help path

Use the help route connected to your account when you want to ask about stored contact details, phone verification records or a privacy request. Including your account identifier helps us locate the right record without asking you to disclose a password or one-time code.

Payment reference check

If your privacy question involves DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, share only the relevant reference and date. We use that limited detail to find the status record while keeping your wallet PIN, password and full payment credentials out of the request.

Security escalation

Tell our support desk promptly if a login event, device signal or phone verification record looks unfamiliar. We can route the concern for an account check, and you should change your password through the account path rather than placing secret credentials in chat or email.

DATA CONTROL POINTS

What We Do With Your Account Data

We apply this policy to the practical records created around your account rather than treating every detail the same way.

Collection limits

We collect details needed for account access, phone verification, security checks, support handling and payment reconciliation. For a QRIS or wallet status question, the useful record is normally a reference and event detail, not your wallet PIN or complete credential.

Cookie settings

Cookies and similar browser storage can remember a session, selected settings or security signals. You can clear site data through your browser settings on Android, iPhone or desktop; clearing it may require you to complete phone verification again before account access.

Account protection

We use login events, device signals and phone verification to help protect your account. Keep your password private and avoid sending one-time codes to support. If an unfamiliar device appears, use the account help path so we can assess the event without exposing private credentials.

Retention choices

We keep account, support and transaction-reference records only while they serve account operation, security, dispute handling or legal duties. When a record no longer has a valid purpose, we remove it or retain it in a form that no longer identifies you where appropriate.

Who receives requests

Privacy requests are handled by the team responsible for account records and support routing. A payment-status question may need the related DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference, but we do not ask you to disclose a wallet PIN or password.

Changes to your record

You can ask us to correct inaccurate account details, explain a data use, provide a copy where applicable or remove data that no longer needs to be kept. We may verify the request through your account email, phone step or another account-matching check.

Privacy Policy Questions for game8jp

These Privacy Policy answers focus on the questions you may have before opening an account or contacting us about stored data. They cover account creation, wallet references, cookies, device access, retention and requests for changes. If your situation is not covered, use the account help path and identify the specific record or event you want us to check. Access and eligibility depend on local law.

It covers account details, phone verification, login and device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account requests. It explains why we use those records, how we protect them, retention and your request options.

Phone verification helps connect account access to the correct account holder and supports security checks when a login or device event looks unusual. We may use the verification record to protect access, but you should never send your verification code or password to support.

Yes. We may retain a limited payment reference, status event and related account record for DANA, OVO, GoPay or QRIS. The same approach can apply to bank transfer and virtual account requests. We do not need your wallet PIN or full payment credential to check a status.

Use the account help path and state which detail is incorrect, such as an email address or phone record. We may ask you to confirm the request through the linked account contact or phone step before changing the record, so another person cannot alter your profile.

You can request deletion through the account help route. We assess which records can be removed and which must remain for security, dispute handling or legal duties. Where retention is required, we can explain the reason and limit the record to that purpose.

Cookies or browser storage may keep your session, selected settings and security signals. You can clear or restrict them through your Android, iPhone or desktop browser. Clearing them may sign you out, reset preferences or require phone verification again when you return.

Start with the account help path and include your account identifier, request type and relevant event date. For a wallet question, provide only the DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference needed to locate the record, never a password or PIN.