Mobile / Sports
This policy explains exactly what data 77w collects when you use your account, make a bKash or Nagad transaction, or browse the lobby — and what we do with it. Access and eligibility depend on your local law and the region where your account is registered.
When you open an account with us, we collect the details you submit during registration — name, contact information and the payment method you choose, whether that is bKash, Nagad, Rocket or Upay. We record transaction references tied to those wallet sessions so your account wallet balance stays accurate and disputes can be reviewed. As you browse game categories — slots, live casino tables, crash games — our systems log session data: device type, connection state and the pages you visit. We use this to keep your session active across a switch from mobile data to Wi-Fi without dropping your place in a hand or spin. We do not sell your personal data to third parties. We share information only where it is required to process your payment (for example, passing a bKash reference to confirm a deposit) or where we are legally required to do so in the eligible region. Cookies and local storage are used to remember your login state and maintain your account preferences between visits. You can manage cookie settings through your browser, though some account functions depend on session cookies to work correctly. This policy applies only where 77w operates in a supported region under applicable local law.
Not every part of your experience on 77w falls under exactly the same rules. The table below separates what this policy covers directly from what sits outside its scope — so you know exactly where to look when a question comes up about your data, your transactions or a third-party link.
Login sessions, registration data and account preferences are covered fully by this policy. We control how that data is stored, how long it is kept and who inside our operation can access it.
When you deposit via bKash, Nagad or Rocket, the reference data we hold is covered here. The payment processor's own handling of your wallet — what bKash or Nagad logs on their side — is governed by their separate policies.
Game session data, live table records and crash game history generated on our platform are covered under this policy. RTP figures and game mechanics published by studios like Pragmatic Play or PG Soft are their own disclosures.
Links to external sites, wallet apps or payment portals that open outside 77w are not covered by this policy. Once you leave our domain, the destination site's privacy rules apply.
Your account dashboard is the first place to check if you want to see what data we hold. After login, the account details section shows the personal information you submitted at registration and the payment methods attached to your wallet. If something is wrong — a name spelled incorrectly, a contact number that has changed — you can update it directly through the account settings fields shown there. For anything you cannot edit yourself, raise it through our support channel and we will action the correction on our end. If you want to know specifically what transaction records we hold against your bKash or Nagad deposits, open a support request with your account reference and we will provide a summary. Requests to remove data are handled in line with the retention rules below and applicable local law in your eligible region. We aim to respond to written data requests within a reasonable period; the current queue time is shown when you submit the form.
Log in and open the account details page. The data we hold on your registration and linked payment methods is listed there. No separate request is needed just to view what you can already see in your dashboard.
Edit fields directly in account settings for most personal details. For changes that require identity verification — like a linked bKash number — submit a support request with your account ID.
If you are unsure whether specific data is being held or how a particular session was recorded, contact support with your account reference. We will confirm what is logged and under which category.
Removal requests are assessed against our retention schedule and local legal requirements in your region. Submit the request through the support form; eligibility and timeline are confirmed when we review your case.
If your question is specifically about how your data is handled — not a game or payment issue — these are the direct routes to the right team. Reference your account ID in any message so we can pull your records without delay.
The account support form, accessible after login, is the fastest way to submit a data or privacy question. Select the privacy category in the dropdown so it routes to the right team.
Send your privacy request to our published support address. Include your registered account name and the specific data question — for example, which bKash or Nagad transaction records you are asking about.
Live chat is available through your account dashboard. For privacy matters, use it to get a reference number first, then follow up in writing so there is a documented trail for your request.
We take a straightforward approach to data security: collect what we need, hold it only as long as the account or legal requirement demands, and restrict access inside our operation to roles that need it. Here is how each part of that works in practice.
We keep account and transaction records for as long as your account is active and for the period required by applicable law in your eligible region. After account closure, records are held for the legally mandated retention window, then deleted or anonymised.
Session cookies keep your login active between pages. Preference cookies remember your language and account settings. You can block non-essential cookies in your browser settings, but session cookies are required for your account to function correctly across a bKash payment flow.
Account access is protected through credentials you set at registration. If you suspect unauthorised access to your account, change your password immediately through the account settings page and contact support with your account reference for a session audit.
When this policy changes materially, we update the version date shown at the top of this page. Continued use of your account after a posted update means you have seen the revised terms. You can request a summary of what changed by contacting support.
These are the questions we get most often about how we handle account data, cookies and your rights under this policy.
We pass only the transaction reference needed to confirm a deposit or withdrawal to the relevant payment processor — bKash, Nagad or Rocket. We do not share your full wallet details or account data with third parties for marketing or any unrelated purpose.
Most of it is visible directly in your account dashboard after login — registration details, linked payment methods and session history. For a full data summary, submit a request through the support form with your account ID and we will compile it.
After closure, we retain records for the period required by applicable law in your eligible region. Once that window passes, personal data is deleted or anonymised. The specific retention period depends on local legal requirements and is confirmed when you request account closure.
Session cookies are required for your login and account wallet to work correctly — including during a bKash deposit flow. Non-essential preference cookies can be declined through your browser settings without losing core account functions.
Log in and go to account settings to update most personal fields yourself. For changes that affect your linked payment method — such as a registered bKash or Nagad number — raise a support request with your account ID and we will process the correction after verification.
This policy covers the data our platform collects during your game session — session logs, account state and wallet activity. Game mechanics, RTP information and studio-level disclosures from Pragmatic Play, PG Soft or other studios are governed by their own published terms, not this policy.