Reference

senopati 2 Privacy Policy For Your Account

Our Privacy Policy explains how senopati 2 handles the details connected with your account, from phone verification to wallet status when you open Live Roulette or Royal Fishing.

Account dataWallet detailsCookie choicesSecurity steps
senopati 2 senopati 2 Privacy Policy For Your Account
HELP WITH YOUR DATA

Get Policy Help Beside Your Account Path

A clear contact route matters when a Privacy Policy question involves your login or wallet record. Use the account help path beside the cashier area and describe the specific item you want checked, such as a QRIS reference, a phone verification record or a device entry. We can then match your request to the relevant account details without asking you to resend unrelated data.

Team online

Account questions

Ask through the account help path when you need to understand which details are connected with your login, phone verification or device record. Include the account identifier shown to you, and we will use that context to locate the relevant Privacy Policy explanation.

Wallet records

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account references, mention the payment rail and the date shown in your account. This gives our support team a focused route to explain the stored status without requesting a full wallet history.

Change requests

If a profile detail is inaccurate or you want clarification about retention, send the request through the same support route. We may ask for an account step or phone check before discussing private records, so the response reaches the right account holder.

ACCOUNT DATA PRACTICE

What Our Privacy Policy Explains

Our handling process follows the account actions you take rather than treating every device visit alike.

Collected details

We may record your account name, phone verification result, sign-in events, device signals and selected wallet status. These details help connect a request to the correct account when you move from login toward the lobby or check a payment reference.

Cookie controls

Cookies can keep a session available, remember a display choice or support account protection. Your browser settings provide the practical control point. Clearing them may require another sign-in, but it does not erase every account record held for security or legal needs.

Security checks

Phone verification before account access gives us a direct account step to compare during support requests. We also examine sign-in and device signals for unusual patterns, helping us protect records linked with Live Roulette, rocketpot or other account activity.

Retention timing

We keep each category only while it serves an explained account, payment reconciliation, security or legal purpose. A QRIS status reference and a cookie setting do not need the same period, so retention depends on the record type and its purpose.

Your requests

You can ask what data we hold, request a correction, seek an explanation of use, or ask about deletion where applicable. Send one clear request through account help and include enough detail for us to identify the record without exposing another person’s data.

Policy contact

Questions about this Privacy Policy belong with our account support route, including questions about device records, cookies, wallet references or access history. We may complete an account check before sharing private details, which keeps the response tied to your own profile.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers focus on the account questions you are most likely to ask before opening an account or checking an existing record. We cover local wallet references, browser cookies, phone verification, device data, correction requests and the access wording used for Indonesian accounts. If your situation is not listed, use the account help route and describe the exact record or policy point you need us to check.

The Privacy Policy covers data connected with your account, including phone verification, sign-in activity, device signals, cookies, wallet status and payment references. It also explains why we use those details for account access, security, reconciliation and support, plus how you can ask about correction or retention.

Yes. The Privacy Policy includes references created when you use DANA, OVO, GoPay or QRIS through your account path. We may use a rail name, status and transaction reference to match a request or explain a cashier record, without needing unrelated wallet details.

Phone verification is an account security step before access. It helps us connect a sign-in or support request with the correct profile and reduces the chance of private records being discussed with someone else. The Privacy Policy explains how that verification result is handled and retained.

Use the account help route and identify the record you believe is inaccurate, such as a phone detail, device entry or wallet status. We may ask for an account check before making changes. This protects your profile while giving us a clear request to investigate.

You can manage cookies through your browser controls on the device you use for account access. Cookies may support a secure session or remember a setting, so clearing them can require another sign-in. The Privacy Policy separates cookie controls from account records kept for security or legal needs.

The Privacy Policy links retention to the reason a record exists. A sign-in event, QRIS reference, support message and cookie setting may follow different periods because they serve different purposes. We keep records for account, security, reconciliation or legal needs and reassess them afterward.

Use the account support path for questions about your profile, device record or policy wording. Access and eligibility depends on local law, so our response can explain the data process without replacing local requirements. We will ask for only the account details needed to address your request.