Rujukan Laman

Privacy rules for Oracle Roulette data

Oracle Roulette, Neon Fruits, Football Studio, Aviator and Alien Hunting create account, device and session records; our Privacy Policy explains how we collect, use, store and share that…

Account data useCookie controlsMalaysia payment recordsPrivacy contact paths
jilicity88 Privacy rules for Oracle Roulette data
CONTACT PATHS

Contact us about your privacy choices

Privacy requests need clear routing, so we separate account help from data-rights handling.

Privacy email Send data access, correction or deletion requests to our privacy mailbox with your account…
Live chat handover Use live chat when you need to locate the right privacy route.
Account centre request When you are logged in, use the account centre to request a data update.
ACCOUNT CARE

How we protect Aviator account data

Our privacy handling covers the records created when you open the lobby, start a game round, verify a payment or speak with support.

Data we collect

We collect account details, contact data, device identifiers, session records, payment references and support messages.

Cookie handling

Cookies help keep you signed in, remember language choices and measure site reliability.

Payment privacy

Touch 'n Go, GrabPay, Boost dan FPX records are used to confirm deposits, check withdrawal requests and resolve payment enquiries.

Security checks

Before we update sensitive account records, we may confirm your email, mobile number, recent login device or payment reference.

Retention choices

Some records can be corrected or removed after verification, while others must be kept for legal, security or dispute reasons.

Vendor sharing

We share limited data with hosting, payment, fraud-screening and support vendors when needed to run your account.

Privacy questions for your jilicity88 account

This FAQ explains the privacy choices you can raise with us before or after opening an account. It focuses on account data, payment records, cookies, session logs, correction requests and contact paths. If your question involves eligibility, access depends on local law and is available where local law permits. For personal requests, we will ask for verification before we discuss account-specific records.

We collect the details needed to create and secure your account, such as contact data, login identifiers, device signals and verification records. Payment references and support messages are added when you use those services.

Payment records help us match deposits, verify withdrawal requests and answer wallet enquiries. We use references, timestamps and status messages rather than asking you for private wallet passwords or full banking credentials.

Yes. Contact us with the detail you want changed and the account identifiers we request. We may verify your identity first, then update eligible records or explain why a record must remain unchanged.

You can request a copy of account data linked to you. We review the request, confirm your identity and provide eligible records in a practical format, subject to legal, security and dispute limits.

Cookies store session, language and security settings so the site can recognise your browser. You can adjust browser settings, but required cookies are needed for login, wallet checks and account protection.

We may share limited data with payment processors, hosting providers, fraud-screening services and customer support tools. Sharing is tied to account operation, security checks, legal duties or your direct request.

Retention depends on the record type, account status, legal duties and unresolved enquiries. Some data can be deleted after verification, while payment, security or dispute records may need to remain longer.