Reference

Open With raja24 Privacy Policy

Our Privacy Policy explains what we collect when you create an account, verify your phone, sign in from a mobile device and use wallet options such as DANA…

Clear data purposesPhone verificationWallet record clarityAccount request path

Explore Our Lobby Read FAQ

Explore What This Privacy Policy Covers

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

This Privacy Policy applies to information you provide during account creation, phone verification, login, cashier activity and support contact. We may record account identifiers, device and browser details, login events, payment references and messages needed to resolve a status question. A DANA, OVO, GoPay or QRIS

1
reference helps us match a deposit status without treating your wallet password as account content. The same approach applies to bank transfer and virtual account references. If you reach us from Semarang or another Indonesian location, the handling described here remains subject to where local law
2
permits and any jurisdiction-specific access rule shown during account entry.

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

REQUEST SUPPORT

Browse Your Privacy Contact Paths

A clear contact route matters when a data question affects your account or wallet status. We ask you to use the support path available after login and include the email or phone detail connected to the account, plus the relevant payment reference where a receipt needs checking. This lets us identify the correct record before discussing it. Where access is unavailable, use the contact route displayed on the raja24 site and describe the request as a Privacy Policy matter.

Team online

Account data request

Ask us to identify the personal data linked to your account after you complete the requested account check. Include your registered phone detail so we can separate your request from another account and reply through the contact route shown in your support area.

Wallet record question

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account record, send the transaction reference and approximate date through account support. We use those details to locate the status record while avoiding requests for your wallet password or private access code.

Correction or concern

Tell us which account detail, device record or cookie concern needs attention. Our support path can route a correction request or privacy concern to the team handling account records, and we may ask for phone verification before changing protected information.

DATA HANDLING

Switch Through Our Privacy Practices

We use practical controls around the information that helps an account work. Login and phone verification events support account security; device details help us recognise unusual access; and payment references help reconcile…

Account creation

When you open an account, we use the details you submit to create the account record and provide account access. Phone verification confirms control of the contact route connected to that record before protected account changes or access questions are handled.

Device signals

A mobile browser or desktop session may provide device, browser, language and login-event details. We use these signals to investigate unusual account access and support a safer sign-in path; they do not replace the account checks required for a protected request.

Payment references

DANA, OVO, GoPay and QRIS activity can create a reference, amount, status and time record connected to your account. Bank transfer and virtual account records follow the same reconciliation purpose, while wallet passwords and external banking credentials remain outside our account record.

Cookies and sessions

Cookies can remember a session, preserve sign-in context and help us understand whether a Privacy Policy page was reached from an account route. You can manage browser cookie settings, although changing them may affect login continuity or the way account pages load.

Retention decisions

We keep account, security, payment-reference and support records for the period needed for the purpose that created them, including dispute handling and applicable legal duties. When a record no longer has a valid purpose, our handling follows the deletion or restriction process available to us.

Changes and requests

You can ask about access, correction, deletion, restriction or the reason a particular record is used. We may request phone verification or another account check before responding, because a Privacy Policy request must not expose your details to someone else.

Check Common Privacy Policy Questions

These answers address the account, device, cookie and payment-record questions most often raised before account access. The full Privacy Policy remains the controlling text for your request, and the route available to you can depend on local law. Keep your registered phone detail and any relevant receipt reference ready when you contact us.

The raja24 Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, account security and how to request access or correction.

Phone verification helps us confirm control of the contact detail attached to your account before we discuss protected records or process certain account changes. It also supports login security. We do not ask you to provide a wallet password or external banking credential for this account check.

We may store a payment reference, status, time and account connection needed to reconcile a DANA, OVO, GoPay or QRIS transaction. This record helps support check a receipt or pending status. It is different from your wallet password, banking login or private wallet security code.

Yes. The Privacy Policy explains that a mobile or desktop browser may provide device, browser, language and login-event details, while cookies can maintain a session and show how a policy page was reached. You can adjust browser cookie settings, but login continuity may change.

Use the support path available after login and describe the request as a Privacy Policy data request. Include your registered phone detail and specify whether you want access, correction, deletion or restriction. We may complete an account check before sharing or changing protected information.

We retain account, security, support and payment-reference records for the period needed for their stated operational, dispute or legal purpose. The exact period can differ by record type and jurisdiction. When the purpose ends, our handling follows the deletion or restriction process available under local requirements.

Use the contact route displayed on the raja24 site and explain that your request concerns the Privacy Policy. Provide the registered phone detail without sending a password, then add a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference only when it relates to your question.

Open With raja24 Privacy Policy

Browse Your Privacy Contact Paths

Account data request

Wallet record question

Correction or concern

Switch Through Our Privacy Practices

Account creation

Device signals

Payment references

Cookies and sessions

Retention decisions

Changes and requests

Check Common Privacy Policy Questions

01 What does the raja24 Privacy Policy cover?

02 Why does raja24 need phone verification?

03 What payment data is stored for DANA, OVO or QRIS?

04 Does the Privacy Policy explain device and cookie data?

05 How can I request my personal data from raja24?

06 How long does raja24 keep account and payment records?

07 Where can I ask a Privacy Policy question if I cannot log in?

Related Pages