Reference

rajaplay Privacy Policy for Your Account

Our Privacy Policy explains how we handle your rajaplay account details, wallet records and device access while you use the Indonesia lobby.

Clear data purposesWallet record handlingPhone access controlsCookie choices
Explore Lobby Read FAQ
rajaplay rajaplay Privacy Policy for Your Account
HELP WITH YOUR DATA

Three Ways To Ask About Privacy

A clear support route helps you act on this Privacy Policy without guessing which account detail matters. Tell us whether your request concerns sign-in records, a wallet reference, a cookie choice or a message sent to support. Include the phone number linked to your account only through the account help route, and do not send a wallet PIN or password. We use the request details to locate the right record and respond under the rules that apply to your access.

Team online

Account access request

Ask us to confirm the account data connected with your verified phone number. We may request an account step before sharing details, so a different person cannot obtain records linked to your rajaplay sign-in.

Wallet record question

If a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference looks unfamiliar, send the date and status shown in your account. We can check the payment record without asking for your wallet PIN.

Correction or deletion

Use our support path when a profile detail is wrong or you want to request removal of eligible data. We first verify the request, then explain any record we must retain under local requirements.

DATA HANDLING DETAILS

Six Privacy Practices Behind Account Use

We keep this policy practical by linking each privacy choice to an account action you can recognise.

Data we collect

We may receive your phone number, account profile details, sign-in time, device type, support messages and payment status references. Using DANA or QRIS can create a transaction reference, while your wallet PIN stays with the payment service.

Cookie controls

Cookies can keep your session active and remember selected settings on a mobile browser. You can manage browser cookie controls, although disabling necessary cookies may require another sign-in before you reach the lobby.

Account protection

Phone verification is an account step before access, and device signals help us review unusual sign-in behaviour. We do not ask you to place a password, PIN or one-time code inside a support message.

Payment references

Our records can show whether a DANA, OVO, GoPay, QRIS, bank transfer or virtual account request is pending, matched or completed. These references help support check a receipt without exposing your payment credentials.

Retention approach

We keep account, support and transaction records only for operational, dispute, safety or legal needs described by this policy. When a retention period ends, eligible data is removed or separated from direct account identifiers.

Change requests

You can ask us to correct profile data, access a copy, or remove eligible details through support. We may retain a necessary transaction or verification record, and we will explain that reason when local rules require it.

Privacy Policy Answers For rajaplay

These Privacy Policy answers focus on the account questions you are most likely to ask before opening or using rajaplay in Indonesia. They explain payment references, phone verification, device access, cookies, data requests and the route for contacting us. If your situation involves eligibility or access, the outcome depends on local law.

The rajaplay Privacy Policy covers account details, phone verification, sign-in and device records, cookies, support messages, and payment status references. It explains why we use each category, how we protect account access, and how you can request access, correction or deletion where local law permits.

No. Our Privacy Policy distinguishes payment status references from wallet credentials. We may record a DANA or QRIS transaction reference and its status to match account activity, but you should never send your PIN, password or one-time code through support.

Phone verification connects an account request to the correct phone number before access is granted. Under this Privacy Policy, the verification result can support account protection and request handling. We may ask for a further account step before releasing personal records to you.

Yes. The Privacy Policy lets you contact our support path to request a copy of eligible account, device, cookie or payment-status data. We verify your identity first, then explain what can be supplied and whether any record must remain for operational or legal reasons.

Our Privacy Policy describes cookies that keep a sign-in session active and remember selected settings on your mobile browser. You can change browser controls, but necessary cookies may be required for another account sign-in before access to the lobby.

Send a correction request through support and identify the profile field that is inaccurate. We may confirm your verified phone number before making a change. The Privacy Policy allows corrections to eligible data, subject to records that must remain under local requirements.

The Privacy Policy applies to data connected with your rajaplay account, support requests, devices and payment references. Account access and eligibility depend on local law. If a local rule affects your request, we will explain the applicable limitation through the support route.

Related Pages

rajaplay Indonesia ormas4d Super Sic Bo Account information Access guide