Rujukan Laman

Privacy Policy for peso888 Malaysia Accounts

Our Privacy Policy explains how account, wallet, device, and lobby data are collected, used, stored, and shared when you open an account, browse Bucharest Roulette, Aviator, or check…

Account data useCookie choiceWallet record careMalaysia privacy contact
peso888 Privacy Policy for peso888 Malaysia Accounts
CONTACT PATHS

Reach Us About Privacy Requests

Privacy requests move faster when the message comes from the account that holds the data. If you cannot log in, we still give you a route to contact us, but we may ask for matching details before making changes. Do not send passwords, full banking credentials, or unrelated screenshots; send only what helps us confirm the account and understand your privacy request.

Team online

Account Centre

Use the privacy form inside your logged-in account when you want a copy, correction, or deletion request. The session already ties the message to your wallet, so we can verify you without asking for extra scans first.

Live Chat

Start chat from the lobby footer and choose privacy support before sending personal data. Our team can route the message to the privacy queue and tell you what proof is needed for account matching.

Email Desk

Write to [email protected] if you cannot reach your account. Include your username, phone or email on file, and the request type; leave out bank passwords, card numbers, and unrelated screenshots.

ACCOUNT SAFETY

Bucharest Roulette Data And Cookie Controls

Handling this policy means writing down what we do, then matching daily account work to that wording.

Account Data Map

Your profile links contact details, login records, wallet history, and support messages under one account ID. The policy explains why each category is kept and which teams may see it during access, payment, or safety checks.

Cookie Choices

Cookies help keep your session active, remember language settings, and detect repeated failed logins. You can clear them in your browser, but some account features may ask you to verify again afterward.

Login Protection

We record sign-in time, IP range, device type, and failed attempts to reduce account takeover risk. If something looks unusual, support may ask security questions before changing contact details or releasing wallet access.

Payment Record Care

For Touch 'n Go, GrabPay, Boost dan FPX, the policy keeps merchant references, timestamps, and status codes needed to reconcile your wallet. Full banking credentials should never be sent to support or stored in chat.

Retention Windows

Some records must stay while your account is active or while a payment query is open. When retention is no longer needed, we remove, anonymise, or archive data under restricted access.

Correction Requests

If your phone, email, or spelling of your name changes, ask for a correction through the account centre. We may verify the request with login history before updating records tied to payments.

Privacy Questions Before You Join

Read these answers before you create an account if you want to know how privacy requests work in Malaysia. Each answer reflects the policy approach for account data, cookies, wallet records, support messages, and access checks. If your situation needs a direct reply, contact us through the account centre or [email protected] so we can match the request to your account.

It covers account details, contact records, login signals, payment references, cookies, device data, game-session logs, and support messages. It also explains why we collect them, how long we keep them, and who may handle them.

Payment data helps us match Touch 'n Go, GrabPay, Boost dan FPX activity to your wallet. We use references, timestamps, and status codes for reconciliation, withdrawal checks, dispute handling, and privacy records.

Yes, you can ask through the account centre or email [email protected]. We may need to verify your identity before sending account data, especially where wallet records or contact changes are part of the request.

Cookies keep your session active, remember language settings, and help detect repeated failed logins. If you clear cookies, you may need to sign in again or complete extra verification before using account features.

Only teams that need access for the request should handle it, such as privacy support, account security, or payment operations. We keep request records so follow-up questions can be linked to the same account.

Retention depends on the record type, account status, payment queries, safety checks, and legal duties. When data is no longer needed, we remove it, anonymise it, or archive it with restricted access.

Yes. Access and eligibility depend on local law and are available where local law permits. The same legal setting may affect what data we collect, how we verify requests, and how we respond.