Reference

Open the raja132situs Privacy Policy

The raja132situs Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or use DANA, OVO, GoPay and QRIS.

Account clarityWallet recordsCookie choicesContact path
Explore Our Lobby Read FAQ
raja132situs Open the raja132situs Privacy Policy
REQUEST HELP

Browse Your Privacy Contact Routes

A clear contact route helps when you want to question a data record, change account details or understand a wallet reference. Start inside your signed-in account so we can connect the request to the correct profile. If you cannot sign in, include only the details needed to locate the account and never send a wallet password or full payment credential.

Team online

Account request

Use the account support path to ask for a copy, correction or explanation of personal data held for your raja132situs profile. We may ask you to complete phone verification before discussing account-specific records, which helps prevent another person from receiving your details.

Wallet question

For a DANA, OVO, GoPay or QRIS privacy question, attach the payment reference and date rather than secret wallet credentials. We can use that reference to locate the status record, while keeping the request focused on the transaction data connected with your account.

Sign-in support

If your phone or browser no longer opens the account page, contact us through the available account support route and describe the device path. We use the minimum details needed to check the sign-in event, and we do not ask you to disclose your password.

DATA CONTROL

Switch Through Your Privacy Choices

Privacy controls are easier to use when each request has a defined account step. We separate identity checks, payment references, device signals and cookie settings so a request can be handled without…

Collection purpose

We collect registration and phone details to create and protect your account, then use sign-in and device signals to identify unusual access. Game activity, such as opening Live Baccarat Diamond, is connected to account records only where needed for security, service operation or a request you make.

Cookie control

Cookies can keep your session active and preserve settings between pages on your phone or desktop browser. You can adjust cookie controls in the browser or device settings. Disabling some storage may require you to sign in again or repeat an account step.

Payment separation

Our records identify the payment rail, amount reference and status for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We use these fields to reconcile an action, not to request your wallet PIN, banking password or one-time security code.

Account security

Phone verification can be required before we disclose account-specific data or change important profile details. Keep your sign-in details private and sign out on shared devices. If a phone is lost, tell support promptly so we can focus the security check on that account event.

Retention approach

We keep personal and transaction records only as long as they support account security, dispute handling, operational reconciliation or a legal requirement that applies where you are located. When a record no longer serves one of those purposes, it can be removed, anonymised or restricted.

Change requests

You can ask us to correct inaccurate profile data, explain a processing purpose or remove eligible details through account support. Include the account phone number and a short description, but omit passwords and wallet secrets. We may verify ownership before completing the requested change.

Browse Privacy Policy Answers

These Privacy Policy answers address the questions we expect before an Indonesian account is opened. They cover the records created by sign-in, mobile browsing and local wallet activity, plus the steps available when you want to ask about your data.

It covers account details, phone verification, cookies, device and sign-in records, game access records, and payment references. It also explains how we handle requests to correct, explain or remove eligible data, with access depending on local law and applicable record-keeping duties.

We use your phone number to create an account, send account-related status messages where enabled and verify ownership before discussing sensitive profile details. If you request a correction or deletion, phone verification helps us avoid changing or disclosing data to the wrong person.

No. For DANA, OVO, GoPay and QRIS, we record the payment reference and status needed to match an account action. We do not need your wallet password, PIN or one-time security code. Never include those secrets in a support request.

Cookies and similar storage help keep your session active, remember selected settings and identify unusual sign-in patterns. You can change cookie permissions in your browser or device settings. Restricting them may sign you out or require repeated verification when you return.

Yes. Send a correction request through the signed-in account support path, identify the inaccurate field and provide the replacement detail. We may verify your phone before acting. Requests are assessed under the Privacy Policy and the rules that apply where local law permits access.

We retain payment references for as long as they are needed for account security, transaction matching, dispute handling or a legal requirement. The period can differ by record type and jurisdiction. Ask support for the purpose and status of a specific DANA, QRIS or bank record.

Sign in and use the account support route, then state whether you want access, correction, an explanation or removal of eligible data. If sign-in fails, describe the device issue without sending a password. We may request ownership verification before sharing account-specific information.

Related Pages

raja132situs Indonesia Krakatau Blast Reels Account information About Us Live Baccarat Diamond