Reference

Privacy Policy for Your rajaasiaa88 Account

Our Privacy Policy explains how we handle the account, device and wallet details you provide when you open rajaasiaa88 access for Live Casino, ayo168 or Fish Hunter.

Account dataCookie choicesWallet checksRequest support
rajaasiaa88 Privacy Policy for Your rajaasiaa88 Account
HELP WITH DATA

Where to Ask About Privacy Policy

A clear support route matters when a Privacy Policy question concerns your own account rather than a general request. Sign in, open the account help area, and include the phone number or transaction reference connected to your question; please do not send a wallet PIN. If login is blocked, use the contact route shown beside the account access prompt. We can then locate the right record, explain the data purpose and direct a correction or deletion request where local law permits.

Team online

Account help path

Use the account help area after sign-in for a Privacy Policy request. Add your registered phone number and the specific record you want checked, while keeping your DANA, OVO, GoPay or QRIS PIN private.

Login access route

If you cannot reach the account page, follow the contact route beside the login prompt. Tell us whether the issue concerns device access, a cookie choice or a personal-data request so we can separate the cases.

Receipt reference

For a wallet-data question, include the payment receipt or reference from DANA, OVO, GoPay, QRIS, bank transfer or virtual account. We use that reference to locate the relevant record without asking for your PIN.

HANDLING YOUR DATA

Six Practical Privacy Policy Checks

We apply this Privacy Policy to ordinary account work, not to a vague promise about the whole lobby.

Account details

When you open an account, we use the phone number and verification result linked to that step to recognise your sign-in. We do not need your wallet PIN for a Privacy Policy request or an account-data explanation.

Device signals

A phone or desktop browser can send sign-in time, browser type and security signals. These details help us spot an unusual access attempt and explain why the same account may receive a verification prompt on a new device.

Cookie controls

Cookies can keep your session and selected page settings available while you move between account pages. You can clear them through your browser settings, although doing so may require another sign-in before a Privacy Policy request is sent.

Account protection

We use phone verification and sign-in checks to reduce unauthorised access. If a device change affects your account, contact us through the account route and describe the prompt; never place a password, PIN or full wallet credential in a message.

Record retention

We keep account, support and transaction references only for the operational, security and legal period needed for the stated purpose. A deletion request can be assessed against those duties, and we will explain any record that must remain.

Change requests

To correct a phone number, ask about stored data or request removal, send the request from the account support path. We may ask for an account step to confirm identity before changing personal records where local law permits.

Privacy Policy Questions for Indonesia

These Privacy Policy answers address the searches we expect from someone checking rajaasiaa88 before opening an account. They cover data categories, wallet references, cookies, device prompts, correction requests and access conditions. If your situation is not listed, use the account support path with only the details needed to identify your request.

It covers account details, phone verification, device and sign-in records, cookies, support messages and payment references. The Privacy Policy also explains why we use each category, how to request correction or removal, and when a record may need to remain for security or legal reasons.

Yes. The Privacy Policy covers references connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account steps. We use a reference to match an account or receipt question; we do not ask you to send a wallet PIN.

We use your phone number for account recognition, phone verification and support matching. If you ask us to correct or remove it, we may request an account step to confirm that the request comes from you, where local law permits.

You can ask for a copy, explanation or correction through the signed-in account help area. Include the relevant field, such as a phone number or receipt reference. We may verify your identity first and will assess the request under local law.

Cookies can retain your sign-in session and page preferences, so they form part of the Privacy Policy explanation. You can clear or restrict them in your browser. Afterward, the account page may ask you to sign in and verify again.

A new phone, browser or desktop can differ from your earlier sign-in pattern. We use device signals to help protect account access, so a verification prompt may appear. Contact support through the account route if the prompt does not match your activity.

You may submit a removal request through account support, and we will assess it under the Privacy Policy. Some security, transaction or legal records may need to remain for a defined purpose. Access or eligibility depends on local law.