Sports / Casino
99dt collects only the information needed to run your account, process wallet transactions through bKash, Nagad and Upay, and keep your session secure. This policy tells you exactly what we hold, why we hold it, and how you can act on it — access and eligibility depend on your local law and the eligible regions we serve.
We collect information in three situations: when you open an account, when you complete a wallet transaction (such as a bKash deposit or Nagad transfer), and when your browser or mobile device interacts with our platform. The information collected typically includes your registered name, contact details, wallet identifiers used with bKash, Nagad or Upay, device type and session activity. We do not collect data we have no use for, and we do not sell or rent your personal records to third-party advertisers. Data retained for transaction verification — including any Nagad or Upay transfer reference — is held for the period required by the operational and compliance obligations that apply to our platform. We use session cookies to keep your login active and to understand which parts of the site you access most. You can clear cookies from your browser settings at any time, though this will end your current session. Where third-party game content from studios such as Pragmatic Play or Habanero is loaded inside the platform, those studios operate under their own data terms for in-session game data. Our policy covers the account layer we control, not the in-game data those providers handle separately.
bKash wallet identifiers linked to your deposit or withdrawal are held for transaction verification purposes only and are not shared with unrelated third parties.
Nagad transfer references are stored as part of your account transaction record and are accessible to you through the wallet history section of your account.
Upay payment identifiers follow the same retention rules as other wallet data and are subject to the same access and correction rights described in this policy.
Not every part of your experience on this platform falls under one single policy layer. Your account, your wallet records and your session activity are all governed by what we set out here. However, third-party services — including game content providers and external payment processors — operate under their own terms. Knowing the boundary helps you understand who to contact when a question arises.
Your registration details, login activity and account preferences are covered by this policy. You can review and request corrections to this data by contacting us through the published support route.
Transaction records tied to bKash, Nagad or Upay deposits and withdrawals fall inside this policy. The payment processor's own terms also apply to the wallet side of the transfer.
Browsing behaviour on our site — which pages you open, how long you stay — is captured by session cookies we control. You may clear these at any time through your browser settings without affecting your account data.
Game content loaded from studios like Spadegaming, CQ9 or Habanero runs under those providers' own data terms for in-session activity. We do not govern or access in-game data they handle on their infrastructure.
You have real, actionable choices under this policy — not just a list of statements. If you want to review what information we hold, the starting point is the account details section once you are signed in. Personal details such as your registered name, contact number and linked wallet identifiers can be viewed there directly. If something is incorrect, you can raise a correction request through our support channel and we will verify the change against the records we hold. Where a data question relates specifically to a bKash or Nagad transaction reference, include that reference when you write to us — it shortens the verification step considerably. You may also ask us what categories of data we retain about your account and for how long. We will respond with the categories that apply to your account type. Requests to close your account and delete associated personal data are handled through the same support route; note that some transaction records may be retained for the period required by applicable operational obligations even after closure. Availability of all these rights depends on your local law and the eligible regions we serve.
Sign in and open the account details section to see the personal information held against your profile, including contact details and wallet identifiers.
Submit a correction request through our support channel with the specific field and the correct value. We verify against existing records before updating.
Ask us what data categories we hold and the retention period that applies. Include your registered contact detail so we can match your enquiry to the right account.
Account closure and data deletion requests go through the same support route. Some transaction records may be retained for the period required under applicable operational obligations.
For any question specifically about how we handle your data — correction requests, retention queries or account closure — use the contact routes published on this site. We do not publish channels we cannot staff, so if a route is shown here, it is active.
Open the chat icon on any page while signed in. State that your question relates to privacy or your account data so the support team routes it correctly from the start.
Send your data or privacy question to the support email address shown in the Help section of your account. Include your registered contact detail and the specific data point you are asking about.
The Help section inside your signed-in account lists current contact options and their scope. Check there first — some data queries can be resolved directly without opening a support ticket.
Handling your account data carefully is a baseline obligation, not an optional feature. We apply access controls so that only the platform functions that need your data for a specific purpose can reach it. Cookie data is session-scoped where possible, meaning it is not carried across sessions unless your device settings or browser configuration retain it. Retention periods for transaction records — including those tied to bKash, Nagad or Upay activity — are set by the operational obligations that apply to our platform, not by preference. When those periods expire, the relevant records are removed from active systems. You can request a summary of the retention period that applies to your account type at any time through our support route.
Your account data is accessible only to the platform functions that require it for a defined purpose. We do not expose personal records to marketing or analytics systems outside our operational scope.
Session cookies keep your login active and help us understand site usage patterns. You can clear them from your browser at any time. Persistent cookies, where used, are documented in the cookie notice inside your account settings.
Transaction records — including wallet references from bKash, Nagad or Upay activity — are retained for the period required by applicable operational obligations and then removed from active systems on schedule.
When this policy changes in a material way, we update the version date shown at the bottom of this page and, where appropriate, notify you through the contact detail registered on your account.
These questions reflect what account holders actually ask when they want to understand their data rights and how this policy works in practice. If your question is not covered here, use the support route listed in this policy.
We collect the details you enter during registration — name, contact information and the wallet identifier you use for transactions such as bKash or Nagad. We also collect session and device data when you browse the platform. We collect only what is needed for your account to function.
Wallet identifiers from bKash, Nagad or Upay are used only to verify and record your transactions. They are not shared with advertisers or unrelated third parties. The payment processor handling the wallet side of a transfer operates under its own separate terms.
Sign in and check the account details section first — much of your registered information is visible there. For a fuller summary of what data categories we hold and for how long, contact us through the live chat or email route listed in this policy.
Yes. Contact us through the support channel and specify which field is incorrect along with the correct value. We verify the change against the records we hold before updating. Including your registered contact detail speeds up the verification step.
We use session cookies to keep your login active and to understand how the site is used. You can clear cookies from your browser settings at any time, though doing so will end your active session. A cookie notice with further detail is available inside your account settings.
Account closure requests are handled through our support route. Personal data tied to your profile is removed once the closure is processed. Transaction records — including those linked to bKash, Nagad or Upay activity — may be retained for the period required by applicable operational obligations before removal.
Our policy covers the account layer we control. In-session game data handled by studios such as Pragmatic Play, CQ9, Habanero or Spadegaming is governed by their own data terms. We do not access or govern the in-game data those providers handle on their own infrastructure.