Reference

rajawali55 Privacy Policy Explained

Our Privacy Policy shows how rajawali55 collects, uses and protects the details linked to your account, wallet activity and device access.

Account dataWallet recordsCookie choicesAccess requests
rajawali55 rajawali55 Privacy Policy Explained
CONTACT ROUTES

Get Privacy Help Through Your Account

A clear contact route makes a privacy request easier to process. Open your account support path and send the email or account detail connected with your request, such as a correction to…

Account privacy request Use the support path attached to your account when you want to ask what personal data we hold, why it is used, or which records relate to your DANA, OVO, GoPay or QRIS activity.
Correction request Tell us which account detail needs changing, such as a phone number or contact address. We compare the request with your account step before applying a correction to protect access.
Receipt and access check For a missing payment reference or unusual login, include the date, device path and wallet rail used. We use those details to locate the record without asking for your wallet password.
DATA PRACTICES

Cookies, Retention and Account Security

Our privacy process follows the data trail created by account access rather than collecting every detail about your device.

Data collected

We may receive your account name, phone verification result, login timestamps, device type, browser details and payment references. We use these fields to connect access, wallet status and support requests.

Cookie controls

Necessary cookies help keep a verified session open between login and the lobby. Preference cookies remember selected settings, while your browser controls let you clear or restrict optional storage.

Payment separation

DANA, OVO, GoPay and QRIS references help us match a transaction, but wallet passwords and private wallet credentials remain outside the details we request for account support.

Security checks

A new device, repeated login failure or unusual account change can trigger an extra account check. We use the device path and verification record to reduce mistaken access.

Retention periods

We keep records for the time needed to operate the account, resolve a payment dispute, investigate misuse or meet a legal duty. When no purpose remains, handling follows our deletion process.

Your requests

You can ask for access, correction or deletion where applicable. Include your account contact and the exact request; we may verify ownership before releasing or changing personal data.

Privacy Policy Answers for Your Account

These Privacy Policy answers focus on the account actions you are most likely to ask about before using rajawali55. We cover wallet references, cookies, device access, corrections and deletion requests in plain language. If your question concerns eligibility or access from Indonesia, the applicable position depends on local law, and our support path can help identify the correct account process.

It covers account details, phone verification, device and browser records, cookies, payment references, support requests, retention and the steps available when you ask to access or change your data.

No. We use transaction references, status and timing to match DANA or QRIS activity. We do not ask for your wallet password when checking a receipt or handling a privacy request.

Device type, browser details and login timestamps help us keep a verified session connected, detect unusual access and investigate an account issue when you move between mobile and desktop.

Open the account support path and state that you want access to your personal data. Include your account contact and request scope; we verify ownership before sharing account-linked records.

Yes. Send the incorrect detail, the requested correction and your account contact through support. We may confirm your phone verification or another account step before making the change.

Necessary cookies support login continuity and session security. Preference cookies can remember settings, while your browser controls can clear or restrict optional cookies without changing the account records needed for access.

You may request deletion where applicable by contacting support through your account path. Some records can remain for payment disputes, security checks or legal duties where local law permits.