Reference

Live Roulette Privacy Before You Join

Live Roulette, Gonzo's Quest, E-Sports Arena and Rocket Crash share one 8tangkas account record, so this Privacy Policy shows what data we collect before you open an account.

Account data explainedDANA OVO GoPay QRISCookie choicesDevice session checks
8tangkas Live Roulette Privacy Before You Join
CONTACT PATHS

Ask Us About Your Privacy Record

Fast privacy help matters when your phone changes, a wallet receipt looks wrong or your profile details need correction.

Live chat privacy desk Live chat is available every day from 09:00 to 23:00 WIB for privacy questions…
Email data request Email privacy requests to [email protected] with your account ID, registered phone number and the…
Profile security path Inside your account, head to Profile > Security > Devices to check recent sessions…
DATA CONTROLS

How Privacy Works Inside 8tangkas

Your privacy settings should be practical, not hidden behind vague wording. We separate account identity, wallet records, cookie signals and support chats so each request can be handled by the right team.

Account sign-up data

When you register, we collect details such as name, phone, email, username and password hash so your account can be created and recovered. We use these records for access checks, support verification and profile changes.

Cookie and device signals

Cookies help remember your session, language choice and basic lobby preferences. Device signals such as browser type, IP range and login time help us spot unusual access without asking you to repeat every step.

Payment privacy handling

For DANA, OVO, GoPay and QRIS, we keep transaction references, status updates and matching results. We do not store your wallet PIN, and we never ask you to send one-time codes through chat.

Live table activity records

Live Roulette and similar table records may include session ID, stake record, round time and balance movement. These records help answer disputes without exposing unrelated profile details to every support agent.

Retention and removal

Some records are kept for security checks, payment matching and dispute handling, then reduced when that purpose ends. You can ask what we hold, request correction, or ask whether removal is available for your account.

Change request checks

Before changing phone, email or wallet details, we verify account ownership through registered contact points and recent activity. This slows down account takeover attempts and keeps privacy requests tied to the real account holder.

Privacy Questions Before You Join

Before you open an account, read these practical answers about what we collect, why we need it and how you can contact us. The answers focus on account privacy, wallet records, cookies, support checks and your choices after registration. If your question involves access to any game area, availability depends on local law and is available only where local law permits.

We collect account details such as name, phone, email, username, password hash and registration time. We also log basic device and IP signals so we can protect sign-ins, answer support requests and match wallet activity.

Yes. We record the payment rail, reference code, status, time and matching result for DANA, OVO, GoPay and QRIS. We do not collect your wallet PIN or private login credentials for those apps.

Contact live chat from 09:00 to 23:00 WIB or email [email protected] from your registered address. Include your account ID and the exact field to correct, but never include passwords or one-time codes.

Device and login records help us detect unusual access, such as a new browser, changed IP range or repeated failed sign-ins. You can check sessions through Profile > Security > Devices after you sign in.

You can ask whether removal is available for your account by contacting support. Some records may need to remain for payment matching, dispute handling, security checks or legal requests before they can be reduced.

Cookies mainly help keep your session active, remember preference settings and protect sign-ins. Where analytics cookies are used, we keep them focused on service performance and do not use them to ask for wallet credentials.

Privacy requests are routed to staff who need the details to verify and answer the case. We ask verification questions first, avoid exposing private records in the opening reply, and keep chat access limited by role.