Rujukan Laman

Privacy Policy for Your Account Data

At lazabet888, we collect the details needed to open your account, keep your sign-in secure, and answer requests about records we hold.

Account dataCookie settingsRequest changesMalaysia law
lazabet888 Privacy Policy for Your Account Data
CONTACT OPTIONS

Send Data Requests Here

If you want access to your data, a correction, or a deletion request where local law allows it, start with the help form in your account or the chat box after you…

Help Form Use the form in your account for access or correction requests. We verify the owner before we act, so the reply is tied to the profile you control.
Live Chat Chat after sign-in if you want a quick check on a privacy point. We can tell you which record type to ask for and what proof may be needed.
Account Email Use the email address shown in your account if you want a written trail for a privacy request. We verify ownership before any change, then reply with the next step.
RETENTION AND ACCESS

How We Keep Records

We store account data behind access controls and log changes to your profile, device, and payment history so we can trace actions if something looks wrong.

Sign-in Records

We keep the login trail, device type, and session time so we can spot unusual access. That record also helps us answer a question about a login you do not recognise.

Cookies

Cookies remember language, page state, and saved settings. You can clear them in your browser, but some parts of the site may ask you to sign in again or reset preferences.

Wallet Traces

Deposit and withdrawal logs help us reconcile Touch 'n Go, GrabPay, Boost dan FPX activity, confirm what appears in your wallet, and resolve a payment question that comes back later.

Retention Window

We keep personal data only as long as needed for the account, legal checks, dispute handling, or fraud checks, then we delete, mask, or archive it according to the record type.

Change Requests

Use the contact path in your account to ask for access, correction, or deletion. We verify the profile first, then reply with the next step or explain why a field must stay.

Security Checks

We limit staff access to people who need it for support, record-keeping, or payment checks. If we spot unusual activity, we may pause the action until the account owner confirms the request.

Privacy Questions You May Ask

These are the questions we hear most when you open an account, change details, or check what we keep on file. If a request depends on local law, we will say so plainly and point you to the account steps that apply. The answers stay focused on data, cookies, retention, and contact paths so you know where to start without extra search.

We keep the details needed to run your account, such as sign-in data, device signals, cookie settings, and records tied to wallet actions or support requests. We do not keep more than we need for the stated purpose.

Yes. Send the request through the contact path in your account, and we will verify ownership first. Where local law allows, we share the data categories linked to your profile and the reason each set is kept.

Yes. Tell us which field is wrong, and add proof if we need it to check the change. We update the record we can control, then tell you what was changed and what stayed the same.

We keep records only while they serve account use, legal checks, dispute handling, or fraud checks. After that, we delete, mask, or archive them according to the record type and the law that applies.

Cookies store language and session state so your account area remembers basic settings. If you clear them, some preferences may reset, and you may need to sign in again before you can reach account pages.

Use the help form or chat after sign-in, then tell us whether you need access, correction, or deletion. We verify the account first so the request reaches the right record set.