Rujukan Laman

Privacy Policy for Malaysia Account Data

Before you open your account, this Privacy Policy explains how alladin99 handles profile details, wallet references, device records and cookie choices tied to your lobby access.

Account data useCookie choicesWallet reference careMalaysia privacy contact
alladin99 Privacy Policy for Malaysia Account Data
CONTACT PATHS

Contact Us About Privacy Matters

Privacy questions deserve a clear route, not a runaround. Use the channel that matches your request: chat for quick account checks, email for written requests with…

Live chat privacy help Use live chat for quick privacy questions about profile data, cookie choices or a…
Email privacy requests Email us when your request needs documents, screenshots or a clear timeline.
Account security area Inside your account, use the security area to update passwords, device access and contact…
DATA RIGHTS

How We Handle Privacy Requests

Our privacy process is built around account checks, clear records and limited access. We separate support conversations from wallet references where we can, and we keep internal access tied to staff roles.

Data we collect

We collect account details, contact data, login records and transaction references needed to run your account. For Touch 'n Go, GrabPay, Boost dan FPX, we keep payment references rather than full wallet credentials.

Cookie handling

Cookies help keep sessions active, remember language choices and spot unusual access patterns. You can clear cookies in your browser, though some account checks may need to run again after that.

Account security

Passwords are stored in protected form, and access to privacy records is limited by role. When a new device appears, we may add checks before showing wallet or profile details.

Retention periods

We keep records for as long as needed for account service, legal duties, dispute handling and security checks. When retention no longer applies, records are deleted or separated from direct account identity.

Request changes

You may ask us to correct contact details, update profile fields or check stored records. We will verify the account first so changes are made by the right person.

Clear response path

Privacy requests go through chat or email, then move to a specialist if records need deeper checking. We aim to respond clearly, with the next step stated in plain language.

Privacy Questions Before You Join

These answers explain how we handle common privacy requests before and after you open an account. They focus on personal records, cookies, wallet references, access checks and contact choices. If your case has special details, send us the account email and a clear request so we can check it properly.

We ask for details needed to create and protect your account, such as contact data, login records, device signals and wallet references. We do not ask for full Touch 'n Go, GrabPay, Boost dan FPX credentials.

Payment references help us match account activity with wallet actions, resolve disputes and check withdrawal requests. We treat those references as account records and limit access to staff who need them for a clear task.

Cookies support login sessions, language choices, security checks and account navigation. You can clear them through your browser settings, but you may need to log in again or complete extra account checks afterward.

Yes, you may ask for a copy of records linked to your account. We will verify your identity first, then provide records we can share under applicable law and account security requirements.

Start with the account security area for simple contact updates. If the change affects verified records, send a privacy request through chat or email so we can check the account before making edits.

Some requests may require temporary checks before account details are changed or shared. Access and eligibility depend on local law and are available where local law permits, so we handle each request case by case.

We keep records while they are needed for account service, security, disputes and legal duties. When those reasons no longer apply, we delete the record or separate it from direct account identity.