Reference

shopee168 Privacy Policy For Your Account

Our Privacy Policy explains how shopee168 handles the account, device and wallet details connected with your access to the lobby.

Account clarityDevice-aware accessIndonesia wallet context
shopee168 shopee168 Privacy Policy For Your Account
CONTACT ROUTES

Privacy Help Beside Your Account Path

A clear contact route helps when you need to ask about Privacy Policy records rather than a game or wallet result. Send your request through the account support path and include the sign-in detail that lets us locate the correct profile without placing sensitive data in an open message. We can explain a data category, clarify a cookie question or point you to the step for correcting account details. Access and any request outcome depends on local law.

Team online

Account request

Use the account support path to ask which personal details are linked to your profile. Include your registered contact detail and the subject of your Privacy Policy request so we can match the enquiry without asking you to repeat the full account history.

Wallet record

If your question concerns DANA, OVO, GoPay, QRIS, bank transfer or virtual account status, mention the payment rail and relevant account reference. We use that context to separate a privacy request from a cashier status question before replying.

Access question

When a new phone or browser changes your sign-in record, contact support through the same account path and describe the device change. We can explain the related security record and the next verification step without exposing another person’s account data.

DATA HANDLING

What We Keep Around Your Login

Privacy Policy choices are easier to understand when each data use has a practical reason.

Account details

When you open an account, we collect the contact and verification details needed to create that profile and help you regain access. We use the details for account administration, not as a reason to request unrelated personal records. You can ask us to correct an error.

Phone verification

A phone verification step helps connect sign-in activity with the account you are trying to access. We record the result and related security event so we can investigate an unusual login. If the number changes, use the account path to request an update.

Device signals

Your browser or mobile device may send technical signals such as session data, device type and connection details. We use them to keep a session working, identify repeated access problems and review suspicious activity. These signals are considered alongside the account record, not alone.

Cookies

Cookies can preserve a login session, remember a selected page and show whether a lobby route loads correctly. You can adjust cookie controls in your browser, although blocking some cookies may affect sign-in or the return path to your account.

Retention

We keep account, support and payment-status records for the time needed to operate the service, protect accounts, resolve disputes or meet a legal duty. When a record is no longer needed for those purposes, our process is to remove it or separate it from direct account identity.

Change requests

To ask for access, correction or deletion, contact us through the account support route and state the request clearly. We may need to confirm that you control the profile before acting. The available action and timing depend on local law and the record involved.

Privacy Policy Answers For shopee168

These Privacy Policy questions focus on the account situations you are most likely to meet while accessing shopee168 from Indonesia. We keep the answers tied to actual account steps, device records and local wallet references, so you can decide what to send when contacting us. If a rule differs by region, the applicable result depends on local law.

The shopee168 Privacy Policy covers account and phone-verification details, device and browser signals, cookies, support messages and payment-status references. It explains why we use those records, how long they may be retained and how you can request access, correction or deletion where local law permits.

Those wallet names show the types of payment-status context that may connect with your account. We may need a rail name or account reference to investigate a record linked to DANA, OVO, GoPay or QRIS, but a privacy request should not include a wallet secret or password.

A new phone or browser can create a technical security record, such as device type, session time and connection details. We use that record to help protect your account and investigate access trouble. If it was your device, contact support through the account path if you need the event explained.

Yes. Send a clear correction request through the account support route and identify the profile detail that appears wrong. We may confirm that you control the account before changing it. Whether a record can be changed, and the steps required, depends on local law.

Cookies can keep your session active, remember a page choice and help us identify whether the mobile route loads correctly. You can manage them in your browser settings. If you block required cookies, the login or return path may not work as expected until they are allowed.

We retain records for the period needed to provide account access, review security events, answer support requests, resolve disputes or meet a legal obligation. Retention differs by record type. A request through the account support path can ask which category applies to your data.

Use the account support path and state whether you want access, correction, deletion or an explanation of a data use. Include your account contact detail and relevant context, such as a device change or QRIS status question, but never send a password or wallet PIN.