Sports / Slots
cd44 collects only the account and payment information needed to run your wallet, process transactions through bKash, Upay or Bank Transfer, and keep your session secure across every device you use. Access to this platform depends on your local law and eligible region.
When you open an account with us, we collect information in two broad categories: identity details you provide during registration (your name, contact address and account credentials) and activity data generated as you use the platform (transaction records, session logs and device identifiers). We need the identity layer to verify that the account belongs to you and to process wallet movements — whether that is a bKash transfer, an Upay deposit or a Bank Transfer instruction. Activity data helps us detect unusual patterns that could signal an unauthorised login or a transaction that did not originate from your device. We do not sell your personal data to third parties. Where we share data with a payment processor — for example, to route a bKash or Upay transaction — we share only what that processor needs to complete the instruction. We do not share account records with advertising networks. Retention periods follow the obligations set by applicable jurisdiction rules; where local law requires us to hold a transaction record for a defined period, we comply with that requirement and then delete it. If your jurisdiction restricts access to this platform, eligibility and data handling both depend on the rules of your local law and eligible region.
This policy covers data we handle directly — your registered account, the payment routes you have configured (bKash, Upay, Bank Transfer), and the content you interact with on cd44. It does not extend to third-party services that open in a separate window or that you reach through a link we do not control. Knowing the boundary helps you understand exactly what this document commits us to.
Any data you submit during login, registration or account recovery falls under this policy. We handle those credentials inside our own systems and do not pass them to unrelated third parties.
Wallet movements made through bKash, Upay or Bank Transfer are logged in your account history. We share only the minimum fields a payment processor requires; the record stays in your account dashboard.
Pages you visit, features you open and session duration are logged at an aggregate level. This helps us keep navigation working correctly across mobile and desktop without storing individual browsing histories tied to your name.
Game studios, external links and payment gateways operate under their own privacy terms. Once you leave a page we control, this policy no longer applies and you should check the relevant third-party document.
You have a set of concrete actions available to you under this policy, and each one has a clear route inside the platform. Start with your account settings page — the transaction history tab shows every bKash, Upay and Bank Transfer record linked to your wallet, with dates and reference numbers. If a record looks incorrect, the first step is to raise a correction request through the support channel listed on the contact page; our team will cross-check it against the payment processor log and respond with the outcome. If you want to know exactly what personal data we hold, send a data access request to the same support route and we will compile the records held against your account ID. Deletion requests are handled according to the retention obligations of applicable local law — where jurisdiction rules require us to keep a record, we will explain that clearly and tell you when deletion becomes available. For any question about eligibility based on your region, access depends on local law and we will direct you to the relevant published terms.
Open the transaction history tab in your account to see every payment log — bKash deposits, Upay transfers and Bank Transfer references are all listed with dates and reference numbers.
If any personal detail on file is wrong, raise a correction request via our support contact page. We match it against the original submission and confirm the update in writing.
Send a data access request through the published support route with your account ID. We compile the records we hold and return them to you via the contact method you used.
Any question about how data is stored, shared or deleted can be sent to our support team. We respond with a plain-language answer tied to the specific part of this policy your question covers.
If you have a question about your personal data, a correction to request or a deletion to consider, the routes below are the ones published on cd44. Use the channel that works best for your device and situation — each one connects to the same account support team that handles privacy requests.
Open the chat icon from any page while signed in. Describe your privacy question and include your account reference so the team can pull the right records without asking you to repeat details.
Send a written privacy or data request to the email address listed on the contact page. Written requests work well for data access queries where you want a documented response you can refer back to.
The help section inside your account contains a privacy and data category. From there you can submit a structured request form — useful if your query involves a specific transaction or payment method record.
Data handling at cd44 is built around the practical reality of a mobile-first account flow — your bKash wallet reference, your Upay transaction log and your Bank Transfer record all travel through encrypted connections between your device and our systems. We do not store full payment credentials on our side; the processor holds those under their own security terms. Below are the four areas where we want to be specific about our approach.
We use session cookies to keep you signed in as you move between pages and to remember your preferred payment method. You can manage cookie preferences through your browser settings; disabling them may affect how account pages load.
Login attempts, device changes and unusual session patterns trigger a verification step shown in your account. We log the device identifier and timestamp for each login so you can review access history from your security settings tab.
Transaction records — including bKash deposits and Bank Transfer references — are kept for the period required by applicable jurisdiction rules. Once that period ends and no dispute is open, the record is scheduled for deletion.
To update, correct or request deletion of personal data, contact us through the published support routes on the contact page. We confirm receipt and give you a timeline based on the nature of your request and applicable local law.
These are the questions we hear most often about account data, payment privacy and your rights under this policy. If your question is not here, use the live chat or email route on the contact page.
We share payment details only with the processor needed to complete your transaction. For a bKash deposit, only the fields that bKash requires to route the transfer are shared. We do not pass wallet numbers or account credentials to advertisers, analytics firms or unrelated third parties.
Send a data access request through the email address or live chat route listed on our contact page. Include your account ID so we can match your request quickly. We compile the records held against your account and return them through the contact method you used.
Yes, you can submit a deletion request via our support contact route. Where local law or a jurisdiction requirement means we must retain a specific record — such as a Bank Transfer reference within a required period — we will explain that clearly and tell you when deletion becomes available.
We log the device identifier, IP address and timestamp of each login attempt. This lets you review your access history from the security tab in your account settings. If a login looks unfamiliar, you can flag it through account help and we investigate the session record.
No. Game studios whose titles appear in the lobby — such as PG Soft, Habanero or CQ9 — operate under their own privacy terms. This policy covers data we collect and process directly; once a game session opens inside a studio environment, their terms govern that data layer.
Go to account settings and check the personal details section first. If the correction requires verification — for example, a name change tied to a Bank Transfer record — raise a correction request through live chat or email with your account ID and the detail you need updated.