Rujukan Laman

How Our Privacy Policy Works

Our privacy policy tells you what we collect when you open an account, use a wallet path or send a support message, and why we keep it.

MalaysiaCookiesAccessRetentionLocal Law
judibos88 How Our Privacy Policy Works
REQUEST PATH

Where to Send Privacy Requests

If you want to check, correct or close a record, send the request from the email linked to your account or use the contact form in the footer. We route privacy cases to a small team, ask for enough detail to verify ownership, and keep the reply attached to the same thread. That way you do not have to repeat the same facts every time you follow up.

Team online

Account message

Use the message thread tied to your account and say which record you want checked, corrected or removed. We use that link to verify ownership before any change is made.

Support form

If email is easier, send the request through the support form with your registered contact address. We record the case, confirm what you want and pass it to the privacy team.

Written reply

When your request needs more detail, we answer in writing so you have a clear trail. That helps when you later ask for an update, correction or copy of the same record.

HANDLING RULES

How We Handle Data Safely

We limit who can see your personal data, payment logs and cookie records. Staff only open the parts needed to solve a request, check a transaction or protect the account from misuse.

Data scope

We collect the details needed to open, verify and maintain your account, plus device and session logs that help us spot misuse, fix errors and answer your request without asking for the same facts again.

Cookie choices

Cookies store language, session and consent settings so the page remembers your preference on a later visit. You can clear them in your browser, and the next session starts with fresh settings.

Payment records

When a transfer runs through Touch 'n Go, GrabPay, Boost dan FPX, we keep the trail needed for reconciliation, dispute handling and legal checks. We do not hold extra notes that are unrelated to the transfer.

Account security

Password checks, session timeouts and device flags help us stop unauthorised access. If something looks unusual, we may pause the session and ask you to confirm ownership before access continues.

Retention period

We keep records only as long as needed for account operations, dispute handling and local legal duties. After that, we delete or anonymise them on a schedule set by the policy team.

Change requests

You can ask to access, correct, restrict or close certain records by contacting support. We verify your identity first, then explain what can be updated or shared under local law.

Questions About Your Privacy Rights

These questions focus on the records we keep, the choices you can make and the limits set by local law. If you want access, correction or deletion, start with the contact path above and use the email linked to your account. We will verify ownership, check what can be shared and explain any record we must keep for legal or operational reasons.

We keep the details needed to open and maintain your account, such as contact data, login events, device signals, support messages and payment records. We do not ask for more than the task needs, and we limit access to staff who need it.

Yes. Send an access request through the support path above and use the email linked to your account. After we verify ownership, we will share what local law allows and explain any record we must keep for legal reasons.

Cookies mainly remember session, language and consent settings. Some logs may show how a page was used, but we keep that data in line with the policy and do not use it for unrelated purposes.

We keep each record only for the time needed to run the account, settle disputes and meet local legal duties. Once that period ends, we delete or anonymise the data on a scheduled cycle.

Only staff and service partners who need the data for account work, support handling, payment checks or security tasks can see it. Access is limited by role, and every request is handled under local law.

Send the request through the support channel above, say which record needs attention and use the email tied to your account. We verify ownership first, then update what we can or explain any limit under local law.

When access or eligibility is discussed, it depends on local law and is available where local law permits. If a request cannot be completed, we will tell you which part is restricted and why.