Reference

rajasport Privacy Policy, Clearly Explained

Our Privacy Policy explains what account, device and payment details we collect when you open rajasport, why we use them and how you can ask about them.

Account dataWallet recordsDevice choicesPolicy requests
Explore Our Lobby Read FAQ
rajasport rajasport Privacy Policy, Clearly Explained
CONTACT THE TEAM

Three Privacy Policy Contact Paths

A clear contact path matters when your data question concerns a live account or a wallet record.

Account access If your phone verification or sign-in record looks wrong, send the account identifier shown in your account area. We will use it to locate the relevant Privacy Policy request without asking for your wallet password.
Wallet status For DANA, OVO, GoPay or QRIS questions, include the payment reference and approximate time. This lets us compare the wallet status with our transaction record while limiting unnecessary personal details.
Data request Ask us to explain, correct or remove eligible personal details through the account support route. We may first confirm account ownership so a private record is not disclosed to the wrong person.
HANDLING DETAILS

What Our Privacy Process Covers

We separate the practical parts of privacy handling so you can understand what happens after an account step, a payment check or a device visit.

Account information

We may store your phone number, verification result and account choices because they connect you to the correct account. These details help us restore the right account path when you sign in from a new device.

Payment records

A DANA, OVO, GoPay or QRIS transaction can create a reference, amount status and time record. We use that information to match receipts and investigate a payment question, not to request your wallet password.

Cookies and devices

Cookies and device signals can remember a session, language choice or security event. If you open Mobile Legends from a phone and later use desktop, these signals help us assess the account visit.

Account security

Phone verification and sign-in checks help us distinguish your account access from an unfamiliar attempt. We may ask for additional confirmation before discussing private account or payment details through support.

Data retention

We keep personal and transaction records only for as long as needed for the stated service, security, dispute and legal purposes. Retention can differ by record type and by rules that apply where you connect.

Policy changes

If our Privacy Policy changes, we will place the updated wording on this page and identify the effective point where appropriate. You can contact support to ask which version applies to your account request.

Privacy Policy Questions About rajasport

These answers address the questions we expect you to ask before opening an account or sending a privacy request. They focus on the records connected with rajasport access, local wallets, device activity and account support. If your situation is different, send the relevant reference through the account support route so we can assess it directly.

It covers account details, phone verification, device and cookie signals, payment references, support messages and related security records. It explains why we use each category, how storage is assessed and how you can request clarification.

Yes. The Privacy Policy includes transaction references, status and timing connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. We use those records to match payment questions.

You can request a correction through the account support route. Include the account identifier and explain the incorrect field, such as a phone detail or verification record. We may confirm ownership before changing or discussing it.

We may use device, browser and connection signals to maintain a session, remember selected settings and identify unusual sign-in activity. The Privacy Policy treats these signals as security and service records, not as wallet passwords.

Retention depends on the record and the purpose involved. Account, payment, security and support records may need different periods for service, dispute or legal reasons. We assess requests under applicable rules and explain the relevant outcome.

You may ask for removal of eligible personal details through support. We first confirm the request relates to your account, then check whether a record must remain for payment reconciliation, security, dispute handling or a legal requirement.

The policy is written for supported Indonesian access, including account and wallet activity from places such as Denpasar, where local law permits. Eligibility and handling can depend on local law, so contact us if your location creates uncertainty.

Related Pages

rajasport Indonesia Aztec Gems Deluxe Access guide Live Casino rajasport Casino