Reference

Privacy Policy For Your raja100 Account

The raja100 Privacy Policy explains what we collect when you open an account, verify your phone, enter the lobby, or use DANA, OVO, GoPay and QRIS.

Account dataWallet activityCookie choicesAccess requests
Explore Our Lobby Read FAQ
raja100 Privacy Policy For Your raja100 Account
CONTACT ROUTES

Where To Ask About Privacy Policy

A direct support request gives us the context needed to locate the right account record without asking you to resend unrelated details. Tell us whether your question concerns phone verification, a wallet reference, a cookie choice or a device sign-in. If you are in Bandung or elsewhere in Indonesia, use the same account support path and include only the details needed to identify your request.

Team online

Account request

Ask us to access, correct or explain personal data linked to your account. Include your registered phone number only through the account support path, and we may verify ownership before discussing private records.

Wallet enquiry

For a DANA, OVO, GoPay or QRIS reference, send the transaction date, amount and status shown in your cashier history. We use those details to trace the record while limiting unrelated account disclosure.

Device concern

Tell us when an unfamiliar browser or phone appears in your access history. We can review the sign-in context, help secure the account and explain which device data was used for the security check.

DATA CONTROLS

Six Privacy Policy Details We Track

Our handling process follows the same practical path you see when moving from phone verification to the lobby and cashier.

Account details

We use your phone verification and account identifiers to provide sign-in, connect your account activity and respond to a Privacy Policy request. We do not need your game choices, such as Live Roulette Turbo, to answer a basic data access enquiry.

Wallet records

A DANA, OVO, GoPay or QRIS reference can be stored with the related account event so we can check a pending status or receipt question. The record is used for the transaction context rather than unrelated messaging.

Device signals

When you sign in from a new phone or browser, we may record technical signals such as session time, browser type and network address. These signals help us detect unusual access without reading unrelated content on your device.

Cookie choices

Cookies can keep your session active and remember settings between the login page and lobby. Your browser can clear or restrict them; doing so may require another sign-in and can affect account access settings.

Security checks

We may compare phone verification, sign-in context and cashier activity before discussing private account records. This step helps prevent one person from receiving another person's data, especially when a request arrives from an unfamiliar device.

Retention and changes

We retain records only as long as needed for the stated account, security or transaction purpose and any applicable legal duty. You can contact us to request correction, access or deletion where local law permits.

Privacy Policy Questions About raja100

These Privacy Policy answers cover the account events that most often prompt a question: opening access, confirming a phone, checking a wallet reference, changing cookie settings and asking what we retain. Each answer is limited to data handling, so you can decide what to share before contacting us.

The raja100 Privacy Policy covers data collected through account opening, phone verification, sign-in, device access, cashier activity, cookies and support contact. It explains why we use each category, how we protect account records and how you can request access or correction where local law permits.

Phone verification links the account to an access step and helps us check ownership before discussing private records. We may use the verification result with sign-in signals when an unfamiliar browser appears. It is not permission to use your phone details for an unrelated purpose.

Yes. The Privacy Policy covers payment references connected to your account, including DANA and QRIS, as well as OVO and GoPay status details. We use those records to match a cashier event, investigate a receipt question or explain a pending status.

Use the account support path and state that you are making a Privacy Policy data request. Include the registered phone number through that protected route, describe the records you need, and complete any ownership check required before we disclose account-specific details.

You can contact us to request correction or deletion of personal data linked to your account. We first confirm the request belongs to you, then assess any active security or transaction need. We process the result where local law permits and explain any retained record.

The Privacy Policy mentions cookies used to maintain a sign-in session and remember settings as you move between the account page and lobby. You can restrict or clear cookies in your browser, although this may sign you out or reset selected access settings.

We may record the device type, session time and network address when access comes from a new phone or browser. If the sign-in looks unfamiliar, contact support through your account route. We can explain the security record and help protect access after ownership checks.

Related Pages

raja100 Indonesia raja100 Casino FAQ Football Goal Rush Account information