Rujukan Laman

Privacy Policy for Your Malaysia Account

wosbet puts account privacy, wallet checks and cookie choices in one policy before you open your account; we explain how data supports your lobby, Touch 'n Go, GrabPay…

Account data useCookie choicesWallet privacyMalaysia access terms
wosbet Privacy Policy for Your Malaysia Account
HELP CHANNELS

Privacy Help for wosbet Account Holders

Privacy questions should reach the right team without making you repeat account details in public spaces. Use the contact path inside your account when you can, because it lets us match your request to the correct wallet, device and login records. If you cannot access your account, send only the details needed to identify it. We may ask for extra checks before changing data, sharing a copy, or closing a request.

Team online

Account chat

Use the chat inside your account for correction requests, cookie questions, or wallet record checks. The session lets us confirm you without asking for more personal data than needed.

Email request

If you cannot log in, write to the address shown on wosbet.fun with your account name and request type. Do not send full card, bank or identity images unless we ask.

Wallet support

For Touch 'n Go, GrabPay, Boost dan FPX privacy questions, include the payment name, date and reference shown in your account. We use those details to locate the record.

ACCOUNT CARE

Data Controls Inside Your Account

Your privacy settings sit beside the account tools you already use, so you can ask for changes without leaving the service. We keep login, wallet and support records in separate access groups.

Data collected

We collect account details, login records, device signals, wallet references and support messages. Game choices such as American Roulette or Gems Bonanza may create activity logs linked to your account.

Cookie use

Cookies help remember your session, language choice, device checks and account safety prompts. You can adjust browser settings, but some account and wallet functions may need essential cookies to work.

Payment records

Touch 'n Go, GrabPay, Boost dan FPX references are used to match deposits, withdrawals and disputes. We store only the record needed for account checks, reconciliation and legal requests.

Account security

We check passwords, device changes, repeated login errors and unusual wallet activity. If a pattern looks risky, we may ask for confirmation before allowing data changes or withdrawal requests.

Retention periods

We keep records while your account is active and for a limited period after closure when required for disputes, accounting, security checks or legal duties. Unneeded records are deleted or anonymised.

Change requests

You can ask us to correct, export or delete eligible data. We first verify the account owner, then explain what can be changed, what must stay, and why.

Malaysia Privacy Questions Before You Join

These answers explain how the policy works before and after you open an account. They cover account data, wallet records, cookie choices, correction requests and location-based access. If your question involves a specific transaction or login, contact us from inside your account where possible. That keeps the request linked to the correct record and reduces the need to share extra data.

We collect the details needed to open and secure your account, such as contact data, login credentials, device signals and account activity. We also keep support messages connected to privacy or wallet requests.

Payment data helps match deposits and withdrawals to your account, handle disputes, and meet record duties. Touch 'n Go, GrabPay, Boost dan FPX references are stored with access limited to relevant teams.

Cookies keep your session active, remember basic account settings, and support security checks. Blocking all cookies may affect login, wallet checks or game access because some cookies are needed for core account functions.

Yes. Contact us from your account and tell us what should be corrected. We verify the request first, then update eligible records or explain why a record must remain unchanged.

We keep data while needed for account use, wallet records, support, security checks and legal duties. When a record is no longer needed, we delete it, anonymise it or restrict access.

Only teams with a work reason can access those records, such as support, payments, security or compliance staff. Access is logged, limited by role, and used for the request or check involved.

Yes. Account access and eligibility depend on local law and are available where local law permits. Location checks may use device, network or account data to apply those rules.