Rujukan Laman

Privacy Policy for Malaysia account data

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

Account data useCookie choicesWallet recordsSupport contact routes
alpha66a Privacy Policy for Malaysia account data
CONTACT ROUTES

Contact us about your data

Privacy questions should reach the team that handles account records, not the general lobby chat alone.

Live chat routing Use live chat when you need quick routing for a privacy request. The agent can confirm your account reference, record your question, and move the case to the privacy queue for a written reply.
Email privacy request Send a clear request to [email protected] if you want access, correction, or removal of account data. Include your registered phone or email, but never send wallet passwords or bank passwords.
Wallet record ticket Raise a wallet ticket when your privacy question concerns Touch 'n Go, GrabPay, Boost dan FPX receipts, withdrawal checks, or transaction references. We match the ticket to account activity before replying.
ACCOUNT CARE

Account privacy at alpha66a

Your Privacy Policy rights make sense only when the handling steps are clear. We separate account identity, payment references, security logs, cookie settings, and support messages so each record has a defined…

Data collection

We collect account details you submit, device signals from logins, wallet references from payments, and activity records from lobby sessions. Each category is tied to account access, security, support, or transaction handling.

Payment records

Touch 'n Go, GrabPay, Boost dan FPX receipts are stored as transaction references, time stamps, status codes, and account links. We do not ask you to share full bank passwords with us.

Cookie controls

Cookies help remember sessions, language settings, risk signals, and basic page performance. You can manage browser cookies, but some account security checks may need session cookies to keep logins working.

Account security

We use password protection, session checks, device signals, and access logs to reduce account misuse. If a login pattern looks unusual, support may ask for identity checks before changing data.

Retention rules

Records are not kept forever. We retain account, payment, dispute, and security data only as long as operational, fraud-prevention, legal, or support needs apply, then reduce or remove eligible records.

Correction requests

If your registered phone, email, name spelling, or wallet reference is wrong, contact us with the account ID and the correction needed. We may request proof before updating privacy-linked records.

Privacy Policy questions for Malaysia

These answers explain how our Privacy Policy works before and after you open an account. They focus on data collection, access, cookies, sharing, retention, correction, and local-law conditions. If your request involves a specific wallet record or login session, contact us with enough detail to locate the account safely.

It covers data linked to your account, wallet activity, device, login sessions, cookies, support messages, and security checks. It also covers records created when you ask us to update, export, or remove eligible data.

We use payment data to match Touch 'n Go, GrabPay, Boost dan FPX transactions to your account, confirm status, handle disputes, and process withdrawals. We keep references and receipts, not full bank passwords.

Yes. You can ask us to correct eligible account data such as phone, email, name spelling, or wallet references. We may verify your identity first so another person cannot change your records.

Cookies support account sessions, language settings, security checks, and basic site performance. You can manage cookies through your browser, but some account pages may need session cookies to keep access working.

We share limited data with payment processors, security vendors, support tools, and legal or regulatory channels when needed. We do not sell your account records, and we limit sharing to the stated purpose.

Retention depends on the record type. Payment, withdrawal, dispute, and security logs may be kept longer than general support messages because they can be needed for account checks, fraud-prevention, and legal duties.

Yes. Access and eligibility depend on local law and are available where local law permits. The same legal setting can affect how we process privacy requests, retention duties, and account data changes.