Reference

Privacy Policy for Your raja cair Account

Our raja cair Privacy Policy explains how we handle the account details, wallet references and device signals connected with your access.

Account clarityWallet recordsDevice controlsCookie choices

Explore Our Lobby Read FAQ

How DANA and QRIS Data Is Used

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

This Privacy Policy covers data gathered when you create an account, complete phone verification, sign in, contact support or move through the wallet area. A DANA, OVO or GoPay reference may be used to match a payment status with your account, while a QRIS receipt helps

1
us investigate a disputed entry. Bank transfer and virtual account records can include a reference linked to BCA, BRI, Mandiri or BNI. We do not use these payment details to create unrelated advertising profiles. Device, browser and cookie signals help protect account access and remember necessary
2
settings. We retain records for the period needed for security, dispute handling and legal duties. Any access or eligibility decision depends on local law, and where local law permits we provide the services described here. You can ask us to explain a record, correct an error
3
or remove data where applicable.

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

DATA HELP

Three Ways to Ask About Your Data

A clear support path matters when a privacy question appears beside an account or wallet issue.

SECURITY LAYER

Six Controls Behind Account Privacy

We apply this Privacy Policy through practical controls rather than broad promises. Account access follows the phone verification step, wallet references stay tied to the relevant transaction, and device signals help us…

Phone verification

Before account access, we use the phone verification step to connect a request with the correct account. This reduces the chance that a privacy request or wallet question is disclosed to the wrong person.

Device signals

Your browser and device can provide security signals when you sign in from mobile or desktop. We use them to assess unusual access patterns, not to read unrelated files or messages on your device.

Cookie settings

Necessary cookies help keep account sessions and selected settings working. Where optional cookies are offered, you can manage that choice through the available cookie control instead of treating every cookie the same way.

Payment matching

A payment reference from QRIS, DANA, OVO or GoPay helps us match a wallet event to your account. We use the reference for status checks and disputes, rather than requesting your wallet sign-in details.

Retention checks

We review stored records against their purpose. Account, security and transaction details may remain while needed for dispute handling or legal duties, then can be removed or de-identified where applicable.

Change requests

You can ask us to correct inaccurate details, explain how a record was used or request deletion where applicable. We may confirm account ownership before making a change to protect your privacy.

Privacy Policy Questions About raja cair Access

These Privacy Policy answers focus on the searches we hear around account access, wallet records and device use. We keep the process practical: identify the account, describe the record and use the support route linked to your account. If a request relates to access or eligibility in Indonesia, the outcome depends on local law.

It covers information connected with your account access, phone verification, device signals, cookies, support requests and payment references. That includes records linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity when those details are needed for status or dispute checks.

We use your phone detail for account creation, verification and ownership checks during privacy support. It helps connect a request to the correct account and can protect wallet records from disclosure. We do not ask for your wallet password or full security code.

We may store a payment reference, status and related account details so we can match a DANA or QRIS event, investigate a dispute and answer your support request. The reference is used for that operational purpose, not as permission to access your wallet.

Yes. When you sign in from a phone or desktop browser, we may use browser, device and session signals to support account security and necessary settings. These signals help identify unusual access; they do not give us access to unrelated files or messages.

We keep each record for as long as its purpose requires, including account security, payment disputes and legal duties. When that need ends, we work toward removal or de-identification where applicable. The period can differ by record type and the request involved.

Use the support route linked to your account and identify the detail that needs correction. Include the verified phone detail or relevant transaction reference, such as a BCA transfer or GoPay record. We may confirm ownership before changing personal data.

You may request deletion through the account support route, and we will assess what can be removed under applicable requirements. Some security, transaction or dispute records may need to remain for a defined purpose. Any access decision depends on local law.

Privacy Policy for Your raja cair Account

Three Ways to Ask About Your Data

Six Controls Behind Account Privacy

Phone verification

Device signals

Cookie settings

Payment matching

Retention checks

Change requests

Privacy Policy Questions About raja cair Access

01 What does the raja cair Privacy Policy cover?

02 Why does raja cair need my phone number?

03 How does the Privacy Policy handle DANA or QRIS data?

04 Does the Privacy Policy cover mobile device data?

05 How long does raja cair keep personal data?

06 How can I request a correction under this Privacy Policy?

07 Can I ask for deletion of my raja cair data?

Related Pages