Rujukan Laman

Open your ezspin2 privacy choices

Our Privacy Policy explains how account data, device signals, cookies, and payment references for Touch 'n Go, GrabPay, Boost dan FPX are collected, used, protected, and updated on…

Account data scopeCookie controlsTouch 'n Go contextMalaysia request path
ezspin2 Open your ezspin2 privacy choices
CONTACT ROUTES

Check your privacy contact routes

Privacy questions need a clear route, not a generic inbox. Use the contact path that matches your request so we can identify the account, confirm ownership, and answer without exposing private details…

Privacy chat For quick policy questions, open live chat and ask for privacy help. Keep bank screenshots cropped to reference lines only, and do not post passwords, full card data, or one-time codes.
Email requests Send detailed correction, deletion, or access requests by email so our team can track the timeline. Include your account name, registered contact, request type, and any payment reference linked to the issue.
Wallet query link If your privacy question involves Touch 'n Go, GrabPay, Boost dan FPX records, contact wallet support first. We separate payment matching from public account activity and escalate data requests when needed.
ACCOUNT DATA

Manage data requests with our team

Our policy work is tied to how the account actually runs: sign-in checks, cookie settings, payment matching, support transcripts, and security alerts.

Data collected

We collect account identifiers, login records, device data, cookie choices, support messages, and payment references when needed to run the account. Sensitive documents, if requested, are handled through controlled channels rather than open chat threads.

Cookie controls

Cookies help keep sessions active, remember language choices, detect repeated failed logins, and measure page issues. You can change browser settings, but some security and account features may not work as intended.

Access checks

When you sign in, we compare device signals, password status, and session history to spot unusual access. If a check looks risky, support may ask you to confirm details before account data is shown.

Retention timing

We keep account and wallet records only as long as needed for service records, dispute checks, security logs, and legal duties. After that, data is deleted, anonymised, or kept in restricted archives.

Payment privacy

Touch 'n Go, GrabPay, Boost dan FPX references help us match wallet activity to your account. We do not need to display full bank details on public pages or routine support replies.

Change requests

You can ask us to correct contact details, update cookie choices, or consider deletion where local law allows. We verify identity first so another person cannot change or remove your data.

Browse privacy answers before you join

Before you open an account, you may want to know what our Privacy Policy means in day-to-day use. These answers explain data collection, cookies, payment references, access controls, retention, and request handling in plain terms. If your case involves a specific account, contact us through chat or email so we can check it safely. We answer based on the details you provide and the rules that apply to your location.

We collect the details needed to create and protect your account, such as contact data, login records, device signals, cookie choices, support messages, and wallet references linked to Touch 'n Go, GrabPay, Boost dan FPX.

Payment references help us match deposits and withdrawals to the correct account, answer wallet questions, and check disputed transactions. We use the reference data for account operations, not for public display on the site.

Yes. Send the correction request through chat or email, and include the account name plus the field you want changed. We verify identity before any update so your data is not altered by another person.

Cookies remember session status, language settings, fraud checks, and page performance signals. You can adjust them in your browser, but blocking every cookie may affect sign-in, account safety checks, or wallet pages.

Support messages are available only to team roles that need them to answer your request, investigate account issues, or record a decision. We ask you not to send passwords or one-time codes in chat.

Retention depends on the data type, account activity, dispute needs, and legal duties. We remove, anonymise, or restrict data when it is no longer needed for the reason it was collected.

You can request deletion where local law allows. We may need to keep certain records for security, transaction history, dispute checks, or legal duties, and we will explain any limit that applies to your request.