Rujukan Laman

Privacy Policy for Your Malaysia Account

Double Ball Roulette, Football Studio and Aviator create account activity, device and wallet records that this Privacy Policy explains in plain terms.

Malaysia account dataCookie choicesWallet record carePrivacy request paths
lucky99a Privacy Policy for Your Malaysia Account
CONTACT ROUTES

Privacy Contact Paths at lucky99a

Privacy questions should reach the right queue, so we separate account help from data requests.

Live chat privacy check Use live chat when you need help locating the Privacy Policy, checking what data…
Email request channel Send privacy requests by email when you need a written record of access, correction…
Signed-in message form The account message form helps us link your request to the right profile without…
SECURITY HABITS

Cookies, Security and Data Retention

Our privacy work follows the same account flow you use in the lobby. We record what is needed for sign-in, payment checks, game session records and support replies, then keep it only…

Account data handling

We collect account details, login records and wallet references to run your profile and handle support. Access is limited by role, and internal views are checked when privacy or security issues are raised.

Cookie use

Cookies help keep you signed in, remember device choices and measure whether pages load correctly. You can change browser settings, though some account and security checks may not work as intended.

Wallet record checks

Touch 'n Go, GrabPay, Boost dan FPX records may include payment reference codes, timestamps and account matching details. We use these records to confirm transaction status and answer wallet-related privacy requests.

Access security

We use password controls, session checks and device signals to reduce account misuse. If unusual access appears, we may ask for extra confirmation before sharing or changing account data.

Retention practice

Some records are kept while your account remains active, while payment and security records may stay longer for audit or legal duties. When retention no longer applies, we remove or anonymise data.

Change requests

You can ask us to correct contact details, check account records or begin deletion where allowed. We may keep limited records when law, security needs or unresolved wallet checks require it.

Privacy Questions Before You Join

These answers focus only on how the Privacy Policy applies to your account, device, wallet activity and support contact. They do not replace the full policy text, but they explain the most common data points before you join or ask us to update your records. If your request involves local eligibility, access depends on local law and is available where local law permits.

We collect details needed to create and manage your account, such as contact data, login records, device signals and wallet references. Some checks help protect access and match transactions to your profile.

Payment references help us confirm transaction status, resolve wallet questions and maintain audit records. We do not ask for wallet PINs, and privacy requests may require account verification before any record is discussed.

Yes, you can contact us through chat, email or the signed-in message form. We may verify your identity first, then explain what records are available and whether any legal retention rule applies.

Cookies remember sign-in state, language, device choices and session checks. You can manage them in your browser, but blocking some cookies may affect account access, security checks or page loading.

Send a request from the signed-in message form or email us with your account name. We will check ownership first, then update details that can be changed without affecting security or audit records.

You can request deletion where local law allows. Some payment, security or dispute records may need to stay for a required period before removal, restriction or anonymisation can be completed.

Only teams that need the messages for account help, privacy requests, security checks or quality control may access them. We keep request logs so privacy actions can be traced and answered properly.