Rujukan Laman

betcity Privacy Policy For Malaysia Accounts

This Privacy Policy explains what data we collect when you create or use a betcity account in Malaysia, including contact details, device signals, account checks, cookie choices and…

Malaysia account dataCookie choicesPayment record careAccess where law permits
betcity betcity Privacy Policy For Malaysia Accounts
PRIVACY HELP

Privacy Help Through Local Channels

Privacy questions should go through channels that can verify your account safely. Use account chat when you can log in, email when you need a written request trail, or the help form when account access is blocked. Please avoid sending full payment screenshots unless we ask for them, because we may only need the transaction reference and account name to assess your request.

Team online

Account chat

Use account chat for a privacy question tied to your profile, wallet history or cookie choices. We may ask for proof that you control the account before we discuss personal data.

Privacy email

Send privacy requests through the email address shown in your account area, using the same contact detail linked to your profile. Include the exact change or copy request you want us to assess.

Access help form

If you cannot access your account, use the help form and describe the device, phone number or email linked to it. We separate access recovery from privacy requests until identity checks are complete.

ACCOUNT SECURITY

How We Care For Your Data

Privacy work is handled through set account processes rather than loose message threads. Our team checks identity before disclosing records, limits access by role and keeps wallet references separate from general support…

Data we collect

We collect data you give us, such as name, contact details and account credentials, plus technical logs from your device. We use it to run your account, check access and meet record duties.

Cookie choices

Cookies help us remember language, session status and security warnings. You can clear them in your browser, but some account features may ask you to log in again after cookies are removed.

Login checks

When a login looks unusual, we may check device details, IP data and recent account actions. These checks reduce account takeover risk while keeping the privacy check tied to your profile.

Payment records

Payment records for Touch 'n Go, GrabPay, Boost dan FPX show transaction references, status and timing. We use them to reconcile your wallet and answer privacy questions linked to financial records.

Record retention

We keep records only for operational, legal and dispute needs, then reduce or remove them when those needs end. Some wallet or identity records may stay longer if local law requires it.

Request handling

You can ask us to correct details, provide a copy of your data or explain how a record is used. We assess each request against account safety, local law and identity proof.

Malaysia Privacy Questions Before You Join

These answers cover the privacy points we are asked about most before and after account opening. They explain what data is collected, why payment references are kept, how cookies work and how you can contact us about a record. If your request involves account access or legal eligibility, the outcome depends on local law and available verification.

We collect the details needed to create and protect your account: contact data, login credentials, device logs, cookie IDs and wallet records. Payment records may include Touch 'n Go, GrabPay, Boost dan FPX references.

They help us match your wallet activity with actual payment status, answer account questions and handle dispute checks. We keep only the transaction details needed for those purposes and related legal duties.

Yes. Contact us through account chat, email or the help form and tell us what needs correction. We may request identity proof before changing details that affect access, wallet records or security.

Cookies support login sessions, language settings, fraud checks and preference storage. If you block or clear them, some parts of your account may ask for fresh login or repeat checks.

Only trained team members who need the request for their role can assess it. We avoid sharing your data outside that process unless law, payment reconciliation or account safety requires it.

Retention depends on record type. Chat logs, cookie records, identity checks and payment references follow different timelines, because each supports a different operational or legal need. You can ask about a specific record.

Yes. Access, eligibility and some data rights depend on local law and are available where local law permits. If a request conflicts with legal duties, we explain what we can do instead.