Reference

Open par188 Privacy Policy Before Joining

par188 Privacy Policy explains what we collect when you create an account, sign in, use DANA or QRIS, and contact our support route.

Clear data purposesWallet record handlingAccount request pathLocal access wording
par188 Open par188 Privacy Policy Before Joining
ASK OUR TEAM

Browse Support Paths For Privacy Requests

A privacy question should not leave you guessing which account step comes next. We route requests through the account support path, where you can identify the account, describe the record involved and attach a payment receipt only when it helps us locate the case. For a wallet-status question from Jakarta or another Indonesian location, mention DANA, OVO, GoPay or QRIS and the relevant transaction reference. We use those details to separate a data request from a cashier-status query.

Team online

Account request

Use the signed-in account support path when asking to view, correct or remove personal details. We may ask for phone verification before discussing records, so a request reaches the right account rather than another person.

Payment record

For DANA, OVO, GoPay or QRIS questions, include the reference shown in your receipt and the approximate time. We use that narrow detail to locate the relevant payment record without asking for an unnecessary wallet password.

Access concern

If a sign-in or device check blocks your privacy request, tell us the device path you used, such as mobile browser or computer browser. We can separate an access problem from a request about stored personal data.

HANDLE YOUR DATA

Switch Through Security And Retention Details

We handle privacy as part of each account action, not as a separate message hidden after payment.

Account details

We use the name, phone details and other fields you submit to create and maintain your account. A clear account path lets us connect a privacy request to the correct profile before changing or disclosing anything.

Phone verification

Before account access or a sensitive data change, we may use phone verification to check control of the account. This step reduces the chance that a third party can request your records by using only a copied username.

Cookies

Cookies and similar browser storage can preserve a sign-in session, remember essential settings and help trace a broken page path. You can manage browser permissions, although changing them may affect sign-in or account request forms.

Wallet references

DANA, OVO, GoPay and QRIS may return a receipt number, amount status and timestamp for matching purposes. We use the reference to reconcile the account record; we do not ask for your wallet password through support.

Device security

Mobile browsers and computer browsers can provide operating-system, language, connection and device signals. These signals help us assess unusual account access and investigate a failed session without treating every device change as a policy breach.

Retention requests

To request a copy, correction, restriction or deletion of eligible data, contact the account support route with your account identifier and the request type. We may retain a limited record where security, dispute handling or legal duties require it.

Check Privacy Policy Answers Before Access

These Privacy Policy answers cover the searches we hear most often before an Indonesian account is opened. We explain the link between account access, phone verification, cookies and local wallet records without turning a privacy question into a general product description. If your situation is not listed, use the account support route with the smallest useful detail, such as the account phone number or a DANA, OVO, GoPay or QRIS reference. Access depends on local law.

The par188 Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, support messages and payment references. It explains why we use each category, how retention works and how you can request access, correction, restriction or deletion where local law permits.

We use your phone number to create or identify the account and to support phone verification before account access or a sensitive data change. This helps us avoid sending account details to the wrong person. We use the number for the stated account and security purposes.

Yes. Privacy Policy covers payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. A receipt number, status and timestamp can help us match a wallet event to your account. We do not request your wallet password through support.

Use the signed-in account support path and state that you want a copy of your personal data. Include the account identifier and complete any phone verification we request. We will assess the request under the applicable rules and explain any data that cannot be supplied.

You can ask us to correct inaccurate account details through the account support path. Tell us which field is wrong and provide the updated value or supporting context. We may verify account control first, then record the change and explain any retention requirement.

We keep personal data for the period needed to provide account access, protect sessions, reconcile a payment reference, handle a dispute or meet a legal duty. Retention depends on the record and request. Ask support which category applies instead of sending extra documents.

Yes. Privacy Policy applies when you use a mobile browser or computer browser. The device may provide language, operating-system, connection and session signals for security and troubleshooting. Cookie or browser changes can affect sign-in, but they do not remove your request path.