Sports / Mobile
xe33 collects only the information needed to run your account, process wallet transactions through bKash and Upay, and keep your session secure. This policy sets out exactly what we collect, why we hold it, and what you can do about it — your access to these rights depends on your local law and eligible regions.
When you open an account on xe33, we record the details you submit during registration — your name, contact address and the credential you use to log in. Each time you start a session, we note the device type, browser version and approximate network region so we can serve the correct mobile layout and keep your account reachable across sessions. When you add a wallet — bKash or Upay — we store the reference needed to match your deposit or withdrawal request to your account record. We do not store full mobile wallet credentials on our servers; the payment rail handles authentication on its own platform. Transaction references, amounts and timestamps are kept in your account ledger and are visible to you from the wallet section of your account page. We retain active account data for as long as your account remains open. If your account is closed, we keep a minimal record for the period required by the applicable financial and legal obligations of the jurisdiction governing this service. Data collected through cookies and session tokens is described separately in the scope section below. Your continued use of xe33 after any update to this policy signals your acceptance of the revised terms, subject always to your local law and the eligible regions where this service operates.
bKash wallet references are stored only as a transaction identifier. Full wallet authentication stays within the bKash platform.
Upay deposit and withdrawal references appear in your account ledger. We do not hold or process your Upay PIN or login credentials.
Name, contact details and login credential collected at registration. Used only for account access and identity verification steps.
Device type, browser and session token logged per visit to maintain mobile layout continuity and account security across return sessions.
This policy covers data processed directly by xe33 in connection with your account and activity on xe33. It does not extend to third-party services that operate under their own terms, even when those services are reachable from within your session. Understanding the boundary between what we control and what sits outside our scope helps you know where to direct any data question.
All data collected when you create or log in to your account falls within this policy. This includes registration fields, login history and any account-level settings you adjust from the account page.
Deposit and withdrawal records created inside xe33 — including bKash and Upay transaction references — are covered by this policy. The payment provider's own data handling sits outside our scope.
Cookies, session tokens and browsing data generated while you are on xe33 are covered here. This includes page-visit logs and the device signals we use to serve the correct mobile layout.
Game studios, payment platforms and any external link you follow from xe33 operate under their own privacy terms. Once you leave xe33 or authenticate directly with a third-party service, this policy no longer applies.
Your account page on xe33 is the starting point for most data-related actions. From there, you can review the personal details we hold, check your transaction ledger and update contact information that has changed. If you spot a detail that looks incorrect — a name spelling, a contact address or a wallet reference — use the edit fields in your account settings and save the change directly. Changes to sensitive fields may trigger a verification step shown on screen. For anything that cannot be adjusted through the account page itself, the support route is your next step: submit your request through the contact channel visible on the site, describe the record you want corrected or removed, and we will respond in line with the obligations that apply in your region. Data requests tied to account closure follow a separate process; the steps are shown in the account closure section of the account settings page. Your rights under this policy are subject to local law and the eligible regions where xe33 operates.
Open the account page and navigate to your profile section. Registration details, wallet references and transaction history are all visible from that single location.
Use the edit fields in account settings to update name, contact address or linked wallet reference. A screen-level verification step may appear for sensitive changes.
For corrections that cannot be made through the account page, contact support through the channel published on xe33, naming the specific record you want addressed.
Account closure and data removal requests are handled through the account settings closure flow. The steps and any applicable retention period are shown there.
If you have a question about how we handle your data, or you want to act on a right described in this policy, use the contact routes published on xe33. We do not publish support hours or response-time commitments we cannot consistently keep, so the route descriptions below reflect what is visible on the site rather than an invented service level.
The live chat widget on xe33 is the quickest way to raise a data or privacy question. Open it from any page while logged in and describe the record or request you need help with.
A support request form is available from your account page. Use it to submit written data requests — corrections, access queries or removal requests — with your account details attached automatically.
An email contact address is published in the footer of xe33. Use this route for formal written data requests where you need a documented exchange for your own records.
We apply consistent data-handling practices across account creation, wallet activity and session management so that what you see in your account reflects what we actually hold. Cookies and session tokens on xe33 serve functional purposes — keeping you logged in across a mobile session, remembering your layout preference and tracking only the session data needed to run the service. Advertising or behavioural tracking cookies from third parties are disclosed in the cookie notice linked from the site footer. Retention periods follow the obligations applicable to the region and jurisdiction governing your account. You can request a copy of the data we hold by using the support routes described above.
Functional cookies keep your session active and maintain mobile layout continuity. Third-party cookie use is disclosed in the cookie notice in the site footer. You can manage browser cookie settings directly on your device.
Login credentials are stored in hashed form. Wallet references — bKash, Upay — are held as identifiers only, not as authentication tokens. Suspicious login attempts trigger a screen-level alert in your account.
Active account data is held for the life of your account. After closure, we retain the minimum record required by applicable financial and legal obligations in the governing jurisdiction.
When this policy is updated, a notice appears on xe33 at your next login. Continued use of the site after that notice constitutes acceptance, subject to your local law and eligible region.
These questions cover what real account holders ask about data rights, wallet records, cookies and how to make a request. If something is not answered here, the support routes on xe33 are the right next step.
We collect the name, contact details and login credential you provide during registration. Device type, browser version and session tokens are also recorded each visit to maintain your mobile layout and keep your account accessible across return sessions.
No. We store only a transaction reference that links a deposit or withdrawal to your account ledger. Your bKash or Upay PIN and wallet login stay entirely within those platforms. We never hold or process your wallet authentication details on our side.
Your account page shows registration details, wallet references and your full transaction history. For a broader data access request, use the support form in your account or the email route published in the site footer, and we will respond according to the obligations applicable in your region.
Yes. Open account settings and use the edit fields to correct your name, contact address or linked wallet reference. Sensitive field changes may trigger a verification step shown on screen. For corrections that cannot be made through the account page, submit a request through live chat or the support form.
After closure, we retain the minimum record required by the financial and legal obligations of the jurisdiction governing your account. The specific retention period and the closure steps are shown in the account settings closure flow. You can request details through the contact routes on xe33.
We use functional cookies to keep you logged in and maintain mobile session continuity. Third-party cookie use is detailed in the cookie notice linked from the site footer. You can manage or block cookies through your browser or device settings at any time, though some functions may be affected.
No. Once you follow a link to a third-party service — a payment platform like bKash, a game studio or an external site — that service's own privacy terms apply. This policy covers only the data xe33 processes directly on xe33 and within your account.