Reference

Privacy Policy for Your DANA and QRIS Account

Our Privacy Policy explains how rejeki game apk handles the details connected with your account, mobile browser access and wallet activity.

Account dataWallet statusCookie choicesPolicy requests
Explore Our Lobby Read FAQ
rejeki game apk Privacy Policy for Your DANA and QRIS Account
CONTACT ROUTES

Get Privacy Help Before Wallet Changes

A clear contact route helps you question a record before an account or wallet change is made. We ask you to use the support path shown after account access and include the phone detail linked to your account, the relevant date, and the payment reference when your question concerns DANA, OVO, GoPay or QRIS. We use those details to locate the right record without asking you to send an unnecessary password.

Team online

Account access

If phone verification prevents access, tell us the account contact detail and device path you used. We can check the access record and explain which Privacy Policy request route applies without asking for your password.

Wallet record

For a DANA, OVO, GoPay or QRIS status question, include the payment reference and approximate time. We use that narrow context to find the transaction record and avoid requesting unrelated account details.

Data request

For a copy, correction or removal request, identify the account contact detail and describe the record concerned. We may ask for a verification step before changing personal data or sharing account-linked material.

SIX DATA CONTROLS

Six Controls Behind Our Privacy Practice

We keep the Privacy Policy practical by connecting each data use to an account task you can recognise.

Collection

We collect account details that you enter, phone verification data, device and browser signals, and payment references needed to connect a DANA, OVO, GoPay, QRIS, bank transfer or virtual account action to your account.

Cookies

Cookies and similar browser storage can retain session settings and help us recognise the device path from login to the lobby. Your browser settings provide a way to restrict or clear them, although account access may then need another check.

Security

We use phone verification before account access and keep payment references separate from your password. Do not send a password through support. If a device changes, we may ask for an account check before discussing wallet records.

Retention

We retain account and transaction records only for operational support, reconciliation, security checks and legal duties that apply to the service. When a record is no longer needed for those purposes, our handling follows the applicable retention process.

Your request

You can ask us to access, correct or clarify personal data connected with your account. Include the relevant phone detail, date or payment reference so we can narrow the search and complete an identity check before responding.

Third parties

Wallet and banking records may involve DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri, BNI or a payment intermediary. We use the information needed to confirm status and do not treat a bank reference as permission to change unrelated account data.

Privacy Policy Answers for Your Account

These Privacy Policy answers address the searches we hear most often before account access or a wallet request. They explain what we collect, why a phone check may appear, how cookies relate to a mobile browser, and where to send a correction request. If your situation involves a payment reference or a device change, include that narrow detail so we can respond to the right account record.

It covers account details, phone verification, device and browser signals, cookies, lobby activity, payment references and support records. It also explains retention, security checks, correction requests and contact paths. Access or eligibility depends on local law, and the policy applies where local law permits.

We use phone verification before account access to help connect the right person with the right account and to investigate an access problem. The check can also support a correction or data request. We do not need your password in a support message.

Yes. We may retain the payment reference, status and account link needed to trace DANA or QRIS activity. The same approach can apply to OVO, GoPay, bank transfer and virtual account records. We use the narrow payment context needed for reconciliation and support.

We may receive browser, device and session signals from the path you use to sign in, including a mobile browser or desktop device. These signals help maintain access and investigate security questions. They are handled alongside account details rather than treated as a separate account.

You can ask us to correct personal data connected with your account. Send the account contact detail and describe the exact record, such as a phone detail or payment reference. We may complete an identity check first so a change is made on the correct account.

We keep records for the period needed for account support, payment reconciliation, security checks and legal duties that apply to the service. The period can differ by record type. When those purposes end, handling follows the applicable retention process described by our Privacy Policy.

Use the support route shown after account access and state that your request concerns privacy. Include the account contact detail, relevant date and, if needed, the DANA, OVO, GoPay or QRIS reference. Do not send your password or unrelated identity documents.

Related Pages

rejeki game apk Indonesia Dice Duel Quick Arena FAQ Badminton Open Bet About Us