Rujukan Laman

Privacy Policy for Your Malaysia Account

Our Privacy Policy puts account data, wallet records, cookies and support chats into plain terms before you open your account.

Account data useCookie choicesWallet record handlingPrivacy contact route
hantubet88 Privacy Policy for Your Malaysia Account
CONTACT ROUTES

Three Ways To Reach Privacy Support

Privacy requests work better when you send the right details the first time. We ask for your account name, registered contact, request type and a short description of what you want checked or changed. If identity checking is needed, we will ask only for what is required to match the account and protect your data from being released to the wrong person.

Team online

Privacy inbox

Email our privacy team through the address shown in your account area. Include your account name and the data request you want handled, such as access, correction, cookie queries or wallet-record clarification.

Live chat handoff

If you start in live chat, our team can move your privacy request to a secure follow-up route. Chat agents may ask account-matching questions before escalating the matter.

Profile message

You can send a request from your account profile after login. This helps us match your request to the right account without asking for extra documents too early.

ACCOUNT CARE

Six Data Practices We Use

Our privacy work is tied to the way your account actually runs. Login checks, game-session records, wallet references and support messages are handled with different access levels inside our team.

Collection limits

We collect account data that helps us create your profile, process wallet records and keep access secure. We avoid asking for extra personal details unless they are needed for account checks.

Cookie control

Cookies help remember your session, language preference and basic device signals. You can adjust browser settings, though some account pages may require session cookies to keep your login active.

Wallet privacy

Touch 'n Go, GrabPay, Boost dan FPX references are stored with timestamps and transaction status. We use them to confirm deposits, check withdrawals and answer wallet disputes.

Game records

Activity in Lucky Blackjack, Crash X or other rooms may create session records tied to your account. These records help settle account queries and protect against access misuse.

Retention checks

We keep account and wallet records only for as long as needed for service, legal, security or dispute purposes. Older records may be archived with tighter access controls.

Correction requests

If your contact details or profile data are wrong, send a correction request from your account or privacy inbox. We may verify identity before making the update.

Privacy Policy Questions Before You Join

These questions explain how the Privacy Policy applies when you create an account, use the wallet, read cookie prompts or contact us about your data. We keep the answers practical so you know what to send, what we check and how we handle account-linked records.

We collect data you provide during account opening, contact details, login records, device signals, wallet references and support messages. We use these records to run your account and handle privacy requests.

Payment references from Touch 'n Go and GrabPay are stored as wallet records with status, time and account links. We use them to confirm activity, resolve disputes and meet record duties.

Yes. Send the correction request from your logged-in profile or privacy inbox. We may ask matching questions before editing records so your account data is not changed by another person.

Some cookies keep your session active, remember basic preferences and help detect unusual access. You can manage cookies through your browser, but account pages may not work properly without required session cookies.

We keep personal data for the period needed to operate your account, handle wallet queries, meet legal duties and resolve disputes. When records are no longer needed, we delete or archive them.

Support messages are available only to teams that need them for account help, privacy requests, security checks or dispute handling. Internal access is role-based and may be logged for audit purposes.

Your privacy rights can be raised through our contact routes even when service access depends on local law. Availability of account features is where local law permits, but privacy requests remain reviewable.