Reference

pragmatic demo Privacy Policy For Indonesia

Our Privacy Policy explains how pragmatic demo collects, uses and protects the details connected with your account, wallet activity and device access.

Clear data purposesWallet record contextAccount contact pathCookie choices
Browse the lobby Read FAQ
pragmatic demo pragmatic demo Privacy Policy For Indonesia
CONTACT ROUTES

Where Privacy Questions Reach Us

A privacy question should not get lost inside a payment query, so we separate the request from ordinary lobby assistance. Use the support channel linked from your account when you need to ask about stored details, a wallet reference or a correction. Include the phone number or account identifier connected with your request, but do not send a password or full payment credential. We may ask for an account step to confirm that the request comes from you before discussing personal data.

Team online

Account support

Open the support route after signing in and select the privacy subject. We use your account identifier and verified phone path to locate the relevant record without asking you to paste a password into a message.

Payment record help

For a DANA, OVO, GoPay or QRIS question, send the transaction reference and date shown in your receipt. We use that narrow detail to check matching records while avoiding unnecessary wallet credentials.

Correction request

Tell us which account detail needs changing and why it is inaccurate. We may request phone verification before making an amendment, then use the same support route to confirm the request status.

DATA PRACTICES

Six Practical Privacy Safeguards

Privacy work is part of the account path rather than a separate promise. We limit collection to details needed for access, payment matching, security and support, and we use account controls to…

Account details

We handle the details you provide during account creation, including your contact route and phone verification status. Those details help us connect your sign-in with the correct account and answer a privacy request accurately.

Wallet references

DANA, OVO, GoPay and QRIS references are used to reconcile an account transaction or check a receipt status. We do not need your wallet password to investigate a payment record submitted through support.

Cookies

Cookies may keep a session active, remember a selected setting or help us understand whether a sign-in request is unusual. You can manage browser cookie controls, although changing them may affect account access.

Device security

Browser type, device signals and sign-in timing can help us spot activity that differs from your usual account path. If a check is needed, we use the verified phone route before discussing protected details.

Retention

We keep personal records for the period needed to operate the account, resolve payment questions, protect the service and meet applicable legal duties. When a record is no longer needed, our handling follows the applicable retention process.

Your requests

You can contact us to ask about access, correction or the handling of your personal data. Include enough account context for us to find the record, and expect an identity check before private details are disclosed.

Privacy Policy Answers For Your Account

These answers focus on the questions you may have before opening an account with pragmatic demo in Indonesia. They explain how our Privacy Policy relates to phone verification, wallet records, cookies, devices and requests for changes. If your situation depends on a local rule, access depends on local law, and our support route can clarify the policy path where local law permits.

It covers personal data connected with your account, phone verification, sign-in activity, device signals, cookies, support messages and payment references. It also explains our purposes for using those details, retention approach, security checks and the route for asking about access or correction.

DANA and QRIS references can appear in account records when you make or check a transaction. We use the reference, date and status to match the correct account or investigate a receipt question. We do not ask for your wallet password through support.

Yes. The policy covers references connected with OVO, GoPay, bank transfer and virtual account activity when those details are used to reconcile an account record. We handle the smallest practical set of payment details needed for matching, security and support.

We use your phone number for account contact, the clear verification step before account access and selected security checks. If you ask about personal data, we may use the verified phone route to confirm that the request belongs to you before sharing account details.

You can contact support and identify the account detail you believe is inaccurate. Include your account identifier and a short explanation, without sending a password. We may verify your phone first, then assess the record and confirm the correction path where local law permits.

Cookies and device signals may help maintain your session and identify unusual sign-in behaviour on a mobile browser. Your browser controls can remove or restrict cookies. If you do so, some account steps may ask you to verify again before access continues.

Sign in and use the support route linked to your account, choosing the privacy subject. For a wallet matter, include the receipt reference and date; for a data request, describe the record involved. Do not send passwords or complete wallet credentials.

Related Pages

pragmatic demo Indonesia FAQ iboaport indoviabola pragmatic demo Casino