Rujukan Laman

qkwin Privacy Policy for Malaysia Accounts

This policy explains what we collect, how we use it, who can see it, and how long we keep it.

MalaysiaCookiesRequestsRetention

qkwin Privacy Policy Scope

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

When you use the site in Malaysia, this policy applies to the details you enter, device and browser signals, cookie choices, support messages and payment references linked to Touch 'n Go, GrabPay, Boost and FPX. We use that data to run account access, answer requests, prevent

1
misuse and keep internal logs for security and service checks. We may also store message timestamps, IP address ranges and session markers so we can trace unusual login patterns without keeping more content than we need. We may share limited fields with service providers that host
2
our systems, send messages or process payments on our behalf, but only for the task they perform and only under the controls we set. Retention depends on the purpose, the record type and local law. Some records stay only as long as needed for account handling,
3
while others remain longer if tax, dispute handling or security checks require it. Where local law permits, you can ask for access, correction or removal through the contact paths below.

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

REQUEST PATHS

How To Reach Us

For access, correction or removal requests, use the same email linked to your account or send a message through the in-account path so we can match the right record.

In-account message Send your privacy request from the message area in your account so we can connect it to the correct profile. This path helps us confirm identity, attach a file if needed and keep the request trail in one place.

Email request You can also write from the email linked to your account and ask for access, correction or removal. We may ask for extra details if the message comes from a different address or lacks a matching reference.

Chat handoff If you start in chat, our team can collect the basics and move the request into the privacy queue. That keeps the process neat and lets us follow up through the same thread without losing context.

CONTROLLED HANDLING

How We Handle Your Data

We store only the fields needed for account access, support and payment checks, and we separate them from marketing lists where possible.

Data scope

We keep contact details, login history, support messages and payment references only when they are needed to run your account or answer a request. We do not collect extra fields just because they are available to us.

Cookie use

Cookies help us remember your session, language choice and browser state. They also help us spot repeated failed logins and keep the page working across mobile and desktop visits without asking you to reset each time.

Access control

Only staff and service partners with a task can see the smallest set of fields needed. Access is logged so we can check who handled a change, a support reply or a privacy request.

Retention timing

We keep records for the period needed to serve the account, meet tax or audit duties, handle disputes and meet local law. After that, we remove or anonymise them where possible and practical.

Change requests

You can ask for a copy, correction or removal through support. We may ask you to confirm your identity before any change so the right record gets updated and no other profile is touched.

Contact route

Use the same email linked to your account or the in-account message path so we can match your data safely. If a request is limited by law, we tell you what we can process.

Common Questions On Privacy

These questions cover the parts people ask us about most: what we collect, why cookies appear, how long we keep records and how to ask for changes. If you send a request from a different email, we may ask for more details before we act, so the right file is updated. Where local law permits, we can confirm what sits in your file, correct a mistake or remove parts that no longer need to stay, while keeping any record we still need for law or security.

We keep the fields needed to run access, handle support and trace payment activity, such as contact details, login logs, cookie choices and request history. We do not hold more than the task calls for, and we trim old fields where possible.

Cookies remember your session, language choice and some page settings, so you do not need to reset them each visit. They also help us spot unusual access patterns, reduce repeated logins and keep the page stable.

Yes. Send a request through support using the email linked to your account, and we will check identity before sharing anything. Where local law permits, we can provide the parts stored under your profile and explain the rest.

Send the correction through the same account channel and include the field that needs updating. We may ask for a matching document or detail so we can fix the right record and keep the rest of your file unchanged.

We keep records only as long as needed for account handling, security checks, tax duties, dispute handling or local law. After that, we remove them or turn them into anonymised logs where possible and allowed.

Use the in-account message path, chat handoff or the email attached to your account. Those routes help us match the file quickly and send the response back through the same channel without confusion.

qkwin Privacy Policy for Malaysia Accounts

How To Reach Us

How We Handle Your Data

Data scope

Cookie use

Access control

Retention timing

Change requests

Contact route

Common Questions On Privacy

01 What data do you keep from my account?

02 Why do cookies appear on my browser?

03 Can I ask for a copy of my data?

04 How do I change wrong details?

05 How long do you keep records?

06 Who should I contact about privacy?

Related Pages