Reference

Open Your Privacy Policy Here

Your account, wallet, and lobby activity sit under one Privacy Policy, so you can see how we handle registration details, cookie choices, and DANA, OVO, GoPay, or QRIS…

DANA data contextOVO and GoPay recordsQRIS receipt checksCookie choices10:00-02:00 WIB support
skor88 Open Your Privacy Policy Here
HELP DESK

Check Privacy Contact Paths

Privacy requests move faster when we can connect your message to the right account step.

Live chat Use live chat from 10:00 to 02:00 WIB for privacy routing, cookie questions, or account access concerns. Our team may ask for your registered phone number and last wallet rail before opening the case.
Email request Send longer privacy requests to [email protected], especially when you need a data copy, correction, or deletion check. Include your account name, contact email, and the payment rail connected to the case.
Account inbox When you are signed in, open Menu > Account > Privacy Request to send a message from the account itself. This path helps us match your request without asking for extra documents first.
DATA CARE

Browse How We Protect Data

We keep privacy controls tied to real account events, not vague promises. Registration, wallet checks, game-room activity, cookie settings, and support cases each have a purpose and a retention reason.

Account data

We use your name, contact details, login record, and verification status to run the account and answer privacy requests. If a detail is wrong, start with Menu > Account > Privacy Request.

Payment records

DANA, OVO, GoPay, and QRIS records help us match deposits, withdrawals, and privacy questions to the right wallet. We keep receipt references separate from game-room activity where the system allows it.

Cookie choices

Cookies keep your session active, remember language settings, and help detect repeated failed access. You can clear browser cookies, but we may ask you to sign in again on the next visit.

Device checks

We record device type, IP range, and sign-in timing to notice unusual access. If you switch phones, we may ask for email confirmation before changing account or privacy settings.

Retention checks

We keep data only for account operation, dispute handling, security checks, and legal duties where local law permits. When data is no longer needed, we remove or reduce it in our records.

Request handling

A privacy request is handled by trained support staff, then moved to account or payments staff only when needed. We log each step so you can ask what changed and when.

Explore Your Privacy Questions

The questions below focus on privacy actions you may need before or after opening an account. Use them to understand what data we collect, how payment records are handled, and how to contact us when something looks wrong. If your case involves another person, a blocked device, or a missing receipt, contact support first so we can verify ownership safely.

We collect account name, contact details, sign-in data, device signals, wallet records, and verification status. We use this data to run your account, process privacy requests, and protect access from unusual activity.

We use payment records to match deposits, withdrawals, receipt questions, and wallet disputes to your account. Privacy staff may check the rail name, time, and reference code before sharing or changing records.

Yes. Send the request through Menu > Account > Privacy Request or email [email protected]. We may ask you to confirm email, phone number, and recent wallet activity before preparing the data copy.

Start from the account inbox and describe the field that needs correction. For contact details, we may send a confirmation code. For wallet-linked details, we may ask for a DANA or QRIS receipt.

Cookies may show that your browser opened a room page or returned to the lobby, but they are mainly used for session status, settings, and security checks. You can clear them in your browser.

Retention depends on the record type and the reason we need it. Account, payment, security, and support records may have different timelines, especially when local law or a dispute requires evidence.

Only staff who need the case can see it. Support routes the request, then account, security, or payment staff may assist if their area is involved. Each handling step is logged internally.