Rujukan Laman

Your Data Terms Before You Join

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

Account data useCookie choicesWallet verificationMalaysia privacy support
super22 Your Data Terms Before You Join
CONTACT PATHS

Privacy Help Without Leaving Your Account

Privacy questions should reach the right team, not sit in a general inbox. Use the contact route that matches your request, include the mobile number or email tied to your account, and…

Account privacy desk Use the account help form when you want a copy of your account data, a correction to profile details, or a privacy request tied to login access. We may ask for identity checks before releasing records.
Wallet record support Contact wallet support if your request involves Touch 'n Go, GrabPay, Boost dan FPX references. Share the transaction time and channel so we can trace only the records needed for your privacy query.
Cookie and device help Message support if cookies, remembered devices or session alerts look wrong. We can explain what was stored by the browser, what stays on our systems, and how to refresh your privacy settings.
DATA CARE

What You Control Inside super22

We handle privacy as an account operation, not as a hidden page. The policy covers the data behind login, KYC-style checks where required, wallet movement, browser cookies, support history and security alerts.

Account identity data

We collect the details needed to create and maintain your account, such as name, contact method, login records and verification status. These records help us confirm access and respond to privacy requests accurately.

Payment privacy context

When you use Touch 'n Go, GrabPay, Boost dan FPX, we keep transaction references, timestamps and status updates needed for wallet records. We do not store full banking credentials from your provider.

Cookie use

Cookies help keep your session active, remember device choices and show us when a page fails to load. You can clear browser cookies, but some account security checks may need to run again.

Security signals

We may record device type, IP region, login time and unusual access patterns to protect your account. If we notice risk, support may ask you to verify ownership before changing privacy settings.

Retention choices

We keep records only as long as needed for account operation, legal duties, dispute checks and security review. You may ask what is retained and request removal where law and account status allow.

Correction requests

If your profile details are wrong, ask support to correct them through the privacy contact path. We may require proof that the updated contact or identity detail belongs to you.

Common Privacy Questions Before Joining

These answers explain how our Privacy Policy works in everyday account situations. They focus on what we collect, why we use it, how you can ask for changes, and what happens when wallet, device or support records are involved.

We collect account details you provide, login records, device signals, wallet transaction references and support messages. The exact data depends on how you use the account and what checks are needed where local law permits.

Wallet data helps us match deposits, withdrawals, refunds and account balance records. For Touch 'n Go, GrabPay, Boost dan FPX, we use transaction references and status details, not full banking credentials.

Yes. Send a request through the privacy contact path and include the email or mobile number linked to your account. We may verify your identity before sending account records to protect your privacy.

Cookies help remember your session, device choice and page performance. You can clear them in your browser, but doing so may require a fresh login or another security check the next time you access the account.

We keep account, wallet, security and support records for the period needed to operate the account, handle disputes and meet legal duties. You can ask what remains on file and request removal where allowed.

Only team members who need the messages to answer your privacy, wallet or account question should access them. We use support history to resolve your request and to keep a record of what was agreed.

Contact the privacy desk from your account and state which detail is wrong. If the change affects identity, mobile number, email or wallet matching, we may ask for proof before updating the record.