Reference

Privacy Policy for raja800 Accounts

Our Privacy Policy explains how raja800 handles the details you provide when you open an account, sign in, use the lobby or check a wallet status.

Account data explainedWallet checks coveredAccess requests welcome
Explore Our Lobby Read FAQ
raja800 Privacy Policy for raja800 Accounts
HELP WITH REQUESTS

Where Privacy Questions Go

A clear contact route matters when you want to understand or change your account data. Our support path is available through the account area, so you can describe a Privacy Policy request without explaining your account history from the beginning. Include the phone number or account identifier linked to your access, the request you are making and any relevant wallet reference. We use those details to locate the correct record, protect the account and avoid changing information for the wrong person.

Team online

Account data request

Ask through the account support path when you want a copy of personal details connected with your raja800 access. We may ask you to complete phone verification before releasing records, because the request must come from the account holder.

Correction request

If your phone number or another account detail is inaccurate, tell us what needs changing and why. We compare the request with the account record and may check the linked wallet status before applying an update.

Wallet privacy query

For a question about a DANA, OVO, GoPay or QRIS reference, include the payment date and visible status rather than sending a wallet password or secret code. We use the reference to trace the record safely.

SIX DATA SAFEGUARDS

What We Do With Your Details

Privacy protection is part of the account path, not a separate promise hidden after payment. We separate the information needed for sign-in, support and transaction matching, and we limit internal access to…

Account details

We use your submitted contact and verification details to create the account, confirm access and answer account requests. Keeping the phone number current helps us match a Privacy Policy request with the correct record.

Security signals

Login time, device type and session activity can be recorded to help detect suspicious access. These signals support account protection around the step from phone verification into the lobby and are not treated as a public profile.

Cookies

Cookies and similar storage can keep sign-in flows, page settings and security checks working on your browser. You can control browser storage, but changing those settings may interrupt access or require you to verify your account again.

Payment references

We may retain a DANA, OVO, GoPay, QRIS, virtual account or bank transfer reference to match a cashier event with your account. We do not ask you to place wallet passwords or secret codes in a support message.

Retention period

We keep account and transaction records for the period needed to operate the service, investigate security events, resolve disputes or meet legal duties. When a record is no longer needed for those purposes, our handling process removes or anonymises it.

Change or access

You can ask what personal details we hold, request a correction or raise a question about deletion through account support. We may verify your identity first, then explain any restriction that depends on local law or a required record.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account and wallet questions you may have before opening access. We keep each answer tied to a practical route, from phone verification and browser cookies to payment references and requests made through account support. If your situation is not covered, send the relevant account identifier without sharing a password or secret wallet code.

The raja800 Privacy Policy covers information used for account creation, phone verification, sign-in, security checks, support and transaction matching. It also explains cookies, retention, change requests and the handling of references connected with DANA, OVO, GoPay, QRIS, virtual account and bank transfer activity.

Phone verification helps us confirm that the person opening or accessing an account controls the linked contact detail. It can also protect a Privacy Policy access or correction request from being submitted by somebody else. Access and eligibility depends on local law.

The policy covers payment references and status details needed to match an account event, not your wallet password or secret code. This can include a DANA, OVO, GoPay, QRIS, virtual account or bank transfer reference, plus the date and visible cashier result.

Yes. Use the account support path and state that you want a copy of the personal details linked to your access. Include your account identifier, but do not send a password. We may complete phone verification before responding, and the request may depend on local law.

Send a correction request through account support, identify the field that is wrong and provide the accurate version. We compare it with the account record and may ask for verification. If a transaction or security record must remain unchanged, we explain that restriction.

We retain records while they are needed for account operation, security checks, support handling, dispute resolution or legal duties. The exact period can differ by record type and local requirements. When continued retention is not needed, we remove or anonymise the record.

Browser cookies can support sign-in, page settings and security checks, but they do not replace your Privacy Policy rights. You can adjust browser storage controls. If that blocks an account step, you may need to sign in again or complete phone verification.

Related Pages

raja800 Indonesia About Us Access guide raja800 Casino Account information