Reference

Open the juara123 Privacy Policy

The juara123 Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, and use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesContact requests
juara123 Open the juara123 Privacy Policy
ASK OUR TEAM

Find Help For Privacy Requests

A clear contact path matters when your account record or wallet reference needs attention. We ask you to contact our support route from the account area and describe the Privacy Policy question in plain English, using the email or phone detail connected to your account where possible. Include a transaction reference only when it is relevant, and never send a password or one-time code. Our team can explain a data request, direct a correction request, and help separate a login issue from a privacy question.

Team online

Account privacy request

Use the support route connected to your juara123 account when you want to ask what personal details we hold. We may ask for an account step or phone verification so we do not disclose information to the wrong person.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference appears in a data question, include the relevant date and transaction reference without sharing a password. We use those details to locate the correct payment record and explain its handling.

Correction follow-up

Tell us which account field needs changing and why it is inaccurate. We can guide you through the account path, request supporting details where needed, and confirm when the correction request has been assigned for checking.

DATA HANDLING

Explore The Controls Behind Your Privacy

We handle this policy area through practical account controls rather than vague promises. Phone verification helps connect a request to the correct account, and device signals can flag a sign-in that does…

Data collection

We collect details needed for account creation, phone verification, sign-in checks, support replies and payment tracing. This can include contact details, account actions, device signals and references connected with DANA, OVO, GoPay, QRIS or bank transfer.

Cookie choices

Cookies can keep your session active and remember a choice made on the privacy prompt. On a shared phone or desktop, sign out after use and clear stored browser data if you do not want the next person to inherit your session.

Account security

Phone verification is part of the account access path, and unusual device behaviour may lead to an additional check. Keep your password private, avoid sending one-time codes to support, and contact us if a login does not match your activity.

Payment records

A payment reference helps us match a deposit or wallet status with the right account. We may retain the necessary DANA, QRIS, virtual account or bank transfer record for tracing, reconciliation and a response to your account question.

Retention timing

We keep personal data only for the period needed for the stated account, security, payment or support purpose, subject to local requirements. When you ask about retention, tell us which record you mean so we can give a precise response.

Change requests

You can ask us to access a personal record, correct an inaccurate field, or explain how a detail is used. Send the request through the account support path, identify the relevant account step, and allow us to verify your identity first.

Browse Privacy Policy Answers

These Privacy Policy answers cover the questions we expect you to ask before opening an account or linking a local payment method. We keep the wording practical: what data is collected, why phone verification appears, how cookies behave on mobile, and how to request access or correction. If your question concerns eligibility or service access in Indonesia, that outcome depends on local law and where local law permits.

It covers personal data used for account creation, phone verification, sign-in checks, device signals, cookies, support conversations and payment references. It also explains retention, security steps and how you can ask for access, correction or clarification about a record.

We use your phone detail to create and verify the account, connect a privacy request to the right account, and help detect an unusual sign-in. Do not send your password or one-time code to support when asking about the Privacy Policy.

Yes. The policy covers the payment references needed to trace DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use the relevant reference and status details for account matching, reconciliation and responses to payment-related data questions.

Use the support route connected to your account and clearly ask for access to your personal data. Include the account phone detail or another requested verification step, but leave out passwords and one-time codes. We will explain the next check.

Yes. Identify the inaccurate field, explain the correction, and send the request through account support. We may ask for phone verification or supporting details before changing it. This protects your account and keeps a correction from being made by another person.

Cookies can support your login session and remember a privacy choice on the browser you use. If you switch from mobile to desktop, each device may hold separate session data. You can clear browser data or contact us about a cookie question.

Retention depends on why the record exists, such as account security, payment tracing, support or a legal requirement. Ask us about a specific account or transaction record through support, and we will explain the applicable retention position where local law permits.