Casino / Sports
This policy explains what data 1xlive collects when you use your account, how we store it, and the choices available to you. Access to this platform and the rights described here depend on your local law and eligible regions.
When you open an account with us, we collect the information needed to operate it: your registration details, session activity, and transaction records tied to payment methods such as bKash, Upay, and Bank Transfer. These records are held to process your requests, maintain account accuracy, and respond to support queries. We do not sell your personal data to third parties for marketing purposes. Data shared with payment processors — including those handling bKash and Bank Transfer transactions — is limited to what is necessary to complete the transaction you have requested. Each processor operates under its own data terms, which we encourage you to review separately. Data retention follows the requirements of applicable law for your jurisdiction. Where local law in Bangladesh or another eligible region prescribes a retention period, we apply it. Where no period is set, we keep data only as long as your account remains active or as needed to resolve any open query. If you have questions about how a specific data type is held, the policy contact route in the support section below is the place to start.
Transaction data from bKash deposits and withdrawals is retained for account accuracy and query resolution.
Upay payment records are handled with the same data standards applied to all wallet transactions on your account.
Bank Transfer records are kept in line with applicable jurisdiction requirements and available to you on request.
Not every service connected to your account falls under this policy directly. Understanding the boundaries helps you know where to direct a data question.
Details you submit when opening or updating your account — name, contact, login credentials — are covered fully by this policy. You can request a review of this data through our policy contact route.
Payment records for bKash, Upay, and Bank Transfer sit within your account wallet history and are covered here. The payment processor handling the transfer also holds a copy under its own policy.
Pages you visit, session duration, and device type are logged to keep the account functional and secure. This data is covered by this policy and is not shared for unrelated commercial purposes.
Links to external services, game studios, or payment provider portals operate under their own terms. Once you leave our platform, this policy does not follow you to those third-party environments.
You have practical options when it comes to the data we hold on your account. These are not abstract rights — each one has a real route you can follow. Your account dashboard shows the registration and wallet details currently on record; checking those fields is the first step before raising any correction request. If something is wrong — a name spelling, a contact detail, a linked payment method — you can update it directly in account settings or write to our policy contact address. For data held outside the editable fields, a written request to our support team opens a formal review. We aim to acknowledge policy requests within a reasonable period and keep you informed of progress. Where your request involves transaction data, such as a bKash or Bank Transfer record, include the relevant date and reference from your account history to help us locate it quickly.
Open your account dashboard after login to see the current state of your registration data and wallet history, including bKash and Bank Transfer entries.
Editable fields in account settings let you update contact information directly. Changes take effect once saved and verified through the on-screen steps.
For data not visible in your dashboard, contact our policy support route with your account reference and a clear description of what you are asking about.
Where local law in your eligible region supports a removal request, we will review it and respond. Outcome depends on retention obligations applicable to your jurisdiction.
If this policy raises a question you cannot resolve through your account dashboard, these are the routes to reach our team. Each channel is monitored; include your account reference so we can locate your records without delay.
Open the live chat widget from your account page. For policy queries, state 'data request' at the start of the conversation so the agent can direct it correctly.
Send your data or policy question to our support email address shown in the account help section. Include the date and method of any relevant transaction — bKash, Upay, or Bank Transfer.
The help centre inside your account lists policy request forms and document submission paths. Check there first for step-by-step guidance before writing to the team directly.
We apply technical measures to keep your account data secure from the point of collection through to storage. Cookies on the platform are used to maintain your session state and remember preferences — not to build advertising profiles for third parties. You can adjust cookie preferences through your browser settings at any time, though some account functions depend on session cookies to work correctly. Data access within our team is restricted to staff with a need to process your account or handle a support query; it is not available to the wider organisation on an open basis. Account security steps — such as the verification fields shown at login — are in place to prevent unauthorised access to your records.
Cookies maintain your login session and record your account preferences. We do not use cookies to share your browsing behaviour with advertising networks.
We keep account and transaction data for as long as required by applicable law in your eligible region. Where no period applies, data is held only while your account is active.
Login verification steps shown in your account are designed to stop unauthorised access. If you notice unexpected account activity, contact support immediately using the chat route above.
When this policy changes in a material way, we publish the updated version here and note the revision date at the top of the page. Continued account use after an update indicates you have read it.
These are the questions we receive most often about data handling, account records and policy rights. If your question is not here, the support routes above will connect you with the right team.
We collect the details you submit during registration — name, contact information, and login credentials. Once your account is active, session data and transaction records, including bKash and Bank Transfer history, are added as you use the platform.
Your account dashboard shows your registration details and wallet transaction history after login. For data held outside those visible fields, submit a written request through our email policy contact and we will review what can be shared.
Editable fields in account settings let you update contact details and linked payment methods directly. For information that cannot be edited by you, contact support with your account reference and describe the correction needed.
We share data only where necessary — with payment processors handling bKash, Upay, or Bank Transfer transactions, and where required by applicable law. We do not sell account data to third parties for marketing or advertising.
Retention periods follow applicable law in your eligible region. Where local law in Bangladesh or another eligible region sets a period, we apply it. Where no specific period applies, we keep data only while your account is active or a query is open.
Closing your account triggers a review of which data can be deleted and which must be retained under applicable law. We will confirm what is removed and what is kept, and for how long, at the time you make the request.
Yes. Transaction records for bKash, Upay, and Bank Transfer are part of your account wallet history and are covered by this policy. The payment processor also holds a copy under its own separate data terms, which you can review directly with that provider.