Reference

jagungbet Privacy Policy for Your Account

Your account details, phone verification and wallet choices receive a clear Privacy Policy on jagungbet, including how we handle DANA, OVO, GoPay and QRIS records.

Account dataWallet recordsCookie choicesRequest access
jagungbet jagungbet Privacy Policy for Your Account
HELP WITH REQUESTS

Get Policy Help Near Your Account

A clear contact path helps when you need a copy of your data, want to correct an account detail or have a question about cookies. From Semarang or elsewhere in Indonesia, sign in and use the account support route; include your registered phone number and request type so we can locate the right record without asking for unnecessary wallet details.

Team online

Account data request

Use the support route after signing in to ask for account data linked to your phone verification. We may confirm ownership before sending details, so your request stays connected to the correct jagungbet profile.

Wallet record question

For a DANA, OVO, GoPay or QRIS reference, provide the receipt number and approximate date rather than sharing a wallet password. We use those details to check the relevant payment record.

Cookie or correction help

Tell us which device path you used, such as mobile browser or desktop, and describe the correction needed. Our support route can explain available cookie choices and the next verification step.

DATA PRACTICE

How jagungbet Handles Policy Details

Privacy work follows the account steps you actually take: opening an account, confirming a phone, signing in, checking wallet status or sending a support request.

Collection at account opening

When you open an account, we collect the details needed to create and protect that profile. Phone verification connects the account to your access request, while optional preferences are handled separately where available.

Payment references only

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account entry can leave a reference, amount status and time record. These references help match a receipt without requiring your wallet password.

Cookies and device signals

Cookies can remember a session choice, while device signals help us identify unusual sign-in behaviour. You can review browser controls on your mobile or desktop path before continuing.

Account security checks

We may ask for phone confirmation or account details before disclosing personal records. This step helps prevent another person from receiving your data through a support request.

Retention and removal

We retain records for the period needed to operate the account, resolve disputes, meet legal duties and protect transaction history. When retention is no longer needed, handling follows the applicable removal process.

Requesting a policy change

If your name, phone detail or permission choice is incorrect, contact account support with the requested correction. We may verify ownership, record the request and explain any limit under local law.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account and payment questions you are most likely to have before opening an account. If your situation is not covered, use the support path above and describe the exact record, device or wallet reference involved.

The jagungbet Privacy Policy explains how we collect, use, protect and retain account, device, cookie, support and payment-reference data. It also describes how you can request access or correction.

We may collect contact details, phone-verification results, sign-in events, device signals, cookie choices and account activity needed for access. Payment references can relate to DANA, OVO, GoPay or QRIS.

Yes. The Privacy Policy covers references connected with QRIS, DANA, OVO, GoPay, bank transfer and virtual account activity. We use those records to match status or receipts, not to request your wallet password.

Sign in, open the account support route and ask for an account-data copy. Include your registered phone number and request type; we may confirm ownership before releasing personal records.

You can ask us to correct an inaccurate name, phone detail or permission choice through account support. Describe the change clearly, and we will explain verification steps and any restriction under local law.

Cookies can preserve a session choice or remember that you opened the Privacy Policy. Your mobile browser controls can manage them, while device signals may still support sign-in protection.

We keep each record only as long as needed for account operation, support handling, transaction history, security or legal duties. The applicable retention period can differ by record type and local law.