App / Sports
bdt688 collects only the account data needed to run your wallet, verify transactions through Nagad or Upay, and keep your session secure. Access to our platform and the scope of this policy depend on your local law and eligible regions.
When you open an account with bdt688, we collect the information you provide during registration — your name, contact details and the payment method you link, such as Nagad or Upay. We also record transaction references generated when you move funds through your account wallet. This data is used strictly for account verification, payment processing and fraud prevention. We do not sell your personal information to third parties. We do not share it with advertisers. Where we work with payment processors, those partners receive only the minimum data required to complete a transaction. Technical data — device type, browser session identifiers and IP address — is collected automatically when you access the platform. This helps us detect unusual login patterns and protect your session. You can find the session and device history inside your signed-in account area. We retain account data for as long as your account remains active and for a period after closure as required by applicable regulations, which vary by jurisdiction. If you are accessing the platform from Bangladesh, your rights and our obligations are shaped by the local law and eligible-region conditions that apply at the time of access.
Transaction references linked to Nagad payments are stored for account reconciliation only.
Upay wallet data is passed to the payment processor in minimal form to complete the transfer.
Your wallet balance and transaction log are visible in the signed-in account area at any time.
Device and session identifiers are held for security monitoring and are not used for marketing profiling.
This policy covers every interaction you have with bdt688 directly — account creation, wallet activity, support contact and browsing the game lobby. It does not extend to third-party sites you reach through any external link, nor to the data practices of payment processors like Nagad or Upay, who operate under their own published terms. Understanding what falls inside and outside our scope helps you know exactly who to contact when a question arises.
Login sessions, profile fields and any information you submit through the bdt688 account page fall fully within this policy.
Payment references we hold on our side are covered here; the payment processor's own records fall under that processor's policy.
Game lobby data, session logs and support ticket content generated on bdt688 are within scope.
External links, studio platforms and wallet apps like Nagad or Upay operate under their own separate privacy terms, not ours.
You have concrete actions available under this policy. First, you can review the personal data we hold by opening the account settings page in your signed-in session — your profile fields and linked payment details are displayed there. If any detail is incorrect, you can update it directly through the account edit screen or raise a correction request through our support channel. Second, you can ask us what data categories we hold for your account; our support team will respond with a factual summary. Third, if you decide to close your account, you can request that we delete active profile data not required for regulatory retention — use the written contact route listed in the support section below. Response timelines depend on the complexity of the request and applicable local requirements, which vary by region. We aim to handle every request through a clear, traceable process so you are not left guessing about the outcome.
Open account settings in your signed-in session to see the profile and payment details we currently hold.
Edit fields directly in the account screen or submit a correction request through the support channel.
Contact support with a written request; we will provide a factual summary of the data categories held for your account.
Submit a written closure and deletion request; we will confirm what data is removed and what is retained under applicable rules.
If you have a question about how your data is handled, or if you want to act on any of the rights described above, use the contact routes published on this site. We do not invent support hours or response commitments here — check the contact page for the channels currently active.
Open the live chat widget from any page in your signed-in session to raise a privacy question with the support team directly.
Send a written privacy request to the support email address listed on the contact page; keep a copy of your message for reference.
The help centre linked from your signed-in account area contains published answers to common privacy and data questions.
We apply access controls so that only the account systems that need your data can read it. Cookies on this site are used for session management and security checks — not for cross-site advertising. You can manage cookie preferences through your browser settings at any time. If you want to request a change to retained data or understand our retention schedule, contact support using the written route described above.
Account data is accessed only by the systems that require it to process your session, wallet activity or support request — no broader internal sharing.
We use session cookies to keep your login active and security cookies to flag unusual access patterns. No third-party advertising cookies are set by us.
Device and session logs in your account area let you spot unfamiliar logins. If you see one, change your password and contact support immediately.
We hold data for the period required by applicable rules. Policy updates are published on this page; continued use after an update means you have seen the revised version.
These are the questions we hear most often about how bdt688 handles account and personal data. If your question is not covered here, use the support routes in the section above.
We collect the name, contact details and payment method you provide at registration, plus session and device identifiers recorded automatically when you log in. Transaction references for Nagad or Upay payments are also stored for account reconciliation.
We do not sell your data. We pass minimum transaction details to payment processors such as Nagad and Upay only to complete a transfer. Those processors operate under their own published privacy terms, which you should review separately.
Open the account settings page in your signed-in session. Your profile fields, linked payment details and session history are displayed there. For a broader summary of data categories, submit a written request through the email support route on our contact page.
You can edit profile fields directly in account settings. To request deletion of data not required for regulatory retention, send a written request through the support email. We will confirm what is removed and what must be kept under applicable rules.
Cookies on this site handle session management and security checks — they keep your login active and help detect unusual access patterns. We do not use advertising cookies. Manage your cookie preferences through your browser settings at any time.
This policy covers your interaction with bdt688 wherever you access it, but your specific rights and our obligations depend on local law and eligible regions. If access is subject to local restrictions, those conditions shape what applies to your account.