Reference

Privacy Policy for raja62 Accounts

Our Privacy Policy explains how raja62 handles the details you provide when opening an account, signing in, checking wallet status or contacting support.

Account clarityWallet dataCookie choicesSecurity steps
Browse Our Lobby Read FAQ
raja62 Privacy Policy for raja62 Accounts
HELP WITH PRIVACY

Get Clear Answers About Your Data

A direct support path helps you resolve a Privacy Policy question without sending sensitive details through random channels.

Account questions Ask how we use your phone verification, login record or account identifier. Our support desk can point you to the relevant Privacy Policy section and explain the identity check required before we discuss account-specific data.
Wallet records For DANA, OVO, GoPay or QRIS status questions, share the transaction reference rather than a wallet password. We use the reference to locate the payment event and explain what data was received, stored or passed for checking.
Change requests Request a correction, access copy or deletion assessment through the same account support route. We first confirm that you control the account, then explain any records that must remain available for security or legal reasons.
DATA CONTROL DETAILS

What Your Privacy Choices Cover

Our handling process separates everyday account activity from information needed to protect your access.

Account data

When you open an account, we use the details supplied in the account form and the phone verification step to create a usable sign-in record. We do not need your password in a support message, and we ask you to keep that secret.

Payment matching

A DANA, OVO, GoPay or QRIS event may produce a reference, amount status and time record so we can match the event to your account. Bank transfer and virtual account checks follow the same purpose: confirming status, not collecting unrelated wallet content.

Device signals

Your phone or desktop browser can send technical signals such as browser type, operating system, session time and security markers. These signals help us recognise unusual access around the login path without treating every device detail as a profile about you.

Cookies

Cookies can keep a session active, remember a selected setting or help us understand whether a page request completed. You can manage cookie settings in your browser; limiting them may require another login or make some account steps unavailable.

Security controls

We use account checks, session controls and the Two Factor Setup option to reduce unauthorised access. If a sign-in looks unusual, we may ask you to confirm account ownership before discussing wallet records, changing details or restoring access.

Retention requests

You may ask how long a particular account, device or payment record is kept and request a copy or correction. We assess deletion requests against active account needs, fraud prevention, transaction reconciliation and duties that may apply where local law permits.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the practical searches you may make before opening an account or asking us to change your records. We keep the wording specific to raja62 account access, Indonesian wallet references, device behaviour, cookies and support requests. If your situation is different, contact us through the account support route with only the details needed to identify your request.

The raja62 Privacy Policy covers account creation, phone verification, login sessions, device signals, cookies, support messages and payment status records. It explains why we use each category, how we protect access, how retention works and how you can request access, correction or a deletion assessment.

We may collect the contact and account details you enter, the result of your phone verification, login and session records, and security signals from your browser or device. We use these details to provide account access, investigate unusual sign-ins and answer a request about your own records.

Yes. The Privacy Policy covers payment status information connected with DANA, OVO, GoPay and QRIS, plus bank transfer and virtual account references. We use a reference, status and timing detail to match an event with your account; we do not ask for your wallet password.

Use the account support route and state that you want a copy of your raja62 data. Include the phone or email linked to the account, but omit passwords and one-time codes. We confirm account control first, then explain the available records and the response steps.

You can request a correction or ask us to assess deletion of a record. We may need to retain some account, security or payment information for active access, transaction matching or legal duties where local law permits. We explain which part can change and why.

Cookies may keep your session active, remember a setting or show whether an account page completed. You can limit them in your browser, but the next login may require extra steps and some account functions may not work as intended. Cookie choices do not replace an account data request.

We use limited technical signals, such as browser type, operating system, session time and security markers, to identify unusual access. These signals support login protection and Two Factor Setup checks. If a sign-in needs confirmation, we ask for an account ownership step before discussing private records.

Related Pages

raja62 Indonesia FAQ raja62 Casino Liga 1 Match Bet Sriwijaya Gold Slots