Rujukan Laman

dv188 Privacy Policy For Malaysia

Your dv188 privacy choices cover account details, device signals, cookies, support chats and payment records from Touch 'n Go, GrabPay, Boost dan FPX.

ACCOUNT DATACOOKIE CHOICESREQUEST PATHSMALAYSIA SCOPE
dv188 dv188 Privacy Policy For Malaysia
REQUEST SUPPORT

Where To Send A Privacy Request

Privacy requests are handled through a clear path: tell us whether you need access, correction, deletion or an explanation about cookies and retention.

Access requests Ask us to confirm the account data we hold, explain its source and provide a usable copy where Malaysian law allows. Include the email or phone linked to your account so we can locate the right record.
Correction requests If a name, contact detail or account record is wrong, send the corrected value through support. We compare the request with account signals before changing a record, helping prevent another person from altering your profile.
Privacy support Use live chat or the support email shown in your account for questions about cookies, retention or a prior request. We record the case number and use it to keep follow-up in one thread, with the request history limited to support needs.
DATA PRACTICE

How We Handle Your Account Data

Our privacy work follows the data journey rather than a broad promise. We collect account, contact, verification and support details for a stated purpose, restrict access by role, record relevant actions and…

Data handling

We use account, contact, verification and support details for the purpose stated when collected, account administration and security. A new use is not added without a corresponding policy change or another lawful basis.

Cookie choices

Cookie records can retain language or session choices and help flag unusual browser activity. You can clear or restrict them in your browser, although some account functions may then need an extra check.

Account security

Login events, device signals and selected account actions may be assessed to spot access that does not fit your normal pattern. We may pause a request and ask for verification before releasing account data.

Retention period

We retain each category for the period linked to its purpose, an open support case or a legal duty. When that period ends, records are deleted, anonymised or placed beyond routine use.

Payment references

Touch 'n Go, GrabPay, Boost dan FPX references can appear in wallet records so a transaction query can be traced. We use each reference for matching and support, not as a reason to collect unrelated details.

Request route

Send a correction, access or deletion request through live chat or the support email on your account. State the record concerned; we may verify identity and explain any local-law exception before acting.

Questions About Your Privacy Choices

These answers clarify the practical choices behind the policy without replacing the wording that applies to your account. They cover what we collect, why payment references appear, how cookies work, when records may be removed and which checks protect a request. If Malaysian law gives a different right or process, that local rule applies where relevant. Use the contact route below if you need a case-specific reply.

We may collect your name, contact details, verification material, device and browser signals, cookie choices, support messages and transaction references. The exact categories depend on the service step, your settings and the legal requirements that apply in Malaysia.

Touch 'n Go, GrabPay, Boost dan FPX references help us match a wallet event with the correct account and answer a transaction query. We use the reference for reconciliation, security and support, while avoiding unrelated collection where the service flow allows.

Yes. Send an access request through live chat or the support email shown in your account, using the contact detail attached to it. After an identity check, we can explain the categories held and provide a copy when Malaysian law allows.

Tell support which detail is wrong, what the corrected value should be and how it appears in your account. We compare the request with existing account signals, then update the record or explain why a legal or security check must come first.

Cookies may remember language, session settings and consent choices, while device signals can help identify unusual account access. You can manage cookies in your browser. Restricting them may remove saved settings or prompt an additional account check.

Retention varies by category, purpose, open support case and legal duty. We keep a record only for the period needed for that reason, then delete it, anonymise it or place it beyond routine use when a longer period is not required.

Use the live chat or support email displayed in your account and state whether you need access, correction, deletion or clarification. Include a case number if you have one; we may verify identity and explain any local-law limit before replying.