Rujukan Laman

Legal terms for Malaysia accounts

Legal terms sit in one place so you can check what applies before you open an account or send a request.

MalaysiaLocal lawAccount termsData use

How our policy applies here

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

We set this policy for accounts used in Malaysia, and it applies only where local law permits. If a local rule is more specific, that rule comes first. This page explains how we collect and keep account data, how we use cookies and device signals, how

1
we verify identity when a request needs it, and how we handle complaints tied to deposits, withdrawals, or access changes. Payment names such as Touch 'n Go, GrabPay, Boost dan FPX may appear in your activity log, and we keep those entries for reconciliation, fraud checks,
2
and support follow-up. You can ask for a copy, a correction, or a clearer explanation from the contact path listed here, and we will point you to the clause that matches your case. When a rule changes, we update the page and keep the new date
3
visible.

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

CONTACT PATHS

How to contact us on policy

If you need help with a policy question, send it from the channel that matches your account activity so we can locate the right record faster.

In-account chat Open a chat from your account when you need a quick read on a clause, a record, or a correction request. The conversation stays linked to your profile, which helps us answer without making you repeat the same details.

Policy email Use email when you want to send a longer request, attach a screenshot, or ask for a written copy of a policy point. We keep the thread so you can track what was answered and when.

Support form Send the form if you want your request routed to the right team on the first pass. It works well for access checks, changes to stored details, and any dispute that needs a clear paper trail.

DATA RECORDS

How we handle your records

We keep policy handling tied to your account trail, not loose notes. Access logs, cookie settings, message history, and change requests are stored only for the time needed to handle support, security…

Data trail

We link data handling to a clear account trail, not loose notes. Login time, request type, and support messages are stored only when they help us process the account, then kept or removed under our retention rules.

Cookie settings

Cookies keep the page state, language, and session stable so your next visit starts in the right place. We also use a few signals to spot unusual access, and we can explain the categories tied to your account.

Account security

If a request looks sensitive, we may ask for a fresh verification step before acting on it. That extra check helps us avoid accidental changes to the wrong profile or to records that belong to another account.

Retention window

We keep records only for the time needed for support, security checks, dispute handling, and legal duties. After that, the data is archived or removed according to the retention rules that apply to your account.

Change requests

When you ask for a correction, add the detail that needs changing and any proof that supports it. We will compare it against the account record and tell you whether we can update it or must keep the original.

Contact route

Use the channel that matches the record you want changed: in-account chat for quick checks, email for written proof, or the form for tracked requests. That keeps the request attached to the correct account file.

Common questions about account policy

These answers cover the parts people ask about most: which law applies, how data is used, how to request changes, and what happens when a clause needs extra verification. If your situation is tied to a specific account or request, use the contact channel inside that account so we can check the right record and reply under the correct policy path.

The terms that apply depend on local law and the place where you open and use the service. If a rule is not allowed where local law permits, we do not apply it to that account.

We use account data to run the service, confirm requests, handle support, and keep a record of changes. Where needed, we also use it for security checks, dispute handling, and legal duties tied to the account.

Yes. Send the request from your account so we can verify it against the right profile, then we will share the record we can lawfully provide or explain why a part must stay private.

Cookies and device signals help us remember your session, keep the page working, and spot unusual access. You can ask which categories are active on your account, why they are used, and request a clearer explanation of each one.

We keep records only as long as they are needed for support, security, dispute handling, and legal duties. After that period, they are archived or removed under our retention rules and local law.

Use the in-account channel or email listed here, include the detail you want changed, and add any proof that supports it. We will check the request against the record before making any update.

Start with in-account chat if the question is tied to your current profile. If you need a written trail, use email or the form so the request stays attached to the right case.

Legal terms for Malaysia accounts

How to contact us on policy

How we handle your records

Data trail

Cookie settings

Account security

Retention window

Change requests

Contact route

Common questions about account policy

01 Which law applies to my account?

02 How do you use my data?

03 Can I ask for a copy of records?

04 How do cookies fit into this?

05 How long do you keep records?

06 How do I request a correction?

07 Who should I contact first?

Related Pages