Rujukan Laman

Privacy Policy for your mamibet account

Classic Blackjack, Pyramid King, Football Studio and Aviator sit behind one account, so our Privacy Policy explains the account data, device signals and payment records we collect before…

Account dataCookie choicesMalaysia contact routeTouch 'n Go records
mamibet Privacy Policy for your mamibet account
CONTACT ROUTES

Three ways to raise privacy requests

Questions about this policy need a clear route, not a long search. Use the contact path that matches your request, and include enough account detail for us to locate the record without asking for more than needed. We may verify your identity before sharing data, changing account fields or discussing wallet records. If your request involves payment evidence, keep full card or bank details out of screenshots unless we ask for a safer version.

Team online

Live chat privacy desk

Open live chat from your account area and ask for privacy help. We may confirm your profile, then explain how to correct account fields, manage cookies or raise a data access request.

Email data request

Email the privacy team through the contact address shown in your account. Include your username, registered mobile number and the request type so we can match the message without exposing extra data.

Wallet record check

If a payment record looks wrong, contact us before sending screenshots in chat. We will ask for the transaction reference from Touch 'n Go, GrabPay, Boost dan FPX only when needed.

DATA HANDLING

Six privacy checks in our account flow

Handling privacy properly means checking data at each point where your account creates a record.

Data collection

We collect registration fields, contact details, login records and wallet references that are needed to run your account. Extra data is requested only when a verification, dispute or privacy request needs it.

Cookie control

Cookies help keep your session active, remember language choices and measure site performance. You can clear browser cookies, but some account security checks may run again when you return.

Payment records

Payment references from Touch 'n Go, GrabPay, Boost dan FPX are kept with your wallet history so we can reconcile failed transfers, verify withdrawals and answer privacy queries about financial records.

Device security

We record device type, IP address and session events to detect unusual access, account takeovers and repeated failed logins. These signals support account safety without changing your privacy rights.

Retention checks

We keep account and wallet records for legal, tax, dispute and security reasons, then assess them on a planned cycle. When a record is no longer needed, we remove or anonymise it.

Correction requests

If your name, mobile number or account field is inaccurate, contact us from your verified account route. We may ask for proof before changing data linked to payments or withdrawals.

Privacy Policy questions before you join

Before you open an account, you should know what happens to your data and how to reach us if something needs changing. These answers explain the privacy points we hear about most often: account records, cookies, payment references, data access, retention and local access rules. They are written for your account relationship with us and should be read together with the full policy on mamibet.im.

We collect your registration details, contact fields, device signals, login times and wallet references. For payments, records can include Touch 'n Go, GrabPay, Boost dan FPX transaction references and verification status.

No. We do not sell your personal data. We share it only with service providers that help run account access, payment processing, security checks, hosting, customer contact or legal requests.

Cookies help your browser keep a session, remember basic settings and support security checks. Some cookies are needed for account access, while analytics cookies help us understand errors and page performance.

Yes, you can contact us through your verified account route and ask for a copy of personal data linked to you. We may verify your identity before releasing any record.

Send a request from the contact route shown in your account and explain which field is wrong. For payment-linked changes, we may ask for supporting proof before updating the record.

We retain records to meet legal, tax, dispute, security and account duties. When those reasons no longer apply, we assess whether the data can be deleted, anonymised or kept in limited form.

If access or eligibility is discussed, it depends on local law and is available only where local law permits. Privacy requests remain available through our contact routes even if access rules change.