App / Sports
md678 is clear about what data we collect, why we collect it, and how you can act on it. This policy applies to your account, your wallet activity across bKash, Nagad and Rocket, and every interaction you have with our platform — subject to your local law and eligible regions.
When you register on md678, we collect the details you provide — your name, contact information, and the payment method you choose to fund your account. For Bangladesh accounts, that typically means a bKash number, a Nagad account or a Rocket wallet reference. We use this data to verify your account, process wallet transactions, and route support queries to the right team. We do not sell your personal data to third parties. We do not share it with advertisers or marketing networks outside our own platform operations. Data shared with payment processors — such as those handling bKash, Nagad or Rocket transfers — is limited strictly to what those processors need to complete your transaction. Session data, including your device type, browser and approximate location, is collected to maintain platform security and improve how the site loads on mobile. Cookies are used to keep your session active and remember your login state. You can manage cookie preferences through your browser settings at any time. All data handling described here depends on the laws and regulations applicable in your region — access to this platform and all associated data practices are subject to local law and eligible regions.
Your bKash number is used only to process deposits and withdrawals linked to your account. It is shared with the payment processor solely to complete that transaction and is not stored beyond what the processor requires.
Nagad wallet details follow the same limited-sharing rule. We pass only the data the transfer requires and retain no payment credentials on our own servers beyond what account verification demands.
Rocket payment references are handled through the same data-minimisation approach. Transaction records appear in your account history, and any dispute about a Rocket transfer can be raised with our support team.
Not every interaction with md678 falls under the same privacy rules. This section maps out what sits inside this policy, what sits outside it, and where the boundary lies between our responsibilities and those of third-party services you might use alongside your account. Understanding scope helps you direct questions to the right place — our support team handles the areas we control directly.
All data you submit during sign-up and login — including contact details and account credentials — is covered by this policy. We control how that data is stored, accessed and deleted on our systems.
Transactions processed through bKash, Nagad or Rocket involve both our platform and the relevant payment processor. This policy covers our side of that exchange; the processor's own privacy terms govern their handling.
Session data generated while you browse the lobby or play a game round is collected by us for security and performance purposes. Game studios such as Joker, PG Soft, Spadegaming and Habanero supply content only; their own data practices apply to their software.
Links or services outside md678 — including any external support tools or partner pages — are not covered by this policy. Once you leave our domain, the privacy terms of that external service take effect.
Your account gives you direct access to several data-related actions without needing to contact us first. Log in and open your account settings to review the profile information we hold — name, registered contact number and linked wallet details are all visible there. If something is wrong, you can edit standard fields directly from the settings screen. For records you cannot change yourself — such as transaction logs tied to a completed bKash or Nagad transfer — raise a query through the support channel and our team will review the record with you. You also have the right to ask what data we hold overall. Submit that request through the published support route and we will respond with a summary of the categories of data linked to your account. If you believe any data has been handled incorrectly, that is the same route to use. All requests are subject to the verification steps shown in your account and to the laws applicable in your region.
Open account settings after logging in to see the profile data we hold. Transaction history, including completed bKash and Rocket transfers, appears in the wallet section of your dashboard.
Editable fields — display name, contact number, linked wallet reference — can be updated directly from settings. Changes take effect once you save and, where required, confirm via your registered contact.
If a record looks wrong or you want to know what specific data we hold, open a support query and describe the account detail in question. Our team will check the record and respond through the same channel.
You may request that we delete your personal data. Submit the request through support. We will assess it against the retention obligations that apply to your account under local law before confirming what can be removed.
If you have a specific question about how your data is handled — or if you want to exercise any of the rights described on this page — use the contact routes published directly on md678. We do not list channels here that are not active; use only the routes you can verify on the site.
Open the chat widget from any page on md678 to ask a privacy-related question. Describe the data point or account record you are asking about and the team will respond in the same session.
Send a written data request or policy question to the support email address listed on the Contact page of md678. Include your registered contact number so the team can locate your account record.
The help centre on md678 covers the most common questions about account data, wallet records and cookie settings. Check there first — many data queries are answered without needing to open a support ticket.
Data security on md678 is applied at the account layer, the session layer and the payment layer. Your login credentials are not stored in plain text. Wallet references — bKash numbers, Nagad accounts, Rocket identifiers — are handled through encrypted channels during every transfer. We retain account data for as long as your account is active and for as long as applicable law in your region requires us to keep records after closure. Session cookies are cleared when you log out; persistent cookies that remember preferences can be removed from your browser settings at any time. If you want to know the specific retention period that applies to your account, raise it through the support route and we will confirm what the applicable rules require.
Login credentials are protected through encryption at rest. Any suspicious login attempt triggers a verification step visible on your account screen before access is granted.
Session cookies keep your login active while you browse. Persistent preference cookies can be cleared through your browser settings. No advertising cookies are set without your interaction with the relevant toggle.
We keep your account data while your account is open and for the period local law requires after closure. Transaction records linked to bKash, Nagad or Rocket transfers are retained to meet financial record obligations.
When this policy changes, the updated version is published on md678 with the revision date shown at the top of the page. Continuing to use your account after a change means you have seen the updated terms.
These are the questions we hear most often about how your data is handled, what rights you have and how to act on them. If your question is not answered here, use the live chat or email route published on md678.
We share wallet details — bKash number, Nagad reference or Rocket identifier — only with the payment processor completing your transaction. That data is not passed to advertisers, third-party marketers or any entity outside that payment chain. The processor's own privacy terms apply to their handling.
Log into your account and open the settings page. Profile data and linked wallet references are visible there. For a full summary of all data categories we hold, submit a written request through the support email published on md678 and we will respond with a breakdown.
Yes. Submit a deletion request through the support channel on md678. We will review it against the retention obligations that apply under local law — some transaction records must be kept for a defined period — and confirm exactly what can be removed and when.
We use session cookies to keep you logged in and preference cookies to remember your lobby settings. No advertising cookies run without your interaction with the relevant control. Clear any cookie type through your browser settings; session cookies are removed automatically when you log out.
After account closure, we retain the data that local law in your eligible region requires us to keep — typically transaction records for a defined period. Data that falls outside those legal obligations is removed on request. Contact support to start the closure and data review process.
Access to md678 and the data practices described in this policy are subject to your local law and whether your region is an eligible one. Check the eligibility information in your account area or raise the question with support if you are unsure whether this policy applies to your specific situation.