Rujukan Laman

Privacy Policy for Your Account

Our Privacy Policy explains how account, wallet, cookie and support data moves through pushy888, including checks tied to Touch 'n Go, GrabPay, Boost dan FPX.

Account data explainedCookie choices coveredMalaysia wallet contextSupport request routes
pushy888 Privacy Policy for Your Account
CONTACT ROUTES

3 Privacy Contact Routes

Privacy questions need a clear route, so we separate account help from data-rights requests. Tell us what you need, and we will ask only for details needed to identify your account and handle the request. For your safety, do not send wallet PINs, full bank details, or one-time codes through email or chat.

Team online

Privacy email

Write to [email protected] with the email or phone tied to your account. We check ownership before discussing data, then reply with the next step for access, correction, deletion, or consent questions.

Live chat privacy handoff

Open chat from the account menu and ask for privacy help. The agent will avoid asking for wallet PINs, confirm your identity inside the session, and send complex requests to our privacy queue.

Security incident route

If you think your account, device, or wallet records were exposed, contact support quickly. We review login history, recent edits, and active sessions before telling you what data may need further protection.

ACCOUNT CARE

6 Data Controls Behind Your Account

Behind this policy, we keep account records, wallet events, support messages, cookie settings, and security logs in separate workflows. That helps us limit who sees each record and why.

Account identity data

When you open an account, we collect identifiers such as name, contact details, login credentials, and verification status. We use them to create your account, protect access, and respond when you ask for data changes.

Wallet record handling

Touch 'n Go, GrabPay, Boost dan FPX references are kept with timestamps, account IDs, and status codes. We use those records to reconcile wallet balances, check disputed entries, and meet record duties.

Cookies and device signals

Cookies help remember session state, language choice, and security checks. Device signals such as browser type and IP range help us spot unusual access without needing to read private files on your device.

Game activity records

If you open Lucky Blackjack, Dragon Fishing, or Aviator, we record session events, stake history, and result references. The policy explains how those records support account history and dispute checks.

Retention periods

We keep data only for account operation, security, dispute handling, and legal record needs. When a record is no longer needed, we remove it, anonymise it, or separate it from direct account identifiers.

Correction requests

You can ask us to correct contact details, update consent choices, or review a record linked to your account. We may ask for identity checks before making changes to protect your data.

Your Privacy Policy Questions Answered

These answers explain the privacy points you may want to check before you open an account or continue using your current one. They focus on data collection, access, correction, cookies, retention, and contact routes. If your question involves a specific wallet entry or account record, contact us from the account that owns it.

We collect account details, login records, wallet transaction references, game-session records, cookie choices, device signals, and support messages. The exact data depends on the actions you take and the checks needed for account safety.

Those payment names explain the wallet records we may process when you use local Malaysia options. We keep references such as status codes and timestamps so your wallet ledger can be checked accurately.

Yes, you can contact us through the privacy email or account chat. We will verify that the request comes from you before sharing account data or explaining why some records cannot be released.

Send the corrected detail through the privacy email or account support path. We may ask for identity checks, especially when the change affects login access, wallet records, or verification status.

Cookies help keep you signed in, remember basic preferences, and support security checks. Some cookies are needed for account sessions, while others help us understand page performance and fix technical issues.

We keep data for as long as needed to operate your account, handle disputes, meet legal record duties, and protect the service. After that, records are removed, anonymised, or separated from identifiers.

Use [email protected] for data-rights requests, or open account chat for urgent access concerns. We check ownership before discussing records, so include your account email or phone but never send one-time codes.