Reference

juraganmain Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open a juraganmain account, sign in on mobile or desktop, and use DANA, OVO, GoPay or QRIS.

Account detailsWallet recordsDevice signalsCookie choices

Explore Our Lobby Read FAQ

How DANA and QRIS Data Is Used

juraganmain Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy covers details you provide during account creation, including contact data used for phone verification before account access. We also receive records needed to match a DANA, OVO, GoPay or QRIS transaction with the correct account, such as a reference, amount and status. Device

1
and connection details help us detect unusual sign-ins and keep a session linked to the right account. We do not describe access as available everywhere: eligibility depends on local law. You can ask us which data is held about you, why it is used, how long
2
it is retained, and whether a correction is possible. Bank transfer and virtual account references may also appear in our records when you choose those routes.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

PRIVACY HELP

Where to Ask About Privacy Policy

A clear support path helps when a privacy question sits beside a login or wallet status issue.

Data access request Ask us to identify the account data linked to your phone verification, sign-in history or DANA receipt. We will use the details you provide to locate the relevant record.

Correction request If your contact detail or wallet status appears incorrect, send the affected field and a matching account reference. We may verify ownership before changing information.

Wallet privacy query For OVO, GoPay, QRIS, bank transfer or virtual account questions, include the transaction reference and status shown in your account. Do not send your password or full security code.

DATA CONTROLS

How juraganmain Handles Your Account Data

Our handling process follows the account journey rather than collecting unrelated details. We use verification data for sign-in checks, payment references for reconciliation, cookies for selected site functions, and device signals for…

Account creation

When you open an account, we collect the contact details needed for the account step and phone verification. This lets us connect later sign-ins with the correct account record.

Phone verification

A verification check confirms that the phone detail belongs with your account before access is granted. We use its result for account protection, not as a public profile.

Cookie choices

Cookies can remember session settings and help pages load consistently on your device. You can manage cookie controls through your browser, although some account functions may then require another sign-in.

Device security

We may record device type, browser details and connection signals to spot unusual access. Opening the lobby on mobile and returning on desktop can therefore create separate security checks.

Payment matching

DANA, QRIS and other wallet or bank references help us match a payment status to your account. We use the reference for reconciliation and do not need your wallet password.

Retention questions

If you ask how long a record remains, tell us the account detail or transaction reference involved. We will explain the applicable retention purpose and the available change request.

Privacy Policy Questions for Your Account

These Privacy Policy answers focus on the account actions you are most likely to take: opening access, verifying a phone, checking a wallet record and changing personal details. If your question is not listed, use the support route with a specific account or transaction reference. Availability remains where local law permits.

It covers account details, phone verification, sign-in and device signals, cookies, payment references and retention. It also explains how you can ask for access, correction or clarification about your records.

We use your phone detail for the verification step before account access and to connect sign-in activity with the right account. We do not ask you to send a password through support.

Yes. The policy covers references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account payments, so we can match a transaction with your account.

Use our support route from your account or the cashier path and ask for a data access request. Include the contact detail linked to your account so we can verify ownership.

You can ask us to correct an inaccurate contact detail, account field or wallet status. Provide the affected field and a matching account reference; we may verify ownership before applying the change.

Cookies can retain session settings and support consistent page behaviour on your browser. You can adjust them in browser controls, but limiting cookies may require another sign-in for account access.

Retention varies by record and purpose. Account, verification and transaction details may need to remain available for account and payment integrity. Ask support about a specific record or reference.

juraganmain Privacy Policy for Your Account

Where to Ask About Privacy Policy

How juraganmain Handles Your Account Data

Account creation

Phone verification

Cookie choices

Device security

Payment matching

Retention questions

Privacy Policy Questions for Your Account

01 What does the juraganmain Privacy Policy cover?

02 Why does juraganmain need my phone detail?

03 Does the Privacy Policy cover DANA and QRIS payments?

04 How can I request my juraganmain data?

05 Can I correct information held under my account?

06 How does the Privacy Policy handle cookies?

07 How long does juraganmain keep my data?

Related Pages