Reference

Privacy Policy for live slot 168

Our Privacy Policy explains what live slot 168 collects when you open an account, use DANA or QRIS, and move between the mobile lobby and cashier.

Clear data purposesWallet detail handlingAccount access choicesPolicy request path
live slot 168 Privacy Policy for live slot 168
CONTACT ROUTES

Privacy help beside your account path

A direct support path helps when a Privacy Policy question appears during login, phone verification or a wallet status check. Keep the account phone number and payment reference ready, but do not send a password or wallet PIN. We use the details you provide to locate the relevant record, explain the handling step and identify any correction needed. Your request remains tied to the policy issue you raise.

Team online

Account data request

Ask support to identify the account details linked to your phone verification step. We can explain the purpose of a field, confirm whether it is required for account access and point you to the next Privacy Policy request step.

Wallet record query

If a DANA, OVO, GoPay or QRIS reference appears unclear, share the reference without your PIN. We use it to trace the matching account event, explain the status record and keep the request focused on payment data handling.

Correction request

When your account detail is incorrect, tell us which field needs attention and why. Support can review the request against your verified account path, ask for a suitable confirmation and explain when the corrected record will appear.

DATA PRACTICE

Six privacy details we keep clear

We keep this policy practical by describing the data actions that occur around your account rather than using broad promises.

Account creation

When you open an account, we collect the details needed to create your profile and begin phone verification. We do not treat every screen visit as a request for full identity data; the field shown should match the purpose explained at that step.

Phone verification

Your phone number helps connect the verification result to the correct account. If access is paused, support may use that same account path to check the event. Do not share one-time codes outside the verification screen or support request.

Wallet matching

DANA, OVO, GoPay and QRIS can create a payment reference linked to your account activity. We use that reference to check a cashier status or resolve a receipt question, while your wallet PIN stays with the wallet provider.

Cookies and devices

Cookies and device records can preserve a session, remember a language choice or help us detect an unusual sign-in. You can manage browser cookie settings on your device, although removing them may require you to repeat the login path.

Retention period

We keep account, payment-reference and support records only as long as needed for account administration, security review, dispute handling or legal duties. A retention question can be raised through support with the specific record or account step you mean.

Policy changes

If this Privacy Policy changes in a way that affects your account data, we will present the revised wording through the policy area. Check the page before using a new account or cashier step so you can see the current handling terms.

Privacy Policy answers for your account

These Privacy Policy answers address the questions you may have before opening an account on live slot 168. They cover the data connected with phone verification, mobile access, local wallets and correction requests. If your situation is not listed, use the support path with the account step, device path or payment reference involved. We will keep the response focused on the policy and the record you are asking about.

It covers account creation, phone verification, mobile and browser sessions, cookies, device records, support requests and payment references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It explains why each record is used, retained and reviewed.

We use your phone number to connect the verification result with your account and help investigate access issues. It can also help support locate the correct account record. We do not ask you to send a verification code or wallet PIN in a support message.

Yes. The Privacy Policy covers payment references and status records connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account steps. We use those references to match an account event or receipt question, not to obtain your private wallet PIN.

Contact the support path and state the account field that is incorrect, such as a phone detail or profile entry. Include enough account context for us to locate the record, but exclude passwords, one-time codes and wallet PINs. We will explain the confirmation needed.

You can ask support to explain the account, verification, device or payment-reference records connected with your profile. Describe the relevant step, such as QRIS status or mobile login, so we can narrow the request and respond according to local requirements.

Cookies and browser storage may keep a session choice or help the mobile lobby remember where your account path paused. You can adjust cookie controls in your browser settings. If you remove them, the next visit may require another login or verification step.

Use the account support path shown beside the login and cashier areas, and mention that your request concerns the Privacy Policy. State whether it relates to account data, a device record or a wallet reference. Access depends on local law, including for Indonesia.