Reference

rajaplay Privacy Policy For Your Account

Our Privacy Policy explains how we use the details connected to your rajaplay account, including phone verification, DANA, OVO, GoPay and QRIS activity.

Account dataWallet recordsCookie choicesDevice security

Explore Our Lobby Read FAQ

Open The Privacy Policy Beside QRIS

rajaplay Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We collect only the details needed to operate account access, confirm phone ownership, record wallet activity and respond to requests about your data. When you use DANA, OVO, GoPay or QRIS, we may retain transaction references, timestamps and status details so a payment question can be

1
checked against the account record. Bank transfer and virtual account references are handled in the same way. Device type, browser settings and security events may be recorded when you sign in, helping us identify unusual access without reading unrelated content on your phone. Cookies support sign-in
2
continuity and policy preferences; you can manage them through your browser. We retain records for the period needed for account support, security checks and legal duties. Access depends on local law, and we apply this Privacy Policy where local law permits. If a wording point is
3
unclear, use the support routes below and include the account step or payment reference involved.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Choose A Privacy Contact Path

A clear contact route helps you ask about personal data without repeating your whole account history.

Account support path Ask which account details we hold, why they are used, or how to request a correction. Include your registered phone number only inside the signed-in support form.

Wallet record request For DANA, OVO, GoPay or QRIS records, send the reference, date and status shown in your account. We use those details to locate the relevant payment entry.

Login help route If phone verification or device access blocks your request, begin with login help. We may ask account-security questions before discussing personal data connected to the profile.

DATA PRACTICE

See How rajaplay Handles Your Data

Our handling process separates account access, payment records and security checks so a support request can be addressed with the right context.

Account details

We use your phone number and verification result to connect you with the correct account. A correction request should identify the field that needs changing without sharing another person’s data.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account entries may include a reference, amount status and time. These records help us resolve a receipt or wallet-status question.

Cookie controls

Cookies can preserve sign-in settings and your policy preference. You can clear or restrict them in your browser, although some account steps may need to be repeated afterward.

Account security

We watch for unusual login patterns and may request phone verification before discussing account data. Keep your access details private and contact support if a device change looks unfamiliar.

Retention period

We retain account, payment and security records only for the period needed for support, fraud checks, account administration or legal duties. A retention question can be sent through support.

Change requests

You can ask us to correct inaccurate account data or explain its use. Submit the request from your account support path, and we may verify ownership before making a change.

Find Privacy Policy Answers Quickly

These answers address the questions we expect you to have before opening an account or sending a data request. They cover the Privacy Policy, Indonesian wallet records, cookies, phone verification and the steps used to confirm that a request comes from the account holder.

It covers account details, phone verification, wallet references, device and browser signals, cookies, security events, retention and the ways you can request access or corrections.

Yes. The Privacy Policy covers references, timestamps and status details linked to DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity on your account.

Yes. Use the signed-in account support path, name the incorrect field and complete any ownership check we request before the account record is changed.

Cookies can keep sign-in settings and your policy choice available. You can restrict or remove them through browser controls, though some account steps may then need repeating.

Phone verification helps us confirm that a request concerns the correct account before we discuss personal details, change a record or respond to an access request.

We keep those records for the period needed for account support, security checks, account administration or legal duties. Ask through support if you need the reason for a record’s retention.

The policy is available for Indonesian account holders, but account access and certain data rights depend on local law. We apply the relevant terms where local law permits.

rajaplay Privacy Policy For Your Account

Choose A Privacy Contact Path

See How rajaplay Handles Your Data

Account details

Payment references

Cookie controls

Account security

Retention period

Change requests

Find Privacy Policy Answers Quickly

01 What does the rajaplay Privacy Policy cover?

02 Does the Privacy Policy apply to DANA and QRIS records?

03 Can I ask rajaplay to correct my account data?

04 How does rajaplay use cookies on my device?

05 Why is phone verification needed for a privacy request?

06 How long does rajaplay keep payment and login records?

07 Does access to this Privacy Policy depend on local law?

Related Pages