Rujukan Laman

Privacy Policy for Your Account

manufc888 puts Classic Blackjack, Sic Bo Live, Football Studio and wallet access under one account, so this Privacy Policy explains the data we need before you open your…

Account data scopeCookie choicesTouch 'n Go contextMalaysia law wording
manufc888 Privacy Policy for Your Account
CONTACT ROUTES

Three Ways to Ask Privacy Questions

Privacy questions should reach the team that can see your account history without exposing it in public channels. Use the route that matches your request: chat for quick account checks, email for formal data requests, or the account centre when you are already logged in. We may ask for verification before changing, sharing, or deleting records because privacy protection also means keeping your account from being altered by another person.

Team online

Live chat

Use live chat when you need a quick privacy check tied to your current session. Our agent may ask for account verification before discussing login records, wallet history, or cookie settings.

Email request

Send privacy requests by email when you need a written reply about access, correction, deletion, or data use. Include your account name and the request type, but do not send full bank details.

Account centre

When you are logged in, the account centre is the safest place to check saved profile details. You can ask us to update inaccurate data after we verify the request.

DATA PRACTICE

Six Privacy Controls We Use

Our privacy work follows a simple rule: collect what is needed, restrict who can see it, and keep records only for the period required for account operation, safety checks, dispute handling, and…

Data minimisation

We ask for account details that support login, wallet checks, service messages, and security review. If a field is not needed for those purposes, we aim not to request it.

Cookie records

Cookies help keep your session active, remember basic preferences, and detect unusual access attempts. You can change browser cookie settings, though some account functions may not work correctly afterward.

Payment verification

Touch 'n Go, GrabPay, Boost dan FPX records are used to match wallet activity with your account. We keep confirmation details for reconciliation, dispute checks, and lawful record duties.

Account access

Only authorised staff and service partners with a defined task may handle privacy-related records. Access is logged where systems allow, and staff should not open account data without a work reason.

Retention timing

We keep data for as long as needed to run your account, answer disputes, meet legal duties, and protect the service. When those reasons end, records are deleted or anonymised where practical.

Correction requests

If your profile data is wrong, contact us through chat, email, or the account centre. We may request verification before changing records so another person cannot alter your account.

Privacy Questions Before You Join

Before you open an account, this section explains the privacy points most likely to matter: what we collect, why payment records are kept, how cookies work, and how to contact us about your data. The answers focus on account privacy only. If you need a specific action, contact support with your account name and the request type so we can route it correctly.

We ask for data needed to create and protect your account, such as login details, contact records, device signals, and wallet activity. We use it for access, verification, support replies, and account safety checks.

Payment records help us match deposits and withdrawals to the correct account, answer disputes, and meet lawful record duties. We use confirmation details for reconciliation rather than sharing full wallet data in public support channels.

Yes. If your account data is inaccurate, contact us through chat, email, or the account centre. We may verify your identity first, then update the record or explain why a change cannot be made.

Cookies keep you logged in, remember limited preferences, and help detect unusual access patterns. You can manage cookies in your browser, but blocking some cookies may affect account entry or security checks.

Privacy requests are handled by staff or service partners who need access to respond, verify, or process the request. We avoid exposing personal data in public channels and may move sensitive matters to email.

We keep account records while they are needed for service operation, support, payment reconciliation, dispute handling, safety checks, and legal duties. When retention reasons end, we delete or anonymise records where practical.

Yes. Account access and eligibility depend on local law and are available where local law permits. Privacy requests are still handled through our support routes, even when access checks require extra verification.