Reference

juara189 Privacy Policy For Your Account

Our Privacy Policy explains what juara189 collects when you open an account, use the mobile lobby, contact support or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesPhone checks
juara189 juara189 Privacy Policy For Your Account
CONTACT OUR TEAM

Privacy Help For Wallet And Login Questions

A clear contact route helps you ask about personal data without sending sensitive wallet credentials.

Account support channel Ask us to explain the Privacy Policy, locate an account record or clarify a phone verification step. Send only the details needed to identify your account, never a wallet PIN or password.
Payment status request If a DANA, OVO, GoPay or QRIS reference looks incorrect, share the transaction reference and timestamp through support. We use that pair to check the recorded status without requesting your wallet login.
Access concern When a login appears on an unfamiliar device, contact us through the account support route and describe the device path. We can help secure the session and explain which records the policy covers.
DATA CONTROL POINTS

What We Do With Your Personal Data

We keep the Privacy Policy practical by separating account access, wallet matching, security checks and cookie functions.

Data we collect

We may collect your account name, phone number, verification result, login events and payment references. These fields support account access, wallet matching and security checks rather than collecting your wallet password.

Cookie handling

Essential cookies keep your session and selected settings available as you move from login to the lobby. We also explain optional cookie choices in the Privacy Policy so you can adjust them through your browser.

Account security

Phone verification connects access to the correct account, while device and login records help us identify unusual activity. If your mobile session looks unfamiliar, contact support before continuing through the account path.

Record retention

We keep account, wallet and security records for the operational, legal or dispute needs stated in this Privacy Policy. When a record is no longer needed for those purposes, our handling follows the applicable retention process.

Correction request

You can ask us to correct inaccurate account details by using the account support channel. Include the registered phone number and the field that needs changing, while leaving out passwords and wallet security codes.

Policy contact

For questions about access, cookies, retention or payment references, contact our support route and write Privacy Policy in your request. We will use the account details supplied to identify the relevant record.

Privacy Policy Questions About juara189

These answers cover the Privacy Policy points most useful before you open an account, from phone verification and cookies to wallet references and requests for access. If your question concerns a specific record, use the support path with only the minimum account details.

The Privacy Policy covers account details, phone verification, device and login events, cookies, DANA, OVO, GoPay and QRIS references, retention, security handling and requests to correct or access your data.

Phone verification helps connect your account to the correct access session and reduces mistaken account matches. We record the verification result, not your phone account password, and use it as described in the Privacy Policy.

No. We use payment references, status and timestamps to match DANA or QRIS activity with your account. Wallet credentials remain with the payment service, and our Privacy Policy does not ask you to send them.

Essential cookies keep your login session and selected settings available as you move from a mobile browser to the lobby. The Privacy Policy explains optional choices, which you can manage through browser settings.

Yes. Contact the account support channel with your registered phone number and the inaccurate field. We use those details to locate the record, while you should omit passwords, wallet PINs and security codes.

We retain wallet references, account details and login events only for the operational, security, legal or dispute purposes described in the Privacy Policy. The applicable retention process determines when a record is removed.

You can send a data access request through our support route and write Privacy Policy in the subject. Include enough account detail for identification, but do not include your wallet password or verification code.