Reference

Privacy Policy For Your shopee168 Account

shopee168 Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between casino, slot, and sports pages.

Account dataCookie choicesWallet recordsSecure access
Explore Our Lobby Read FAQ
shopee168 Privacy Policy For Your shopee168 Account
CONTACT ROUTES

Get Privacy Help Beside Account Support

A privacy question should not require you to search through the lobby. We keep the account support route close to the login and cashier areas so you can ask about a stored detail, cookie choice, phone verification record, or wallet reference without sending sensitive material through an unrelated channel. If you are in Bandung or elsewhere in Indonesia, use the contact option displayed in your signed-in account and include the email or phone tied to your profile. We will use that match to locate the right request.

Team online

Account contact

Open the support contact shown after login and state that your request concerns the Privacy Policy. Include your account identifier, preferred reply route, and the type of record involved; do not send your password, wallet PIN, or one-time verification code.

Wallet record check

For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account question, attach only the payment reference and date after removing unrelated account details. We can compare that reference with the stored status without asking you to disclose your wallet password.

Login privacy request

If a phone verification record or device session looks unfamiliar, tell us through the account support path and change your password from the security area. We can review the sign-in context while keeping your verification code private and unavailable to support staff.

HANDLING DETAILS

Six Practical Rules Behind Our Privacy Policy

We keep this policy practical: each record has a reason tied to account access, payment reconciliation, safety checks, or support.

Account records

We may hold your name or chosen account details, phone verification result, login history, and support messages because these records help us identify your profile and respond to account requests. We use the minimum account context needed to handle the specific question you send.

Payment references

A wallet or bank reference can be stored with its status, amount context, and time so a receipt can be matched to the correct account. DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri, and BNI details are handled as transaction references rather than wallet passwords.

Cookies and sessions

Cookies help remember a signed-in session, language setting, security state, and selected page. You can clear or restrict cookies in your browser settings, though doing so may require another login or interrupt the route from phone verification to the lobby.

Device security

We may record browser type, device signals, approximate session timing, and sign-in events to spot unusual account access. We do not need your phone contents to protect the account, and support will not ask for your password, wallet PIN, or one-time code.

Retention choices

We retain account, payment, and support records only for the operational or legal period that applies to them. A deletion or restriction request may be limited where a record is needed to resolve a dispute, prevent misuse, or meet a valid local requirement.

Requesting changes

You can ask us to correct an account detail, explain a stored record, or request removal through the signed-in support route. Tell us which field is wrong and use the phone or email connected to your account so we can verify the request safely.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account questions we expect before registration or a wallet request. They cover what shopee168 records, how cookies work on a mobile browser, how payment references are handled, and how you can ask for a correction or removal. If your situation is different, use the account support path and describe the exact record involved.

The shopee168 Privacy Policy covers account creation, phone verification, login activity, browser cookies, device signals, support messages, game-page activity, and payment references. It explains why we use each category and how you can ask about, correct, restrict, or remove a record where applicable.

No. Our Privacy Policy distinguishes wallet credentials from transaction references. When you use DANA, OVO, GoPay, or QRIS, we may receive a status, time, and reference for reconciliation, but support does not need your wallet password, PIN, or one-time code.

Device and browser signals help us recognise a familiar session and investigate unusual login activity. A mobile browser opening Fishing War Mobile Play may create a session record, such as browser type and timing, without giving us access to your photos, messages, or other phone content.

Use the support contact shown inside your signed-in account and identify the field that needs correction. Send the phone number or email connected to your profile, but never send a password or verification code. We may verify ownership before changing the record.

You can submit a removal request through the account support path. Our Privacy Policy allows us to assess the request against retention duties, unresolved payment questions, security needs, or local requirements. We will explain if a particular record must remain and why.

Cookies can keep your login state, security setting, and selected route available while you move between pages. You can clear or restrict them through your mobile browser controls. After that change, you may need to complete phone verification again before account access.

Yes. Account eligibility and access depend on local law, and our Privacy Policy is applied where local law permits. If you need a jurisdiction-specific explanation, contact us from the account support route and state your country or region without sending unnecessary personal details.

Related Pages

shopee168 Indonesia Basketball IBL Bet Indonesia QRIS Help 514 About Us Live Baccarat Turbo