Reference

Privacy Policy For Your Account

pragmatic168 Privacy Policy explains what we collect when you open an account, sign in from a mobile device, use DANA or QRIS, and contact support.

Clear data purposesWallet record handlingAccount access controlsCookie choices
Browse Our Lobby Read FAQ
pragmatic168 Privacy Policy For Your Account
REQUEST HELP

Contact Us About Privacy Questions

A clear contact route matters when you want to ask what we hold, correct an account detail, or question a device record. We handle Privacy Policy requests through the support path linked from the sign-in and account areas, so you can identify the account concerned without sending sensitive details through an unrelated channel. For a faster response, include your account phone number, the request type, and any relevant payment reference. We may ask you to confirm ownership before changing or disclosing account data.

Team online

Account support path

Open the support route from your pragmatic168 sign-in or account area and select a Privacy Policy request. We use the account details already connected to your request to reduce confusion about which record you want us to check.

Wallet record query

If your question concerns DANA, OVO, GoPay, QRIS, or a bank transfer reference, include the relevant transaction identifier rather than a full wallet password. We compare the reference with our account record and explain what we can access.

Access correction

For a phone number, email, device, or account detail that needs correction, tell us what appears wrong and what should replace it. We may request phone verification before applying a change to protect your account.

DATA PRACTICES

Explore How We Handle Your Details

Privacy is part of the account flow, not a separate promise hidden away from the lobby.

Account information

When you open an account, we may collect your name, phone number, email address, verification status, and sign-in details. These records help us connect your account activity with the correct person and let support answer an account-specific request.

Device and browser signals

A mobile or desktop sign-in can provide device type, browser details, IP address, session time, and security events. We use these signals to identify unusual access and protect the account, not to replace the account information you provide.

Cookies and choices

Cookies or similar tools can remember a session, keep security controls working, and show whether a policy choice has been made. You can adjust browser settings, although removing necessary cookies may affect sign-in or the path to your lobby.

Wallet and payment records

DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity can leave references such as amount, status, time, and matching account details. We use the references available to us for reconciliation, security checks, and support responses.

Retention and deletion

We retain information while it supports your account, security checks, unresolved disputes, transaction reconciliation, or applicable legal duties. When a record is no longer needed for those purposes, we remove it, anonymise it, or restrict access according to our internal process.

Your data request

You can ask what personal data we hold, request a correction, ask about processing, or raise a deletion request where local law permits. Send the request through account support; we verify identity first and explain any limit that applies.

Browse Privacy Policy Answers

These Privacy Policy answers address the questions we expect before an Indonesian account is opened or used from a phone. They cover account records, wallet references, cookies, access requests, and the practical support path. If your situation is not listed, contact us through the account support route and include enough detail for us to locate the correct record. We will handle the request according to the policy and where local law permits.

It covers information linked to your account and visits, including contact details, phone verification, sign-in events, device signals, cookies, support messages, and payment references. It also explains purposes, retention, security handling, your request options, and the limits that can depend on local law.

Phone verification helps us connect account access to the correct person, reduce mistaken account changes, and protect wallet-related records. If you ask us to change a phone number or disclose account data, we may use verification before completing the request.

We may receive a reference, status, time, amount, and account-matching details for a DANA or QRIS action. We do not need your wallet password for that reconciliation. The payment provider may hold additional data under its own privacy terms.

Yes. A phone or desktop session can create records such as device type, browser, IP address, session time, and security events. We use these details to help detect unusual access and keep your account secure, while cookies may support sign-in continuity.

Use the support route linked from your pragmatic168 account or sign-in area and state whether you want access, correction, processing details, or deletion where local law permits. Include your account phone number, then complete any ownership check we request.

We keep records for as long as they support account administration, security, payment reconciliation, disputes, or legal duties. Once a record is no longer needed, we remove it, anonymise it, or restrict access under our internal retention process.

You can adjust available cookie choices through your browser or the relevant preference control. Some necessary tools support sign-in and security, so removing them may affect account access. For other processing questions, contact support and we will explain the available option.

Related Pages

pragmatic168 Indonesia pragmatic168 Casino About Us FAQ Account information