Reference

9zkgames Privacy Policy For Your Account

9zkgames explains how we handle account details, wallet records and device signals while you move between Live Blackjack Table, Fishing War Mobile Play and local payment options.

Account clarityWallet recordsDevice controlsCookie choices
9zkgames 9zkgames Privacy Policy For Your Account
REQUEST HELP

Get Help With A Privacy Request

A clear support path helps when a Privacy Policy question involves your login, wallet status or an old account record. Start from your signed-in account support route and describe the request in plain English, then include the phone verification status or payment receipt reference only when it relates to your question. We use those details to locate the right record without asking you to send a password. If you are in Makassar or elsewhere in Indonesia, access still depends on local law.

Team online

Account request

Use the account support route to ask for a copy, correction or explanation of personal data connected with your 9zkgames account. We may ask for a phone verification step before discussing account-specific records.

Wallet record

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, attach the payment receipt reference rather than wallet credentials. This lets us match status data while limiting the details included in your message.

Login concern

If a device or sign-in event looks unfamiliar, tell us through the same support route and change your password from the account security path. We can check access records and explain the next account step.

DATA CONTROLS

What Our Privacy Process Covers

We keep this Privacy Policy practical: you should be able to see why a record exists and what action is available.

Account data

We use the details you enter during account creation to identify your account, complete phone verification and connect your selected wallet or bank reference. Keeping those fields accurate helps us answer a Privacy Policy request without mixing records.

Cookie settings

Cookies can preserve a session and remember practical choices on the lobby page. You can manage cookie behaviour through your browser settings; turning some cookies off may require you to sign in again or repeat a device step.

Device security

We may record device type, browser signals and sign-in timing to identify unusual account access. These signals support account security around a mobile login and are not a substitute for your password or phone verification.

Wallet matching

A DANA, OVO, GoPay or QRIS reference helps us match a payment status to the correct account. We use the reference and status needed for that task, while you should never send a wallet PIN or password to support.

Retention choices

We retain records for the period needed for account operation, security checks, payment reconciliation and legal duties that apply where you are located. You can ask why a record remains and whether deletion or restriction is available under local law.

Change request

To request correction, access, deletion or a copy, contact us from the signed-in account support route with the affected field and reason. We may verify your phone before responding, and we will explain the result in clear terms.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers focus on the records you are most likely to ask about before opening an account: phone verification, wallet references, cookies, mobile devices and contact requests. We keep the answer tied to the account step involved, so you can decide what to share and where to ask for clarification. Account access depends on local law and is offered where local law permits.

It covers account details, phone verification, device and session signals, cookies, payment references and support messages. It also explains why we use each category, how retention works and how you can request access, correction, deletion or clarification where local law permits.

Phone verification helps us connect an account to the person requesting access and reduce mistaken or suspicious sign-ins. Before we discuss account-specific data, we may ask you to complete that step. We do not need your phone password or wallet PIN for verification.

Yes. The Privacy Policy covers the transaction reference, amount, status and account link created when you use DANA, OVO, GoPay or QRIS. Bank transfer and virtual account references are also covered, while wallet credentials should remain private and never be sent to us.

You can request a correction through the signed-in account support route. Name the field that needs changing and explain the issue. We may confirm your phone verification before making or discussing the change, and the result depends on local law and the record involved.

Cookies can keep a session active and remember selected settings when you use a mobile browser. Your browser controls whether cookies remain. If you block some of them, you may need to sign in again or repeat a device check before reaching account data.

We keep each record for the period needed for account operation, security review, payment reconciliation and applicable legal duties. The period can differ by record type and location. You may ask why a record is retained and whether deletion or restriction is available.

Use the support route inside your signed-in account and describe the Privacy Policy request, such as access, correction, deletion or an explanation. Include a payment receipt reference only when relevant. We may verify account ownership before sharing personal records or processing the request.