Reference

rajawali500 Privacy Policy For Your Account

The rajawali500 Privacy Policy explains how we handle your account details, wallet records, device signals and support requests when you open an account or use our lobby.

Account clarityWallet recordsCookie choicesLocal access
rajawali500 rajawali500 Privacy Policy For Your Account
CONTACT ROUTES

Browse Privacy Help Beside Wallet Support

A clear support path helps when your Privacy Policy question concerns login, phone verification or a wallet receipt. We ask you to contact us through the support route shown in your account area and include the email or phone connected to the account, without sending a password. This process works for you in Bandung and across Indonesia where local law permits.

Team online

Account requests

Ask us to locate the personal data connected to your account by giving the registered contact detail and a short description of the Privacy Policy request.

Wallet questions

For DANA, OVO, GoPay, QRIS or bank transfer records, include the receipt reference and date so we can separate payment matching from unrelated account data.

Access concerns

If sign-in or phone verification appears unusual, contact support from the account path and avoid sharing passwords, one-time codes or complete wallet credentials in your message.

DATA PRACTICES

Explore How We Handle Privacy Requests

Privacy is handled through ordinary account operations rather than vague promises. We separate login, wallet and support records, use device signals to help protect account access, and keep…

Account records

We use your submitted contact details and phone verification status to connect you with the correct account, reduce mistaken access…

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references can help us trace a receipt or status question without…

Device signals

Browser type, device signals and login events may be checked when an account session looks unusual.

Cookie choices

Cookies can remember session settings and help us understand whether an account page loads correctly.

Retention approach

We retain records for the operational or legal reason that requires them, then remove or separate them when that reason…

Change requests

To correct contact details, ask about access, or question a retention entry, use the support route in your account area.

Find Privacy Policy Answers Before Joining

These Privacy Policy answers address the account steps Indonesian customers usually ask about before opening access. Each answer points back to a practical action, whether you are checking cookies on mobile, asking about wallet records or requesting a correction.

It covers account details, phone verification, login events, device signals, cookies, wallet references, support messages and retention. It also explains how to ask for access, correction or clarification where local law permits.

Yes. The Privacy Policy describes how DANA and QRIS references, along with OVO, GoPay, bank transfer and virtual account details, may be used to match receipts and answer status questions.

Use the support route shown in your account area and provide the registered email or phone detail. We may check account ownership before locating or sending data covered by the Privacy Policy.

Yes. Send a correction request through the account support path, identify the detail that needs changing and explain the accurate value. We may verify your identity before updating the record.

Cookies can retain session settings and help diagnose page loading on a mobile browser. You can restrict them through browser controls, although login or phone verification steps may need to be completed again.

Contact support through your account path without sending a password or one-time code. Include the approximate time and device context so we can check access events under the Privacy Policy.

It applies to supported account activity in Indonesia where local law permits. Access and eligibility depend on local law, so your available account path may differ by jurisdiction.