Reference

Open panglima4d Privacy Policy Clearly

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

Account collectionWallet recordsCookie choicesAccess requests
panglima4d Open panglima4d Privacy Policy Clearly
ASK ABOUT RECORDS

Contact Us About Privacy Requests

You can ask us about a Privacy Policy point without guessing which account route to use.

Account privacy request Use the support route shown after account access and state whether your request concerns…
Payment data question For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, include the payment…
Correction or removal Tell us which personal detail is inaccurate or which record you want reviewed under…
DATA HANDLING PATH

Explore Six Privacy Controls

We keep this policy practical by describing the data path behind common account actions. A mobile sign-in through Chrome or Safari can create device and security records, while a move from login…

Data we receive

We may receive your registration details, phone verification result, sign-in time, device signals, session activity and payment references. If you browse VIP Baccarat, rocket168 or bingo4s, the related account session can help us connect your request to the correct record.

Cookies and devices

Cookies and similar device data can keep a sign-in session working, remember selected settings and help identify unusual access. You can manage browser cookie controls on your phone or desktop, although changing them may affect the account path.

Account protection

Phone verification is an account step before access, and we use sign-in and device signals to investigate activity that does not match your normal pattern. Never send us a wallet password; support may request limited account details instead.

Payment matching

A DANA, OVO, GoPay or QRIS reference helps us match a payment status to your account. Bank transfer and virtual account records are handled for reconciliation, receipt checks and support questions about the transaction.

Retention choices

We retain records for the period needed to provide account support, resolve payment questions, protect access and meet applicable requirements. When a record is no longer needed for those purposes, our handling follows the deletion or archival process that applies.

Changes and access

Ask us for a copy, correction or clarification through the account support path. Include the registered phone or email and the specific data category, such as cookies, device activity or a QRIS reference, so we can handle the request accurately.

Check Common Privacy Policy Answers

These Privacy Policy answers address the searches we hear before an account is opened or a wallet is connected. They explain the practical data steps behind access, payments, cookies and support without asking you to interpret technical wording. If your question is not listed, use the account privacy route and identify the record involved.

The panglima4d Privacy Policy covers registration details, phone verification, device and sign-in activity, cookies, account sessions, payment references and support messages. It also explains why we use each category, how you can request access or correction, and when local law affects availability.

We use your phone number for the account access step and phone verification, helping connect you to the correct account and identify unusual sign-in activity. We may use the registered detail when handling a Privacy Policy request, but you should not send a wallet password.

Yes. The Privacy Policy covers payment references and status details connected with DANA, OVO, GoPay and QRIS. Bank transfer and virtual account records are also included when they support reconciliation, receipt checks or a question about the payment attached to your account.

You can request access through the account support path and name the categories you want, such as registration details, device activity, cookie settings or payment references. We may confirm your registered phone or email before sharing account-related data, where local law permits.

Send a correction request through the privacy support route, identify the inaccurate field and provide the registered account detail used to locate it. We can explain the next account step and whether a payment or security record must remain unchanged for a stated purpose.

We keep account, security, payment and support records only for the period needed for account access, payment questions, security checks and applicable requirements. The exact period can differ by record type, and we follow the relevant deletion or archival process afterward.

Yes. Your Chrome or Safari settings let you manage cookies and similar storage on a phone or desktop. Some changes may interrupt the login-to-lobby path or remove saved preferences. Our Privacy Policy explains the purposes so you can choose settings with context.