Reference

Open joker39 Privacy Policy Clearly

joker39 Privacy Policy explains what we collect when you open an account, use the lobby, or connect DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record detailsContact and change stepsIndonesia access terms
joker39 Open joker39 Privacy Policy Clearly
HELP WITH RECORDS

Ask Us About Your Privacy Policy

A clear support route matters when your account data or wallet status needs checking. We handle Privacy Policy questions through the account help path, where you can describe an access issue, request a record check, or ask how to correct personal details. Keep your account email or phone reference nearby, but never include your password or one-time security code. For you in Bandung or elsewhere in Indonesia, the same policy contact route applies whenever access is available where local law permits.

Team online

Account help path

Use the account help path for a Privacy Policy question about your name, phone number, login record or account status. We can direct the request to the relevant account process without asking you to post private details in a public message.

Wallet status check

If DANA, OVO, GoPay or QRIS shows an unclear status, send the transaction reference through account help. We use the reference to locate the payment record and explain what personal data is connected to that request.

Policy change request

Ask us to correct an inaccurate account detail or explain a stored record through the same support route. We may need an account step to confirm that the request comes from the person connected with the record.

DATA HANDLING PATH

Explore How We Handle Your Records

We apply this Privacy Policy to the details needed for account access, wallet checks and service protection.

Account details

We may use your account name, phone contact and verification state to create and protect your access. Phone verification comes before account access, helping us connect a request with the correct account instead of relying on an unconfirmed message.

Cookies and sessions

Cookies and device session data help keep your account path consistent between login and the lobby. On mobile, this can reduce repeated prompts when you move from account access to a wallet status page, subject to your browser settings.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we may retain references, status details and account links needed to match a request. We do not need your password or security code to investigate a receipt.

Account protection

We use login events, verification results and device signals to identify unusual account activity. If access appears inconsistent, we may ask you to complete an account check before discussing personal details or changing the contact attached to your account.

Retention choices

We keep data only while it has an operational, dispute or legal purpose, with retention depending on the type of record. A deletion request may be limited where a transaction, account protection event or legal duty requires continued storage.

Your request route

Contact us through account help to ask for access, correction, deletion details or an explanation of processing. Include the account reference and the specific request; we may verify your identity before sharing or changing any record.

Check Common Privacy Policy Questions

These Privacy Policy answers address the account and payment questions you are most likely to have before opening access. We keep the wording practical, so you can see which details may be used, how to contact us and what an account check involves. If your situation is not covered, send the question through account help.

The joker39 Privacy Policy covers account details, phone verification, login and device sessions, cookies, wallet references, payment status records and support requests. It also explains retention, security checks and how you can ask for access, correction or details about deletion limits.

Phone verification helps connect account access with the correct person and reduces confusion when a login or wallet request needs checking. We may use the verification state as part of account protection, but you should never send your password or one-time security code to support.

Yes. The Privacy Policy covers DANA and QRIS payment references, status details and the account link needed to investigate a deposit or withdrawal request. The same approach can apply to OVO, GoPay, bank transfer and virtual account records when you use those routes.

Use the account help path and state whether you want access to a record or correction of a specific detail. Add your account reference so we can locate the request. We may complete an identity check before sharing information or changing the account.

We use cookies and device session signals to keep your login path connected as you move between account access, the lobby and wallet status. Your browser settings affect cookie storage. Removing cookies can require another login or account check on the next visit.

Retention depends on the record and its purpose. Account, payment and security records may remain while needed for service operation, dispute handling or legal duties. A deletion request may therefore have limits, and account help can explain the reason for a continued record.

You can ask through account help about the data connected with your Indonesia account and the steps available to you. Service access depends on local law, so eligibility and any request outcome can vary where local rules apply. We will explain the relevant account path.