Rujukan Laman

Open duit2u88 Privacy Policy

Your account data, wallet records, cookie choices and support messages are explained here so you know how duit2u88 handles privacy before you open your account.

Malaysia privacy scopeCookie choicesAccount data requestsTouch 'n Go context
duit2u88 Open duit2u88 Privacy Policy
CONTACT ROUTES

Check privacy contact paths

Privacy questions should reach the team that can see your account record, not a general inbox without context. Use live chat for quick identity checks, email for written requests, or wallet support when your question involves Touch 'n Go, GrabPay, Boost dan FPX references. We may ask you to confirm account details before sharing or changing any personal data, because privacy requests must protect you as well as answer you.

Team online

Live privacy chat

Open live chat when you need a quick privacy check on login records, cookie choices or account access. We will confirm your identity before discussing data tied to your wallet or activity history.

Email data request

Send an email request when you want a written record of what you asked us to view, correct or remove. Include your account name, contact email and the privacy action you want considered.

Wallet record help

Choose wallet support if your privacy question relates to Touch 'n Go, GrabPay, Boost dan FPX receipts. We check the payment reference, account match and any related support messages before replying.

ACCOUNT HANDLING

Manage account privacy controls

Our privacy work sits inside the same account flow you use to log in, verify wallet activity and ask for support.

Account data

We collect details you provide during account setup, support contact and wallet checks.

Game activity records

When you open tables or titles such as Auto Roulette, Aviator or Fan Tan, we may keep session records tied…

Cookie handling

Cookies help keep your session active, remember language and check whether pages load correctly.

Security checks

We monitor login attempts, password reset activity and device changes to protect your account data.

Retention periods

We keep personal data only for account operation, legal, security and dispute needs.

Correction requests

You can ask us to correct contact details, update account records or consider removing data that is no longer needed.

Browse Privacy Policy questions

These answers focus on how the Privacy Policy works for your account, wallet activity and support contact. They explain what we collect, why some records are kept, how cookies work and how to ask for access or changes. If your request depends on a legal requirement in Malaysia or another supported area, we will handle it where local law permits and explain the next step.

We collect the details needed to run your account, verify access and answer support requests. This can include contact details, login records, device signals, payment references, wallet activity and messages you send us.

Wallet records help match Touch 'n Go, GrabPay, Boost dan FPX activity to your account, resolve payment disputes and meet record duties. We keep only what is needed for those purposes and security checks.

Cookies help keep you logged in, remember settings and check whether pages work correctly. Some cookies are essential for account and wallet functions, while browser settings may let you block or clear others.

Yes. Contact us by live chat or email and ask for access to your account data. We will confirm your identity first, then explain what records can be shared under applicable law.

You can ask us to correct contact details or consider removing data that is no longer required. We may need to keep some records for legal, security or dispute reasons before deletion is possible.

We share limited data with payment and verification partners when needed to process wallet records, confirm references or resolve disputes. We do not sell your personal data to unrelated third parties.

Use live chat for quick checks or email for a written request. Include your account name, contact email and the privacy action you want, so we can route it correctly and reply after verification.