Reference

shop888 Privacy Policy for Your Account

The shop888 Privacy Policy explains how we handle your account details, wallet records and device activity when you use our site.

Account data explainedWallet records coveredPolicy contact path
shop888 shop888 Privacy Policy for Your Account
POLICY HELP DESK

Where to Ask About Privacy

A clear contact route matters when you want to understand a record or change a detail. Our support path is available through the account area, with policy questions kept separate from game or wallet troubleshooting. Include the phone number or email attached to your account, but do not send a password or one-time code. We can then locate the relevant request, explain the next account step and direct payment-record questions to the right team.

Team online

Account contact route

Open the support path from your signed-in account when you need to ask about a Privacy Policy request, stored contact detail or phone verification record. We use the account context to reduce mistaken identity before discussing personal data.

Wallet record query

If a DANA, OVO, GoPay or QRIS record looks unfamiliar, send the payment date, amount reference and account contact through support. We can check the matching transaction trail without asking you to share your wallet password.

Policy change request

To request a correction, access copy or eligible removal, state the exact data concern and the account email or phone number. We may ask for an account step that confirms the request is really from you.

DATA HANDLING

What We Do With Your Details

We keep the Privacy Policy practical by linking each data use to a visible account action.

Account details

We collect details you enter during account opening and phone verification so we can identify the account connected to a request. If a detail changes, contact us from the account route and tell us which field needs checking.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may appear in account records when you use those routes. We use the references to reconcile status and answer a receipt question, not to request your wallet password.

Cookies and sessions

Cookies can keep a signed-in session working and remember basic site choices on your browser. You can clear them through your browser settings, although doing so may require the phone verification step again before account access.

Device security

Our records may include browser, device and sign-in event details used to spot unusual access. If you move from a mobile browser to desktop, a fresh verification request can protect the account before the lobby opens.

Retention approach

We retain account, payment and support records only for the period needed for the stated purpose, account security or a legal requirement. When a record is no longer needed, our handling follows the retention rules described in this Privacy Policy.

Your requests

You can ask what personal data we hold, request a correction, or ask whether removal is available under applicable rules. Send the request through account support with enough detail for us to identify the record and respond safely.

Privacy Policy Questions for shop888

These answers focus on the questions you may have before opening an account or checking a wallet record. The Privacy Policy applies to the account journey, from phone verification through mobile browsing and payment matching. If your situation is not covered here, use the account support route and describe the specific data concern. Access remains where local law permits.

It covers account details, phone verification, device and session records, cookies, payment references, support messages, retention and requests about your data. It also explains why we use each category and how you can contact us about access, correction or eligible removal.

Yes. When you use DANA or QRIS, we may retain references needed to match the account, check payment status and answer a receipt question. The same approach applies to OVO, GoPay, bank transfer and virtual account records.

Use the support path inside your signed-in account and state that you want to request your personal data. Include the account phone number or email, but never send a password or one-time code. We may use phone verification to confirm the request.

Yes. Tell us which account detail is wrong and what it should say through the account support route. We may ask for an account confirmation step before making a change, particularly when the request affects phone verification or wallet matching.

Cookies help maintain a signed-in session and remember basic browser choices. They can also support security checks when your access changes from mobile to desktop. Clearing cookies is possible in your browser, but you may need to verify your phone again.

We keep records for the period needed for the stated account, security, support or legal purpose. The exact handling depends on the record type and applicable rules. Our Privacy Policy describes the retention approach, and support can clarify a specific request.

Yes. Account access and related data processing depends on local law, and you should use the site only where local law permits. If you are unsure about your position, check the rules that apply to you before opening an account.