Reference

Privacy Policy for Your Account

Live Dealer Lobby, Aviator and Fish Hunter each create account, device and session records, so our Privacy Policy explains exactly how we handle them when you open an…

Account data useDANA recordsOVO receiptsGoPay logsQRIS checks
gudangcuan Privacy Policy for Your Account
CONTACT ROUTES

Three Ways to Ask Us

Privacy questions should reach the right person fast, not sit inside a general inbox. We separate privacy requests from gameplay chats so you can ask about access, correction, deletion, cookies or payment records with enough context. Include your registered phone number, email address and the last four characters of a recent payment reference when it helps us verify the account.

Team online

Live chat privacy queue

Use live chat between 09:00 and 23:00 WIB for account data questions. Tell us you are asking about the Privacy Policy, then share your registered phone number so we can route the request correctly.

Email request desk

Send privacy requests by email when you need a written trail. We ask you to describe the data area involved, such as login records, cookies, DANA receipts or profile edits, before we respond.

Account page message

From your account, open Settings, choose Help, then select Privacy Request. This path attaches your account ID to the message, which reduces back-and-forth when you ask for changes or copies.

DATA HANDLING

Six Controls Behind the Policy

A privacy promise only matters when the account flow supports it. We map each data type to a reason: registration, payment matching, login security, customer support or legal record keeping where local…

Registration records

When you create an account, we collect the details needed to identify your profile and protect access. We use them for login checks, support matching and account notices connected to this Privacy Policy.

Payment references

DANA, OVO, GoPay and QRIS transactions create reference numbers, timestamps and status results. We store those records to match wallet activity, investigate mismatches and answer privacy questions about payment data.

Device and session logs

Mobile and desktop sessions leave device type, browser, IP range and login time records. We use these logs to spot unusual access and to help you confirm whether a session was yours.

Cookie choices

Cookies help keep your session active, remember language choices and measure page errors. You can clear cookies in your browser; after that, we may ask you to log in again.

Retention checks

We keep records only for account operations, dispute handling, security checks and legal needs where local law permits. When a record is no longer needed, we remove it or reduce identifying details.

Correction requests

If your phone number, email address or saved profile detail is wrong, contact us through chat or the account page. We may ask for verification before changing data tied to payments.

Common Privacy Policy Questions

These answers focus on what you can ask us to check, change or explain under our Privacy Policy. Keep your request specific, because account data, payment records, cookies and support messages follow different handling steps. If you contact us, use the same phone number or email connected to your account.

We collect the details needed to create and protect your account, such as contact data, login records, device signals and wallet activity. Payment references from DANA, OVO, GoPay and QRIS are kept for matching.

Payment records help us match deposits, confirm withdrawals and investigate mismatched wallet activity. We store references, timestamps, status results and related account IDs, not extra banking details beyond what the payment flow provides.

Yes. Contact live chat, email or the Privacy Request path inside Settings. We verify that the request comes from you before sharing account data, because payment logs and support messages can be sensitive.

Open your account settings first and update the fields available there. If a detail is locked because it connects to payment checks, message support and we will verify ownership before making the change.

Our cookies are used for session access, preference memory and page performance checks. You can clear them through your browser settings; the next visit may require a fresh login and new preference choices.

Support messages are available to the team members who need them to answer your request, check account history or resolve privacy questions. We do not use chat records for unrelated third-party marketing lists.

Send a privacy request through email, live chat or Settings. We review what can be deleted and what must be kept for security, payment disputes or legal needs where local law permits.