Reference

Privacy Policy For Your jaguar88 Account

Your account data, DANA, OVO, GoPay and QRIS wallet records, and device signals sit under this Privacy Policy before you open the lobby for Super Sic Bo, Plinko…

Account data useWallet record handlingCookie and device controlsPrivacy support paths
jaguar88 Privacy Policy For Your jaguar88 Account
CONTACT ROUTES

Reach Us About Privacy

Privacy questions should reach the same account you use in the lobby, because that lets us confirm you without exposing wallet records in open chat.

Live chat Use the chat button after login for account-specific privacy checks. Our team answers 10:00-22:00 WIB, asks for your username, and records the ticket inside your account panel safely.
WhatsApp Send privacy questions through the WhatsApp link shown in your account menu, not through random numbers. We check your registered phone, then confirm whether a data change or access request can proceed.
Email Email privacy requests to the address in our footer and include your username, registered phone, and the payment rail involved. We reply with the next step instead of asking for wallet passwords.
ACCOUNT CONTROLS

How We Handle Account Data

Clear privacy handling keeps your account usable while reducing unnecessary exposure. We use login checks, cookie controls, payment references, and internal access rules so a support agent only sees what is needed…

Account data

We collect registration fields, login records, and profile changes so your account can be identified when you contact us. Extra documents are requested only when a privacy or wallet check requires them.

Device and login

We record device type, IP range, browser, and failed login patterns to protect your account session. If a new device appears, support may ask a security question before changing privacy data.

Wallet references

DANA, OVO, GoPay and QRIS references help us match deposits, withdrawals, and privacy tickets to the right account. We do not ask for PINs, OTP codes, or full wallet passwords.

Cookie choices

Cookies keep your session active, remember language settings, and help us spot repeated failed logins. You can clear browser cookies anytime, but you may need to log in again afterward.

Retention handling

We keep account and wallet records only for operational, dispute, security, and local rule needs. When a record is no longer needed, we delete it or reduce it so it no longer identifies you.

Data change path

To correct a phone number, email, or wallet name, go to Account > Privacy > Data Request. We confirm ownership first, then tell you what can be changed and what must remain locked.

Privacy Questions You May Search

These answers explain how our Privacy Policy works when your account touches payments, cookies, support tickets, and game records. They are written for practical account use, not legal jargon. If your request involves local access rules, identity checks, or wallet ownership, our support team will confirm the next step through your registered contact channel.

We collect the fields needed to create and secure your account, such as username, registered phone, email, login records, device signals, cookie choices, and wallet references tied to DANA, OVO, GoPay or QRIS.

Yes. The policy covers the payment references we receive when you use DANA, OVO, GoPay or QRIS. We use those references to match transactions, answer wallet questions, and handle privacy requests.

Open Account > Privacy > Data Request after login, or contact support from your registered email. We verify account ownership first, then explain which records can be shared and how they will be delivered.

You can request a correction through the privacy path in your account. We check your username, registered phone, and recent wallet reference before changing details that affect login or transaction matching.

Cookies help keep you signed in, remember display settings, and detect repeated failed logins. If you clear cookies on your browser, the site may ask you to log in and confirm your session again.

We keep account data while your profile is active and for periods needed for security, disputes, wallet checks, or local rules. When data is no longer needed, we delete or reduce it where possible.

Only team members assigned to support, account safety, or wallet checks can access a privacy request. We limit the view to the fields needed for the task, such as username, ticket text, and contact channel.