Reference

joker11 Privacy Policy for Your Account Data

The joker11 Privacy Policy explains how we collect, use and protect details connected with your account, mobile browser and payment activity in Indonesia.

Account recordsWallet activityCookie choicesContact requests
joker11 joker11 Privacy Policy for Your Account Data
REQUEST A HAND

Where To Ask About Privacy Policy

A direct request helps us connect your privacy question with the right account record. Use the support path attached to your account when you need a copy, correction or explanation, and include the phone number linked to your profile. If a DANA or QRIS reference looks wrong, keep the receipt details ready so we can separate a payment query from a general data request.

Team online

Account privacy

Ask through your account support route for access, correction or deletion questions. We may request the phone verification detail linked to your profile before discussing account data.

Wallet records

For DANA, OVO, GoPay or QRIS references, provide the relevant receipt or transaction code. We use that detail to locate the matching record without requesting unrelated account content.

Policy changes

Send a policy question through the same support path when wording is unclear. We will explain how a change affects stored records, cookies or your account access where local law permits.

HANDLING YOUR RECORDS

What We Do With Account Data

Privacy work is part of the account path, not a separate page you must decipher later. We limit collection to records needed for account access, security, payment matching and support.

Account creation

When you open an account, we record the submitted account details and phone verification result. This lets us connect later support requests to the correct profile and reduce confusion between duplicate records.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us reconcile a cashier event with your account. We do not need your unrelated wallet conversations or personal files.

Cookies and sessions

Cookies and session markers can keep your sign-in path working across the mobile browser and lobby pages. You can manage browser cookies, although removing them may affect remembered settings or account access.

Security signals

We may assess device type, sign-in time and unusual account behaviour to protect access. A change from mobile to desktop can therefore create a security check without changing your profile details.

Retention periods

We retain records only as long as needed for the stated account, payment, security or legal purpose. When a record is no longer needed, our handling follows the applicable retention requirement.

Your choices

You can ask us to access, correct or remove eligible personal data through account support. Include enough account detail for verification, and we will explain the result or any lawful reason for keeping it.

Privacy Policy Answers for Indonesia

These common questions focus on the records you are most likely to notice while using joker11. We keep the answers practical, from phone verification and cookies to wallet references and requests made through your account support route.

It covers account details, phone verification, device and session data, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification connects you to the correct account and helps protect sign-in access. We record the verification result so support can check ownership before discussing private account or payment details.

Yes. The policy includes device type, session markers and cookies created when you use a mobile browser. Removing cookies may change remembered settings or interrupt the account path.

We use DANA and QRIS references to match a payment event with your account and resolve status questions. A receipt or transaction code helps us locate the correct record without unrelated data.

You can request access through the account support route. Include your linked phone detail for verification, and we will explain which records can be supplied under the applicable local requirements.

Yes. Send a correction request through account support and identify the field that appears wrong. We may verify ownership first, then update eligible records or explain why a record must remain unchanged.

Access and eligibility depends on local law. The Privacy Policy applies where local law permits, while any local privacy rule affecting your request will be considered when we respond.