Rujukan Laman

Legal Rules For Your eclbet Account

eclbet sets account terms, privacy duties, cookie use and transaction record rules in one Legal page, with payment context for Touch 'n Go, GrabPay, Boost dan FPX.

Account termsCookie choicesData request pathMalaysia law context
eclbet Legal Rules For Your eclbet Account
CONTACT ROUTES

Three Legal Contact Paths

Legal questions need a clear route, so we separate privacy requests, account-term questions, and transaction-record checks.

Privacy request desk Use [email protected] when your request concerns personal data, cookie consent, correction of account details, or deletion where the law allows. Include your account email and avoid sending card or bank secrets.
Account terms help Use the support chat for questions about account terms, access rules, or a notice shown after login. We may ask for a ticket reference before discussing any record tied to your account.
Transaction record check For payment-related legal requests, send the date, amount, method, and receipt reference for Touch 'n Go, GrabPay, Boost dan FPX. We compare those details with wallet records before replying.
DATA HANDLING

Six Ways We Handle Legal Duties

Our legal duties do not sit apart from your account experience; they shape how we collect, secure, keep, and correct records.

Account data scope

We keep identity details, contact data, login records, wallet activity, and service messages where needed for account operation, legal duties, dispute handling, and security checks tied to your eclbet account.

Cookie control

Cookies help us keep sessions active, remember consent choices, and detect unusual access. Where a cookie is not needed for core account use, we record your choice and apply it to that browser.

Security checks

When a legal request involves personal data or wallet records, we verify account control before replying. This may include email checks, phone confirmation, or matching a payment receipt to account history.

Retention period

We keep records only for as long as needed for account operation, legal duties, dispute handling, audit checks, or payment reconciliation. When a record is no longer needed, we remove or anonymise it.

Correction requests

If your name, phone, email, or other account detail is wrong, you can ask us to correct it. We may request proof before changing records that affect access, identity, or payment matching.

Internal access

Only authorised staff can access account records, and access is tied to the task being handled. Legal, support, payment, and security teams see different record sets based on the request.

Legal Questions Before Account Access

These answers explain how our Legal page applies to your account, your data, and your requests. They are written for Malaysia readers who want to understand the rules before opening an account or contacting support. If your situation involves a legal deadline, court order, or regulator request, send the document through the contact route so we can assess it properly.

The terms on this page apply to account creation, access, wallet records, privacy requests, cookies, and account security. Access depends on local law and is available only where local law permits.

We use your data to operate the account, verify access, keep transaction records, answer legal requests, and protect the service from misuse. We do not ask for details that are not needed for those purposes.

Yes. Send the correction request through [email protected] with the account email and the detail you want changed. We may ask for proof before updating records linked to identity, access, or payments.

Payment records are kept so we can reconcile wallet activity, handle disputes, answer lawful requests, and confirm account ownership. We store the transaction details needed for those purposes, not your private app login credentials.

Cookies support login sessions, consent records, security checks, and service measurement. Where cookies are optional, your browser choice is recorded, and you can change browser settings if you want to manage them further.

Access is limited by work role. Support may see contact and ticket records, payment staff may see wallet references, and security staff may see login signals when investigating account safety concerns.

We may update access rules, account checks, record retention, or request handling to reflect local law. If a change affects your account, we will apply the current terms shown on this page.