App / Mobile
cae44 operates under a defined set of legal terms that govern your account, your transactions through bKash, Rocket, or Upay, and your access to the platform. What applies to you depends on your local law and the eligible region you access from — this page sets out the framework clearly.
The terms on this page govern the relationship between cae44 and you as an account holder. They apply when you log in, when you move funds through supported local payment methods such as bKash, Rocket, or Upay, and when you interact with any part of the platform — including game lobbies, account dashboards, and published support routes. Availability of any feature or transaction method depends on your local law and the region from which you access the site. We do not make legal representations about outcomes or eligibility that fall outside what published policy documents state. Where a conflict arises between a general site notice and these terms, these terms take precedence. We revise our legal documents when our operational or regulatory position changes; the current version is always the one shown on this page, and continued use of the account after any revision means you have accepted the updated terms. If you have a question about how a specific clause applies to your account, the correct route is to raise it through our published support contact rather than to infer an interpretation. Your bKash, Rocket, or Upay transaction records remain visible in your account wallet history and are subject to the data retention terms described further down this page.
Transaction records linked to bKash deposits or withdrawals fall under these terms and are visible in your account wallet history.
Rocket payment activity on your account is logged and subject to the retention and correction rights described in this policy.
Upay transfers are treated as account transactions under the same legal framework, with correction and query routes open to you.
Not every interaction with cae44 falls under the same clause. This section maps which parts of your experience this legal framework directly governs and where the boundary sits with third-party services or external law.
Login, session management and account suspension decisions are within scope. We set access rules, and you can query any access decision through our published support route.
Deposits and withdrawals processed via bKash, Rocket, or Upay are governed by these terms on our side. The payment provider's own terms also apply independently.
Game availability, lobby layout and promotional notices published on the site fall within this policy's scope. Content accuracy is our responsibility.
External links, payment provider interfaces and game studio platforms operate under their own terms. We are not legally responsible for third-party policy decisions or service availability.
Knowing what you can actually do is more useful than reading abstract rights. Under the terms cae44 publishes, you have several practical routes open to you. You can review your transaction history — including bKash, Rocket, and Upay activity — directly inside the account wallet section without contacting support. If a record looks incorrect, you can raise a correction request through our support channel, and we will review it against the logged data on our side. You can also ask for a copy of the account data we hold against your profile by sending a written request through the published contact route; we will respond within the timeframe stated in the current policy version. If you believe a policy clause has been applied incorrectly to your account — for example, an access decision or a transaction flag — you can escalate that question formally through the same support route. We do not require you to accept a decision without explanation. Each of these routes exists inside the platform and is accessible from a signed-in account.
Open your account wallet to see a full log of bKash, Rocket, and Upay activity. No support ticket needed for standard history access.
If your registered details are wrong, go to account settings and follow the verification steps shown there to submit a correction.
Any clause you want clarified can be submitted through our published support contact. Reference the specific section so we can respond accurately.
Send a written data request via our support route. We log the request date and respond within the period stated in the current policy version.
If a section of this policy raises a question you cannot resolve by reading it, or if you need to raise a formal query about your account rights, the routes below are where to start. Use the channel that matches your situation — routine account questions and data requests both come through support, while formal policy disputes should be flagged clearly so they reach the right review team.
Open the chat widget from your signed-in account to ask a policy question or flag an access issue. Keep the relevant section reference ready.
For formal data requests or written policy queries, use the support email address listed in your account help section. Written requests create a timestamped record.
The help section inside your account contains published answers to the most common policy questions, including how to request data or contest an account decision.
We hold account data only for as long as it serves a documented purpose — active account management, transaction record-keeping, or a legal obligation. When a purpose ends, data is removed or anonymised according to the retention schedule in the current policy version. Cookies we set on the site are explained in the separate cookie notice linked from the footer; you can manage preferences from within your browser settings on any device.
Account and transaction data — including wallet activity from bKash, Rocket, or Upay — is kept for the period stated in the current policy. After that period, it is removed or anonymised.
Cookies used on cae44 are documented in the cookie notice in the site footer. You can adjust browser-level cookie settings on any device you use to access the site.
Your account is protected by the login and verification steps set at registration. If you suspect unauthorised access, use the account security section to change your credentials immediately.
When we update this policy, the revised version replaces the previous one on this page. Continuing to use your account after a revision constitutes acceptance of the updated terms.
These are the questions we hear most often about how our legal framework applies to your account. If yours is not here, raise it through the support contact route.
Access and applicability depend on your local law and the region you access from. If access is available in your region, these terms govern your account. We do not make representations about legal status in specific jurisdictions — check your local rules before you proceed.
Yes. The version shown on this page is always the current one. We do not keep previous versions publicly available, but you can request a summary of material changes through our support contact if you need to understand what has changed since you last reviewed the policy.
Log in to your account and open the live chat or use the support email listed in the help section. State clearly that you are raising a policy dispute, reference the decision date and the relevant payment method — bKash, Rocket, or Upay — so the review team can pull the correct record.
We hold profile data, login records, and transaction history for the period stated in our current retention schedule. After that period, data is removed or anonymised. You can request a copy of what we hold by submitting a written request through the published support email route.
Yes. Any bKash, Rocket, or Upay transaction processed through your account is logged and falls under our data retention and correction terms. Your wallet history inside the account shows these records, and you can raise a correction request if something appears wrong.
If you continue to use your account after a policy revision, that is treated as acceptance of the updated terms. If you do not accept the new version, you should stop using the account and raise a formal account closure request through the support contact route before the revision takes effect.