Rujukan Laman

brickbear888 Privacy Policy for Malaysia

Our privacy policy tells you what we collect, why we keep it, and how you can ask for access or correction.

Account dataCookie usePayment recordsLocal law

Browse Lobby Read FAQ

brickbear888 Data Use and Jurisdiction

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

This page sets out which data we handle, how we share it only with service providers that help us process requests, and when we may keep a record after closure. That can include contact details, sign-in history, device data, cookie preferences, and logs tied to Touch

1
'n Go, GrabPay, Boost dan FPX. We use those records to confirm identity, stop duplicate requests, repair transaction mismatches, and answer questions about access, correction, or deletion. If a right does not apply in your location, access or eligibility depends on local law and is available
2
where local law permits. We remove or anonymise data once the purpose ends, unless a longer hold is needed for dispute handling, fraud checks, or legal duty.

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

REQUEST ROUTES

How to Reach Our Privacy Team

To send a privacy request, use the route that matches your record. Registered email is the fastest way to confirm identity, the in-account message path keeps the thread tied to your profile, and the written route is there when you want a dated record. We may ask for extra proof before we disclose or change sensitive data, and we answer within the channel shown in your account.

Team online

Registered email

Send the request from the email linked to your account so we can match it quickly. We use that route for access, correction, deletion, and follow-up checks tied to identity.

In-account message

If you are signed in, use the privacy message path in your account area. It keeps the thread attached to your profile and helps us answer without mixing records across accounts.

Written request

For a dated paper trail, use the written route shown in your account area. We check the identity details first, then file the request and reply through the same contact channel.

CONTROLLED HANDLING

Data, Cookies, and Retention Controls

We keep privacy controls close to the account. Cookie settings store only the choices needed for the site to remember language and session preferences, while access logs help…

Data minimisation

We collect the contact, device, and transaction details needed to operate the account and answer privacy requests.

Cookie settings

Preference cookies remember language and session choices, while essential cookies keep sign-in and request handling working.

Sign-in security

Password rules, device checks, and session logs help us spot account access that does not match your normal pattern.

Retention period

We keep records only as long as needed for the stated purpose, then remove or anonymise them unless law, dispute…

Access requests

You can ask for a copy of your stored data and check whether any part needs correction.

Change requests

If you want deletion, correction, or a restriction on processing, send the request through the privacy route in your account…

Common Questions About Privacy

These are the privacy questions we hear most when you open an account, send a data request, or ask how long records stay on file. The answers below stay within the same policy rules used across the site: we only process what we need, we confirm identity before changes, and we follow the law that applies in your location. If access is restricted, it depends on local law and is available where local law permits.

It covers how we collect, use, store, and remove account data, cookie records, and payment traces linked to Touch 'n Go, GrabPay, Boost dan FPX. It also explains how you can contact us about access or correction.

We may keep contact details, sign-in history, device signals, cookie choices, and the records needed to check deposits or withdrawals. We do not keep anything without a clear account, security, or legal purpose.

Yes. Essential cookies keep sessions and request forms working, while preference cookies remember language and display choices. You can clear them in your browser, but some settings may need to be chosen again.

We keep each record only for the time needed to answer your request, maintain the account, or meet legal and dispute duties. After that, we delete or anonymise it when the hold ends.

Yes. Send the request through your registered email or the in-account privacy path, and we will check your identity before we release a copy or update the record. Some requests can be limited by local law.

Only the team handling the case and the service providers needed to verify identity or process the change will see it. We keep request logs so we can trace what happened and when.

We follow the rule that applies where you are. If a request cannot be completed in your location, we will tell you the reason and the next lawful option where local law permits.

brickbear888 Privacy Policy for Malaysia

How to Reach Our Privacy Team

Registered email

In-account message

Written request

Data, Cookies, and Retention Controls

Data minimisation

Cookie settings

Sign-in security

Retention period

Access requests

Change requests

Common Questions About Privacy

01 What does this privacy policy cover?

02 What data do you keep from my account?

03 Do you use cookies here?

04 How long do you store my data?

05 Can I ask for a copy or correction?

06 Who sees my privacy request?

07 What if local law differs from this page?

Related Pages