Reference

yuk88 Privacy Policy for Your Account

The yuk88 Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, or check a wallet status.

Account dataCookie choicesWallet recordsSecurity steps
yuk88 yuk88 Privacy Policy for Your Account
HELP WITH REQUESTS

Get Privacy Help Beside Your Account

A clear support route helps when you need to ask about the Privacy Policy rather than a game or wallet result. Sign in first when you can, then use the account support path and include the email or phone detail linked to your profile. If you cannot sign in, provide only the minimum details needed for us to locate the record. We may ask for an account step before discussing personal data. Keep payment receipts private, especially when asking about DANA, QRIS or a bank transfer.

Team online

Account access

If you cannot sign in, use the account support route and state that your request concerns the Privacy Policy. We will ask for enough account detail to locate you without requesting a wallet PIN or full payment password.

Wallet records

For a DANA, OVO, GoPay or QRIS query, send the transaction reference and date shown in your account. Remove unrelated balances, passwords and security codes before attaching a receipt to your privacy request.

Data requests

Ask us to review, correct or explain eligible personal data through the support path connected to your account. We may verify your identity first, so another person cannot obtain details from your yuk88 profile.

DATA HANDLING

How We Protect Your Privacy Choices

Privacy work is tied to practical account events: opening an account, confirming a sign-in, checking a device session and matching a wallet reference.

Account details

When you open an account, we use the details you submit to create and maintain your profile. A clear phone verification step may be required before account access, helping us separate your request from an unknown sign-in.

Device signals

A mobile or desktop browser can send session and device signals that help us recognise an active sign-in and investigate unusual access. These signals support account security; they are not a request for your device password.

Cookies

Cookies can keep a session working, remember selected settings and help us understand whether a page request belongs to an active account. You can raise a cookie question through support if a setting behaves differently than expected.

Payment references

We may retain a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference so a wallet status can be matched to your account. We do not need your wallet PIN to check that reference.

Security controls

We use account verification, session checks and restricted handling for personal records. Never send a password or one-time security code in a support message, even when asking us to correct Privacy Policy data.

Retention requests

Records stay available for the period needed for account operation, security checks or legal duties. You can ask why a record remains, request a correction or ask whether deletion is available under the law that applies to you.

Privacy Policy Answers for yuk88

These Privacy Policy questions cover the account actions people ask about most: what we collect, why a device appears in a session record, how wallet references are handled and how to send a request. Read the answer that matches your concern, then use the account support path if you need a case-specific response. We apply access rules where local law permits.

It covers account details, contact data, phone verification, device and session signals, cookies, payment references, retention and requests about your personal data. It also explains how we use those records for account access, wallet status checks, security and support.

Phone verification helps us confirm that an account access request is connected to you rather than an unknown person. We may use the verified contact detail for account security and support, while access remains subject to local law.

Yes. We may keep a DANA or QRIS reference, along with OVO, GoPay, bank transfer or virtual account details, to match a status or receipt to your account. We do not ask for your wallet PIN to perform that check.

Cookies can maintain your sign-in session, remember a setting and help connect a page request to the active account. A mobile browser and a desktop browser may handle these files differently, so contact support if a cookie choice needs clarification.

You can send a correction request through the account support path and identify the record that appears wrong. We may verify your account before changing it. Include only necessary details, and do not attach passwords, wallet PINs or security codes.

We retain records for as long as needed for account operation, security checks, payment matching or legal duties. The period can depend on the record and the law that applies. You may ask support why a particular record is still retained.

Sign in and use the account support path, then state that your message concerns the Privacy Policy. If access is unavailable, provide the minimum account detail needed to locate you. We may request identity checks before discussing or changing personal data.