Live / Sports
7h66 is clear about what data we collect, why we collect it, and how it stays protected while you access the platform. Your information — including wallet details linked to bKash, Rocket, or Bank Transfer — is handled with care, and this policy tells you exactly where it goes.
This policy applies to all information you provide when you create an account, make a transaction, or contact our support team through any route we publish. When you link a payment method — whether that is bKash, Rocket, or a direct Bank Transfer — the wallet identifiers and transaction references involved are treated as account data under this policy. We collect the minimum information needed to operate your account: your registered contact detail, your payment method identifiers, and the activity record your account generates during sessions. We do not sell, rent, or share your personal data with third parties for their own marketing purposes. Data may be shared only where a legal obligation requires it or where a service provider we engage to run platform functions needs it — and in those cases, they are bound by the same data-handling standards we hold ourselves to. Your access to 7h66 and the applicability of this policy both depend on your local law and the eligible regions in which the platform operates. If local law changes how we can process your data, we will update this policy and notify you through your registered contact detail. The current version of this policy is always the one shown on this page.
When you transact via bKash, the wallet number and reference ID are stored as part of your account transaction record. We use these only to reconcile payments and handle any query you raise about that transaction.
Rocket transaction references linked to your account are held in the same way as other payment data — accessible to you through your account history and to our support team when you raise a question.
For Bank Transfer deposits or withdrawals, the reference numbers and account details you submit are retained for the duration required to resolve any transaction dispute and comply with applicable record-keeping obligations.
Not every service you reach from the 7h66 platform is covered by this policy. We control what happens inside your account and on our platform directly. Third-party payment processors, studio game servers, and external links operate under their own terms. Knowing the boundary helps you understand where to direct a data question.
Any information you submit at login — your registered contact detail, session token, or device identifier — is fully within this policy. We determine how it is stored, how long it is kept, and who inside our team may see it.
When a transaction moves through bKash, Rocket, or Bank Transfer, the portion processed on our side is covered here. The payment provider's own processing falls under their privacy terms — we do not control that leg of the transaction.
Session activity recorded on our servers — which games you opened, how long a session ran — is account data held under this policy. Game content served from a studio's infrastructure is subject to that studio's data practices.
If you follow a link from our platform to an external site or service, this policy stops at our domain boundary. We cannot speak to how third-party destinations handle your information once you leave our pages.
You have concrete steps available to you under this policy — not just abstract rights. If you want to see what data we hold against your account, send a request through the support route published on this page and we will provide a summary of your account record. If any detail in your account is wrong — a contact number, a registered name, a linked payment identifier — you can correct it directly from the account settings section after logging in, or ask support to assist if a field is locked. Where you believe data is being held beyond what is needed, you can raise that question with us directly; we will review the retention against our published criteria and respond. Availability of certain data actions depends on local law and the eligible region your account is registered under. We do not make decisions about data requests without acknowledging them first — every request receives a response through your registered contact detail.
Send a written request via our published support route. We will confirm what data we hold for your account, including transaction references and session records, within the timeframe stated in our response.
Log in and navigate to account settings to update contact or payment details directly. If a field cannot be edited from the account page, contact support with the correction and we will action it after verifying your identity.
If you have a specific question about how a piece of your data is used — for example, how a bKash reference is stored — use the support contact route and mark your message as a privacy query. We route those separately.
For anything beyond self-service — a deletion request, a data portability question, or a concern about third-party sharing — contact us through the published support channel with your account detail ready.
If you have a question about this privacy policy, your account data, or a specific transaction record — including anything connected to your bKash, Rocket, or Bank Transfer history — use the contact routes published on this site. We respond through your registered contact detail, so make sure the detail on your account is current before you write in.
The live chat widget is accessible from the account area when you are logged in. Use it to raise a privacy question in real time. Have your account identifier ready so we can locate your record quickly.
Send a written privacy query to the support email address published on the contact page. Include your registered contact detail and a clear description of your request. We reply to your registered email address.
After logging in, you can send a message directly from the account dashboard. This route keeps all correspondence linked to your account record, which is useful for follow-up on data or transaction queries.
We apply access controls to your account data so that only the team functions that need it can see it. Cookies on this site are used to keep your session active and to remember your device across visits — not to build advertising profiles. Retention periods are tied to the purpose: transaction records are kept for as long as is needed to resolve disputes and meet any applicable obligation; session data is held for a shorter period. If you want to know the retention period for a specific category of your data, ask us via the support route and we will state it clearly.
Your account data is accessible internally only to the team roles that need it to operate your account or handle your support requests. We do not give broader internal access than the task requires.
Cookies maintain your session state and device continuity when you return to the platform on mobile or desktop. We do not use third-party advertising cookies. You can manage cookie settings through your browser at any time.
We keep transaction records — including bKash and Rocket references — for as long as needed to resolve disputes and meet any applicable obligation. Session and browsing data is held for a shorter, defined period.
When we update this policy, the revised version appears on this page and we notify you through your registered contact detail. The date at the top of the policy always reflects the most recent revision.
These questions cover the situations we hear about most often — data access, payment references, cookies, and how to correct your account record. If your question is not here, reach us through the support route published on this page.
We collect the contact detail you register with, the payment method identifiers you link — such as a bKash number or Bank Transfer account reference — and the activity record your sessions generate. We do not collect more than is needed to run your account.
Your wallet identifiers are used only to reconcile your transactions and respond to any payment query you raise. They are not shared with third parties for marketing. The payment processor handling your transaction may see the reference, but they operate under their own privacy terms.
Send a request through our published support route — live chat, email, or the in-account message option. State clearly that you are asking for an account data summary. We will respond to your registered contact detail with the information we hold.
Log in and go to account settings — most fields can be updated there directly. If a field is locked and you cannot edit it yourself, contact support with the corrected detail. We will verify your identity and make the change.
Access to the platform and the application of this policy both depend on your local law and the eligible region your account falls under. If local law affects how we process your data, we update this policy and let you know through your registered contact detail.
Cookies keep your session active and recognise your device when you return — useful if you switch between mobile and desktop. We do not use advertising cookies. You can adjust cookie behaviour in your browser settings without affecting your ability to log in.