cba44 Privacy Policy: How We Handle Your Information
cba44 keeps your personal information, payment activity and account records under a clear, written policy — so you always know what we collect, why we collect it, and how you can act on it. Access to this platform and its data practices depends on your local law and eligible regions.
Account data protection
bKash, Rocket, Upay transaction records
Your right to review and correct
Published contact route for data queries
POLICY POSTURE
What This Policy Covers and How We Apply It
When you open an account on cba44, we collect the information needed to run that account: your registration details, the device and browser you use to connect, and the transaction records tied to your chosen payment method — whether that is bKash, Rocket or Upay. We do not sell your personal data to third-party marketing lists. We do not share your payment credentials with any party other than the payment processor completing your transaction. Data we hold is kept only as long as your account remains active or as long as we are required to retain it for record-keeping purposes under applicable rules. You can ask us at any time what data we hold on you, and we will respond through the support route you used to make the request. If your local law restricts the use of online platforms of this kind, your access to this site and the protections described here may be subject to those restrictions. We aim to be transparent about every category of data we touch — account credentials, wallet identifiers for bKash, Rocket or Upay, browser session logs and support correspondence. This policy applies to all of those categories without exception.
bKash wallet identifiers
Rocket transaction logs
Upay payment records
Account session data
Support correspondence
POLICY SCOPE
Where This Policy Applies and What It Does Not Cover
Not every data interaction on cba44 falls under this single document. Understanding the boundary helps you know where to direct a question — whether it belongs with us or with an external service you have connected to your account. The four areas below draw that line clearly.
Account Access
Your login credentials, session tokens and account profile fields are fully within scope. We control how that data is stored, who inside our team can view it and how long it is retained after an account closes.
Payment Transactions
Records of deposits and withdrawals processed through bKash, Rocket or Upay sit within scope for the reference data we hold. The payment processor's own handling of your wallet PIN and transaction authorisation falls under that processor's separate privacy terms.
Site Content and Cookies
Pages you browse, game sessions you open and cookies set by our platform are within scope. We use session cookies to keep you logged in and analytics cookies to understand how the site performs. You can manage cookie preferences in your browser settings.
Third-Party Services
Links leaving cba44 — including any external payment gateway page or provider documentation — are outside this policy's scope. Once you follow a link away from our domain, the privacy practices of that destination apply, not ours.
YOUR ACCOUNT RIGHTS
Practical Steps You Can Take Under This Policy
Your rights under this policy are actionable, not just stated. You can review the personal data tied to your cba44 account by opening the account settings section after you log in — the profile and verification fields shown there reflect what we currently hold. If any detail is incorrect — a name spelling, a registered mobile number linked to your bKash or Rocket wallet — you can request a correction through our support channel and we will update the record once we confirm your identity. You can also ask us to tell you which data categories we hold, why we hold them and how long the retention period runs. If you want to close your account and request deletion of non-essential data, that request goes through the same support route. We cannot delete records we are obligated to keep under applicable financial or platform rules, but we will tell you exactly which records those are and why they are retained. Every step here starts inside your account or through a direct support message — no external form or third-party portal is needed.
Review Your Records
Log into your account and open the profile section. The fields visible there — name, contact details, linked wallet identifiers — represent the core personal data we hold. Check them for accuracy at any time.
Correct Account Details
If a detail is wrong — including the mobile number tied to your bKash or Rocket payment — contact support with the correction. We verify your identity first, then update the record and confirm the change back to you.
Raise a Data Query
You can ask what data categories we hold, the reason we hold each one and the retention period. Send the question through the live chat or email route shown in the support section of this page.
Request Account Closure
A closure and deletion request goes through the support channel. We will confirm which records we can delete immediately and which we are required to retain, giving you a clear written summary of the outcome.
REACH OUR TEAM
How to Contact Us About This Privacy Policy
If your question is about data held on your account, a transaction record linked to bKash, Rocket or Upay, or any aspect of this policy, use one of the routes below. We respond through the same channel you used to reach us. Availability of each channel depends on the published schedule shown on the site's support page.
Live Chat
Open the live chat widget from any page while you are logged in. Describe your data question clearly and our support team will pull up your account record to address it directly.
Email Support
Send your privacy or data query to the support email address published on our contact page. Include your registered account identifier so we can locate your record without asking follow-up questions.
Account Help Section
The help section inside your logged-in account contains a form for account and data requests. Submit your request there and it routes directly to the team that handles policy and data queries.
HOW WE PROTECT DATA
Data Handling, Retention and Account Security at cba44
We apply access controls so that only the team members who need your data to perform a specific function can view it. Payment identifiers — the mobile numbers you register with bKash, Rocket or Upay — are stored in a way that separates them from your login credentials. Session data is cleared when you log out, and we do not retain device identifiers beyond the session unless you have chosen a remembered-device option in your account settings. Retention periods differ by data type: account profile data is held while your account is open; transaction reference data is held for the period required under applicable record-keeping rules; support correspondence is held for a defined period after the conversation closes. We do not transfer your data to jurisdictions with weaker protections than those described in this policy without putting equivalent safeguards in place first.
Access Controls
Your account data is accessible only to team members with a verified need. Payment identifiers like bKash and Rocket wallet references are stored separately from login credentials to limit exposure if one system is ever queried.
Cookie Management
We set session cookies to keep you authenticated and analytics cookies to monitor site performance. You can clear or block non-essential cookies at the browser level at any time without affecting your ability to log in.
Retention Schedule
Profile data is held while your account is active. Transaction references tied to bKash, Rocket or Upay are kept for the period required by applicable rules. Support chat logs are retained for a set period after each conversation closes.
Policy Change Notification
When we update this privacy policy in a material way, we post a notice in the account notification area before the change takes effect. You will see the update the next time you log in, giving you time to review it.
POLICY FAQ
Frequently Asked Questions About cba44 Privacy
The questions below cover the data and privacy topics we hear most often from account holders. If your question is not answered here, the support routes listed above are the right next step.
What personal data does cba44 collect when I open an account?
We collect the details you enter during registration — name, contact information and the mobile number linked to your chosen payment method such as bKash or Rocket. We also log device and browser session data each time you connect. No additional data is collected without your action.
Does cba44 share my bKash or Rocket payment details with third parties?
Your wallet identifiers are passed only to the payment processor completing your transaction. We do not share them with advertisers, data brokers or any other third party. The payment processor handles your PIN and authorisation under its own separate privacy terms.
How long does cba44 keep my account and transaction data?
Account profile data is held while your account remains open. Transaction reference records linked to bKash, Rocket or Upay are kept for the period required under applicable record-keeping rules. Support correspondence is retained for a defined period after each conversation closes, then removed.
Can I ask cba44 to delete my personal data?
Yes. Send a deletion request through live chat or the account help form. We will delete non-essential data promptly and tell you which records must be retained under applicable rules and for how long. You will receive a written summary of what was deleted and what was kept.
How do I correct a detail that is wrong in my account — for example, the mobile number linked to my Upay wallet?
Contact support through live chat or email with the correction you need. We verify your identity first, update the record and then confirm the change back to you. This applies to any profile field, including payment-linked mobile numbers for bKash, Rocket or Upay.
Does this privacy policy apply if I am accessing cba44 from Bangladesh?
Access to this platform and the data practices described in this policy depend on your local law and the eligible regions covered at any given time. If local regulations restrict the use of this type of platform, those restrictions apply to your access and to how this policy interacts with your rights under local law.