Reference

Open your privacy view with bbni4d

Your account data, wallet records, and cookie choices are handled in one privacy flow before you enter live casino, slots, or sportsbook areas, with DANA, OVO, GoPay, and…

DANA wallet recordsOVO account checksGoPay login alertsQRIS transaction markers
bbni4d Open your privacy view with bbni4d
CONTACT ROUTES

Check privacy help channels

Privacy questions need a human path, not a buried form. Whether you write from Denpasar or another Indonesia city, our team checks privacy requests through live…

Live chat privacy desk Use live chat from the lobby footer between 10:00 and 02:00 WIB.
WhatsApp account check Send privacy requests through our WhatsApp channel if you cannot reach the lobby.
Email privacy request For access, correction, or deletion requests, email our privacy inbox with your registered phone…
DATA CARE

Browse how we protect your records

Our Privacy Policy is built around the actions you actually take: opening an account, logging in, setting a password, adding a wallet, and entering game areas such as Lightning Roulette or Jewels…

Account data collection

When you join, we collect the phone number, username, password hash, referral marker if used, and login time. These records let us run access checks, protect your wallet, and answer account privacy requests.

Payment record handling

DANA, OVO, GoPay, and QRIS entries are stored as wallet references, timestamps, and status markers. We use them to trace deposits and withdrawals, not to read unrelated app balances or personal contacts.

Cookie choices

Cookies remember language preference, session state, and security checks. You can clear browser cookies from your device settings, but we may ask for login verification again when the saved session disappears.

Game area records

If you open Lightning Roulette, Fishing God, Crash Games, or League of Legends markets, we record session time, category, and wallet impact. The policy treats these as account activity, not public profile material.

Retention and removal

We keep records while your account is active and for a reasonable period needed for wallet tracing, dispute handling, and legal duties. You may ask us to correct or delete eligible records.

Security settings path

Go to Account > Security > Active Sessions to check device access. If you see an unfamiliar phone, browser, or city marker, contact us so we can close that session and refresh your password.

Check privacy answers before you join

These answers cover the privacy questions we hear before account opening and after wallet activity. They explain what we collect, why we keep it, how payment references are handled, and how you can ask us to correct or remove eligible records. For anything tied to local access, our answer may depend on local law.

We collect your phone number, username, password hash, registration time, device marker, and consent choices. If you add a wallet, we also store the payment reference needed to match DANA, OVO, GoPay, or QRIS activity.

Yes. Contact live chat, WhatsApp, or email with your registered phone number and the request type. We verify account control first, then provide the eligible account and wallet records we can share.

We use payment references to confirm wallet activity, trace settlement issues, and answer account questions. We do not need your unrelated app data, contact list, chat history, or full payment app profile.

Yes. Cookies support session memory, language choice, login security, and consent prompts. You can clear them in your browser settings, but the next visit may require a fresh login and device check.

Send a privacy correction request through live chat or email. We may ask you to pass an account security check and provide the correct detail before changing the record in your account profile.

You can request deletion of eligible records by email. Some wallet and access records may remain for dispute handling, security tracing, or legal duties, and access decisions may depend on local law.

Only support and account staff assigned to privacy handling can view the request details. Payment references, login markers, and identity checks are shared internally only when needed to answer your request.