Live / Mobile
cjt1117b keeps this policy clear so you always know what account data we hold, how we use it, and what choices you have. Access to our platform depends on your local law and eligible regions — read this policy before you open an account.
When you create an account on cjt1117b, we collect the details you provide during registration — your name, contact information, and the credentials you choose. If you add a payment method such as bKash, Upay, or Bank Transfer, we record the transaction identifiers needed to process your deposit or withdrawal request. We do not store your full bKash or Upay wallet PIN; only the reference data our payment flow requires is retained. We also collect session data automatically: device type, browser version, IP address, and the pages you visit within the site. This helps us serve the account area correctly and detect unusual access patterns that could affect your account security. Your data is processed for account management, transaction verification, and fraud prevention. We do not sell your personal details to third parties for marketing purposes. Where we share data with payment processors or identity-verification services, those parties are bound by their own data agreements and handle only the minimum information needed to complete the service you requested. Retention periods follow the obligations that apply under the law of the eligible region where your account is registered. If you have questions about what we hold, the support route at the bottom of this page is the right place to start.
This policy covers data we handle directly through the cjt1117b platform. It does not extend to third-party sites you may reach by following an external link from our pages. Understanding the boundary clearly helps you know when our obligations apply and when another party's terms govern your information.
Any data you submit when creating or updating your cjt1117b account — including login credentials, contact details and wallet identifiers — falls within this policy. We control how that data is stored and who can view it.
Payment records connected to bKash, Upay or Bank Transfer actions on your account are covered here. We retain transaction identifiers as required for verification and dispute resolution, within the retention rules for your eligible region.
Data generated when you browse game categories, open the sportsbook section or interact with any feature inside the cjt1117b site is logged as session activity. This falls within our policy and is used only for account integrity and service delivery.
Links or integrations that direct you away from cjt1117b — including external payment apps or provider portals — are governed by those parties' own policies. We have no control over data those services collect once you leave our domain.
You have concrete options when it comes to the data cjt1117b holds on your account. Reviewing your records is the first step: once you log in, the account area shows the profile details and payment method references currently attached to your account. If any detail is incorrect — a misspelled name, an outdated contact number, or a wallet reference you no longer use — you can submit a correction request through the support route we publish on this site. For questions about what specific data we hold beyond what the account area displays, or if you want to understand the retention period that applies to your records, contact our support team directly. They can tell you what categories of data are on file and what the process looks like to request a change. Eligibility for certain data actions may depend on the law of your region, so responses are assessed case by case. We aim to acknowledge every request and respond with the appropriate next step.
Log in and open the account area to see the profile and payment details we currently hold. The fields there reflect what is on file for your session and wallet history.
If a name, contact detail or payment reference is wrong, raise a correction through the support route. We will confirm the update once the request is verified against your account.
For data categories not visible in the account area — such as log retention or third-party reference sharing — contact support with your account identifier and a clear description of what you want to know.
If you want to close your account or understand what happens to your data after closure, our support team handles these requests individually and explains the steps that follow based on your eligible region.
If this policy raises a question you cannot answer by reading it, use one of the contact routes below. Keep your account identifier ready — it helps us locate the right records quickly and respond to your request accurately.
Open the chat widget from any page while logged in. Describe your data or policy question and include your account reference so the team can pull up the correct file.
Send your query to the support email address shown in the site footer. Use a clear subject line referencing the privacy policy and state the specific data point or account action you are asking about.
The Help section inside your signed-in account area lists published support routes and links to the policy documents that apply to your account. Start there for quick answers before escalating to live contact.
Data handling at cjt1117b follows a minimal-collection approach: we ask for what we need to run your account, process your bKash or Bank Transfer request, or resolve a support case — nothing more. The sections below cover the four areas we get asked about most.
We use cookies to keep your session active, remember your language setting and detect unusual login patterns. You can adjust cookie preferences through your browser settings. Disabling certain cookies may affect how the account area loads on your device.
Access to your stored data is restricted to account systems and support staff who need it to complete a verified request. We do not display full wallet credentials — bKash or Upay numbers — in the account interface at any point after initial setup.
How long we keep your data depends on the obligations that apply in your eligible region. Transaction records tied to Bank Transfer or wallet payments are retained for the period required by applicable rules. You can ask support for the specific retention period relevant to your account.
When this policy changes in a way that affects your data rights, we post a notice on the site and update the version date shown at the bottom of this page. Continuing to use the platform after a notice is posted means you have seen the updated terms.
These questions come up regularly when account holders read through the policy. If yours is not here, the support routes listed above are the right next step.
We collect the name, contact details and login credentials you enter during registration. If you connect a payment method like bKash or Upay, we store the transaction reference data needed to process your request — not your full wallet PIN or bank login.
We share data only with the payment processors and verification services required to run your account. Those parties handle minimum necessary data under their own agreements. We do not sell your personal details to marketing companies or unrelated third parties.
Log in and open the account area — the profile and payment reference sections show what is currently on file. For data categories not displayed there, contact support with your account identifier and a description of what you want to review.
Yes. Raise a correction request through live chat or email support, quoting your account reference and the specific detail that needs to change. We verify the request against your account record before making any update, so have your verification information ready.
Retention periods depend on the obligations that apply in your eligible region under local law. Transaction records, including Bank Transfer and wallet payment history, are kept for the period required by those rules. Ask support for the figure that applies to your account.
Access to the platform and the data rights available to you depend on your local law and the eligible regions we serve. This policy sets out our general data handling approach; specific entitlements may vary based on where you are accessing the platform from.