Reference

Privacy Policy for Your pasar88 Account

pasar88 Privacy Policy explains how we collect, use and protect the details connected with your account, mobile access and wallet activity.

Account dataCookie choicesWallet recordsAccess depends on local law
pasar88 Privacy Policy for Your pasar88 Account
HELP WITH YOUR DATA

Three Ways To Ask About Privacy Policy

A clear contact route matters when your account details or wallet record do not look right.

Account access If you cannot reach the account area after phone verification, use the support path…
Wallet record For a DANA, OVO, GoPay or QRIS question, include the payment rail and reference…
Policy request You can ask us to clarify a Privacy Policy point, correct an inaccurate detail…
SIX DATA CHECKS

What Privacy Policy Covers At pasar88

The practical controls behind this Privacy Policy begin when you create an account and continue while you use the mobile browser or desktop path.

Account creation

When you open an account, we handle the contact details needed for login and the phone verification step before access. Keeping these records together helps us distinguish your account from another wallet reference and gives support a clear route when access stalls.

Mobile device path

Our mobile browser path may create session and security records linked to your device or browser. These signals help us notice an unusual login, while they do not replace your password or phone verification. You can ask support to explain a device-related record.

Cookies

Cookies can remember a login session, preserve language or account-area settings and help us detect technical errors. We do not treat every cookie as the same: some support the page request, while others may be used to understand how a session behaves.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can be used to match a cashier event with your account. We use that connection to investigate status questions and avoid attaching a payment record to the wrong account.

Account security

Login details, phone verification results and device signals support account security checks. We do not ask you to share a password through support. If access looks unusual, keep your account details private and use the account contact route so we can assess the event.

Retention and changes

We retain records only for the operational, payment, security or legal reason that applies to them. You may request access, correction or clarification through support. Where a deletion request conflicts with a required transaction record, we explain that limit and the remaining retention reason.

Privacy Policy Questions Before Account Access

These Privacy Policy answers focus on the questions you may have before opening an account or checking a wallet record. We explain the data connected with login, phone verification, mobile browsing, cookies and payment references in plain language. If your question concerns a specific account, device or transaction, use the support path beside the account area and include only the details needed to locate it.

It covers account details, phone verification, login activity, device and browser signals, cookies, support requests and payment references. It also explains why we use each category, how long records may remain and how you can ask for access, correction or clarification.

We use your phone number for the account path and the phone verification step before account access. It helps us identify the correct record when login stalls. We do not ask you to send your password through support, and you can ask how the number is handled.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those references to match a cashier event with your account and investigate a status question without requesting unnecessary wallet details.

Cookies may keep a session active, remember account-area settings and help us identify technical or security errors. Device and browser signals can also support unusual-login checks. You can contact us if you want a clearer explanation of a cookie or device record.

You can contact us through the support route beside your account and ask to access or correct a record. Include the account detail that needs checking, not your password. We assess the request under applicable rules and explain any limit on changing a payment or security record.

Retention depends on the reason for holding the record, such as account support, payment matching, security checks or legal duties. We do not promise one period for every data type. Ask support about a specific record, and we will explain the relevant retention reason.

Use the contact route shown in your account area or beside the cashier path. Describe the policy point and the affected account step, device path or payment reference. Access and eligibility depends on local law, so we assess requests for Indonesia under the rules that apply.