Rujukan Laman

Open your Privacy Policy choices

Account registration, wallet checks, cookies and support chats all create data records, so this Privacy Policy explains what we collect, why we use it, and how you can…

Account data explainedCookie choicesPrivacy requestsMalaysia support
iringgit9 Open your Privacy Policy choices
CONTACT ROUTES

Start a privacy request with us

Privacy contact should start from a channel that can verify you without exposing extra data.

Account chat Use live chat after login when your request needs account checks. We ask only for the details needed to find your profile, confirm control, and record what privacy action you asked us to take.
Email thread Send privacy questions to our email channel when you want a written thread. Include your username, registered mobile number, and the data topic; leave bank card images or unrelated files out of the message.
Web form The web form suits correction or deletion requests that need attachments. We check each file, mask unnecessary numbers, and reply with the next step once account ownership has been matched.
DATA CARE

Browse how your data is handled

We handle privacy work in the same flow as account operations: collect only what the task needs, limit internal access, secure login checks, and set retention around legal and payment duties.

Data we collect

We collect registration details, login records, device signals, payment references, and support messages so we can run your account and answer privacy requests. We do not ask for documents unless a check truly needs them.

Payment verification

When a Touch 'n Go, GrabPay, Boost dan FPX transaction is checked, we store the reference, status, time, and account match. Wallet balances outside our system are not read by our team.

Cookie use

Essential cookies keep your session from dropping while you read the policy or manage settings. Analytics cookies help us count errors and device types; you can clear browser data when you prefer a fresh session.

Account security

Account security checks use passwords, device patterns, one-time codes when triggered, and login alerts where available. If a login looks unusual, we may pause sensitive privacy changes until you confirm control.

Retention periods

Retention periods follow legal, payment, tax, dispute, and security needs. When records no longer serve those purposes, we remove them, anonymise them, or keep only a limited audit marker.

Change requests

You can ask us to correct, delete, or restrict certain data. We compare your request with account safety, payment history, and local law before we confirm what action can be completed.

Check your Privacy Policy questions

These answers explain how the Privacy Policy applies when you create an account, manage your wallet, browse from a mobile browser, or contact us about a data request. They are written for Malaysia, but your actual rights and our response steps can change when local law, payment duties, or account security checks require a different route. Use them before you send us a request.

We collect the details needed to create and protect your account, such as name, contact details, login records, device signals, wallet references, and support messages. Extra documents are requested only when verification cannot be completed another way.

For Touch 'n Go, GrabPay, Boost dan FPX, we record transaction references, status messages, timing, and account matches. That helps us trace payment issues without collecting more wallet data than the request or check needs.

Yes, you can ask for correction, deletion, or restriction through chat, email, or the web form. We verify account control first, then check whether legal, payment, tax, or security duties require us to keep certain records.

No. Cookies used by our site relate to session management, security checks, language choices, and page performance. They do not give us full access to your phone, contacts, photos, or apps outside the browser.

Access is limited to staff and service partners who need the data for account support, payment checks, security monitoring, legal duties, or privacy requests. We separate roles so a payment task does not expose unrelated support chats.

Retention depends on the record type and the reason it was collected. Payment references, dispute logs, and security alerts may stay longer than general support messages when law, tax, or account protection requires it.

Access and eligibility depend on local law and are available where local law permits. If a location rule affects your account or request, we explain what data can be used, changed, or withheld under that rule.