Reference

Open juara404 With Clear Privacy Terms

juara404 explains how we use account details, device signals, wallet records and support messages before you open the lobby.

Account dataWallet recordsCookie choicesContact path
juara404 Open juara404 With Clear Privacy Terms
CONTACT FOR PRIVACY

Open A Support Request About Your Data

Questions about the Privacy Policy should reach us through the same account path you use for access or wallet status. We keep the route practical: start from the sign-in screen if you cannot enter the account, or use the support link near the cashier area when your request concerns DANA, QRIS or another transaction record. Include the email or phone linked to your account, but do not send a password or wallet PIN.

Team online

Login support form

If you cannot reach the account, use the support form linked from the sign-in screen. Tell us that your request concerns the Privacy Policy, provide the account contact detail, and describe whether you need access, correction or removal of stored information.

Cashier support path

For a wallet record connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account, open the support link beside the cashier status. Share the transaction reference only; keep your wallet PIN, one-time code and full login password private.

Privacy request route

To ask how your information is used or request a policy-related change, choose the privacy subject in our support contact path. We may ask you to verify the account phone before discussing personal records or applying a correction.

HOW WE HANDLE DATA

Explore The Privacy Steps Behind Your Account

The policy is practical because each data category has a defined account purpose. We use contact details for sign-in and phone verification, device signals to identify unusual access, and wallet references to…

Account details

When you open an account, we receive the contact details and phone verification result needed to connect you with sign-in. We use this information for access messages and account checks, not as a reason to request your wallet PIN or one-time code.

Device and browser signals

A mobile browser may send device, browser and connection signals when you sign in. We use these signals to recognise unusual access, protect an active session and investigate a security concern. Clearing cookies can require you to complete account checks again.

Wallet and transaction records

A DANA, OVO, GoPay or QRIS reference, along with bank transfer or virtual account details, can appear in the payment record. We use that trail to match status to the correct account and respond when a receipt needs checking.

Cookies and session storage

Cookies help keep a sign-in session connected to the right account and remember choices made on the site. You can manage cookies through your browser settings, although removing essential cookies may interrupt access or require another phone verification step.

Security and retention

We restrict account records to operational purposes and retain them only as long as needed for access security, transaction reconciliation, dispute handling or a legal obligation. A deletion request may not remove records that must remain for those specific purposes.

Requests and corrections

You can ask for a copy, correction, clarification or deletion through the privacy contact route. We may verify the phone or email linked to the account before changing records, and we will explain when local law requires a record to stay.

Browse Answers About Privacy Policy

These answers focus on the questions we expect you to ask before opening or using an account. They cover the juara404 Privacy Policy, local wallet records, mobile access, cookies and requests for personal data. If your situation is not covered, use the privacy contact route and include only the account detail needed to identify your request.

The juara404 Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages, wallet references and transaction records. It also explains why we use each category, how long records may remain, and how you can request access or correction.

Phone verification connects account access to the contact detail you provide and helps us respond to an access request. We may use the verification result during a security check, but you should never send us your one-time code, wallet PIN or full password.

Yes. The Privacy Policy covers payment references created when you use DANA, OVO, GoPay or QRIS, as well as bank transfer and virtual account records. We use these details to match a status or receipt with the correct account and answer a support request.

When you sign in from a mobile browser, the site may receive account, browser, device and connection signals linked to that session. We use them for access continuity, cookie operation and security checks. Browser settings can control optional cookies, while essential session storage may be required.

Use the privacy contact route from the sign-in screen or support area and state whether you want access, correction, clarification or deletion. Include the account email or phone, but not a password or wallet PIN. We may verify ownership before discussing personal records.

You can submit a deletion request through the privacy support path. Where local law permits, we assess the request against account security, transaction reconciliation, dispute handling and legal retention needs, then explain which records can be removed and which must remain.

The current Privacy Policy is linked from the site footer and the account access area, so you can read it before sharing details. Access or eligibility depends on local law. If a section is unclear, contact us through the privacy route before completing phone verification.