2222nd takes a direct approach to privacy — we collect only what your account needs to function, and we explain clearly how that information is handled. Access to this platform and its policy protections depends on your local law and eligible regions.
Account data only
Nagad & Upay context
No third-party sale
Bangladesh-region scope
POLICY FOUNDATION
How We Handle Your Personal Information
When you create an account on 2222nd, we collect the information you submit directly — your name, contact details, and the payment method you choose to use, whether that is Nagad, Upay, or Bank Transfer. We also collect technical data generated by your device and browser as you navigate the lobby, including session identifiers, device type and connection metadata. This data helps us keep your account accessible, process wallet transactions accurately and respond to support requests without delay. We do not sell your personal information to third parties. Where we share data with service providers — for example, payment processors handling a Nagad or Bank Transfer transaction — that sharing is limited to what those processors need to complete the task. We retain account data for as long as your account is active and for a period after closure that our operational and legal obligations require. You may request a summary of what we hold about you at any time by contacting our support team through the published channel in your account area. Eligibility to use this platform, and the rights that come with it, depends on your local law and the eligible regions we serve.
Nagad transaction records
Upay wallet activity
Bank Transfer history
Account session logs
Support correspondence
INSIDE VS OUTSIDE
Where This Policy Applies on 2222nd
This policy covers the data 2222nd collects and processes directly. It does not extend to third-party services that operate independently of our platform — including external payment processors, mobile wallet providers and any linked websites. Knowing the boundary helps you understand where to direct a privacy question.
Account Access
Login credentials, session tokens and account verification steps are all covered. We handle this data only to authenticate your access and keep your account secure. How you choose to recover access is also recorded within this scope.
Wallet Transactions
Records of deposits and withdrawals made through Nagad, Upay and Bank Transfer sit within our data scope, but the payment processors themselves operate under their own privacy terms. We see transaction references, not full wallet credentials.
Site Content Interaction
Browsing behaviour within the lobby — which game categories you open, how long a session runs, device and browser signals — falls inside this policy. We use this data to improve navigation, not to profile you for external advertising.
Third-Party Services
Links to external sites, the mobile wallet apps you use to fund your account and any provider-hosted game environments are outside our policy boundary. Those services control their own data collection and you should check their terms directly.
ACTIONS AVAILABLE TO YOU
Your Practical Choices Under This Policy
You have real, actionable rights over the data connected to your 2222nd account — not just a statement on a page. The most common requests we handle are: reviewing what information we hold, correcting details that are out of date, asking a question about how a specific piece of data was collected and requesting that we close your account and handle retention according to our published terms. To start any of these, open the support section in your account and use the contact route listed there. We aim to acknowledge every privacy request and direct it to the right team without unnecessary delay. Note that some requests — particularly around account closure and data retention — have a processing period tied to our operational obligations, which we will explain when you submit. Eligibility for certain actions may depend on your region and local law, and we will let you know if that affects your specific request.
Review Your Records
Submit a request through the published support channel and we will confirm what account data we hold, including transaction references and session records tied to your profile.
Correct Account Details
If your name, contact information or linked payment method details are incorrect, open the account settings page and follow the update fields shown there, or contact support if the field is locked.
Raise a Privacy Question
Any question about how a specific data point was collected or why it is retained can be sent through the support route in your account. We will respond with a clear, specific answer rather than a generic policy reference.
Request Account Support
If you want to understand your account closure and data retention options, contact us through the published channel. We will walk through the steps and timelines that apply to your account type.
REACH THE PRIVACY TEAM
How to Contact Us About This Policy
Privacy questions and data requests go to the same support team that handles your account. Use only the contact routes published inside your signed-in account area — we do not publish separate privacy-only channels, and we do not operate contact lines that are not visible in your account settings. Every request is logged and directed to the appropriate team member.
Account Support Inbox
Open your signed-in account, navigate to the support section and submit your request through the inbox form shown there. This is the primary route for all privacy-related questions and data access requests.
Live Chat in Account Area
If a live chat option is active in your account dashboard, you can use it to raise a privacy question directly. The agent will log your request and escalate it if a formal data review is needed.
Help Centre Articles
The help section accessible from your account menu includes published articles on data handling, account closure and how to submit a correction request. Check there first for step-by-step process details before raising a ticket.
HOW WE PROTECT YOUR DATA
Data Handling, Cookies and Account Security
Our approach to the data connected to your account is built around limiting collection to what is operationally necessary and being clear about retention. We use cookies and similar browser-level identifiers to keep your session active, remember language and region settings and detect unusual login activity. You can manage cookie preferences through your browser settings; note that disabling certain cookies may affect how your account loads. Account security is enforced at the login and transaction level — if you notice an activity you do not recognise, report it through the support channel in your account immediately. We keep transaction references — including Nagad and Bank Transfer records — for the period required by our operational obligations, then remove or anonymise them according to our internal retention schedule.
Cookie Management
Session and preference cookies are active when you browse the lobby. Manage them through your browser settings. Disabling functional cookies may affect account loading and wallet transaction confirmation screens.
Transaction Record Retention
Nagad, Upay and Bank Transfer transaction references are retained for the period our operational obligations require. After that period, records are removed or anonymised in line with our internal retention schedule.
Account Security Signals
Unusual login activity triggers a review flag in our system. If you see account activity you do not recognise, report it through the support inbox in your account area so the team can review the session log promptly.
Policy Change Notification
When this privacy policy changes in a way that affects your rights, we will publish the update in the account area and note the effective date. Continuing to use the platform after that date means you have seen the updated terms.
POLICY FAQ
Privacy Policy Questions Answered
These are the questions we receive most often about how 2222nd collects, stores and handles personal data. If your question is not covered here, submit it through the support inbox in your account.
What personal data does 2222nd collect when I open an account?
We collect the details you submit during account registration — name, contact information and your chosen payment method such as Nagad or Bank Transfer. We also collect device and session data generated automatically when you access the lobby. We do not collect more than what account operation requires.
Does 2222nd share my data with third parties?
We share data only with service providers who need it to complete a specific task — for example, a payment processor handling a Nagad or Upay transaction. We do not sell personal information. Third parties we work with are limited to what their task requires, and they operate under their own terms.
How do I request a copy of the data held about my account?
Open the support section inside your signed-in account and submit a data access request through the inbox form. We will confirm receipt and let you know what records we hold linked to your account, including transaction references and session history.
How long does 2222nd keep my account and transaction records?
Account data is retained while your account is active and for a defined period after closure based on our operational obligations. Transaction references — including Nagad, Upay and Bank Transfer records — follow the same retention schedule, after which they are removed or anonymised.
Can I correct incorrect information stored on my account?
Yes. Open account settings and use the editable fields shown there to update contact details or payment method information. If a field is locked and the detail is incorrect, contact support through your account inbox and we will guide you through the correction process.
Does the privacy policy apply to all regions, including Bangladesh?
This policy covers data we collect from all accounts. However, access to the platform and the specific rights available to you depend on your local law and eligible region. If you are accessing from Bangladesh, check that use is permitted under your local regulations before proceeding.