Reference

Privacy Policy for Indonesia Accounts

Your Privacy Policy view explains what data we use when you open Auto Roulette, Starlight Princess or Boxing Betting, with DANA, OVO, GoPay and QRIS records kept separate…

Account data explainedDANA and QRIS contextCookie choices statedSupport privacy path
besok4d Privacy Policy for Indonesia Accounts
PRIVACY CONTACTS

Reach us about privacy

Privacy questions should reach the team that can verify your account without exposing extra data. We keep three contact paths active so you can choose speed, written records, or account-linked requests. For safety, we never ask for your password or OTP code in a privacy request, and we may pause a request until account ownership is confirmed.

Team online

Live chat

Live chat is open 09:00-01:00 WIB from the help bubble after login. Send privacy questions there when you need quick confirmation of account email, phone number, or a recent DANA reference.

Privacy email

Email [email protected] if you need a written trail. Include your username, registered phone number, and the request type; never send passwords, OTP codes, or full wallet screenshots.

Account inbox

Inside your account, open Profile > Help > Privacy Request on mobile web. That path lets us link your message to the correct account without asking you to repeat sensitive data.

ACCOUNT CONTROLS

How we handle your data

Privacy works when the account flow is clear. We connect each data type to a specific purpose: login safety, wallet checks, cookie settings, support replies, and legal record keeping where local law…

Account data

We ask for data that helps identify your account, such as username, phone number, email, and login credentials. The open account form collects these fields before you reach wallet settings or game categories.

Payment records

DANA, OVO, GoPay and QRIS activity creates reference IDs, timestamps, and account-matching data. We use those records to confirm wallet activity, trace failed requests, and answer privacy questions about payment history.

Cookie use

Cookies help keep your session active, remember language choice, and detect unusual login patterns. You can clear them in your browser settings, though we may ask you to log in again afterward.

Session security

When you log in from mobile web or a computer browser, we record device type, IP address, and time. Check Account > Security > Active Sessions if you need to close an old session.

Record retention

We keep account and wallet records only for business, security, support, and legal needs where local law permits. Some payment references may remain after closure so unresolved wallet questions can be checked.

Correction requests

If your phone number, email, or account name is wrong, contact live chat or [email protected]. We confirm ownership first, then update the field or explain why a record must stay unchanged.

Privacy questions before you join

Before you open an account, you may want to know what happens to your data after login, wallet activity, and support contact. These answers focus only on our Privacy Policy. If your question involves your own account, use live chat or email so we can check the matching record safely.

We collect the details needed to create and protect your account, including username, phone number, email, password data, device signals, and login time. Payment data is added only when you use DANA, OVO, GoPay or QRIS.

We store transaction references, timestamps, status records, and account-matching data. We do not need your wallet password or OTP. If support asks about a payment, share only the reference requested.

Cookies keep your session active, help detect unusual logins, and remember basic site choices. You can clear cookies through your browser, but the next visit may require a fresh login and security check.

Yes. Contact live chat, account inbox, or [email protected] with your username and request type. We verify account ownership first, then correct eligible fields such as phone number or email.

We keep records for account operation, wallet checks, security, support, and legal needs where local law permits. When data is no longer needed for those reasons, we remove it or reduce it.

Access is limited to team roles that need the record for support, wallet checks, security alerts, or privacy requests. Staff should not ask for passwords, OTP codes, or full wallet login details.

We post the current version at /privacy-policy/. If a change affects how we collect, use, or keep account data, we may also show a site message after login.