Reference

joker123net Privacy Policy for Clear Account Access

joker123net Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet activity.

Account data explainedWallet activity coveredDirect request path
joker123net joker123net Privacy Policy for Clear Account Access
HELP WITH PRIVACY

Get a Direct Answer About Your Data

A clear contact route matters when your question concerns Privacy Policy rather than a lobby screen.

Account privacy request Send an access, correction or deletion request through the account support path. We use the contact detail already attached to your account to confirm that the request concerns you before discussing stored profile or phone-verification data.
Wallet data question If your question involves DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, include the payment reference and date. We use those details to locate the relevant record while keeping your password and verification code private.
Access or device concern Tell us if Privacy Policy questions follow a sign-in issue on your phone, tablet or desktop. Our support path can compare the account record with the device details connected to that access without asking you to disclose a secret credential.
DATA HANDLING DETAILS

What We Do With Your Privacy Choices

The policy is designed to match what happens when you use the account path, not to hide the practical details in broad wording.

Account records

We may keep the name, contact detail and phone-verification result needed to create and protect your account. These records help us distinguish an account request from an unauthorised attempt and let us respond to a Privacy Policy access question.

Payment references

A DANA, OVO, GoPay or QRIS receipt may contain a reference, amount and status used to match your account activity. Bank transfer and virtual account records support the same check, without requiring us to store your wallet password.

Cookies and sessions

Cookies can remember a session setting or help us understand whether a sign-in request belongs to an existing device. You can manage browser cookies, but changing them may require another account sign-in or phone verification.

Device security

We may record device type, browser details, connection data and sign-in times to identify unusual access. This can protect the account when you move from a mobile lobby to a desktop session or return after a failed login.

Retention approach

We retain account and transaction records only as long as they support account security, support handling, dispute checks or a legal requirement that applies to the service. You can ask which category relates to your request and why it remains stored.

Change or removal

To request a correction or removal, contact support from your account-linked email or phone detail and describe the exact record. We may need to verify identity, and some records may remain where local law requires retention.

Answers Before You Open an Account

These Privacy Policy answers address the questions we expect you to ask before using joker123net from Indonesia. They cover account creation, phone verification, wallet records, device access, cookies and requests to change stored data. If your situation is not covered, use the account support path and describe the specific record or activity you want us to check. Access depends on local law, so the response to a request can vary according to the applicable rules.

The Privacy Policy covers data connected with your account, phone verification, device access, cookies, support requests and payment references. It explains how we use those details for account security, transaction checks and support, including records linked with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

Phone verification helps us confirm account ownership before access and before discussing personal details through support. It can also help us identify an unusual sign-in. We use the verification result for account security, while your verification code should remain private and never be sent to support.

Yes, you can send a Privacy Policy access request through the account support path. Use the email or phone detail linked to your account, describe the data category you want checked, and complete any identity step we request. We will explain what can be provided under applicable rules.

We use DANA and QRIS references to match a wallet transaction with the correct account and status. A receipt may show a reference, date, amount and result, but we do not need your wallet password. The same process applies to OVO, GoPay, bank transfer and virtual account records.

Yes. The policy covers device type, browser details, connection data and sign-in timing when those details support account security or access checks. This helps us investigate a move from the mobile lobby to desktop without treating your device record as a replacement for your account identity.

You can request a correction or deletion by contacting support with the exact record you want changed. We first confirm that you are the account holder. Where local law permits, eligible data can be changed or removed; certain security, support or transaction records may need to remain.

Use the account support path from your linked contact detail and write that your request concerns Privacy Policy. Include the category, such as phone verification, cookie, device, account or wallet reference. Do not include a password or verification code. We can then route the request for a privacy response.