Rujukan Laman

Privacy Policy for Malaysia accounts

pussyy88 keeps account, wallet, device and game-session data within a clear Privacy Policy before you open your account.

Account data explainedWallet data coveredCookie choices includedMalaysia access wording
pussyy88 Privacy Policy for Malaysia accounts
CONTACT PATHS

Three routes to privacy support

Your privacy questions should reach a real support path, not a generic inbox with no context. Use the in-account chat for quick identity checks, email for document requests, or the account ticket form when you want a written trail. We ask for only enough detail to locate your account and handle the request. If a request involves wallet records, we may ask you to confirm a recent Touch 'n Go, GrabPay, Boost or FPX reference.

Team online

In-account chat

Use chat after login when you need help with cookie choices, device sessions, or a privacy setting. We can confirm your account through the active session before sharing or changing any data.

Privacy email

Send email when you need a copy, correction, deletion request, or a longer written answer. Include your account name and a safe contact address, but do not send wallet passwords or bank codes.

Account ticket

Open a ticket from your account area for requests linked to wallet records, login alerts, or verification files. The ticket keeps messages in one thread so we can track each privacy step.

ACCOUNT CARE

Six controls behind this Privacy Policy

We handle privacy as an account operation, not as a footer link. The policy covers data capture at account opening, wallet activity, game-session logs, cookie settings, support chats, and retention schedules.

Data collection

We collect account details, contact fields, device signals, login time, wallet references and session records. For titles such as Aviator or Turkish Blackjack, session logs help settle activity and investigate account disputes.

Wallet records

When you use Touch 'n Go, GrabPay, Boost dan FPX, we record the transaction reference, amount, time and status. We do not ask for wallet passwords, app PINs or bank login secrets.

Cookie choices

Cookies keep your session active, remember language settings, measure page faults and reduce repeated security checks. You can change browser settings, but some account pages may require session cookies to work.

Security checks

We use device signals, login alerts, password resets and unusual activity checks to reduce account misuse. If a privacy request could expose data, we confirm control of the account first.

Retention periods

Some records are kept while your account remains active, while payment and dispute records can be kept longer where record duties apply. We remove or anonymise data when it is no longer needed.

Request handling

You can ask for access, correction, deletion or limits on certain processing. We answer through the channel you used, and complex requests may need extra identity checks before any change is made.

Privacy Policy questions from Malaysia

These answers explain the privacy points you are most likely to check before opening or using an account. They focus on account data, wallet records, cookies, support contact, retention and your request options. If your concern is personal to your account, contact us through chat, email or ticket so we can verify you before discussing private records.

We collect the details needed to create and protect your account, such as contact fields, login credentials, device signals and verification status. We also record session activity after login so wallet and account actions can be traced.

No. For Touch 'n Go, GrabPay, Boost dan FPX, we only receive transaction details needed to match your wallet activity, such as reference, amount, time and status. Never share app PINs or bank login secrets.

We keep account records while your account is active and retain some payment, security and dispute records where record duties require it. When data is no longer needed, we remove it or anonymise it.

Yes. Send your request by in-account chat, email or ticket, and we will verify your identity before sharing or changing records. This protects your account from requests made by someone else.

Cookies support login sessions, language settings, security checks and page performance measurement. You can adjust browser settings, but blocking session cookies can affect account pages that require a secure login state.

We share limited fields with processors that help with payments, verification, support tools, security checks and analytics. Each processor receives only what is needed for its task, not your full account history.

Access and eligibility depend on local law and are available where local law permits. If legal requirements change, we may adjust account checks, retention duties or access controls to match those requirements.