Live / Sports
wd77 collects only the information needed to run your account, process wallet activity through bKash, Nagad or Rocket, and keep your sessions secure. This page sets out exactly what we collect, why we collect it, and what you can do about it — with access subject to your local law and eligible regions.
When you open an account on wd77, we collect the details you enter during registration — your name, contact address and login credentials. When you add a wallet such as bKash, Nagad or Rocket to your account, we record the transaction reference and wallet identifier so that deposits and withdrawals can be matched to your account record. We do not store your full mobile banking PIN or one-time passwords; those remain between you and your payment provider. We also collect session data: the device type, browser version and pages visited within the lobby. This helps us keep the site working correctly on the devices our users actually carry. Cookie data and session tokens are used solely for authentication and site function — not sold to third parties. All collected data is retained only as long as your account is active or as required to meet legal obligations in the jurisdiction where access is permitted. If you close your account, we follow a structured deletion schedule for personal data, except where retention is required by applicable law. Any questions about what we hold can be directed to our published support route. Access to and use of wd77 depends on your local law and the eligible regions we serve.
When a bKash deposit is made, we record the transaction reference and wallet number only — no PIN or OTP is ever stored on our side.
Nagad transfers generate a reference we keep in your account ledger. The underlying Nagad authentication stays entirely within the Nagad platform.
Rocket payment identifiers are logged to your account history so you can match any transaction to a date and amount in your wallet view.
This policy covers the data wd77 directly controls — your account record, wallet links, session tokens and support correspondence. It does not extend to third-party services you reach through our platform, including your mobile banking provider or any studio game environment that runs on an external server. Knowing the boundary helps you ask the right questions to the right party.
Login credentials, device fingerprints and session tokens created when you sign in fall fully within this policy. We control how they are stored, how long they persist and when they are cleared.
Transaction references from bKash, Nagad and Rocket that appear in your account ledger are covered here. The payment provider's own data practices are governed by their separate privacy terms.
Pages you browse within the wd77 lobby and game sessions you open are logged at the platform level. Game mechanics data processed inside a studio environment is outside our direct control.
Links or tools that take you away from wd77 operate under the privacy terms of those external services. We are not responsible for data handling outside our own platform.
You have real, actionable options under this policy — not just abstract language. If you want to see the personal data we hold against your account, you can request a data summary through our support channel and we will compile what we have on record. If any detail is wrong — a misspelled name, an outdated contact address — you can ask us to correct it by raising a support ticket with the corrected information. We will confirm the change once it has been applied. For wallet records tied to bKash, Nagad or Rocket, the transaction history visible in your account area reflects what we have logged. If you spot a discrepancy, contact support with the transaction reference and date. We will cross-check our records and respond through the same channel. Closing your account and requesting deletion of personal data is also an option; just reach out through our published support route. Access to these rights depends on applicable local law and eligible regions.
Request a summary of personal data we hold by contacting support. We will share what is stored against your account in a readable format.
Raise a support ticket with the correct information and we will update your account record and confirm once the change is applied.
If a bKash, Nagad or Rocket entry in your transaction history looks wrong, send us the reference and date. We will check and respond through the same channel.
Contact support to close your account and request removal of personal data. Retention obligations under applicable law may affect how fully or quickly this can be completed.
If you have a question about how your data is handled, a request to access or correct it, or a concern about a specific transaction record, use any of the contact routes published on wd77. We do not publish response-time promises here, but our support team handles privacy queries through the same channels used for account and payment questions.
Open the chat widget on wd77 and select the account or privacy topic. Our team will pick up the conversation and direct your query to the right place.
Send a written privacy request to the email address listed on our contact page. Include your account identifier and a clear description of what you need so we can respond accurately.
Log into your account, open the support section and submit a ticket tagged as a data or privacy request. The ticket creates a reference number you can use to follow up.
We keep your account data behind authentication layers and session controls. Cookies on wd77 are used for login persistence and site function only — no advertising profiling, no cross-site tracking shared with third parties. Data is retained on a schedule tied to your account status and any legal obligations that apply in regions where access is permitted. You can request a change, correction or deletion at any point through our published support routes.
Cookies we set are limited to authentication tokens and site-function preferences. They expire when your session ends or on a short fixed schedule. No advertising cookies are set by our platform.
Login credentials are stored in hashed form. We do not store your bKash, Nagad or Rocket PIN. Access to account data internally is limited to staff with a direct operational need.
Personal data is retained while your account is active. After closure, we follow a deletion schedule except where local law or a legal obligation requires us to keep specific records longer.
When this policy changes materially, we note the revision on this page. Continuing to use the platform after a posted update means you have seen the new version; contact support if you have questions.
Below are the questions we get most often about how wd77 handles your data. If your question is not here, use the live chat or support ticket route on the site.
We collect the name, contact details and login credentials you enter at registration. If you link a bKash, Nagad or Rocket wallet, we log the wallet identifier and transaction references — not your PIN or OTP. Session and device data is also recorded for site function.
We do not sell your personal data. Transaction references are shared with payment processors like bKash, Nagad or Rocket only to the extent needed to process your wallet activity. Game content studios receive only the session data required to run the game you open.
Contact our support team through live chat, email or the in-account ticket system. Ask for a data summary and include your account identifier. We will compile what we hold and share it with you through the same channel.
Yes. Raise a support ticket with the correct information and we will update the record. We confirm the change once it is applied. For wallet-linked details, include the relevant bKash, Nagad or Rocket reference so we can match it accurately.
We follow a structured deletion schedule for personal data after account closure. Some records may be retained longer where applicable local law or a legal obligation requires it. Contact support for details specific to your account and region.
This policy covers data wd77 collects through wd77. Access to the platform itself depends on your local law and the eligible regions we serve. If local law restricts your access, this policy applies only to the extent you are permitted to use the service.