Rujukan Laman

How kwin99 protects Malaysia account data

Your account data, wallet records for Touch 'n Go, GrabPay, Boost dan FPX, and device signals are described here in plain language, so you know what we collect…

Account data explainedCookie choices coveredMalaysia payment recordsContact paths included
kwin99 How kwin99 protects Malaysia account data
CONTACT ROUTES

Contact us about your privacy requests

Privacy requests should reach the team that can trace account, wallet and device records without sending you through general lobby chat.

In-app privacy chat Use chat after logging in when your request involves account records, wallet entries or device sessions. The agent can confirm your identity, open a privacy case and tell you what proof is needed next.
Email data request Send privacy requests by email when you need a written trail. Include your registered contact, the date range, and whether the request concerns correction, access, deletion or payment-record clarification.
Wallet record help If your request relates to Touch 'n Go, GrabPay, Boost dan FPX, tell us the method and transaction time. We compare wallet logs with account records before sharing or changing stored data.
ACCOUNT CARE

How we handle data inside kwin99

Our Privacy Policy is written around the account flow you actually use: login, wallet activity, support contact, cookie settings and verification.

Data we collect

We collect account details, login signals, wallet records, device data and support messages when they are needed for account creation, identity checks, payment tracing, security monitoring or privacy request handling.

Cookie handling

Cookies help us keep your session active, remember language choices and understand basic site performance. You can manage browser cookie settings, though some login and security checks may need cookies to work.

Account security

We use access controls, verification steps and activity checks to reduce account misuse. If a privacy request asks for sensitive records, we confirm ownership before any data is shared or changed.

Record retention

We keep account, wallet and support records for the period needed to manage your account, meet legal duties, resolve disputes and trace transactions, then remove or anonymise records when retention is no longer needed.

Correction requests

If your name, contact detail or payment reference is wrong, ask us to correct it. We may request proof, compare internal records and confirm the change once the account match is clear.

Partner sharing

Payment partners and verification providers receive limited data only when needed for transaction checks, identity confirmation or legal compliance. We do not share full account profiles for unrelated use.

Privacy answers for Malaysia accounts

These questions cover the Privacy Policy choices you may care about before opening or managing an account. They explain what we collect, why payment records are kept, how cookies work, and how you can ask us to access, correct or remove data. For any request involving eligibility or access, local law applies and service is available where local law permits.

We collect the details needed to create and manage your account, such as contact data, login records, device signals and wallet activity. We also keep support messages when they help answer privacy or account requests.

Payment records help us confirm account ownership, trace deposits or withdrawals, resolve transaction questions and meet legal duties. We keep only the details needed for those purposes, not unrelated wallet activity outside our service.

Yes. Contact us through chat or email and state that you want account data access. We will verify ownership first, then prepare the relevant records we can share under applicable law.

Yes. If your registered name, contact detail or payment reference needs correction, send the accurate detail and any proof we request. We check the account match before changing stored records.

We keep records for as long as they are needed for account management, payment tracing, security checks, legal duties and dispute handling. When those reasons no longer apply, records are removed or anonymised.

Cookies store session and preference data, and they help us detect unusual access. You can adjust browser settings, but disabling some cookies may affect login, verification or account-security functions.

Only staff with a work reason can access relevant records, such as support, payment checking, security or privacy handling. Access is limited by role, and sensitive requests need verification before action.