Rujukan Laman

Open what this policy covers

This page explains what we collect when you create an account, sign in, contact us, or move funds through Touch 'n Go, GrabPay, Boost dan FPX in supported…

Account dataCookiesSecurityLocal lawSupport
cikgu88 Open what this policy covers
REQUEST CHANNELS

Check ways to contact us

If you want to ask about access, correction, or a record we hold, use the contact path that matches your account details.

Email us Send your request from the account email, name the page or record you want checked, and add the change you want. We use that detail only to match the right file and answer you clearly.
Live chat If you need a faster reply, chat with us and say whether you want access, correction, or deletion. We may ask for a short identity check before we touch any private record.
Account request form Use the account request form when you want a copy of your data or a note added to your file. The form keeps the trail tidy, and our team replies through the same route.
DATA HANDLING

Explore how we handle your data

We keep the data needed for sign-in, device checks, payment tracing, and support history, then remove or anonymise it when the reason for keeping it ends.

Collection

We collect only what is needed to open and run your account: contact details, login events, device signals, support messages, and payment references. We do not ask for extra profile data unless the request or law requires it.

Cookies

Session cookies keep you signed in, remember language choices, and store privacy settings between visits. They help the page work properly, but they do not reveal your password or reach into other apps on your device.

Security

We protect sensitive changes with password checks, session expiry, and extra verification when the request looks unusual. Access is limited by role, so only staff who need the record for support or security can open it.

Retention

We keep personal data only as long as we need it for account service, dispute handling, fraud checks, or legal duties. After that, we delete or anonymise the record when our systems and the law allow.

Requests

You can ask for a copy, a correction, or deletion where local law permits. We will verify the request, process it through the same account thread, and tell you if any rule limits the change.

Contact

To change consent choices or ask how a record was used, contact us through support and include the account email. A request from Johor Bahru or anywhere else follows the same privacy process.

Discover common privacy questions

These questions cover what we collect, why we keep it, and how you can ask for changes. If your request affects account safety or a legal record, we may ask for a quick identity check before we make any change. That helps us protect your file and gives you a clear reply with the next step. We answer through the same contact route you used so the thread stays with your record.

We collect the details you give when you open an account, contact support, or confirm access, plus device and session data that help us keep the record accurate and reduce misuse.

Yes. Cookies keep your session active, remember your language choice, and store privacy settings. They do not give us your password, and you can change some browser controls if you want less tracking.

Yes. Send the correction through support with your account email and the exact field you want changed. We verify the request first, then update the record where the law and our systems allow.

We keep it only while it is needed for account work, support history, security checks, tax or legal duties, and dispute handling. After that, we remove or anonymise it when retention rules let us.

Only staff who need it for support, verification, security, or legal handling can access it. We limit access by role and keep a trail of sensitive changes so we can check unusual activity.

Use the support paths on this page and include your account email, the request type, and any relevant dates. If local law affects what we can share, we will explain the limit in our reply.