Rujukan Laman

Privacy Policy for Your ibet4u Account

Speed Roulette, Kingdoms Rise, Football Studio and Crash X sit behind an account flow that asks only for data we need to run access, wallet checks, security alerts…

Account data useCookie choicesPayment record carePrivacy request routes
ibet4u Privacy Policy for Your ibet4u Account
CONTACT ROUTES

Reach Us About Privacy Requests

Privacy requests should go through channels that let us verify you without exposing extra data. Send the same name, phone or email linked to your account, then describe whether you want access, correction, deletion or a copy of eligible records. We may ask for one more check before making changes, especially where wallet activity or withdrawal history is involved.

Team online

Email privacy desk

Email is suited to longer privacy requests, including access, correction or deletion. Include your account email and a short reason, but do not send card numbers, bank passwords or screenshots that show unrelated personal data.

Live chat handoff

Chat can point your request to the privacy desk after basic account checks. Use it when you need the right form, want to confirm receipt, or need help describing the records you want changed.

Account security queue

If you think your login, phone number or wallet record was used without permission, ask for the security queue. We can pause sensitive changes while we check device signals, recent sessions and payment references.

ACCOUNT CARE

Cookies, Retention and Account Safeguards

Our privacy work is tied to real account tasks: login checks, wallet reconciliation, session safety, cookie settings and request handling.

Account data collected

We collect account details you provide, such as name, contact method, login credentials and verification data. We also keep account activity needed to run sessions, process wallet actions and answer privacy requests accurately.

Payment record handling

Touch 'n Go, GrabPay, Boost dan FPX references help us match deposits and withdrawals with your account. We store transaction IDs, timestamps and status results, not private wallet passwords or banking login secrets.

Cookie controls

Cookies help remember sessions, protect logins and understand which privacy settings your device has accepted. You can adjust browser controls, though blocking some cookies may affect login flow or request verification.

Security checks

We use device signals, session history, password checks and wallet reference matching to reduce account misuse. If a change looks unusual, we may delay it until you confirm ownership through a safer channel.

Retention periods

Some records must stay for dispute handling, withdrawal verification, fraud prevention or legal duties. When those reasons end, we delete, anonymise or archive records with tighter access, depending on the record type.

Change requests

You may ask us to correct profile details, access eligible records or erase data where the law allows. We confirm identity first so changes are made for the account owner, not an outside person.

Privacy Questions Before You Join

Before you open an account, it is fair to ask what data we need and how you can control it later. These answers cover the practical privacy points around account setup, cookies, payment records, access requests and security checks, so you can decide what to share with us.

It covers data linked to your account, including contact details, login records, verification checks, wallet references, device signals, cookie settings and messages you send to us about your account or privacy rights.

Payment records let us match Touch 'n Go, GrabPay, Boost dan FPX activity to your wallet, confirm withdrawal requests and resolve disputes. We keep references and status results, not your private banking passwords.

Yes. You can ask for access to eligible account records through email or chat handoff. We verify your identity first, then provide what we can share under applicable law and security rules.

You can request correction for inaccurate profile details or deletion of eligible records. Some data may stay where needed for fraud prevention, payment disputes, withdrawal checks, tax duties or legal retention rules.

Cookies keep sessions active, remember privacy choices and help detect unusual account access. You can manage cookies in your browser, but blocking some may affect login, wallet checks or request verification.

We share limited data with partners that help run hosting, payment checks, security screening, messaging and analytics. They receive only what is needed for their task and must handle it under agreed safeguards.

Start with email for detailed requests or chat for routing help. Share the contact method linked to your account and the privacy action you want, then we will confirm identity before acting.