Reference

Privacy Policy for Your toko56 Account

Baccarat, Aztec Gems, Basketball Betting and Rocket Crash create account, wallet and device records, and this Privacy Policy explains how we handle those records before you open your…

Account data useCookie choicesDANA recordsQRIS checks
toko56 Privacy Policy for Your toko56 Account
CONTACT ROUTES

Privacy Contact Paths With WIB Hours

Privacy questions move faster when you send them through the right channel.

Live chat privacy desk Use live chat from 09:00 to 23:00 WIB when you need a quick privacy…
WhatsApp account check Message our WhatsApp line during support hours for privacy requests tied to DANA, OVO…
Email privacy record Send longer requests to [email protected] if you want access, correction or deletion checks.
ACCOUNT CARE

How We Handle Your Privacy Requests

We treat privacy work as part of account operations, not a side form. Each request is checked against your account step, device trail and payment record so we do not change data…

Account data scope

We collect details you enter during account creation, including username, contact number and login credentials. Those details help us open your wallet, protect access and send account-specific privacy replies.

Payment record handling

DANA, OVO, GoPay and QRIS activity creates transaction references, time stamps and status records. We use those records to match wallet movements, answer privacy questions and investigate mismatched receipts.

Cookies and device signals

Cookies help keep you signed in and show whether your device accepted account security checks. On Android Chrome, you can change them through Settings > Site settings > Cookies before returning to the lobby.

Game session records

When you open Baccarat, Bingo, Fish Hunter or Rocket Crash, session logs may record page time, round reference and device status. We use these records to answer account and privacy disputes.

Retention checks

We keep account, wallet and support records only for operational, legal and dispute needs. When a record is no longer needed for those purposes, we remove it or separate it from direct identity details.

Change requests

You can ask us to correct account details, check stored data or remove eligible records. Start from Profile > Security or contact support, then we verify identity before any privacy action is made.

Privacy Questions Before You Join

These answers focus on the privacy choices you usually check before opening an account. We explain what data we collect, how payment records are used, how cookies behave and how you can contact us. If your request relates to eligibility, account access or transaction records, our reply will also consider local law where access is permitted.

We collect the details you submit, such as username, contact number, login credentials and wallet choices. We also record device and session data so we can secure access and respond to account privacy requests.

We use payment records to match wallet activity with your account, receipt time and payment reference. These records help us confirm deposits, withdrawals and privacy questions tied to transaction history.

Yes. Contact us by live chat, WhatsApp or [email protected] and tell us what you want to check. We verify identity first, then prepare the account data we can share under applicable rules.

Log in and go to Profile > Security for basic contact and access details. If the field is locked, contact support from 09:00 to 23:00 WIB and provide the account proof we request.

Some cookies may remain to keep login status, security checks and language choices working. On Android Chrome, open Settings > Site settings > Cookies if you want to change how your device keeps them.

You can request deletion by email or support chat. We remove eligible data when it is no longer needed for account security, transaction disputes, legal duties or payment record matching.

Use live chat or WhatsApp from 09:00 to 23:00 WIB for quick questions, or email [email protected] for detailed requests. Include your username, registered phone number and request type.