Mobile / Slots
tdb22 takes a straightforward approach to your personal data — we collect what we need to run your account and process your wallet transactions, and we do not share it beyond what this policy describes. What we collect, why we keep it and how you can act on it are all set out here, section by section.
This policy applies to every interaction you have with tdb22 — creating an account, logging in from your mobile browser, depositing through bKash or Nagad, browsing the game lobby, and reaching out to our support team. We collect information in three broad ways: data you enter directly (your registration details, contact address and wallet identifiers), data generated by your activity (session logs, game history and transaction records), and data collected automatically by our site (cookies, device type and referring URL). We keep each category only as long as it serves the purpose for which it was collected. Transaction records tied to bKash or Nagad deposits are retained for the period required to resolve any account or payment query you raise; after that retention window closes, they are removed from active systems. We do not sell your data to third parties. Where we work with a service partner — for example, a payment processor handling your Nagad transfer — we share only the minimum fields that partner needs to complete the transaction. Your use of this site and its services is subject to the laws and regulations applicable in your region; access and eligibility depend on local law and the regions we currently support.
Not every digital touchpoint connected to your experience falls under this single document. Understanding which parts are governed here — and which are handled separately — helps you know exactly where to look when a question comes up about your data. The four areas below map out the boundary clearly.
Your login credentials, registered mobile number and account profile sit fully within this policy. We control how that data is stored, how long it is kept and who inside our operations can view it. You can request a correction or deletion through the contact route listed in this policy.
When you deposit or withdraw using bKash, Nagad or Rocket, the transaction passes through the payment processor's own infrastructure. We hold a record on our side; the processor holds theirs. Their handling of your financial data is governed by their own privacy terms, not by ours.
Pages you browse, game lobby sections you open and any cookie preferences you set are covered here. We use cookies to keep your session active and to understand which parts of the lobby you visit most. You can adjust cookie settings through your mobile browser at any time.
Links to external sites, third-party game studio interfaces and any partner service that opens in a new tab operate under that party's own policies. Once you leave our domain, our policy no longer applies. We do not control and are not responsible for how those parties handle your data.
You have several concrete options when it comes to the data we hold about your account. First, you can request a summary of what personal information is attached to your registered profile — this includes your contact details, wallet identifiers on file and any preferences stored against your account. Second, if any of that information is wrong — a mobile number that has changed, for instance — you can ask us to update it and we will do so once we can verify the correction against your account. Third, if you believe data is being held beyond the retention period described in this policy, you can raise that directly with our support team. Fourth, you can ask us to stop using your data for any optional communications; mandatory operational messages tied to your account security or active transactions will still be sent. All of these actions start through the contact route described in the support section below. We aim to acknowledge your request promptly, though response times depend on the complexity of what you ask and current queue volume.
Contact support to request a summary of the personal data fields held against your account. We will send you the details we can confirm once your identity is verified through your registered contact information.
If your registered mobile number, email or wallet identifier has changed, reach out via the published support route. Bring the details you registered with so the correction can be matched to your account accurately.
Any question about how a specific piece of your data is being used — a transaction record, a session log or a cookie preference — can be directed to our support team. Describe the data type and your concern as clearly as possible when you write in.
If you close your account and want to ask about data deletion, submit the request through our support channel. Some records may need to be held for a defined period to satisfy transaction resolution requirements before they can be removed.
If you have a specific question about this policy, want to exercise one of the rights described above, or need to flag something about how your data has been handled, use the routes below. We do not publish estimated response times here because queue volumes vary; what we can confirm is that each request is reviewed and handled in the order it arrives.
Open the chat widget from any page on tdb22 while logged in. Describe your data or privacy question clearly so the agent can route it to the right team without a follow-up round.
Send your privacy request to the support email address published in your account's help section. Include your registered mobile number and a clear description of the data question or correction you need handled.
The help section inside your signed-in account area contains policy contact links and a form for submitting data requests directly. Log in, navigate to Help, and choose the Privacy or Data query option from the menu shown there.
The way we manage your information reflects the account-first approach we take across the whole platform. Every data practice described in this section is operational — not a marketing statement — and each one applies from the moment you open an account.
We use session cookies to keep you logged in and functional cookies to remember lobby preferences. No advertising or cross-site tracking cookies are set without your consent. You can clear or block cookies at any time through your mobile browser settings, though some account features may stop working if session cookies are removed.
Access to the personal data fields in your account profile is restricted to authenticated sessions. If you believe your account has been accessed without your knowledge, change your password immediately and contact support through the live chat route so we can review the session log attached to your account.
We hold account registration data for as long as your account is active. Transaction records — including bKash and Nagad deposit histories — are kept for the period needed to resolve any payment queries you raise. Once that window passes and no open query exists, records move out of active systems on a scheduled basis.
When we update this policy, the revised version is published at this URL with a note at the top indicating the change. Continuing to use your account after a policy update means you have seen the new version. If a change affects how we use your data in a material way, we will notify you through your registered contact details.
These are the questions we get most often about how tdb22 handles personal data, wallet records and account privacy. If your question is not covered here, use the support contact routes listed above.
We collect the details you enter during registration — your mobile number, contact email and any wallet identifier you provide, such as a bKash or Nagad number. We also record the device type and browser used at the time, which helps us keep your session secure.
Your wallet identifier is shared only with the payment processor handling your specific transaction. That processor uses it solely to complete the deposit or withdrawal. We do not share your bKash or Nagad details with advertisers, data brokers or any unrelated third party.
Transaction records, including bKash deposits and Nagad withdrawals, are retained for the period needed to resolve any query you raise about that transaction. Once no open query exists and the retention window has passed, those records are removed from active systems on a scheduled basis.
Yes. After closing your account, you can submit a deletion request through the support email or live chat route described in this policy. Some records may need to be held temporarily to settle any outstanding transaction queries before full removal can be completed.
Contact support via live chat or email and provide your current registered details alongside the correct number you want on file. We will verify the change against your account before updating it. The help section inside your signed-in account area also has a data correction form.
This policy covers all accounts on tdb22. Whether you can access and use the platform depends on local law and the eligible regions we currently support. If you are in Bangladesh, check the eligibility information in your account area for the regions where access is currently available.