Reference

premier88 Privacy Policy, Clearly Explained

premier88 Privacy Policy explains what we collect during phone verification, how device data supports account access, and how wallet references from DANA or QRIS are handled.

Account dataDevice cookiesWallet referencesYour access rights
premier88.club page image
REQUEST HELP DIRECTLY

Help With Privacy Requests And Access

A clear support path helps when your account record, device session, or wallet status needs attention. Sign in first when possible so we can match the request to your account; if sign-in stalls, include the phone number used for verification without sending a wallet PIN. We use the same support route for access questions, correction requests, and receipt-status checks.

Team online

Account data request

Open the support path from your account and state whether you want access, correction, or deletion details. We may ask for phone verification before discussing private account records.

Wallet reference check

For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account questions, send the transaction reference and date. Do not include a wallet PIN or full security credential.

Device access issue

If a phone or browser session no longer opens your account, tell us the device type and approximate sign-in time. This gives our support team a safer starting point.

SIX DATA PRACTICES

Six Ways We Handle Account Data

Privacy choices matter most when they match the steps you actually take. We connect account records to phone verification, device sessions, and payment references so support can identify the right request without…

Account details

We use the details submitted during account opening and phone verification to create, identify, and maintain your account record. Please keep your contact details current so requests reach the right account.

Cookies and sessions

Cookies and session signals help remember sign-in state, detect unusual device behaviour, and keep the account path working across mobile browsers and desktop browsers.

Access protection

Phone verification, sign-in records, and device signals help us investigate an account access concern. We will not ask you to post a wallet PIN in a support request.

Retention periods

We keep records for the period needed to provide account support, trace a transaction reference, resolve a dispute, or meet applicable legal duties. Some records may remain after closure.

Who to contact

Use our support path for questions about the Privacy Policy, stored account details, cookies, phone verification, or a DANA, OVO, GoPay, or QRIS reference.

Changes to records

Where local law permits, you can request access or correction by identifying your account and describing the exact field or record. We may verify ownership before making a change.

Privacy Policy Questions From Indonesian Accounts

These answers address the Privacy Policy questions we expect you to ask before opening or using an account. They cover the records created by phone verification, mobile browsing, wallet references, cookies, retention, and requests sent through our support path. If your situation is not listed, contact us with the smallest amount of account detail needed to identify your request.

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

Our account support route should not receive your wallet PIN. We may handle a payment reference, amount status, or date to match a transaction, but keep private wallet credentials out of messages.

Phone verification helps connect an account request to the correct account holder and supports access checks when a sign-in or device session looks unusual. Account access depends on local law.

Use the support path while signed in when possible, identify the phone number connected to your account, and ask for access to your records. We may verify ownership before responding.

Yes, where local law permits. Send the field that needs correction and the accurate replacement through support. We may request phone verification so a change is not applied to another account.

Retention varies by record type and purpose. Account, support, device, and transaction references may remain while needed for access support, dispute handling, security checks, or applicable legal duties.

Cookies and session signals can affect sign-in continuity on a mobile browser. Clearing them may require another login or phone check; our support path can help identify a session issue.