Reference

Open pragmatic168 with clear Legal terms

pragmatic168 Legal terms explain how account access, wallet activity and personal data are handled before you enter the lobby.

Account termsPrivacy controlsLocal-law accessWallet records
pragmatic168 Open pragmatic168 with clear Legal terms
CONTACT ROUTES

Find Legal help beside your account

A clear contact route helps you resolve a Legal question without guessing which team handles it. From the account area, send the relevant issue with your registered phone details, payment receipt or access message. We use that context to separate an account question from a wallet-status question, while access remains subject to local law.

Team online

Account access

If phone verification or account entry stops, use the support path connected to your account. Include the registered number and the exact message shown, so we can assess the Legal and identity steps without asking you to repeat the full history.

Payment record

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, attach the receipt reference and payment date through the account contact route. We can then check whether the transaction belongs to your account and whether a policy check is pending.

Policy request

When you need a clause clarified or want to request a correction to your account data, state the Legal topic directly in your message. We will use the registered account details to identify the request and explain the next available step.

DATA PRACTICE

Explore how Legal records are handled

Legal handling is practical: we collect the details needed for account access, phone verification, payment matching and support replies.

Account data

We use your registered phone details and account identifiers to connect access requests with the correct record. Keeping those details accurate helps us handle Legal questions, payment matching and requests to change personal data.

Cookies

Cookies help keep your signed-in session connected to the correct policy and account pages. You can review browser cookie controls on your device, though changing them may affect account access or require another phone verification step.

Device checks

A new phone or browser may trigger an account-security check before the lobby opens. This step is part of our Legal access process; do not share verification codes, and contact support if the device is not yours.

Payment matching

We compare the account identity with DANA, OVO, GoPay, QRIS, bank transfer or virtual account records when a wallet event needs checking. A mismatch can delay a decision while we confirm the source and account details.

Retention period

Account, payment and support records remain available for the period required to operate services, settle disputes and meet applicable Legal duties. If you ask about retention, include your registered phone details so we can locate the right record.

Change request

To request a correction, write from the account contact route and identify the field that needs changing. We may ask for a phone verification step before applying an update, because Legal records must stay connected to the correct account holder.

Browse answers about Legal access

These Legal answers cover the questions we expect before an account is opened or a wallet is connected. The wording is written for Indonesian account holders, including anyone checking access from Bandung or using a mobile browser. If your situation is different, use the registered account contact route and include the policy point you need clarified.

Legal covers account creation, phone verification, permitted access, privacy, cookies, payment matching, data retention and support requests. It also explains when we may pause an account check. Access depends on local law, so read the current terms before continuing.

Access is available only where local law permits and where your account meets the current policy conditions. Your location, account details and verification status can affect access. Check the Legal notice before opening an account or connecting DANA, OVO, GoPay or QRIS.

Phone verification links the account to a contact detail you control and helps us handle access requests, data changes and payment checks. If the code does not arrive, use the account support route and provide the registered number rather than creating another account.

We use payment references to match DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity with the correct account. If the source or account details do not match, we may pause the check and ask for a receipt or clarification.

Yes. Send a request through the registered account contact route, identify the data field and explain the correction needed. We may complete a phone verification step before changing the record, so the request remains connected to the correct account.

Cookies help maintain your signed-in session and display the relevant account and policy pages. Browser settings can remove or restrict them, but that may interrupt access or require another verification step. Your browser controls determine which cookies remain on your device.

Use the support route shown inside your account and name the Legal issue in the first line. Add your registered phone details, payment reference or access message where relevant. We can then direct the request to the correct policy or account check.