Reference

raja mania Privacy Policy Explained Clearly

Our Privacy Policy shows what data we collect when you open a raja mania account, use the mobile lobby, or check wallet status through DANA, OVO, GoPay and…

Account dataDevice choicesWallet recordsPolicy requests
raja mania raja mania Privacy Policy Explained Clearly
PRIVACY HELP ROUTE

Get Privacy Help Beside Wallet Status

A clear support path matters when a privacy question appears beside a payment receipt or login event.

Account access request Ask us to check account details, login records or verification status through the account help path. We may request an account identifier and a confirmation step before discussing personal data, so the request reaches the correct raja mania profile.
Wallet record question For DANA, OVO, GoPay or QRIS questions, include the payment reference and date shown in your receipt. We can trace the related account record without asking for your wallet password, then explain what the Privacy Policy allows us to change or disclose.
Data change request Use the support area when you want to correct contact details, ask about stored device information or question a retention period. We review the request against your account record and explain any identity check or local-law condition before making a change.
DATA CONTROL DETAILS

Keep Your QRIS Account Data Clear

Our Privacy Policy is built around practical controls you can understand before using the lobby. We separate account identity details from payment references, use device and login signals for account protection, and…

Account data

We use the contact details and verification information you submit to create your account, confirm account ownership and respond to support requests. If you correct a detail, we may keep the earlier record where it is needed for transaction matching or account-security history.

Cookie choices

Cookies and related browser storage can remember a session, language preference or privacy choice. You can adjust browser settings to limit them, but some account pages may not behave as expected when essential session storage is blocked.

Device signals

When you move from login to the mobile lobby, we may record device type, browser details, network signals and security events. These records help identify unusual access and troubleshoot a session without reading private content from your device.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may create references, amounts and status markers in our records. We use them to match a receipt with your account and investigate a payment query, not to request your wallet password.

Retention periods

We retain records for the period needed for the purpose described in this Privacy Policy, such as account support, payment reconciliation or security checks. When a record is no longer needed, our handling follows applicable retention duties and internal deletion processes.

Your requests

You can contact us through the account help path to ask for access, correction or clarification about personal data. We may ask you to complete an account step before releasing details, and some requests can be limited where local law permits.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions you may have before opening an account or connecting an Indonesian wallet. We keep the wording practical: what we collect, why a device record appears, how payment references are matched and how to request a change. For a case involving your own account, use the account help path so we can verify the correct record. Any access or eligibility condition depends on local law and applies where local law permits.

It covers personal data connected with your account, including submitted contact details, verification records, login events, device signals, cookies, support requests and payment references. It also explains why we use those records, how retention works and how you can ask for access or correction where local law permits.

Our payment handling uses transaction references and status details to match activity with your account. We do not need your wallet password for that process. If support asks about a receipt, send the reference and date shown in the payment record, never your private wallet credentials.

A device type, browser detail or security event can appear when you sign in and move to the mobile lobby. We use these signals to recognise unusual access, protect your account and troubleshoot session problems. They do not give us access to private files stored on your phone.

Start through the account help path and state whether you want access, correction or clarification. Include the account identifier connected with the request, but do not send a wallet password. We may complete an account verification step before sharing or changing personal records.

Retention depends on why a record exists. Account details may support account operation, while DANA, QRIS, bank transfer and virtual account references may be kept for payment matching or support. We remove or de-identify records when they are no longer needed, subject to local duties.

Yes. Cookies and similar browser storage may remember a session, language choice or privacy setting and may help us understand page activity. You can adjust your browser controls, although blocking essential storage may affect login, account access or the way policy choices are saved.

It describes our handling for Indonesian account and wallet activity where local law permits. Access and eligibility depends on local law. If your location or account status creates a legal restriction, we will follow the applicable condition and explain the available privacy request path.