Reference

Privacy Policy for Your Account Data

Your account details, device session, and DANA, OVO, GoPay, or QRIS records are covered by this Privacy Policy before you open the lobby.

Account data useDANA receipt checksCookie choicesWhatsApp 09:00-01:00 WIB
bosgacor88 Privacy Policy for Your Account Data
CONTACT PATHS

Reach Us About Privacy Requests

Privacy questions need a clear route, not a generic inbox. Use the same contact path linked to your account so we can match your request with your registered phone, wallet receipt, and…

Live Chat Open live chat from the account menu between 09:00 and 01:00 WIB. Tell us the request is about privacy, then share your account ID only after the agent asks inside the chat window.
WhatsApp Message our WhatsApp support line during the same 09:00 to 01:00 WIB window. We use it for identity checks, correction requests, cookie questions, and follow-up when a payment record needs matching.
Email Email privacy requests when you need a written trail for access, correction, deletion, or export questions. Include your registered phone suffix, payment rail used, and the date of your latest account activity.
DATA HANDLING

How We Protect Your Privacy Choices

We keep this policy practical: every data point should support account access, wallet matching, security, or support.

Account records

We collect the details you submit during account creation, including username, registered phone, password hash, and login timestamps. These records help us confirm account ownership before we discuss any privacy request.

Payment traces

DANA, OVO, GoPay, and QRIS references may be stored with transaction time, amount, and status. We use those records to match wallet activity, check disputes, and answer payment-related privacy questions.

Device sessions

Mobile browser, Android WebView, and laptop sessions can create device IDs, IP records, and cookie entries. We use them to spot unusual access and to keep your account session from being misused.

Cookie control

Cookies remember login state, language choice, and basic site performance signals. You can clear them in Chrome through Settings, Privacy and security, Clear browsing data, then sign in again.

Retention checks

We keep records only for operational, security, accounting, and legal needs. When a record is no longer required, we remove it or separate it from direct account identity where practical.

Change requests

If your phone number, wallet name, or account detail is wrong, contact support with your account ID and a recent QRIS or e-wallet reference. We verify first, then update the relevant record.

Answers About Your Data Rights

These answers focus on real privacy tasks: seeing what we store, changing account details, handling cookies, and asking us to remove data where possible. If your request involves payment records, keep your DANA, OVO, GoPay, or QRIS reference nearby so we can trace it safely.

We collect the details needed to run your account: username, registered phone, password hash, login time, device session, and wallet references. Payment records may include DANA, OVO, GoPay, or QRIS status and timestamps.

We keep payment references to match deposits and withdrawals, answer transaction questions, and check unusual wallet activity. Support may use the time, amount, and receipt reference to confirm the record belongs to your account.

Yes. Contact live chat, WhatsApp, or email and say you want account data access. We will verify your registered phone and recent activity before sharing a summary of records tied to your profile.

Send a correction request through support with your account ID, masked old detail, and the new detail. For wallet changes, we may ask for a recent QRIS or e-wallet reference before updating records.

Cookies can remember session status and basic activity paths, including pages opened around games such as Book of Dead or Andar Bahar. They are used for access, security, and site performance, not to sell your profile.

You can request deletion through support. Some records may need to stay for security, accounting, dispute handling, or legal reasons, but we will remove or separate eligible data after identity checks.

Reply through the same channel used for the request and ask for privacy escalation. Include the case time, account ID, and contact method so we can review the handling without exposing extra personal details.