Mobile / Slots
This page sets out the legal framework that governs your use of tdb22 — covering account access, transaction records, data handling and the scope of our service. Availability of any feature or account function depends on your local law and the eligible regions we serve.
tdb22 operates under a policy framework that reflects the legal environment of the regions where access is available. Whether you reach us through a bKash wallet deposit, a Nagad transfer or a Rocket payment, the same account policy applies to your session and transaction record. We do not apply different terms based on which local payment method you use — all three sit under the same account agreement. Where local law restricts access to online account-based services, it is your responsibility to confirm eligibility before opening or maintaining an account. We do not make legal representations about access in any jurisdiction, and we do not provide legal advice. The terms published in your account portal are the operative document; anything described on this page is a plain-language summary of the policy posture we maintain. If a conflict exists between this summary and the account-level terms, the account-level terms take precedence. We update these terms when our service scope changes, and we publish those changes in the account notice area before they take effect. Reviewing your account notice area periodically keeps you informed of any revision.
Transactions made through bKash fall under the same account agreement as all other payment methods. No separate legal terms attach to the bKash deposit route specifically.
Nagad transfers are processed under the standard account transaction policy. The terms governing your wallet balance apply equally whether the source is Nagad or any other configured rail.
Rocket payments sit inside the same account framework. Your transaction record is accessible from your account wallet page regardless of which payment rail you used.
This policy applies to the account you hold with us and the activity recorded against it. Four distinct areas shape where the policy reaches — and where it stops. Understanding the boundary between what we control and what falls outside our policy helps you know where to direct a question or a dispute.
The terms govern how you open, maintain and close your account. Eligibility is subject to your local law and the eligible regions we serve. We do not extend account access where local regulation prohibits it, and we do not make access determinations on your behalf.
All wallet activity — deposits via bKash, Nagad or Rocket, and any withdrawal processed through the account — falls within this policy. Transaction records are viewable from the wallet section of your account. We retain records in line with our data retention schedule.
Game content supplied by studios including Pragmatic Play, PG Soft and Habanero is subject to each studio's own content terms in addition to our account policy. We do not alter studio-level RTP disclosures or content classifications, and we display only what each provider publishes.
External services — payment processors, identity verification services and mobile network integrations — operate under their own terms. Our policy does not extend to those third-party terms, and we are not responsible for their data practices or service availability.
The policy is not just a statement we maintain — it gives you concrete steps you can take when you need to review, correct or question anything attached to your account. Your account portal is the starting point for most of these actions. From the account settings section, you can view your registered details and request corrections to inaccurate information by following the fields shown on that page. Transaction records — including bKash, Nagad and Rocket deposits — are listed in the wallet history tab, and you can use that record if you need to raise a discrepancy. If you have a question about how your data is handled or stored, our support route is available through the contact section described further on this page. We do not require you to submit a formal legal request to ask a basic account question; the support channel handles those directly. For anything that goes beyond an account correction — for example, a request to delete records or to understand retention periods — direct that to us in writing through the published contact route.
Open the wallet history tab in your account to see a full transaction log. Each entry shows the payment method used, date and status. This is the record to reference if you need to raise a question about a specific transaction.
Go to account settings and follow the editable fields shown there. If a field is locked and requires a support action to change, the page will indicate that. Do not attempt to circumvent locked fields — contact support instead.
Use the published support contact route to ask how your personal data is stored, processed or retained. We do not require formal legal language; a plain description of your question is enough for us to respond on policy grounds.
If you want to request deletion of records or changes to how we hold your data, submit that request in writing through the published contact route. We will respond with the applicable process and any limitations set by our retention obligations.
Policy questions follow the same contact paths as account support. Use the route that matches how quickly you need a response. All three channels below are published on this site; we do not operate any channel that is not listed here.
The live chat icon is visible in the bottom corner of the site. Use this for account-level policy questions where you need a direct exchange. Chat agents can escalate to a policy review if the question goes beyond standard account support.
For written policy requests — including data questions and correction requests — email the address shown on the Contact page. Written requests create a record on both sides, which is useful for any question that may require a formal response.
The Help Centre section of the site covers common policy questions including account scope, wallet records and data handling. Check there first; if your question is not answered, use live chat or email to escalate.
Knowing how your account data is stored and who can access it matters. Here is how each area of data practice works on this site. These are operational facts, not marketing claims — check your account settings and our published cookie notice to verify the details that apply to your session.
We keep account and transaction records for the period required by our operating obligations. If you close your account, certain records are retained for the minimum period set by applicable policy before deletion. The exact retention schedule is available on request through our email support route.
Cookies are used for session management, fraud detection and site performance. The cookie notice shown on your first visit sets out which categories are active. You can adjust non-essential cookie preferences from the cookie settings link at the bottom of every page.
Access to your account is controlled by the login credentials you set. If you believe your account details have been compromised, use the password reset path shown on the login page, then contact support through live chat to flag the issue for review.
Policy matters — including data requests, correction requests and questions about what we hold — go to the email contact route published on the Contact page. Live chat handles initial queries and can escalate if a written record is needed.
These are the questions we see most often about how our policy works. If you do not find your answer here, use the live chat or email route described in the contact section above.
No. The account policy applies equally regardless of which local payment method you use. bKash, Nagad and Rocket deposits all sit under the same account terms. Your wallet history records each transaction the same way regardless of the payment rail.
Availability depends on your local law and the eligible regions we serve at any given time. We do not make eligibility determinations on your behalf. It is your responsibility to confirm whether access to account-based online services is permitted under the laws that apply to you.
Yes. Send a written deletion request through the email contact route published on the Contact page. We will respond with the applicable process. Note that certain records must be retained for a minimum period set by our operating obligations before full deletion is possible.
The cookie notice shown on your first visit lists active cookie categories. You can also access cookie preferences through the link at the bottom of every page. Non-essential cookies can be adjusted there; essential session cookies remain active while you are logged in.
Wallet records and transaction history are retained for the minimum period required by our policy even after account closure. You can request a copy of your records before closing the account by contacting support through the email route. After the retention period, records are deleted in line with our data schedule.
Your account-level terms take precedence in any conflict with this summary page. This page is a plain-language description of the policy posture we maintain. The operative document is the terms published inside your account portal. Check there for the exact wording that applies to your account.