Rujukan Laman

Your Privacy Policy Starts Here

livebett88 keeps account records, wallet activity, cookie choices and support messages inside one Privacy Policy so you can see how your data is collected, used and protected.

Account dataCookie choicesWallet recordsSupport requests
livebett88 Your Privacy Policy Starts Here
PRIVACY HELP

Reach Us About Privacy

Privacy questions deserve a direct path, not a generic queue. Use the contact option that matches your request so we can verify your account, find the…

Live chat privacy check Use chat when you need a quick status check on cookie settings, account access…
Email data request Send email when you want a copy, correction or removal request assessed in writing.
Security escalation Contact us through the security path if you suspect another person accessed your account.
DATA CARE

How We Handle Policy Duties

We write this policy around the records we actually handle: account details, wallet references, device signals, support messages and cookie choices.

Account records

We collect details you provide during account setup and later checks, such as contact data and verification markers. These records help us maintain account access, answer privacy requests and reduce unauthorised changes.

Wallet activity

Payment references from Touch 'n Go, GrabPay, Boost dan FPX are kept with wallet activity so we can match transactions, investigate mismatches and support records needed for lawful accounting or security checks.

Cookie controls

Cookies help remember session state, language choice and safety checks. You can adjust browser settings at any time, though some account pages may need essential cookies to keep sign-in and wallet screens working.

Access protection

We use device signals, sign-in timing and account-change records to detect unusual activity. When something looks wrong, we may pause sensitive actions until you confirm the request through a safer contact channel.

Retention checks

We keep records only for purposes described in this policy, such as account service, dispute handling, security checks and legal duties. When a record is no longer needed, we remove or reduce it where suitable.

Change requests

You may ask us to correct inaccurate data or assess deletion of eligible records. We explain the outcome in plain language, including any record we must keep for security, transaction or legal reasons.

Privacy Questions We Answer

These answers cover the practical parts of our Privacy Policy: what we collect, why we keep it, how you can ask for changes and what happens when security or local law affects a request. If your question involves your account, contact us from the registered channel so we can verify you safely.

We collect the details needed to create and protect your account, such as contact data, login records, device signals and verification markers. We also keep support messages if you contact us about access or privacy.

Wallet records are used to match deposits, withdrawals and account balances. References from Touch 'n Go, GrabPay, Boost dan FPX help us trace payment status, resolve mismatches and meet record duties where required.

Yes, you can ask us to assess a data copy request through the registered contact path. We verify your account first, then provide eligible records or explain why some details cannot be shared.

You may ask us to correct inaccurate contact or account details. We may request proof before changing sensitive records, especially where the change affects access, wallet activity or previous support history.

Cookies help keep you signed in, remember settings and support security checks. You can change browser settings, but essential cookies may still be needed for account pages, wallet screens and privacy request forms.

Retention depends on the record type and purpose. Account, wallet and security records may be kept while needed for service, disputes, fraud checks or legal duties, then removed or reduced where suitable.

Use live chat for quick questions or email for formal requests about access, correction or removal. We check account ownership before sharing details, and access or eligibility depends on local law where it applies.