Rujukan Laman

peti4d Privacy Policy for Malaysia Accounts

The peti4d Privacy Policy sets out how your account details, login activity, cookie choices and wallet context are handled when you explore No Comm Baccarat, Book of Cleopatra…

Malaysia data clarityCookie choice basicsWallet record handlingPrivacy request paths
peti4d peti4d Privacy Policy for Malaysia Accounts
CONTACT PATHS

Ask Us About Privacy Requests

If you want to ask about this Privacy Policy, start with the contact path that matches your account status. Signed-in requests help us verify ownership before we discuss records.

Account privacy inbox Use the privacy contact route when you need a copy, correction or deletion request assessed. We may ask for account identifiers and recent login context so we can match the request to the right account.
Signed-in chat When your account is open, the chat route lets our team confirm the request inside your session. Avoid sending full card, bank or wallet secrets; partial references are usually enough for tracing.
Security escalation If you believe an account, password or wallet record has been exposed, tell us quickly through the security path. We can check recent access logs and advise the next verification step.
ACCOUNT SAFETY

Controls Around Cookies And Account Security

Our privacy handling is built around practical account controls rather than broad promises. We separate login checks, wallet references, game-session records and support conversations so each record type is handled for its…

Data we collect

We collect account details you provide, login timestamps, device signals, wallet references and service messages. Game-session records may show table or slot access, but they are used for account operation and dispute checks.

Cookie handling

Cookies help keep your session active, remember language choices and protect sign-in flows. Some cookies support security checks, while others help us understand page errors so we can repair account paths.

Wallet privacy

Touch 'n Go, GrabPay, Boost dan FPX records are stored as wallet transaction context. We use references, amounts, time stamps and status markers to confirm requests and investigate mismatched wallet entries.

Game-session records

Activity around No Comm Baccarat, Football Studio, Bombing Fishing or Book of Cleopatra may create session logs. Those logs help confirm account history, resolve disputes and check unusual access patterns.

Retention approach

We keep data for account operation, security checks, legal duties and request handling. When a record no longer serves those purposes, we either remove it or reduce it so it no longer identifies you.

Your change requests

You can ask us to correct inaccurate account data, review stored records or assess deletion. We need to verify that the request comes from you before changing details tied to wallet or login history.

Privacy Questions Before You Join

These answers explain the parts of the Privacy Policy most account holders ask about before opening an account or returning to the lobby. They focus on data collection, cookie choices, wallet records, access requests and how we verify you before making changes to account-linked records.

We collect the details needed to create and operate your account, including contact data, login records, device signals and wallet references. Extra checks may apply when a payment or security event needs verification.

Wallet records help us match Touch 'n Go, GrabPay, Boost dan FPX activity to your account. We keep references, status markers and time stamps so deposits, withdrawals and disputed entries can be checked.

Yes. Send a correction request through the privacy contact path or signed-in chat. We first verify that you control the account, then assess the change against wallet history, security logs and legal duties.

Cookies support sign-in sessions, language settings, security checks and error detection. You can manage cookie settings through your browser, but blocking some cookies may affect account access or session stability.

Support messages are handled by team members who need them to answer your request, verify account ownership or investigate a security matter. We do not treat support chats as public profile content.

Retention depends on the record type and purpose. Account, wallet and security records may be kept while needed for operation, legal duties, dispute handling or fraud checks, then removed or reduced.

Some privacy rights, eligibility rules and access conditions depend on local law. Where we discuss account access, it is available where local law permits, and we handle requests based on the rules that apply.