Reference

Read pro88 Privacy Policy Before Opening Your Account

Your account data, wallet records and device details are handled under the pro88 Privacy Policy before you enter the casino or sportsbook areas.

Clear data categoriesWallet-linked recordsRequest paths
pro88 Read pro88 Privacy Policy Before Opening Your Account
REQUEST SUPPORT

Contact Us About Privacy Policy Requests

A privacy request should include the account phone number, the subject of your request and a safe way for us to reply. Use our support chat for a stalled login or wallet-status question, or send an account request through the contact route shown on pro88. We may ask for phone verification before changing data, because the Privacy Policy requires us to protect the account from an unauthorised request.

Team online

Support chat

Ask about a Privacy Policy request when login, DANA status or QRIS matching looks wrong. We will first confirm the account path and will not ask you to disclose a wallet PIN or one-time code.

Account request

Use the account contact route to ask for a copy, correction or deletion review. Include your registered phone number and the exact record you want us to check under the Privacy Policy.

Payment record check

If a GoPay, OVO, bank transfer or virtual account reference is attached to the wrong account, tell us the date and reference shown in your receipt for a focused data check.

DATA CONTROLS

Protect Your Data Across Account Steps

We keep the Privacy Policy practical by tying each data use to a visible account action. Phone verification supports access control, wallet references help reconcile a payment, and device signals help us…

Account opening

When you create an account, we collect the details needed to identify the account and send access messages. The Privacy Policy explains why a phone number is checked before the lobby opens.

Phone verification

A verification step helps connect the person requesting access with the account record. We keep the result and related event details so a later correction or access request can be checked safely.

Cookies and sessions

Our site may use cookies to keep a signed-in session working and to understand page errors. You can clear site data in your browser settings, though this may require another sign-in.

Device path

On a mobile browser, we can record sign-in time, browser type and device signals linked to account protection. These details help compare an unusual login with your normal access pattern.

Payment matching

DANA, OVO, GoPay and QRIS references are used to match a cashier event with your account. We use the reference and status, not your wallet PIN, to investigate a payment record.

Retention requests

We retain records only while needed for the stated account, payment, security or legal purpose. Ask support which record is held, why it remains and whether correction or removal is available.

Find Privacy Policy Answers Before Access

These Privacy Policy answers address the account steps that usually matter before access: phone verification, wallet references, cookies, device use and requests for copies or changes. Read them with the full policy text, and contact support if your account record does not match the details shown after login.

It covers account details, phone verification, login events, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps us confirm that an access request belongs to the account holder. We record the verification result and related event, but support will not ask for your one-time code.

No. The Privacy Policy distinguishes payment references and status records from private wallet credentials. We use a reference to reconcile the account event and do not ask you to provide a PIN.

Yes. Send an account request with your registered phone number and describe the records you want. We may verify your identity first, then explain what can be supplied under the Privacy Policy.

Contact support chat or the account request route with the incorrect field and the correction you seek. We may request evidence linked to the account before changing phone, payment or access records.

Cookies can keep your session active and help identify page errors. Clearing them through your mobile browser removes the local session record, so you may need phone verification at the next sign-in.

Some access and processing choices depend on local law. Where local law permits, we apply the stated account and data controls; contact us if a regional restriction affects your request.