Reference

See How Your Account Data Stays Protected

This page explains exactly how BK 6666 collects, stores and uses the details tied to your account, from your login number to the mobile wallet you deposit with.

Login & Device DatabKash, Nagad, Rocket RecordsCookie ControlsData Access Requests
BK 6666 See How Your Account Data Stays Protected
ACCOUNT DATA SAFEGUARDS

How BK 6666 Secures And Retains Your Details

Keeping your wallet history and login details in order isn't a one-time setup — it's something we handle every time you deposit, withdraw or switch devices. Below is the practical side of that: where your data sits, how cookies work on our end, how long records stay on file, and what to do if something needs correcting.

Encrypted Account Storage

Your login credentials and wallet reference numbers sit behind encrypted storage on our servers, and only the account-verification team can view the payment details tied to your bKash, Nagad or Rocket deposits.

Cookie Preferences

We use cookies to remember your last login and your preferred payment chip so switching between the app and mobile browser doesn't reset your session; you can clear them anytime from your device settings.

Record Retention

We hold transaction and verification records only as long as needed to resolve disputes or meet the rules that apply in your region, and older records are removed on a rolling basis after that.

Request A Change

If any detail on your account is wrong — a mobile number, an old wallet reference, a saved address — contact support with proof of account ownership and we'll update or remove it for you.

REACH OUR TEAM

Get Help With Privacy Questions Fast

If something about your account data doesn't add up, you don't need to dig through a long document to fix it. We've set up a few direct routes so you can ask a real question and get a real answer about what we hold, why we hold it, and how to change it.

Live Chat Support Open live chat from your account menu when you have a question about your stored bKash, Nagad or Rocket transaction details, and an agent walks you through what we hold.
Email Support Email us for a written record of any privacy question — ask what personal data we hold on your account, request a copy, or ask us to correct a wrong mobile number or wallet reference.
Account Verification Desk If you're verifying your identity for a withdrawal and want to know what documents we keep on file, reach the verification desk through your account panel and ask for the retention details directly.

Common Questions About Your Data

Here are the questions we hear most often about how BK 6666 handles account data, cookies and payment details. If your question isn't covered here, our support channels above can walk through the specifics with you directly.

We collect the mobile number you register with, basic device details, and the wallet details tied to each bKash, Nagad or Rocket transaction so we can match deposits and withdrawals to your account correctly.

No — we use your payment details only to confirm and process your own transactions, and we don't pass this data to outside marketers or unrelated third parties without a legal reason to do so.

Yes — reach out through live chat or email support and request removal; what we can delete and how quickly depends on your local law and any records we're required to keep for verification.

Yes, cookies keep you logged in and remember your last payment chip between sessions; you can clear or block them from your browser or app settings, though some features may work less smoothly after that.

Your account sits behind your registered mobile number and login credentials, and we monitor for unusual login patterns; if something looks off, our verification desk can pause the account until it's confirmed as you.

Start with live chat from your account menu or send an email through our support channel; both routes reach the team that handles account data, verification records and privacy requests directly.
Reference

Privacy Policy

Service availability depends on eligible regions and local law. Users should check local rules before opening an account.

Access may be available only where local law permits.