Reference

rajadewa Privacy Policy For Your Account

The rajadewa Privacy Policy explains how we collect, use and protect details linked to your account, phone verification and wallet activity.

Clear data purposesPhone verification explainedIndonesia account access

Explore Our Lobby Read FAQ

How Wallet Details Stay Connected

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

Our Privacy Policy covers details you provide during account creation, including your contact details and the phone check required before account access. When you select DANA, OVO, GoPay or QRIS, we use the payment status and reference details needed to match an activity to your account,

1
resolve a failed step and answer a support request. Bank transfer and virtual account references may also be retained for matching and security checks. We do not describe these rails as anonymous because a clear account trail helps us investigate wallet status. Cookies may remember sign-in
2
preferences on your device, while security records help identify unusual access. Where local law permits, we process these details for the services you request; otherwise, eligibility depends on local law. The policy also explains how to ask about a record, request a correction or contact our
3
support route.

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

HELP WITH PRIVACY

Get Clear Answers About Your Data

A direct support path matters when a phone check, wallet reference or cookie setting raises a question.

Account support route Send your Privacy Policy question through the account support path and include your account identifier. We check ownership first, then explain the relevant data purpose without exposing private details.

Wallet status check If DANA, OVO, GoPay or QRIS shows an unclear status, share the reference and time shown on your account. We use those details to trace the record and respond to your privacy request.

Phone verification help A phone verification concern can be raised before account access is completed. Tell us which step stopped, and we will explain the security reason and the data connected with that check.

DATA CONTROL POINTS

What You Can Check And Change

Privacy is easier to manage when each record has a clear purpose and contact path. We describe how account details, cookie signals, phone checks and wallet references support requested services, security and…

Data collection

We collect details you submit for an account, plus records created by phone verification and requested payment steps. The Privacy Policy connects each category to account access, security, support or the service you selected.

Cookie choices

Cookies can keep a sign-in preference or help us recognise a returning device. You can review browser controls on your mobile or desktop path, while changing them may affect account access checks.

Account security

Phone verification before account access helps us check that the person requesting entry controls the supplied contact route. We may examine sign-in and wallet records when a security concern needs attention.

Retention timing

We keep account, payment-reference and security records only for the period needed for the stated purpose, support handling, dispute checks or a legal requirement that depends on local law.

Correction request

If your name, phone detail or account record is inaccurate, contact support from your account and describe the requested change. We may ask for an ownership check before editing private account data.

Access request

You can ask what account details we hold and why they appear, including records linked to DANA, QRIS, bank transfer or virtual account activity. We reply through the account support path.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the questions you may have before opening an account or using a wallet route. If your situation is not covered, use the account support path and include only the details needed to identify your request.

It covers account details, phone verification, cookies, sign-in records, payment references and support requests. It also explains purposes, retention, correction requests and how to contact us about your data.

Phone verification helps us check account ownership before access and respond to security concerns. The Privacy Policy explains how the contact detail and verification result are used for that specific account step.

Yes. It explains that DANA, OVO, GoPay and QRIS references may be used to match a requested wallet step, investigate a status issue and answer a support request.

You can request a correction through the account support path. Describe the inaccurate phone or account detail, and we may complete an ownership check before changing the record.

We retain payment and security records for the period needed for the stated purpose, support handling, dispute checks or a legal requirement. The applicable period depends on local law.

Contact us from the relevant account and ask for a data access request. Include the account identifier and the category you want checked, such as cookies, phone checks or wallet references.

Cookies may remember a sign-in preference or help recognise a returning device on a mobile browser or desktop. Your browser controls can change cookie settings, though access checks may respond differently.

rajadewa Privacy Policy For Your Account

Get Clear Answers About Your Data

What You Can Check And Change

Data collection

Cookie choices

Account security

Retention timing

Correction request

Access request

Privacy Policy Answers For Indonesia

01 What does the rajadewa Privacy Policy cover?

02 Why does rajadewa need phone verification?

03 Does the Privacy Policy mention DANA and QRIS data?

04 Can I ask rajadewa to correct my account data?

05 How long does rajadewa keep payment references?

06 How do I request access to my Privacy Policy data?

07 Does rajadewa use cookies on mobile devices?

Related Pages