Rujukan Laman

Clear Privacy Terms Before You Join

Our Privacy Policy explains how we handle your account details, device data, cookies, payment records for Touch 'n Go, GrabPay, Boost dan FPX, and messages sent to our…

Account data useCookie choicesMalaysia payment recordsSupport contact path

Explore the lobby Read FAQ

What Our Privacy Policy Covers

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

This Privacy Policy explains what personal data we collect when you create an account, verify access, use the lobby, contact support, or make a payment request. We collect only what we need to run your account, protect wallet activity, answer your questions, and meet legal duties

1
that apply to us. Payment names such as Touch 'n Go, GrabPay, Boost dan FPX may appear in records so we can match a transaction to your account and resolve any mismatch. We may also record device, browser, location, cookie, and session data to help prevent
2
unauthorised access. Where access or eligibility is discussed, it depends on local law and is available where local law permits.

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

PRIVACY HELP

Contact Paths For Data Requests

If you want to ask about this Privacy Policy, update account details, or request a copy of data linked to your profile, contact us through the…

DATA CARE

How We Handle Your Privacy

We treat privacy as part of account operation, not a side page. The policy covers collection, use, storage, sharing, cookies, security checks, and deletion requests.

Data we collect

We collect account details, login records, device data, cookie IDs, payment references, and support messages. Each category has a purpose, such as verifying access, keeping the wallet accurate, or replying to your privacy request.

Cookie control

Cookies help keep you signed in, remember language choices, and detect unusual sessions. You can adjust browser settings, but some account functions may not work properly if essential cookies are blocked.

Account security

We use session checks, access logs, and verification steps to reduce unauthorised account use. If we see a login pattern that does not fit your normal activity, we may ask for extra confirmation.

Retention periods

We keep records only as long as needed for account operation, payment matching, dispute handling, legal duties, and security checks. When a record is no longer needed, we delete or anonymise it where possible.

Sharing rules

We share data only with service providers that help run account access, payment checks, support tools, security monitoring, or legal response. They receive the parts needed for that task, not open-ended access.

Change requests

You can ask us to correct details, check stored records, or assess whether deletion is available. We may keep certain records if required for payment proof, account safety, or legal duties.

Questions About Your Privacy Rights

These answers explain how the Privacy Policy applies when you open an account, use cookies, make payment requests, or contact our team. They are written for quick reading, but the full policy terms remain the main source for how we handle your data.

We collect details you provide, such as account name, contact data, payment references, support messages, and verification records. We also collect login times, device data, cookie IDs, and session activity for security and account operation.

Payment records help us match Touch 'n Go, GrabPay, Boost dan FPX transfers to your account, investigate mismatches, and answer disputes. We keep the reference data needed for these tasks and legal duties.

Yes, you can contact us through the account privacy channel and ask for eligible records linked to your profile. We may verify your identity before sharing data so another person cannot access your private account details.

You can request a correction if profile details are outdated or wrong. Some fields may need verification before we change them, especially where the detail is tied to payment matching, access checks, or legal records.

Cookies support sign-in status, language display, device recognition, and fraud checks. You can manage many cookies through your browser, although blocking essential cookies may affect account access or session security.

Use the privacy contact path inside your account or email us with your account ID and request type. Avoid sending wallet passwords, full banking details, or screenshots that show data we do not need.

Yes. When access or eligibility is discussed, it depends on local law and is available where local law permits. Our privacy handling also follows duties that apply to account records and payment activity.

Clear Privacy Terms Before You Join

Contact Paths For Data Requests

How We Handle Your Privacy

Data we collect

Cookie control

Account security

Retention periods

Sharing rules

Change requests

Questions About Your Privacy Rights

01 What personal data does dink2 collect?

02 Why do you keep payment records?

03 Can I ask for my account data?

04 Can I correct details in my account?

05 How does the cookie part of the policy work?

06 Who can I contact about privacy concerns?

07 Does local law affect account access?

Related Pages