Sports / Live
8855h is direct about how your personal data is collected, stored and used when you access your account or complete a transaction. This policy covers what we hold, why we hold it, and the steps you can take to review or correct it — subject to your local law and eligible regions.
When you open an account with us, you share certain personal details — your name, contact information and, where applicable, the payment method you use to fund your wallet. We collect this information to process your account, verify your identity as required, and keep your transaction history accurate. Payment routes such as Rocket, Upay and Bank Transfer each involve their own data exchange with the relevant provider; we retain only what is necessary on our side to maintain your account record and process your requests. We do not sell your personal data to third parties for marketing purposes. Data shared with payment processors is limited to what those processors need to complete the transaction you initiate. Your account activity — deposit records, withdrawal requests, game session logs — is stored in line with standard platform retention practice and is accessible to you through the account area while your account remains active. Where local law in Bangladesh or applicable eligible regions requires us to hold data for a statutory period, we comply with that obligation. If you have a question about a specific data point we hold, the contact routes in the Support section of this policy are the right place to start.
Not every part of your experience falls under the same privacy framework. Understanding where our policy applies — and where it does not — helps you know who to contact when a data question comes up.
When you log in, create a profile or update your details, that activity falls fully within this policy. We control that data directly and you can request a review or correction through your account settings.
Deposits and withdrawals via Rocket, Upay or Bank Transfer involve a shared data exchange with the payment provider you choose. We hold the reference on our side; the provider holds its own record under its own privacy terms.
Game titles, lobby pages and promotional notices are served from our platform. Browsing these pages generates session data we use to maintain site function, not to profile you for third-party advertising.
Links to external sites, payment gateways or game studios outside our platform are governed by those parties' own policies. We have no control over what those third parties collect once you leave our pages.
Your data is not locked away. Several actions are available to you directly, and others can be initiated by contacting us through the published support routes. Start by logging into your account — the account area shows the profile details we currently hold, including the name, email and mobile number attached to your wallet. If anything looks incorrect, you can submit a correction request through the same area or by messaging support directly. For transaction records linked to Rocket, Upay or Bank Transfer, the history view in your account dashboard reflects what we hold on our side. If a record appears missing or inaccurate, raise it with our support team and reference the transaction date and payment method used. Where local law in Bangladesh grants you a formal right to request deletion or restriction of certain data, you can make that request in writing through our contact route. We will respond in line with the applicable legal timeframe for your eligible region.
Open your account profile to see the personal details we hold — name, contact information and linked payment methods. This view is available any time you are logged in.
If a name, mobile number or email address is wrong, submit a correction through your account settings or contact support with the correct information and we will update the record.
For questions about what specific data we hold, how long we keep it, or why a particular record exists, contact us through the support route listed in this policy. Be as specific as you can about the record in question.
Where your local law allows a formal data request — access, restriction or deletion — send it to the contact address published below. We will confirm receipt and respond within the timeframe required under applicable rules.
If your question is about the data we hold on your account, a transaction record linked to Rocket or Upay, or a formal data request under local law, use the contact routes below. We do not publish operating hours or response-time commitments we cannot verify — check the contact page on site for the current published routes.
The live chat icon in your account area connects you to the support team. Use this route for account data questions, transaction record queries or to start a formal data request.
Send written data queries or formal requests to the email address published on our contact page. Include your account reference and the specific data point or transaction you are asking about.
The Help section in your logged-in account covers common data and privacy questions. Check there first — it may resolve your query without needing to wait for a reply from the team.
We apply standard platform-level controls to protect the data linked to your account — covering access credentials, payment references and session records. No system is without risk, but we limit internal access to data on a need-to-know basis and do not retain payment credentials like full Rocket wallet numbers or Bank Transfer account details beyond what the transaction process requires.
We use cookies to keep your session active and to remember account preferences across visits. You can manage cookie settings in your browser, but disabling them may affect how your account area functions on mobile.
Access to your account is protected by your login credentials. We do not store your password in plain text. If you suspect unauthorised access, change your password immediately and contact support through the live chat route.
We keep your account data for as long as your account is active and for any period required by applicable law in Bangladesh or your eligible region. When data is no longer required, we delete or anonymise it in line with our standard retention schedule.
We update this policy when our practices change or when legal requirements in applicable regions require it. The current version is always the one published at this URL. Continued use of your account after an update means you have seen the revised terms.
These are the questions we hear most often about how we handle your data. If your question is not covered here, contact support through live chat or email using the routes in the Support section above.
We collect the name, email address and mobile number you provide at registration, plus the payment method you use — such as Rocket, Upay or Bank Transfer. We also hold transaction references and session logs needed to maintain your account.
Yes. Your account area shows the profile data we currently hold. For a full record including transaction history and session logs, contact support through live chat or email with your account reference and we will compile what we can share under applicable law.
We share data only where necessary — with payment processors handling your Rocket, Upay or Bank Transfer transactions, and where required by law. We do not sell your personal data to advertisers or unrelated third parties.
Log in and open your account profile to edit basic details. For changes that require verification — such as a linked mobile number used for Rocket or Upay — contact support directly with the correct information and your account reference.
We retain data for the period required by applicable law in Bangladesh and eligible regions. Some records — especially those tied to financial transactions — may need to be held for a statutory period even after account closure. Contact us if you want details about a specific record.
Change your password immediately using the account security settings, then contact our support team through live chat. Provide your account reference and the date you noticed the issue so we can check the access log on our side.