Reference

Privacy Policy for Your Account Data

Super Sic Bo, Pyramid Bonanza and Aviator sit behind one account, and this Privacy Policy explains the data we collect when you browse, join, pay, or ask us…

Account data scopeDANA and QRIS recordsCookie choicesSupport request trail
borneo jitu Privacy Policy for Your Account Data
CONTACT ROUTES

Privacy Contacts Without Waiting Around

Privacy requests should reach the team that can act on them, not a general inbox with no context. We keep three contact paths open for account data questions, correction requests, and cookie concerns. Have your username, registered phone number, and the payment rail involved ready before you write; that helps us confirm the account without asking you to repeat private details across several messages.

Team online

Live chat privacy desk

Use the chat button after login between 09:00 and 23:00 WIB for account data questions. We can check your recent login trail, confirm the request type, and tell you which record may need correction.

WhatsApp account check

Our WhatsApp path is shown inside your account menu, so you do not need to search for a random number. Send your username and request reason; never send wallet PINs, passwords, or full ID photos.

Privacy ticket in account

From Profile to Help Center, choose Privacy Request and add the affected area, such as DANA record, QRIS receipt, cookie choice, or phone number update. Tickets keep the conversation tied to your account.

ACCOUNT CARE

Aviator Data and Cookie Handling

Privacy is handled at account level, not as a side note after you enter the lobby.

Registration data

When you join, we collect the username, password record, phone number, and basic account settings needed to open your profile. We use those fields to authenticate access and to contact you about privacy requests.

Wallet records

DANA, OVO, GoPay and QRIS references are kept with time, amount, and account match status. We use them to trace deposits, check payout requests, and resolve mismatched transaction screenshots without exposing your wallet PIN.

Device activity

We record browser type, device model category, IP range, and login time when you access the account. This helps us spot unusual access and answer your question if a session looks unfamiliar.

Cookie choices

Open Account, then Privacy, then Cookie Preferences to adjust non-essential cookies. Required cookies keep login sessions and payment pages working, while optional cookies help us understand page errors and menu performance.

Data retention

We keep account and payment records only for operational needs such as transaction checks, dispute handling, and legal requests where local law permits. When a record is no longer needed, we remove or de-identify it.

Change requests

If your phone number, display name, or payment label is wrong, send a Privacy Request from Profile. We may ask for a recent transaction reference to confirm you control the account before changing it.

Privacy Questions You May Search

These answers focus only on privacy choices, account data, payment records, cookies, access logs, and how to contact us about a correction. If your question involves a payment result, include the rail name such as DANA or QRIS and the time shown in Wallet History. That gives us enough context without asking you to expose passwords or wallet PINs.

We collect the details needed to create and protect your account, including username, password record, phone number, account preferences, login time, and device activity. Payment records are added only when you use DANA, OVO, GoPay or QRIS.

Go to Profile, choose Help Center, then select Privacy Request. Add the field you want corrected and a short reason. For payment-related corrections, include the transaction reference from Wallet History, not your wallet PIN.

We use payment details to match deposits, verify payout requests, and resolve transaction disputes with the relevant payment rail. We do not publish wallet details in the lobby or use them for public account display.

Device and login records help us confirm that access matches your usual account behavior. If you report a suspicious session, we can compare time, browser type, and IP range before advising password reset steps.

Yes. Open Account, then Privacy, then Cookie Preferences from your mobile browser. Required cookies keep login and wallet pages working; optional cookies can be adjusted when you want less performance tracking.

We keep records for operational needs such as transaction checks, account disputes, security reviews, and legal requests where local law permits. When a record is no longer required, we remove it or de-identify it.

Use live chat from 09:00 to 23:00 WIB or submit a Privacy Request in Profile. Include your username, registered phone number, and the affected area, such as cookies, login logs, or QRIS payment record.