Rujukan Laman

Privacy Policy for Your bvk888 Account

bvk888 keeps this Privacy Policy close to the account flow: it explains what data we collect, why we need it, how long we keep it, and how you…

Malaysia data careCookie choicesAccount securityPayment record checks
bvk888 Privacy Policy for Your bvk888 Account
HELP DESK

Reach Us About Privacy Requests

Privacy requests should reach the team that can see account records, not a public comment space. If you contact us from Klang or anywhere else in Malaysia, include your registered phone number or email, the request type, and any payment reference you want us to check. We may ask for a short identity match before sharing or changing records, because we need to confirm the account belongs to you.

Team online

Logged-in chat

Use live chat after logging in when you need a quick privacy status check. Our agent can confirm that your request was received, explain the next verification step, and move complex matters to email.

Privacy email

Send email when your request needs documents, screenshots or a longer explanation. We keep the thread with your account record, so you can refer to the same case without repeating every detail.

Account message centre

Open the account message centre for replies that should stay behind your login. It is useful for correction requests, cookie questions and wallet record checks linked to Touch 'n Go, GrabPay, Boost dan FPX.

ACCOUNT CARE

How We Handle Your Account Data

We handle privacy work in layers. Account details sit behind login controls, payment references are matched with wallet events, and cookies are separated by purpose so you can understand what each setting…

Data collection

We collect profile details you provide, wallet references, login records, cookie choices and device signals. Each category is tied to account creation, payment matching, service security, support handling or legal record duties in Malaysia.

Cookie use

Cookies help remember your session, language choice and basic security checks. You can change browser settings, but some cookies are needed for login, wallet handshakes and keeping your account page from mixing with another session.

Access checks

Login records, IP signals and device fingerprints help us spot unusual access attempts. If a privacy request involves sensitive records, we may ask you to confirm a code or account detail before we respond.

Payment records

Touch 'n Go, GrabPay, Boost dan FPX references are stored with wallet events so deposits and withdrawals can be matched. We do not publish payment records, and support uses them only for account checks.

Retention timing

Retention periods depend on the record type. Support chats may be kept for case history, payment references for accounting and dispute handling, and security logs for detecting repeated unauthorised access.

Change requests

You can ask us to correct profile details, update contact records or remove data that is no longer needed. We will check identity first, then tell you what we changed or why a record must stay.

Privacy Questions Before You Join

These privacy questions help you decide what to share before you open an account and what to expect after you join. The answers focus on account data, cookies, payment references, support records and your request options. For any eligibility matter, we follow local law and make access available only where local law permits. If your case needs a personal response, use the contact paths above.

We collect details you give during account creation, such as name, phone number and email, plus wallet references, login records, device signals and cookie choices needed to run the account and protect access.

Payment references help us match Touch 'n Go, GrabPay, Boost dan FPX activity with your wallet. They support deposit confirmation, withdrawal checks, dispute handling and fraud prevention without exposing your records publicly.

Send your request through logged-in chat, email or the account message centre. Tell us which record looks wrong, add a clear reference, and complete the identity check before we edit account details.

Cookies record session needs, language choice, security checks and certain preference signals. We do not use this policy to publish your play history, and browser controls can reduce optional cookies.

We keep records while they are needed for account operation, legal duties, disputes, accounting or security. When the purpose ends, we remove the record or move it into restricted storage.

Only the staff needed to handle your case can see the request details. Support may pass a matter to security or wallet teams when the record type requires a specialist check.

Yes, you can ask us to remove data that is no longer needed. Some records may remain where law, accounting, dispute handling or security duties require us to keep them.