Reference

Privacy Policy For Your raja pola Account

Our raja pola Privacy Policy explains what account, device and wallet details we use when you open access to titles such as Speed Blackjack Live or Badminton Thomas…

Account dataDevice permissionsWallet recordsPolicy requests
raja pola Privacy Policy For Your raja pola Account
REQUEST A RESPONSE

Get Privacy Policy Help Without Guesswork

A clear contact path matters when you want to change, access or question personal data.

Account support path Open the support area after signing in and state whether your request concerns account data, phone verification, device access or a payment record. We use the account path to reduce mistaken matches and may ask for a safe confirmation before discussing private details.
Wallet record request For DANA, OVO, GoPay or QRIS questions, include the transaction reference and date rather than sharing a wallet password. We can check which account record is linked to the receipt and explain what the Privacy Policy allows us to retain.
Access correction If a sign-in or phone verification detail is wrong, tell us which field needs correction through support. We may compare the request with your account record before making a change, helping keep another person from altering your private data.
DATA HANDLING PROMISES

What Our Privacy Policy Covers Daily

We apply this Privacy Policy to ordinary account activity rather than treating every data point alike.

Account details

We use the details you provide at account creation and phone verification to identify your account, support sign-in and connect your choices to the correct profile. If a name, phone detail or other account field changes, contact support so we can assess the requested correction.

Wallet and payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can help us confirm which account activity a receipt belongs to. We use these records for matching, status checks and account support, not as a reason to request your wallet password.

Device and session signals

When you sign in from a phone or browser, we may record technical signals such as session activity and device characteristics. These signals help us identify unusual access around the lobby, wallet area or phone verification step without needing access to unrelated device content.

Cookies and saved choices

Cookies or similar browser storage can remember a session choice and help the account path load correctly. You can manage browser storage through your device settings, though clearing it may require another sign-in or remove a saved preference used during your next visit.

Retention and deletion

We keep records only for the operational, security or legal purpose connected to them, and retention can differ by record type. Ask support which category applies to your request. We will explain whether a record can be removed, restricted or retained for a stated reason.

Your privacy requests

You can ask to access, correct or clarify personal data held for your account through the support path. Include the email or phone detail attached to the profile and a short description of the request; we may verify account control before sharing or changing anything.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers focus on the questions we expect you to have before account creation or when checking a wallet record. They cover the account step, device behaviour, local payment references and the support route. If your situation is not listed, contact us from the account area with the smallest amount of personal detail needed to identify your request.

The raja pola Privacy Policy covers data used for account creation, phone verification, sign-in, device sessions, lobby access, wallet status and support requests. It also explains cookies, retention, security checks and how you can ask to access or correct details connected with your account.

Phone verification helps connect the person completing the account step with the correct profile and supports sign-in protection. We use the verification detail for that account purpose and may ask you to confirm control before discussing a private record or changing an account field.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. We use a receipt reference, date or status detail to match activity with your account, while you should never send a wallet password.

We may use technical session and device signals connected with your browser or phone, such as activity needed to identify unusual access. This does not mean we need unrelated device content. You can contact support if a session signal appears unfamiliar or your sign-in path behaves unexpectedly.

Sign in and open the account support path, then name the field or record you believe is wrong. Provide the account phone or email detail needed for matching, but do not send a password or one-time code. We may verify account control before applying a correction.

You can ask support whether a particular account, device or payment record can be deleted or restricted. We assess the request by record type because some data may need to remain for security, transaction matching or a legal reason. We will explain the result and its basis.

Yes. Account access and eligibility depends on local law, including the rules that apply in your Indonesia region. This Privacy Policy explains data handling where access is available, but it does not change local requirements. Ask support if you need help locating the applicable account path.