Rujukan Laman

Privacy Policy for Malaysian Account Data

This Privacy Policy explains what we collect when you open an account, send a request, or use the site on mobile or desktop.

Account dataCookie useLocal lawRequest help
judi66 Privacy Policy for Malaysian Account Data
REQUEST CHANNELS

Where to Send Privacy Requests

If you want to ask about this policy, reach us through live chat, email, or the account form.

Email Us Write to our privacy mailbox with your account email, the change you want, and any date range that helps us locate the record. We reply after we check the request and the matching details on file.
Live Chat Use chat for quick questions about data use, cookie choices, or access requests. If the matter needs a deeper check, we move it into the same privacy queue and keep the thread linked to your account.
Account Form Send a form request when you need correction, deletion, or a copy of stored details. Add the account name and contact address so we can match the file without sending it to the wrong inbox.
DATA SAFEGUARDS

How We Handle Your Data

We store only what the policy needs, and we separate account records from marketing contacts where possible.

Collected Fields

We keep account contact details, login timestamps, device signals and request history so we can run the service, trace misuse and respond when you ask about your records.

Cookie Use

Cookies help us remember your session, chosen language and security state. They also let us spot repeated failures or unusual access. You can clear them in your browser at any time.

Security Checks

We watch for unusual logins, mismatched device data and sudden changes to contact details. When a check fails, we may pause the request and ask for extra verification before moving ahead.

Retention Window

Records stay only as long as we need them for service, dispute handling or a legal duty. After that, we remove, mask or archive them according to the rule that applies.

Access And Correction

You may ask for a copy of stored details or request a correction where local law allows it. Tell us the account email, the item in question and any dates that narrow the search.

Contact Channel

Send privacy requests to support, and mark the message clearly so it reaches the right queue. We verify the account first, then reply with the next step or the result you need.

Questions About This Privacy Policy

These questions cover what we collect, why we use cookies, how long records stay on file, and how you can ask for access or changes. We keep the answers tied to this page so you know where to send a request and what details help us verify it. If local law gives extra rights, we follow those rules for the account in question. When your request needs proof, we ask for the minimum needed.

We keep contact details, login records, device signals and request history. When you use Touch 'n Go, GrabPay, Boost dan FPX, we retain only the references needed to match the transaction and prevent mistakes.

Cookies help us remember your session, language choice and security state. They also let us spot repeated failures or unusual access. You can clear browser cookies at any time, though some parts may need them to stay signed in.

We use payment references to confirm the source and status of a request, then store them with the account file only for the time needed to settle it or meet a legal duty.

Retention depends on the reason we collected the data. Active account records stay while they are needed for service, then we remove, mask or archive them once the purpose ends and no legal duty remains.

Yes. Send the account email, the exact item you want checked, and any date range that helps us find the file. If local law permits, we can share a copy or update the record after verification.

Use live chat or email support, and tell us that the message is for a privacy request. We will route it to the right team, check identity where needed, and reply with the next step.

If local law changes what may be collected or stored, we follow the rule that applies to your account at that time. Any update to this page will explain the change in plain language.