Reference

Privacy Policy for Your Account

Sic Bo, Hi Lo, Aviator and Royal Fishing sit behind one account, and this Privacy Policy explains what account, device and payment data we use when you browse…

Account data useCookie choicesDANA and QRIS recordsSupport privacy requests
totopediaslot Privacy Policy for Your Account
CONTACT ROUTES

Privacy Contact Paths for You

Privacy questions should reach the team that can check account logs, not a general inbox.

Live chat privacy queue Use live chat between 09:00 and 23:00 WIB for cookie questions, device alerts or…
Email data requests Send privacy requests from the email linked to your account, including the topic and…
WhatsApp account check WhatsApp support can help you confirm whether a privacy ticket is open, but we…
ACCOUNT CARE

How We Protect Your Data

We treat privacy work as part of account operations, not a separate formality. Each request is checked against login history, wallet status and the account step you completed…

Account profile data

We use your name, contact detail and account status to keep the profile connected to the correct login.

Payment privacy logs

DANA, OVO, GoPay and QRIS entries are stored as transaction references, times, amounts and status results.

Cookie controls

Cookies help us keep your language, session state and security checks working between pages.

Device security signals

We record device type, browser, approximate region and login time to spot account access that looks unusual.

Retention handling

Support tickets, wallet records and game session logs are kept only for the period needed for account service, dispute checks…

Change requests

You can ask us to update contact details, close an old session or check stored account data.

Privacy Policy Questions You Ask

This FAQ answers the privacy points we hear most from Indonesia account holders before they open the lobby or connect a wallet. Each answer focuses on what data we use, why we use it, and how you can ask for a check. If your case involves a payment reference, include the rail name and time so support can trace it faster.

We collect the details needed to run your account: contact data, login credentials, account status, device signals and wallet references. We use them to confirm access, answer support requests and keep your activity tied to your profile.

No. We store transaction references, payment times, status results and account links needed for reconciliation. Your private wallet app password or PIN stays with the payment provider and should never be sent to our support team.

Contact live chat or email from the account email and state what needs correction. We may confirm your phone, last login or recent wallet route before changing profile data to prevent another person editing your account.

Cookies keep your session active, remember language settings and support security checks while you move between account pages. If you clear them through your browser settings, you may need to sign in again.

Yes. Open Profile > Security > Devices to check active sessions on mobile or desktop. If a device looks unfamiliar, contact support during 09:00-23:00 WIB so we can help close that session.

Retention depends on the record type. Payment references, support tickets and security events are kept for account service, dispute checks and safety checks, then restricted or removed when they are no longer needed.

Start with live chat for a quick privacy question, or email us for access, correction or deletion requests. Use the email linked to your account so we can verify you before discussing private records.