Rujukan Laman

Open super22 privacy terms clearly

super22 keeps your account, wallet and support data under one Privacy Policy, so you can see what we collect before you open an account.

Malaysia data useCookie choicesWallet record carePrivacy request path
super22 Open super22 privacy terms clearly
CONTACT ROUTES

Check your privacy contact paths

Privacy questions should reach the team that can verify your account and handle data requests safely.

Privacy email Send a privacy request from the email tied to your account. Include the data area you want us to check, such as profile details, wallet records or cookie choices, so we can verify you safely.
Live chat handoff Start with chat when you need help finding the right privacy route. Our team can confirm what details are needed, then move account data matters to a safer channel when identity checks are required.
Account message Use the message area after login for requests linked to your profile. This path keeps the request near your account record, making it easier to track status and reduce repeated verification questions.
POLICY CARE

Browse how we care for data

We treat the Privacy Policy as a working rule for account operations, not a static page.

Account data scope

We collect the account details needed to identify you, keep your profile accurate and manage service records. Optional fields are treated separately, so they are not used for a purpose that does not fit the policy.

Cookie controls

Cookies help remember sessions, detect unusual access and measure page use. You can adjust browser settings, but some account features may need essential cookies so your login and security checks work correctly.

Wallet record checks

Payment references for Touch 'n Go, GrabPay, Boost dan FPX are stored with account activity to support reconciliation, dispute checks and audit needs. We limit staff access to roles that handle those tasks.

Retention decisions

We keep data only for account operation, legal, dispute, audit and security needs. When a retention reason ends, records are deleted, anonymised or reduced so they no longer identify you directly.

Correction requests

You can ask us to correct account data that is wrong or out of date. We may ask for proof when the change affects identity, wallet checks or account recovery safeguards.

Sharing controls

We share data only with service partners that help operate account access, payments, security, support or legal duties. Each sharing purpose is checked so unrelated use is not allowed under this policy.

Ask about your privacy rights

These answers explain how to read the Privacy Policy when you manage your account. They focus on data access, correction, storage, cookies, payment references and contact routes. If your question involves a law that applies in Malaysia or another location, our response may depend on that law and the records linked to your account.

It covers account details, login records, device signals, wallet references, support messages, cookie data and verification records. The exact data depends on how you use your account and which requests you send us.

We use account data to create and maintain your profile, protect access, process wallet records, answer support matters, handle privacy requests and meet legal duties. We do not use it for unrelated purposes outside this policy.

Yes, you can ask for access to data linked to your account. We will verify your identity first, then explain what can be shared and whether any legal reason limits part of the response.

You can ask us to correct outdated or inaccurate data. If the change affects identity, wallet checks or account recovery, we may request proof before updating the record to protect your account.

Payment references are kept with your wallet history for reconciliation, dispute checks, audit needs and security monitoring. We do not store more payment data than needed for those purposes under this Privacy Policy.

Retention depends on the type of record and the reason it was collected. We keep data for account operation, legal, audit, dispute and security needs, then delete, anonymise or reduce it when no longer required.

Use the email or message path tied to your account whenever possible. That helps us verify you safely, track the request and respond through a channel that protects personal data from being shared wrongly.