Rujukan Laman

Privacy Policy for winbest88

This page explains what we collect, why we keep it, and how you can ask us to change it.

Account dataDevice dataCookiesVerification records
winbest88 Privacy Policy for winbest88
REQUEST CHANNELS

Send Privacy Requests Here

If you want to access, correct, or delete certain data, start with the contact paths below.

Email request Send your privacy request to our support email with the account name, contact number, and a short description of what you want changed. We use that detail to verify the record before we act.
In-account message If you are already signed in, use the message area and attach a clear request. That keeps the trail inside the same account file and helps us match the right record faster.
Web form The web form suits access or correction requests when you want a structured path. Add the data category, the change you want, and a way for us to verify ownership before we reply.
DATA CARE

How We Handle Your Data

Our policy is written so you can see what we collect, how cookies work, how long records stay in our files, and who can see them.

Collection

We only collect details that help with account setup, security checks, service messages, and lawful record keeping. That can include contact details, device signals, and the pages or actions you used on the site.

Cookies

Cookies help us keep you signed in, remember language choices, and measure whether forms load correctly. You can clear them in your browser, but some saved settings may reset when you do.

Account security

We keep login checks, session timestamps, and change logs so we can spot unusual access and protect the account. If a password or contact route changes, we may ask you to confirm a matching detail first.

Retention

Records stay only as long as we need them for the stated purpose, legal duties, or a live request. After that, we delete or anonymise them according to our internal retention rules.

Request handling

When you ask for access, correction, or deletion, we look at the account record, confirm the link to you, and process the file through the privacy team. The response may be limited where local law requires us to keep a record.

Contact routing

If your question is not about privacy, we still route it through the right team first, then move it to the privacy contact if needed. That keeps the file in one place and avoids duplicate replies.

Privacy Questions You May Ask

These questions cover the main privacy rights and contact paths on this page. Each answer focuses on what we collect, how long we keep it, how cookies behave, and how to request access or correction. If local law affects a request, we handle it within that limit and may ask for a matching account detail before we release or change a record.

We collect the details you send when you open an account, contact us, or complete checks we need for security and legal record keeping. That can include contact details, device data, session logs, and file updates tied to your account.

Cookies help us keep your session active, remember display choices, and understand whether forms or pages load as expected. They do not give us more than the browser shares, and you can clear them anytime in your browser settings.

We keep records only for the time needed to run the policy, answer requests, meet legal duties, or protect the account. After that, we delete or anonymise them under our retention rules.

Yes. Send the request through our contact paths with the account details we need to match the file, and tell us what should change. We will respond after we verify the link to you.

We share data only when it is needed to operate the request, handle security, or meet a legal duty where local law permits. We do not share more than the task requires.

If a privacy request touches a record linked to Touch 'n Go, GrabPay, Boost dan FPX, we keep the details only to confirm the action or resolve the file, not for unrelated use.

Use email, the in-account message area, or the web form listed in the support section. Add the account detail and a short explanation so we can route the request without delay.