Reference

joker404 Privacy Policy For Your Account

Our Privacy Policy explains what joker404 collects when you open an account, use DANA or QRIS, and move between the lobby and your wallet.

Account detailsDANA and QRIS recordsCookie choicesLocal-law access
joker404 joker404 Privacy Policy For Your Account
HELP REQUESTS

Account Help For Privacy Requests

A clear contact route matters when a name, phone detail, wallet reference, or device record needs attention. Start from the support contact shown inside your joker404 account and describe the privacy request in plain English, including the account step where the issue appeared. We may ask for limited verification before discussing personal data, so your details are not disclosed to the wrong person.

Team online

Account contact

Use the support contact available in your account area for a copy request, correction request, or question about how your personal data is used. Include the relevant account detail, but do not send a password or wallet PIN.

Wallet receipt check

If your privacy question concerns DANA, OVO, GoPay, QRIS, or a bank transfer, share the transaction reference and approximate date through the account help route. We use those details to locate the right record without asking for unnecessary wallet credentials.

Access concern

When a device check or phone verification interrupts account access, explain the screen path and device type in your message. We may confirm account ownership before changing a record, and eligibility still depends on local law.

HANDLING DETAILS

Device Security Beside Auto Roulette

Privacy protection works through small account steps rather than a single promise. We separate necessary account records from optional cookie activity, use verification before discussing sensitive details, and keep transaction references available…

Data collected

We may collect the details you enter during account creation, such as contact data and verification material, together with sign-in events, device signals, support messages, and payment references needed to connect DANA, OVO, GoPay, QRIS, or bank activity to your account.

Cookie choices

Cookies and similar device storage can remember a sign-in path, protect an account session, or help us understand which page caused a technical issue. Your browser settings can remove or restrict optional cookies, although some account functions may then need another verification step.

Account security

Phone verification and device signals help us identify unusual access before account details or wallet records are discussed. Keep your password private, sign out on shared devices, and contact the account help route if the device path no longer looks familiar.

Retention period

We retain account, support, security, and payment records for the period needed to provide the service, investigate disputes, protect accounts, or meet applicable legal duties. When a record is no longer needed for those purposes, we remove it or handle it in a form that no longer identifies you.

Requesting changes

You can ask us to correct inaccurate account details, explain a data use, or provide access to personal data connected with your account. Send the request through the support contact in your account area; we may verify ownership before making a change.

Policy contact

For a question specifically about this Privacy Policy, state the word privacy in your account message and name the record involved, such as a cookie, phone check, or QRIS receipt. We will assess the request under the rules that apply to your location and account.

Privacy Questions Before Account Access

These answers address the searches we hear before an Indonesian account is opened or a wallet is connected. They focus on the joker404 Privacy Policy, not on general lobby features, so you can check what data may be involved and which account route to use for help.

It covers account details, phone verification, sign-in and device activity, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account. It also explains retention, security checks, data requests, and local-law conditions.

Phone verification helps us confirm account ownership before we discuss personal details or change an account record. It can also help identify unusual access from a new device. We use the verification step for account security, while eligibility for access depends on local law.

Yes. The Privacy Policy covers payment references needed to match DANA or QRIS activity with your account, check a receipt, and respond to a status question. We may also handle related records for OVO, GoPay, bank transfer, and virtual account activity.

You can send a data access request through the support contact shown inside your account area. Tell us which records you want, such as profile details, device events, cookie activity, or payment references. We may verify ownership before releasing personal data.

Use the account support route and identify the incorrect field, such as a phone detail or contact record. Explain the correction clearly and provide only the material needed to locate your account. We may request verification before editing the record.

We keep those records only for the time needed for account operation, security, dispute handling, and legal duties that apply. The period can differ by record type and location. When the reason ends, we remove the record or use a form that no longer identifies you.

Send a message through the support contact displayed in your account area and identify whether your question concerns cookies, account data, device activity, or payment records. We assess requests under the rules that apply to your location, and access depends on local law.