Reference

Legal access for your rajawin account

rajawin Legal sets out how account access, identity checks, payments and personal data are handled before you enter the lobby.

Account termsData and cookiesLocal-law access
rajawin Legal access for your rajawin account
POLICY HELP ROUTES

Get help with Legal and access

A clear contact route matters when a policy question affects your account or wallet status.

Access questions Ask us to clarify how Legal access applies to your location before you complete…
Payment records If a DANA, OVO, GoPay or QRIS record does not match your account status…
Data requests Use the same support route to ask what account data we hold, request a…
DATA HANDLING DETAILS

How rajawin handles policy duties

Legal is practical only when you can see how it affects an account. We use the details you provide during registration and phone verification to maintain account access, match payment records and…

Registration data

Your account contact, phone verification result and registration details are used to connect you with the correct account. Check these details before submission; an inaccurate phone number can delay access questions and make a later correction request harder to confirm.

Payment matching

When you use DANA, OVO, GoPay or QRIS, the transaction reference helps us compare the cashier status with your account record. Bank transfer and virtual account requests follow the same matching principle, so keep the receipt until the status is settled.

Cookies

Necessary cookies help maintain a signed-in session and remember required choices as you move between account pages. On a phone, clearing browser data can remove that session and require phone verification again; the policy explains the purpose of those cookies.

Account security

We use the account contact and phone verification step to reduce mistaken access. Keep your password and wallet credentials private, sign out on shared devices, and contact us through the account path if you see an unfamiliar session or payment reference.

Record retention

Some account, payment and contact records may remain available after a request because they are needed to resolve a transaction, protect account access or meet a policy obligation. We can explain the category involved and the reason before handling a deletion request.

Policy changes

When Legal wording changes, we place the updated text where you can read it before relying on the affected account step. If a change affects access, data handling or payment records, contact us with the relevant section and we will clarify its practical meaning.

Questions about rajawin Legal

These answers focus on the Legal points Indonesian customers usually need before opening an account or asking for a policy change. Read the full wording on the page that applies to your request, then use the account contact route if a detail remains unclear. We answer access, data, cookie, payment and account questions directly rather than sending you to unrelated lobby content.

Legal covers account creation, phone verification, access conditions, payment-record matching, cookies, personal-data handling, retention and requests for corrections or deletion. It also explains where local law permits access and how to contact us when a policy point affects your account.

Access depends on local law and your location. We show the applicable policy before account use, so check the wording for your Indonesian region and stop if the stated conditions do not apply. Contact us if you need help understanding that access position.

Phone verification connects the registration details to the correct account and helps us handle access or payment questions safely. If your number is wrong, update the request through the account contact path; do not send a password, wallet PIN or verification code in a message.

A DANA or QRIS transaction reference helps us compare the cashier status with your account record. OVO and GoPay follow the same matching approach. Keep your receipt until the status settles, and provide only the reference needed for us to investigate a mismatch.

Send a request through the account contact path and identify the detail that needs changing, such as a phone number or registration field. We first confirm the account contact, then explain the correction step or any reason the existing record must remain.

Yes. Legal describes necessary cookies used to maintain the signed-in path and required choices. Clearing browser data on your phone can end the session and require phone verification again. You can ask us which cookie category relates to the account step you are checking.

Use the account-linked support route for access, data, cookie or payment-record questions. Include the relevant Legal section and a transaction reference when needed, but never include your password or wallet PIN. We confirm ownership before discussing personal account details.