Reference

Privacy Policy for Your jajabet Account

jajabet keeps one Privacy Policy for account data, wallet records, cookies, device signals, and lobby activity such as Sic Bo, Crash Games, or Fish Hunter history.

DANA record handlingOVO and GoPay receiptsQRIS confirmation dataCookie controls09:00-23:00 WIB privacy help
jajabet Privacy Policy for Your jajabet Account
PRIVACY DESK

Privacy Contact Paths for Your Account

Fast privacy help starts with the channel that matches your request. Use live chat for account access checks, email for data access or correction requests, and the in-account form when you are already logged in. We may ask you to confirm your phone number, email, or recent DANA, OVO, GoPay, or QRIS reference before we change personal records.

Team online

Live chat 09:00-23:00 WIB

Use live chat when you cannot enter your account or need a privacy record checked quickly. We verify your account step, then send sensitive details only after the identity check is complete.

Email [email protected]

Send access, correction, deletion, or cookie questions to [email protected]. Include your account ID and a contact number, but never send wallet PINs, card images, or passwords in the email.

Account form path

When logged in, open Account > Profile > Privacy to send a request tied to your account. This route helps us match your message with device logs and wallet records safely.

ACCOUNT CARE

Cookies, Sic Bo Logs, and Retention

Useful privacy controls work only when you know what each record does. Our policy separates profile details, wallet confirmations, device signals, cookies, game-session logs, and support messages so you can ask about…

Profile details

Your name, phone number, email, and account ID help us create your login and answer account questions. You can request a correction when a spelling, contact number, or email address needs an update.

Wallet confirmations

DANA, OVO, GoPay, and QRIS references are kept with transaction time, amount, and account match data. We use them to confirm wallet activity and handle privacy questions about payment records.

Device signals

We record device type, IP range, browser version, and session time to protect account access. Open Account > Security > Sessions to review recent devices and tell us if one looks unfamiliar.

Cookie choices

Cookies keep you signed in, remember language settings, and help us spot unusual session patterns. You can clear browser cookies, then log in again to rebuild only the records needed for access.

Game-session records

Crash Games, Fish Hunter, and table sessions create timestamps, round references, and balance movements. These records help us answer privacy access requests and account disputes without exposing another person’s data.

Record retention

We keep account and wallet records only for operational, security, legal, and dispute needs. When a record is no longer required, we remove it or detach it from details that identify you.

Privacy Policy Questions Before You Join

Before you open an account, you should know what data we collect, why we collect it, and how to reach us when something needs changing. These answers focus on the Privacy Policy, including account records, wallet references, cookies, device logs, and your choices under local law where access is permitted.

It covers account details, contact data, device logs, cookie records, wallet references, support messages, and lobby activity timestamps. We use these records for account setup, access checks, wallet matching, security, and privacy request handling.

We keep wallet references so deposits, withdrawals, and account checks can be traced to the correct account. The record usually includes payment rail, time, amount, reference code, and match status, not your wallet PIN.

Email [email protected] or use Account > Profile > Privacy after login. We may ask you to confirm your phone number, email, recent QRIS reference, or another account detail before sharing any data.

Yes, you can request a correction through live chat from 09:00 to 23:00 WIB or by email. We check the account owner first, then update eligible profile details and record the change date.

Cookies can remember session state, language, and security signals, while game-session records store activity such as Sic Bo or Crash Games timestamps. You can clear cookies in your browser, but some access checks may run again.

We can delete or detach eligible records when they are no longer needed for account safety, wallet traceability, dispute handling, or legal reasons. If a record must stay, we explain the reason in our response.

We share data only when needed for account operations, wallet verification, security checks, support handling, or legal requests. Any access or eligibility matter depends on local law and is available only where local law permits.