Reference

Open raja899: Privacy Policy For Your Account

Our Privacy Policy explains how raja899 handles the details you provide when you open an account, sign in, contact support or use DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record controlsAccount access requestsCookie choices
raja899 Open raja899: Privacy Policy For Your Account
CONTACT PATHS

Check Privacy Questions Through Support

A direct support request is the quickest way to ask about your personal data, a wallet reference or an account record.

Account support Use the support path connected to your account to ask which personal details we…
Wallet records For a DANA, OVO, GoPay or QRIS reference, send the receipt detail and the…
Login concerns If a sign-in alert, device change or phone verification issue concerns your privacy, tell…
DATA PRACTICES

Explore How We Handle Your Details

Privacy work follows the same account path you use each day: account creation, phone verification, sign-in, wallet status and support.

Account data

We collect details you submit during account opening, including contact data needed for phone verification and account access. We use those details to maintain your profile, respond to policy requests and connect activity to the correct account rather than to an unidentified device.

Cookies and devices

Cookies and similar device records help keep a sign-in session active, remember a language or region choice and detect unusual access. On mobile, we may record browser and device signals from the login-to-lobby path; clearing cookies can require you to sign in again.

Wallet references

A DANA, OVO, GoPay or QRIS status can create a reference linked to your account, while BCA, BRI, Mandiri or BNI transfer details may support reconciliation. We use these records to match a payment event, investigate a receipt and protect account accuracy.

Account security

Phone verification, sign-in records and device signals help us identify access that does not match your usual account path. Never send a password or one-time code in a support message. If a device changes unexpectedly, contact us from the account support route.

Retention choices

We keep personal data only as long as its purpose requires, subject to payment reconciliation, account security and legal needs. When those reasons end, records move through our removal process. Some transaction references may remain longer than ordinary profile details for audit handling.

Requests and corrections

You can ask who handles your data, request a copy, correct an inaccurate detail or ask whether deletion is available. Send the request through support using your linked account contact. We may verify ownership before making a change, and we will explain any limit clearly.

Find Answers About Privacy Policy

These Privacy Policy answers address the searches we hear most often from people opening an account in Indonesia. They cover account data, cookies, payment references, device access and requests for changes. If your case involves a specific receipt or sign-in event, use the support path so we can check the record connected to your profile.

The raja899 Privacy Policy covers data you submit for account opening and phone verification, records created during sign-in, device and cookie signals, wallet references and support messages. It also explains purposes, retention, security steps and how you can request access, correction or deletion.

We use your phone number to support account creation, complete the phone verification step and help protect account access. It can also help us identify the correct profile when you ask about personal data. We do not ask you to place passwords or codes in support messages.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account reconciliation. We use those records to match a payment event, check a receipt or resolve a wallet status question linked to your account.

Cookies can keep your sign-in session active, remember a selected setting and help identify unusual access. Our mobile path may also receive browser or device signals for security. If you clear cookies, you may need to complete sign-in and phone verification again.

You can ask for a copy of personal data connected with your account through the support path. Include your linked phone or email detail so we can locate the profile. We may verify account ownership first, then explain which records can be provided and in what form.

Send a correction request through account support and identify the detail that appears wrong, such as a contact field or account preference. We may ask you to complete an ownership check before changing it. Payment records can have separate reconciliation requirements, which we will explain.

A request may be limited when releasing or removing a record could expose another person’s data, weaken account security, interrupt payment reconciliation or conflict with a legal requirement. If that applies, we will describe the reason and tell you which part of the request remains available.