Reference

raja788 Privacy Policy for Your Account

The raja788 Privacy Policy explains how we collect, use, protect, and retain the details connected to your account, device, and wallet activity.

Account dataCookie choicesWallet recordsSecurity checks
raja788 raja788 Privacy Policy for Your Account
CONTACT ROUTES

Get Privacy Policy Help Directly

A clear contact route matters when you want to ask about personal data rather than a wallet status. Use the support channel linked on our site and include the account phone number, the subject of your Privacy Policy request, and the relevant date. We use those details to locate the correct record without asking you to send a password, PIN, or full wallet credential.

Team online

Account data request

Ask us to identify the account details we hold, explain their purpose, or correct a phone number after we confirm that you control the account.

Cookie question

Tell us which device or browser shows a cookie concern. We can explain the related setting and how it affects sign-in continuity or security checks.

Wallet record query

For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, provide the reference and date so we can trace the relevant payment event.

DATA PRACTICES

How We Handle Your Privacy Requests

We keep this policy practical by linking each data practice to an account action you can recognise.

Collected account details

We may handle your phone number, account identifiers, sign-in events, and verification results so we can connect a request to the correct account without exposing another person’s details.

Device and cookie signals

Browser type, device signals, and cookies can help keep a session recognised and flag unusual sign-in behaviour. You can ask us what category was used for a specific event.

Payment references only

For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity, we may retain references and status details rather than private wallet PINs or banking passwords.

Account security steps

Phone verification before account access helps us distinguish an authorised sign-in from a suspicious attempt. Never place your password, PIN, or one-time code in a support message.

Retention by purpose

We retain records for the period needed for security, account support, payment tracing, or legal duties. When a purpose ends, handling follows the applicable retention requirement.

Changes and correction

If your account detail is wrong or your data request needs clarification, contact us through the site support route. Include the affected field, but omit passwords and wallet credentials.

Privacy Policy Answers for raja788

These Privacy Policy answers address the account and payment questions you are most likely to have before access. They explain the records connected to sign-in, device use, cookies, wallet references, and requests for access or changes. If your case involves a specific transaction or phone number, use the support route so we can check the right record.

The raja788 Privacy Policy covers account details, phone verification, device and cookie signals, security events, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

We use your phone number to create and identify your account, complete the phone verification step before access, respond to account requests, and investigate sign-in events. We do not need your wallet PIN or banking password.

Yes. The Privacy Policy covers cookies and related device signals used to maintain sign-in continuity, remember security context, and identify unusual behaviour. You can ask support about a cookie linked to a particular browser or device.

We may retain the payment reference, amount status, account link, and event time needed to trace a DANA or QRIS transaction. We do not ask you to send a wallet PIN, password, or one-time code.

You can contact support to ask what account data we hold or to correct an inaccurate field. Include your account phone number and request details after verification; the outcome depends on local law and retention duties.

Retention depends on the purpose of the record, such as account security, payment tracing, support, or a legal duty. We keep information only for the applicable period and can explain the reason for a specific record.

Where local law permits, you can request deletion through the site support route. Some records may need to remain for security, payment tracing, dispute handling, or legal duties, and we will explain any limitation.