Rujukan Laman

Open your account with privacy clarity

Live Baccarat, 5 Lions Dance, Football Studio, Cash Rocket, Mega Fishing and Pyramid Ramesses can create account records such as login time, device signal, wallet movement and cookie…

Malaysia data clarityCookie choicePayment privacyAccount security

Explore lobby Read FAQ

Explore how this policy applies

bgrich Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

Your privacy matters from the first account screen, so this policy sets out what we collect, why we need it and how long we keep it. When you create or access an account, we may process contact details, login records, device checks, wallet activity, KYC documents

1
where required and service messages tied to your account. We use that data to run the lobby, secure access, verify withdrawals, answer privacy requests and meet legal duties that apply to Malaysia access where local law permits. Payment names such as Touch 'n Go, GrabPay, Boost
2
dan FPX are used as context because wallet events may be recorded for reconciliation, fraud checks and dispute handling. We do not sell your account data, and we limit sharing to processors, payment partners and legal requests that need a lawful basis.

Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

CONTACT ROUTES

Check privacy contact paths

Privacy requests should reach the team that can see account and wallet logs, not a public comment thread.

Email privacy desk Send privacy questions, correction requests or deletion requests to our email channel with your account ID and contact number. We may ask for extra checks before releasing data or changing wallet-linked records.

Live chat handover Use live chat when you need help finding the privacy channel or raising a request from inside your account. Chat can verify basic details, then pass the case to the privacy team.

Account centre request Open the account centre to update contact details, cookie choices and security settings. For deeper privacy actions, submit a request there so the case stays linked to your login history.

DATA CONTROLS

Browse bgrich data handling controls

Privacy controls sit beside account security because the same records help us confirm access, prevent unauthorised wallet use and respond to your requests.

Account data collected

We collect details you provide, such as name, contact number and account credentials, plus records created during login, wallet movement and support contact. These records help us keep your account traceable and secure.

Cookies and devices

Cookies remember session status, language choice and basic device signals. You can adjust browser settings, but blocking every cookie may affect login, account verification and wallet pages tied to this policy.

Payment privacy

Touch 'n Go, GrabPay, Boost dan FPX events may create reference numbers, timestamps and reconciliation records. We use those details to match deposits, verify withdrawals and handle payment privacy questions.

Security checks

Login alerts, password resets and device changes may be logged so we can spot unusual access. If you ask about these logs, we confirm identity before sharing any account-linked details.

Retention periods

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

Change requests

You can ask us to correct contact details, update privacy preferences or explain a record tied to your account. Some payment or legal records may need to stay until the required period ends.

Discover privacy answers before joining

This FAQ focuses only on the Privacy Policy and how it affects your account data. It explains what we collect, why payment references appear, how cookies work and how you can ask for changes. If your question is about a specific wallet entry or login event, contact support from your account so we can match the request to your records.

It covers details you provide, login and device records, wallet activity, support messages, verification files where required and cookie data. The policy also covers payment references linked to Touch 'n Go, GrabPay, Boost dan FPX.

Payment records help us match deposits, verify withdrawals, answer disputes and detect unusual account activity. We keep only the details needed for those purposes, such as method name, reference number, timestamp and account link.

Yes. You can ask us to correct contact details, update account preferences or explain a record linked to your account. We may verify your identity first, especially when the request affects wallet or security records.

Cookies can remember login status, language choice and basic device signals. They help keep your session stable and support security checks. You can manage cookies in your browser, but some account features may be affected.

Access is limited to staff and processors who need the records for account support, security, payment reconciliation or legal duties. We do not sell your account data, and sharing requires a lawful reason.

Retention depends on the record type and reason for keeping it. Account, payment and security records may be held for service operation, dispute handling, audit needs or legal requests, then deleted or anonymised.

Access and eligibility depend on local law and are available where local law permits. This policy explains how we handle privacy records for Malaysia account access within the legal duties that apply to us.

Open your account with privacy clarity

Check privacy contact paths

Browse bgrich data handling controls

Account data collected

Cookies and devices

Payment privacy

Security checks

Retention periods

Change requests

Discover privacy answers before joining

01 What personal data does this Privacy Policy cover?

02 Why do you need payment records for privacy purposes?

03 Can I ask to change my account data?

04 Do cookies track my account sessions?

05 Who can see my privacy records?

06 How long do you keep my data?

07 Why does the policy mention local law?

Related Pages