Rujukan Laman

Privacy Policy for your winningw account

winningw keeps account registration, wallet records, cookie choices, device checks and support messages under one Privacy Policy so you can see what we collect, why we collect it…

Account dataCookie choicesWallet recordsSupport access

Browse Lobby Read FAQ

How we use account data in Malaysia

winningw Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

This Privacy Policy explains how we collect and use data linked to your account, wallet, device, gameplay records, support chats and identity checks. We use that data to create and protect your account, process wallet activity, confirm payment references, resolve support requests, keep fraud checks active

1
and meet legal duties that apply to our service. Access and eligibility depend on local law and are available only where local law permits. We do not sell account data as a product. When we share data, it is limited to payment processors, verification partners, game
2
suppliers, hosting providers, support tools or lawful requests, each tied to a clear operating need. If you ask for access, correction or deletion, we check the request and reply through the contact route you used.

Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

CONTACT ROUTES

Three privacy contact paths

Your privacy question should reach the right team without being mixed into game or promo chat.

Live chat privacy desk Use live chat when you need a quick explanation of what data is visible in your account area. We can point you to cookie settings, wallet records and current contact details after basic account checks.

Email data request Send an email request when you want a copy, correction or deletion check for account data. Include your account name, current contact address and the privacy action you want us to assess.

Wallet record help Contact wallet support if a Touch 'n Go, GrabPay, Boost or FPX reference needs a privacy check. We compare transaction identifiers, account ownership and support history before changing any stored record.

ACCOUNT CARE

Six ways we protect your data

Privacy works only when the account flow is handled carefully from first login to wallet checks and support follow-up.

Account collection

We collect the data needed to create your account, keep contact details current and link wallet activity to the right profile. Extra data should have a clear purpose, not sit in our systems without use.

Cookie choices

Cookies help us keep you signed in, remember device settings and measure whether pages load correctly. You can change browser cookie settings, but some account and security features may need cookies to work.

Payment records

Wallet records may include payment channel, amount, time, status and reference codes from Touch 'n Go, GrabPay, Boost dan FPX. We use these records to match deposits, verify withdrawals and answer account queries.

Access controls

Only staff with a work need should see account data, and privacy requests are checked before action is taken. That helps prevent an unrelated person from changing your email, wallet record or identity file.

Retention periods

We keep data while your account is active and for periods needed for payment checks, dispute handling, security monitoring or legal duties. After that, data may be deleted, anonymised or archived with tighter access.

Change requests

You can ask us to correct data that is outdated or wrong. We may need a fresh document or account confirmation before changing identity details, phone numbers, email addresses or wallet-linked records.

Privacy Policy questions before you join

Before you open your account, it is fair to ask what happens to your data and who can see it. These answers explain the Privacy Policy in plain words, including account records, payment references, cookies, correction requests and contact steps. If your request depends on local law, we will say so during the support exchange and handle the account action where local law permits.

We collect account registration details, contact data, login activity, device signals, wallet records, cookie choices and support messages. If verification is needed, we may also collect identity files to confirm account ownership and payment safety.

Payment records help us match deposits, verify withdrawals, resolve wallet queries and keep transaction history tied to the right account. We keep reference codes and status details only for service, security and legal needs.

Yes. Contact us by email or live chat and state that you want a copy of your account data. We may verify your identity first, then share available records through a suitable channel.

Yes. Send the correct detail and, where needed, proof that links it to your account. We check the request before changing email addresses, phone numbers, identity records or wallet-linked details.

Cookies may remember login status, device settings, language choices and page performance signals. They also help with account security checks. You can adjust browser settings, though some account tools may not work fully.

Support messages are available to staff who need them to answer your request, check account ownership or resolve a wallet issue. We do not open support history for unrelated tasks or casual viewing.

If access, eligibility or a privacy request depends on local law, we assess it against the rules that apply to your location. Our service is available only where local law permits.

Privacy Policy for your winningw account

Three privacy contact paths

Six ways we protect your data

Account collection

Cookie choices

Payment records

Access controls

Retention periods

Change requests

Privacy Policy questions before you join

01 What data does winningw collect when I open an account?

02 How are Touch 'n Go, GrabPay, Boost dan FPX records used?

03 Can I ask for a copy of my account data?

04 Can I correct data that is wrong?

05 Do cookies track my account activity?

06 Who can see my support messages?

07 What happens when local law affects access?

Related Pages