Rujukan Laman

Open with clear privacy terms

Before you open an account, this Privacy Policy explains how iscr2u collects, uses, stores and protects data linked to your account, wallet, device and support contact.

Account data controlCookie clarityMalaysia law checksWallet record access
iscr2u Open with clear privacy terms
CONTACT ROUTES

Check privacy contact paths

Privacy questions should reach the right desk quickly, especially when they involve account access, wallet records, or changes to your personal details.

Privacy email Send data access, correction, deletion, or consent questions through the privacy email shown inside your account area. Include your registered phone or email, but do not send passwords or full card details.
Account help desk Use live support when your privacy concern is tied to login, device access, wallet records, or a changed phone number. The team checks your identity before moving the case further.
Data request form Use the form inside your account when you want a copy, correction, or deletion request. We ask for verification first, then route the request to the privacy team for handling.
DATA CARE

Browse how we protect your data

Our privacy work covers the full account path: registration, login, wallet activity, cookies, support chats, security checks and account closure requests.

Account data

We collect account details you provide, such as name, contact details and login identifiers. These records support access, verification, service messages and privacy requests tied to your account.

Wallet records

Transactions through Touch 'n Go, GrabPay, Boost dan FPX create wallet records. We use them to match payments, process withdrawals, trace errors and answer account questions without exposing full payment credentials.

Cookie choices

Cookies help remember your session, language and security state. Some cookies are needed for login safety, while optional analytics cookies can be adjusted where the account tools allow it.

Security checks

Device, IP and login pattern data help us detect unusual access. When a risk appears, we may ask for extra verification before changing personal details or releasing account records.

Retention periods

We keep different records for different periods based on law, payment tracing, dispute handling and security needs. When those reasons end, we delete the record or remove identifying details.

Request handling

You can ask to access, correct or delete personal data where local law allows. We verify your identity first, then respond through the contact channel linked to your account.

Discover privacy answers before joining

These answers explain common privacy points before you create or use an account. They cover the data we collect, why we keep certain records, how you can ask for changes, and how payment or support activity affects your privacy file. If your case involves local legal access rules, availability depends on Malaysian law and where local law permits.

It covers account details, login records, wallet activity, device signals, cookies, support chats and documents you submit for verification. It also explains why we use each data type and how long records may be kept.

Wallet records help match deposits, withdrawals, refunds and disputed transfers through Touch 'n Go, GrabPay, Boost dan FPX. We keep the transaction trail needed for account service, security checks and legal duties.

Yes, you can ask for a copy of personal data linked to your account where local law allows. We verify your identity first, then provide the data through a safe account-linked channel.

Start from your account area or support channel and explain which detail needs correction. We may request proof before changing name, phone, email, bank or wallet details to protect the account.

Cookies help keep you signed in, remember settings and protect sessions from unusual access. Analytics cookies may measure page use, but they are handled separately from the records needed for wallet and account safety.

Only teams or service partners who need the request for verification, support, legal handling or technical action can access it. Access is limited by role, and sensitive requests are handled through account-linked channels.

You can request deletion where local law permits. Some records may need to be kept for payment tracing, dispute handling, security checks or legal duties before they can be removed or de-identified.