Rujukan Laman

Privacy Policy for Your mba66vip Account

mba66vip keeps your account data, cookie choices and payment context tied to Touch 'n Go, GrabPay, Boost dan FPX in one privacy framework, so you know what we…

Malaysia privacy scopeCookie choice recordsPayment context onlyLocal law applies
mba66vip Privacy Policy for Your mba66vip Account
CONTACT ROUTES

Contact Paths for Privacy Requests

Privacy questions need clear contact routes, not a generic mailbox. Use the channel that matches your request so we can verify your account, find the relevant record, and answer without exposing data…

Privacy Helpdesk Send privacy requests through live chat or the help email shown inside your account. We check identity first, then route access, correction, cookie, or retention questions to the team handling data records.
Account Verification If you ask us to change account data, we may request matching phone, email, payment reference, or login date. This keeps your privacy request connected to you rather than another person with similar details.
Payment Data Queries For Touch 'n Go, GrabPay, Boost dan FPX references, share only the transaction time and reference shown by your wallet or bank. Do not send wallet passwords, security codes, or screenshots showing unrelated data.
HANDLING STANDARDS

Data Handling Around Turkish Blackjack Sessions

Our privacy work follows a simple order: collect what we need, use it for the stated purpose, restrict access, and remove or anonymise records when retention no longer applies.

Data Collection

We collect account identifiers, contact details, login records, wallet references, cookies, and support messages when they are needed for access, verification, transaction matching, or legal records. We avoid asking for unrelated personal data.

Cookie Controls

Cookies help remember sessions, language choice, device checks, and fraud signals. You can adjust browser settings, but some account security steps may need cookies to keep the session linked to your device.

Account Security

Login alerts, password resets, device patterns, and wallet matching help us detect account misuse. Access to these records is limited internally, and support staff see only the fields needed to answer your privacy request.

Record Retention

We keep transaction and account records for the period needed for service history, legal duties, dispute handling, and security checks. When a record is no longer needed, we delete it or anonymise it.

Limited Sharing

We share data with payment processors, verification partners, hosting services, analytics tools, and advisers only where needed. Each sharing path is tied to account operation, security, legal compliance, or your specific support request.

Correction Requests

You can ask us to correct contact details, account identifiers, or payment reference errors. We may need proof that the change belongs to you, especially when wallet records or withdrawal checks are involved.

Privacy Questions Before You Open an Account

The questions below focus on your Privacy Policy choices rather than game rules or account offers. They explain what data we collect, why we hold it, how cookies work, and how you can reach us if something needs changing. If your request involves eligibility or access, the answer depends on local law and applies only where local law permits. Use them before you open or update an account.

We collect account details, contact data, login records, device signals, wallet references, cookies, and support messages. Each category links to account access, security, transaction matching, service messages, or duties required by applicable law.

Payment references help match your wallet action to your account without storing full wallet credentials. For Touch 'n Go, GrabPay, Boost dan FPX, we keep reference numbers, status, time, and matching outcome.

Yes. Contact support from your account channel and tell us the data range you want. We verify identity before sharing any record, because privacy access should not expose your details to another person.

Send the correction request through live chat or the help email shown in your account. We may ask for matching phone, email, wallet reference, or login history before updating privacy records.

Cookies keep sessions active, remember language settings, and support device checks. You can manage cookies in your browser, but turning off some cookies may affect account access, security checks, or wallet matching.

We share only when a provider helps run account access, payment matching, hosting, analytics, verification, or legal handling. We limit the data shared to the task and expect the provider to follow our instructions.

We keep data for as long as needed for account history, transaction records, legal duties, security checks, and dispute handling. After that, we delete, anonymise, or separate records where the law allows.