Reference

kedai168 Privacy Policy For Your Account

Our Privacy Policy explains how kedai168 handles the details you provide when opening an account, checking Live Casino or Speed Winner, and using DANA, OVO, GoPay or QRIS.

Clear data purposesWallet detail contextAccount request pathMobile cookie choices
kedai168 kedai168 Privacy Policy For Your Account
CONTACT ROUTES

Ask About Your Account Data

A direct support request gives you a practical route for Privacy Policy questions, especially when a phone check, wallet reference or account access step needs clarification. Tell us the account email or phone detail connected to the request, describe the action you took, and avoid sending a password or full payment credentials. We use the supplied details to locate the right record and respond safely.

Team online

Account data request

Ask which account details we hold, why a phone verification record appears, or how to correct a profile field. We may confirm ownership before discussing private account data.

Wallet status question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, include the reference and date. We can explain the stored status without requesting your wallet password.

Policy access help

If the Privacy Policy page or a cookie setting is difficult to open on your phone, contact our support route with your device type and browser so we can trace the issue.

HANDLING DETAILS

Data Controls Across Your Account

We handle Privacy Policy requests as account matters rather than treating them as general lobby questions.

Collected account data

We may hold your name, phone or email detail, verification result, account settings and support messages. These fields help us connect your request to the correct kedai168 account.

Session and device data

Browser type, device signals, login time and pages opened can help protect access and diagnose a mobile path. We use these details to investigate unusual sessions or broken screens.

Cookie choices

Cookies can keep a session active, remember selected settings and show whether a page loaded correctly. Your browser controls can limit cookies, though some account steps may then need repeating.

Account security

We may compare login activity with phone verification and transaction references when access looks unusual. Never send a password, wallet PIN or full card credential in a support message.

Retention approach

We retain account, security and transaction records only for the period needed for service operation, dispute handling, security checks or legal duties. Ask support which record category applies.

Requesting a change

Send a clear request through support with your account contact detail and the change you want. We may ask for an ownership check before correcting, exporting or removing data.

Privacy Policy Questions For kedai168

These Privacy Policy answers focus on the searches we hear around account creation, wallet records, cookies and data access. If your situation is not covered, use the support route and describe the exact account step, device behaviour or payment reference involved. We will keep the request focused on your privacy concern.

It covers data used when you open or access an account, complete phone verification, browse Live Casino or other lobby areas, use cookies, contact support, or create a DANA, OVO, GoPay or QRIS transaction reference.

Phone verification helps connect you to the correct account and detect unusual access. We may use the result during a privacy request, but you should not send your verification code or wallet PIN to support.

Contact support with the phone or email detail attached to your account and ask for a data access request. We may confirm ownership before describing records linked to your profile or sessions.

Yes, ask support to correct an inaccurate account field and explain what should change. Include the relevant account contact detail; an ownership check may be required before we edit the record.

We may store a payment reference, status and timing so an account action can be matched to the correct wallet event. We do not need your wallet password or PIN for that check.

Yes. It covers browser sessions on phones and desktops, including device signals, cookies and login activity. If Mobile Legends or Fish Hunter loads incorrectly, support may ask for your browser type.

You can submit a deletion request through support. We assess the request under local requirements and may retain security, account or transaction records where needed for legal duties or dispute handling.