Rujukan Laman

Privacy Policy for Your Account Data

Clear account data rules, cookie choices and payment-record handling sit in one Privacy Policy so you know what daddywin88 collects before you open your account.

Account data scopeCookie choicesMalaysia privacy supportTouch 'n Go context
daddywin88 Privacy Policy for Your Account Data
PRIVACY HELP

Reach Us About Privacy Requests

Privacy questions deserve a clear route, not a long hunt through the lobby. Use the account help area when you are signed in, or send a message with your registered phone number and a short request summary. We may ask for identity checks before changing account data, because the same request path could affect wallet records and login access.

Team online

Live chat privacy desk

Ask our chat team for the privacy desk when you are signed in. We verify your account first, then route access, correction or cookie questions to the people handling data requests.

Account email request

Email is useful when your request needs attachments or a longer explanation. Include your registered phone number, the data area involved and whether you want access, correction or deletion considered.

Verification before changes

Before we edit sensitive records, we may confirm your login, payment reference or recent support contact. This protects your wallet history from changes requested by someone using the wrong details.

ACCOUNT CARE

Your Data Controls Inside daddywin88

We treat privacy as part of the account flow you use every day. That means login checks, cookie settings, payment references and support tickets are handled with defined access, retention and correction…

Data we collect

We collect account details you give us, device signals, login times, wallet activity and support messages. Game choices such as Speed Baccarat or Panda Fortune may appear in activity records when needed for account checks.

Cookie controls

Cookies help keep your session active, remember language choices and measure page errors. You can adjust browser settings, though some account functions may need essential cookies to confirm your signed-in session.

Wallet records

For Touch 'n Go, GrabPay, Boost dan FPX, we keep payment references, timestamps, amounts and status results. We use them to reconcile your wallet and answer transaction-related privacy questions.

Access protection

Login attempts, device changes and password reset requests create security records. These logs help us detect unusual access and confirm that privacy requests come from the account holder.

Retention periods

We keep different records for different periods, depending on legal, accounting, security and support needs. When a record is no longer required, we delete it or reduce it where practical.

Request handling

You can ask to access, correct or delete data connected with your account. We assess each request against verification results, legal duties and any live wallet matters before acting.

Privacy Questions Before You Join

Before you open an account, you may want to know what data is needed, who handles it and how you can ask for changes later. These answers explain the privacy points that come up most often around account setup, payment records, cookies, support messages and lawful access in Malaysia.

We collect the details needed to create and secure your account, such as registered contact data, login credentials, device signals and verification records. We also keep wallet and support records once you start using those areas.

Wallet records help us match Touch 'n Go, GrabPay, Boost dan FPX activity with your account balance and support requests. We keep references, timing, status and amount details, not your full bank login credentials.

Cookies may remember session status, language choices and page behaviour so your account works correctly. Some analytics data may show which lobby areas you opened, but we use it to maintain service quality and resolve errors.

Yes, you can ask us to correct account data that is wrong or outdated. We may request verification before changing sensitive details, especially if the change could affect wallet records or account access.

Retention depends on the record type. Security logs, payment references, support messages and verification data may be kept for different periods because legal, accounting and account-protection needs are not the same.

Access is limited to teams that need the data for account checks, wallet reconciliation, security, support or legal duties. We do not give every staff role the same level of access.

If access rules change, eligibility depends on local law and remains available where local law permits. We may adjust account checks, retention steps or service access to meet legal requirements.