Reference

Privacy Policy for Your rajawin Account

rajawin Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between the lobby and cashier.

Account dataWallet recordsCookie choicesAccess depends on local law
rajawin Privacy Policy for Your rajawin Account
PRIVACY CONTACT

Where to Ask About rajawin Privacy

A clear contact path matters when a phone number, wallet reference or device record needs checking.

Account route Open the support path from your account area and describe the Privacy Policy request.
Cashier path If access stalls during a DANA, OVO or GoPay status check, use the contact…
Privacy request For correction, access or deletion questions, state the request plainly and identify the account…
DATA PRACTICE

What We Keep Secure in Your Account

Privacy controls work best when they match the steps you take on the site. We separate account access details from the wallet references used to reconcile DANA, QRIS, bank transfer and virtual…

Account details

We may hold your phone number, verification result and account settings so we can authenticate access and connect your requests to the right account. Please keep the verified number current through the account process.

Payment references

A DANA, QRIS, bank transfer or virtual account request can create a reference, amount and status record. We use those fields to reconcile the cashier event, not to request your wallet password or bank login.

Device signals

Your browser type, device path, login time and security events may help us identify unusual access. On mobile, these signals support the route from phone verification to the lobby without storing the contents of your private device.

Cookie controls

Cookies can remember a session choice and help us see whether an account page is working. You can review cookie controls in your browser, although restricting them may require you to repeat a login or verification step.

Retention checks

We keep personal records for the account, payment matching, security and legal purposes described in this Privacy Policy. When a purpose ends, we assess whether the record can be removed, anonymised or kept for another valid reason.

Change requests

You can ask for access, correction or deletion of eligible personal data through the support route shown in your account area. We verify the request first, then explain what can be changed and any reason a record must remain.

Privacy Policy Questions About rajawin

These Privacy Policy answers focus on the account actions you are most likely to search for before opening access. They explain the data connected with phone verification, wallet status, mobile browsing, cookies and correction requests. If your question concerns a specific record, keep the account phone number and payment reference ready, then use the support route displayed on the account or cashier page.

It covers account details, phone verification, device and browser signals, cookies, security events and payment references linked with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, contact steps and requests to access or correct eligible data.

We use your phone number to create and identify the account and to complete the clear verification step before account access. Keeping it accurate helps us match a privacy request or cashier question to the correct account without asking for a wallet PIN.

Yes. The Privacy Policy covers payment references, amounts and status details needed to match DANA or QRIS activity with your account. We use those records to investigate a pending cashier event and do not need your wallet password to check the transaction.

We may receive device type, browser details, login time and security signals connected with your mobile session. These details help protect the account and keep the path from phone verification to the lobby working; they do not give us the private contents of your device.

Use the support route shown in your account area and identify the phone number on the account, then name the field or record that needs correction. We verify the request before making a change, especially when it affects payment matching or account access.

You can request deletion of eligible personal data through the published privacy contact path. We first confirm that the request comes from the account holder, then assess whether a record must remain for payment reconciliation, account security or a legal purpose described in the Privacy Policy.

Where local law permits, you can ask for a copy or explanation of eligible account data through the support route beside your account or cashier page. Include the verified phone number and a precise request so we can locate the relevant record and respond clearly.