Sports / Live
This page sets out the legal framework that governs your use of tk2223 — covering account access, your rights under our policy, and the steps available to you when something needs to be reviewed or corrected. Access to tk2223 depends on your local law and the eligible regions we serve; please read this policy alongside the terms shown in your account.
tk2223 publishes this legal notice to be direct about how the platform operates and what obligations apply on both sides of the account relationship. Our policy governs the way your account data is held, how transactions are recorded, and what actions we take when a dispute or access question arises. Availability of the platform — including wallet transactions made through bKash, Nagad, or Upay — depends entirely on your local law and the eligible regions where we operate. We do not make legal certainty claims about access in any jurisdiction; instead, we ask that you confirm your eligibility before opening or continuing to use an account. Wallet activity connected to bKash, Nagad, and Upay is recorded at the transaction level and can be reviewed through your account history at any time. If any clause in our published terms conflicts with an applicable local rule, the local rule takes precedence to the extent required. We update this policy when operational changes affect user rights, and we publish those changes inside the account area before they take effect. Your continued use of the account after a change is posted constitutes acknowledgement of the updated terms.
bKash wallet transactions are recorded and visible in your account history.
Nagad activity is logged at transaction level for account and policy reference.
Upay transfers are subject to the same record-keeping conditions as other wallet rails.
Not every activity connected to your use of tk2223 falls under the same policy rules. The four areas below clarify what this legal notice covers directly and where responsibility sits with a third party or a separate published document.
Login credentials, session behaviour, account-level controls and opt-out routes are all covered by this policy. These are managed entirely within your tk2223 account and are subject to the terms published there.
Transactions made via bKash, Nagad, or Upay are recorded within our system under this policy. The payment provider's own terms also apply on their side of the transaction; we do not control those separately.
Game content supplied by studios such as Pragmatic Play, PG Soft, and Habanero is governed by the content agreements those studios hold. This policy covers your account interaction with that content, not the content itself.
Any external link, third-party tool or service you reach from tk2223 operates under that party's own terms. We are not liable for the policy positions of services we do not operate or control.
The rights available to you under this policy are practical and accessible from your account without needing to contact support first. Your transaction history — including wallet activity through bKash, Nagad, or Upay — is visible in the account area at any time, and you can download or screenshot records you need. If account details such as your registered contact or display name are incorrect, the correction route is available directly through the account settings screen; follow the fields shown there and confirm the change. For policy questions that go beyond self-service, our published support route is the right path. Any formal request — such as asking what data we hold or requesting a record correction — should be submitted through the support channel so it can be tracked and responded to properly. We do not accept policy requests made through informal channels. Each request is logged with a reference, and you should note that reference for follow-up if needed.
Open the transaction history section in your account to see all wallet activity. Records from bKash, Nagad, and Upay transactions are listed there by date and amount.
Update your registered name, contact number or email through account settings. Follow the verification fields shown on screen; changes take effect once confirmed.
For anything not resolved through self-service, use our published support route. Describe your question clearly and keep the reference number you receive for follow-up.
If you want a record of what account data we hold, submit a formal request through support. We process these requests in the order received and respond to the contact detail on file.
Policy-related questions and formal account requests should come through the contact routes published on this site. Use the channel that matches your query type — general policy questions, account corrections, and formal data requests each have the same route but should be described clearly in your message so we can direct them correctly.
Our live chat route is accessible from the account area. Use it to raise a policy question or ask where to direct a formal request. Have your account reference ready when you open the chat.
For written policy requests or formal data queries, email is the right channel. Include your registered account contact and a clear description of what you are requesting so we can log and route it properly.
The help section inside your account lists published policy documents and links to the correct support route for each type of request. Check there before reaching out to confirm you are using the right path.
We take the handling of information seriously, and this section outlines the practical measures in place across the four areas that matter most to returning members.
Account records — including wallet transactions through bKash, Nagad, and Upay — are retained for the period required under the terms of service. You can review active records in your account at any time; retention periods for closed accounts are stated in the published terms.
We use cookies to maintain your session state and remember account preferences between visits. You can adjust cookie settings through your browser at any time; some site functions may behave differently if session cookies are blocked.
Access to your account is protected by the login credentials you set. If you believe your account has been accessed without your knowledge, use the published support route immediately to report it and request a security review.
For questions about what data we hold, how long we keep it, or how to request a correction, the published support route is the right path. Formal requests submitted through support are logged and tracked to your account reference.
These are the questions we hear most often from members reading this policy. If your question is not covered here, use the support route to submit it directly.
Yes. Wallet activity through bKash, Nagad, and Upay is recorded under this policy and visible in your account transaction history. The payment provider's own terms also apply on their side of the transfer, which is separate from our policy.
Access depends on your local law and the eligible regions we serve. We do not make legal certainty claims about availability in any specific jurisdiction. Please confirm your eligibility under local law before opening or continuing to use an account.
Open account settings and follow the fields shown for name, contact number or email correction. Verification steps are displayed on screen. If the field you need to change is not editable, submit a correction request through our published support route.
We hold the registration details you provided, your login history, and your transaction records including wallet activity. To request a summary of what we hold, submit a formal request through the support channel with your registered account contact included.
Use the published support route — live chat or email — and describe the issue clearly. Include your account reference so the query can be logged and tracked. Informal messages sent outside these channels are not treated as formal policy submissions.
We update the policy when operational changes affect user rights or account obligations. Changes are published inside the account area before they take effect. Continuing to use your account after a change is posted acknowledges the updated terms.