Rujukan Laman

Privacy policy for your dfkaya account

Q: Can I ask to correct my account data?

Yes. Email privacy@dfkaya.club with the detail that needs correction and the account contact you used. We may ask for identity checks before changing data so your account remains protected.

Your account data, payment records and cookie choices are handled under this Privacy Policy before you open your account and enter the lobby.

Account data useCookie choicesPayment privacyMalaysia contact route

Explore The Lobby Read FAQ

How payment privacy applies in Malaysia

dfkaya Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

This Privacy Policy sets out how we collect, use, store and share data linked to your account, wallet activity, support chats, device access and payment references. When you use Touch 'n Go, GrabPay, Boost dan FPX, we may receive status codes, transaction references and timing details

1
so your wallet record can match the payment outcome. We do not need your full banking password or full card credentials. Access rules, identity checks and account availability may change by location, so eligibility depends on local law and is available where local law permits. If
2
a law, payment provider request or security event requires extra checks, we may keep related records for a lawful period and restrict access while we verify the account.

Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

CONTACT ROUTES

Reach us about privacy matters

Privacy questions should reach the right desk, not get lost inside general chat.

DATA CARE

How we care for account data

Our Privacy Policy covers the full account flow: joining, sign-in, wallet activity, cookies, support cases and security checks.

Account details

We collect details you provide when you open an account, such as name, mobile number, email and login records. These help us keep your wallet matched to you and handle access checks.

Cookie settings

Cookies help remember session status, language choice and security signals. Some are needed for account access, while analytics cookies help us measure page errors and improve privacy controls without reading private chat content.

Security logs

We keep device, IP and sign-in records to detect unusual access. If a new device, rapid failed login pattern or payment mismatch appears, we may add checks before showing wallet data.

Payment records

Touch 'n Go, GrabPay, Boost dan FPX records may include reference numbers, payment status and timing. We use them to reconcile your wallet, answer disputes and meet lawful record duties.

Retention periods

Some records are kept while your account stays active, while payment and security records may remain longer where law or dispute handling requires it. We remove or anonymise data when it is no longer needed.

Change requests

You can ask us to correct inaccurate account details or check what data we hold. We verify your identity first so another person cannot use the privacy process to reach your account.

Privacy policy questions before you join

These answers explain the Privacy Policy in plain terms before you open your account. They cover what we collect, why payment records matter, how cookies work, how to request changes and what happens when legal or security duties require us to keep certain records.

We collect account details you enter, sign-in records, device data, support messages and payment references. We use these to run your account, protect access, reconcile wallet activity and respond to privacy requests.

Touch 'n Go, GrabPay, Boost dan FPX references help us match a payment status to your wallet record. They also help us answer disputes, check unusual activity and meet lawful record duties.

Yes. Email [email protected] with the detail that needs correction and the account contact you used. We may ask for identity checks before changing data so your account remains protected.

Cookies support sign-in, session security, language choice and error measurement. Some are required for account access, while other settings may be adjusted through your browser or device where available.

We share only what is needed to process or verify a payment, handle a dispute or meet legal duties. Payment providers may also keep their own records under their separate privacy terms.

Retention depends on the record type. Account data may remain while your account is active, while payment, security and dispute records may stay longer where law, audit needs or safety checks require.

Yes. Account access, eligibility and certain data requests depend on local law and are available where local law permits. If legal duties apply, we may need to verify your identity or restrict access while checking records.

Privacy policy for your dfkaya account

Reach us about privacy matters

How we care for account data

Account details

Cookie settings

Security logs

Payment records

Retention periods

Change requests

Privacy policy questions before you join

01 What personal data does dfkaya collect?

02 Why do you keep payment references?

03 Can I ask to correct my account data?

04 How do cookies affect my privacy?

05 Do you share my data with payment providers?

06 How long do you keep my records?

07 Can local law affect access to my account?

Related Pages