Rujukan Laman

Privacy Policy for Your Malaysia Account

Our Privacy Policy explains how mrds66 collects, uses, stores and protects the personal data linked to your account, wallet activity, device sessions and support messages.

Account data clarityCookie choicesTouch 'n Go contextGrabPay, Boost dan FPXRights request path
mrds66 Privacy Policy for Your Malaysia Account
CONTACT PATHS

Three Contact Paths for Privacy Requests

Privacy requests need a clear route, not a sales reply. Use the contact channel that matches your account status, then include your registered phone number or email so we can locate the…

Account chat Open chat after signing in when your request concerns account data, wallet records or a recent security alert. The team can verify your session first, then route the privacy request without asking you to repeat every detail.
Privacy email Use the privacy email when you cannot access your account or need a written record of your request. Include your registered contact, request type and any payment reference from Touch 'n Go, GrabPay, Boost dan FPX.
Account form The account form suits correction and deletion requests because it captures the fields we need in one place. We check ownership before making changes, then tell you if any records must be kept for lawful reasons.
ACCOUNT CARE

Six Ways We Protect Account Data

Privacy work is handled through everyday controls in the account, wallet and support areas.

Account collection

When you open an account, we collect contact details, sign-in records and security markers needed to run your profile. We do not ask for unrelated personal data, and extra checks are used only when the account requires them.

Payment records

Payment data from Touch 'n Go, GrabPay, Boost dan FPX is used to match deposits, withdrawals, refunds and dispute checks to your account. Full payment credentials are not displayed inside support replies or public-facing screens.

Cookie controls

Cookies help keep your sign-in session active, remember language choices and detect unusual access patterns. You can adjust browser settings, but blocking some cookies may require repeated sign-ins or limit account-security checks.

Security checks

We use device data, IP records and login patterns to detect account takeovers, duplicate requests and payment mismatch risks. Access to these records is limited, logged and used for account safety rather than unrelated profiling.

Retention periods

Some records are deleted when they are no longer needed, while payment and security records may be kept longer for dispute handling or legal duties. We assess requests case by case before erasing account-linked data.

Rights handling

You may ask to access, correct or delete personal data, or raise a concern about how it is used. We verify identity first, then respond through the channel that keeps your account details private.

Privacy Questions Before You Join

These questions explain how our Privacy Policy applies before and after you create an account. They focus on personal data, cookies, account access, payment records and request handling for Malaysia. If your concern is specific to your account, contact us through the private support route after signing in.

We collect contact details, sign-in records, account settings, security markers and wallet activity needed to create and maintain your account. Extra identity details may be requested only when account checks, payment matching or legal duties require them.

Payment records are used to match deposits, withdrawals, refunds and disputes to your account. We keep transaction references, status, time and method, while sensitive payment credentials are handled by payment partners and not shown in support chats.

Our cookies focus on sign-in sessions, language choices, device recognition, fraud checks and site performance on mrds66.vip. If third-party tools are used, they are limited to service purposes described in this Privacy Policy.

Yes. You can request access to personal data connected to your account after we confirm your identity. Some records may be summarised or withheld where disclosure could affect security checks, another person’s privacy or legal obligations.

Send a correction request through account chat, privacy email or the account form. We may ask for supporting details before updating phone numbers, names, payment references or identity records, so the change is made on the right account.

You can ask for deletion, and we will assess the request against security, payment, dispute and legal record duties. Data that no longer needs to be kept will be removed or separated from active account use.

Access is limited to staff and service partners who need the data for account support, payment processing, security checks or legal duties. Internal access is role-based, and sensitive requests require extra verification before any change is made.