App / Live
This page sets out what 222nd collects when you hold an account with us, why we hold it, and how you can open, correct or question your own records. It covers the lobby, your wallet history and the pages you browse on 222nd from a phone or a desktop browser, and it sits alongside the local law and eligible regions that apply to you.
Keeping this short matters more than making it sound formal, so here is the plain version. When you hold an account with 222nd, we keep the details you type at registration, the wallet activity that follows — including the Nagad, Upay and Bank Transfer steps you complete — and the messages you send us. We also record basic device data: browser type, screen size and the pages you open inside the lobby. That mix is what lets your account, game history and wallet balance stay consistent. Use decides how much we hold. If you only browse public pages, we hold very little beyond cookie data. Once you sign in, we tie that activity to your account so the records match what you see on screen. Not everything is fixed. Data rules follow the law where you live, and Bangladesh rules are not always the same as those in another region, so what we may store and for how long can differ. The service itself is also limited to eligible regions, and access depends on your local law. What we do not do is sell your personal details. Where another party is involved, it is because a service you picked needs it — a payment rail you chose, or a technical service that keeps the site loading. We name those areas in the scope section below so you can tell which parts sit inside our policy and which sit under someone else's terms.
Not every part of your time on the site sits under the same rules, and knowing the line saves you a support message later. Your account, the wallet records inside it and the pages we publish are ours to run, so everything from sign-in to game history is covered here. What falls outside is anything you reach once you leave our pages. A payment app you open to finish a Nagad, Upay or Bank Transfer step runs under its own notice, and it is that notice which governs what it stores. Support messages sent through a messaging app sit partly under that app's terms too. Inside the site the rule is simple: if you typed it into your 222nd account, or it happened while you were signed in, this policy applies. If it happened somewhere else entirely, it does not. We keep that split visible rather than buried, because a member who can tell the difference can act on their own records without waiting on us.
Registration details, your sign-in email, device and browser type, and the preferences you set on the account pages all sit inside this policy. We use them to keep your session consistent and to show the same wallet and game history whichever device you open.
Wallet activity linked to 222nd, including the Nagad, Upay and Bank Transfer steps you complete from your account area, is recorded here. Those records are the ones you can open yourself in the account pages, so what you see and what we hold should match.
Pages you browse, the games you open and the cookie choices you make are covered by this policy. Cookie data keeps the lobby loading and remembers small display choices. You can adjust or clear them in your browser settings, though clearing them may reset a few display preferences.
Anything you reach after leaving our pages is outside this policy. A payment app, a messaging app you use to contact us, or a service that handles a step for you runs under its own terms. We only involve another party where a service you chose needs it.
You keep real control over your own details, and none of it needs an email to a stranger. Sign in, open the account area and you can see what we hold for you: your registration data, your wallet history and the activity tied to your sign-ins. If something is wrong — an old phone number, a misspelled name, a wallet detail that no longer matches — correct it in the account pages rather than leaving it there. For anything you cannot edit yourself, use the support route shown inside your account and tell us what should change. You can also ask what we hold, ask why we hold it, or ask us to close the account and remove what we no longer need for legal or accounting reasons. Questions about this policy travel the same route. What we cannot do is rewrite a stored transaction entry to match a wish; those stay as they were, since your wallet history is a factual log.
Sign in and open your account pages to view registration details, wallet history and sign-in activity. The records shown there are the ones tied to your profile. If you want a copy of something you cannot see on screen, ask through the support route inside your account.
Phone number, name spelling, address and linked wallet details can be updated from the account pages. Keep them current so wallet steps and account notices reach you properly. If a field is locked because it was verified earlier, send the correction request through the published support route.
Ask us what we hold, why we hold it, or how long we expect to keep it. We answer policy questions through the support route published inside your account. Say clearly which record you mean so we can point you to the right page or answer without guesswork.
You can request that we close your account. We remove what we no longer need, though records tied to wallet activity or legal obligations may be kept for the period the law requires. Submit the request from the account area, then follow the confirmation shown there.
If something about your data does not look right, the fastest route is the one already on your screen. Sign in, open the account menu and use the support option shown there; your message arrives with your account attached, which means we can look at the actual record instead of asking you to describe it from memory. The contact link published in the site footer works too, and it is the route to take if you cannot sign in. Tell us plainly what you need: a correction, a copy of a record, an explanation of why we hold something, or a request to close the account. One detail helps more than a long message — the page or wallet entry you are asking about. We do not run a separate privacy desk with its own hours, and we do not promise a response time; every question reaches the same team that handles account help, and we work through them in the order they arrive. What we will not do is ask for your password through a message.
The support option inside your signed-in account is the route to use for anything tied to your records. Your message carries your account details, so we can check the wallet entry, registration field or game history you are asking about without extra back-and-forth.
The contact link published in the site footer is there for questions you cannot raise while signed in — a locked account, a sign-in problem, or a policy question you want to ask before you hold an account. It reaches the same team.
Ask about this policy, request a copy of your details, or tell us what should change. Include the page or record you mean. We answer through the same support channel rather than a separate desk, and no reply time is promised in advance.
Data handling is mostly unglamorous work: keep what the account needs, protect it, and remove what has stopped being useful. We hold account details while your account is open, wallet and transaction records for the period local law requires, and support messages long enough to resolve the question and keep a trace of what was agreed. Cookie data is limited to what keeps the lobby loading, remembers small display choices and shows us which pages behave badly on a phone. Wallet steps through Nagad, Upay or Bank Transfer happen inside the wallet or bank app you chose, so those credentials stay with that provider rather than with us. Account safety starts with your sign-in. Use a password you do not reuse elsewhere, keep your email account secure, and never pass a one-time code to anyone who messages you first. If you think someone else has reached your account, change the password and tell us through the support route inside your account so we can look at the sign-in activity with you.
Registration fields, wallet and game history, support messages and basic device data. Each has a purpose: running your account, keeping your records consistent, answering you, and spotting sign-in problems. Nothing is held for a stated future use that we cannot explain today.
Account details stay while the account is open. Wallet and transaction entries are kept for the period local law and accounting rules require. Support messages stay long enough to resolve the question. Where no rule forces us to keep something, we remove it once it is no longer needed.
Cookies keep the lobby loading, remember small display choices and show us which pages behave badly on a phone. You can block or clear them in your browser settings. Clearing them may reset display preferences, and some parts of the site may not behave as expected.
Use the support option inside your account for anything tied to your records, and the footer contact link if you cannot sign in. Say which entry should change. We handle policy questions and account help in the same place rather than through separate desks.
Your registration fields, sign-in email, basic device and browser data, wallet and game history, and any support messages you send. We also keep cookie data tied to how you browse the lobby. All of it exists to run your account and answer you, not to be sold on.
Yes. Sign in, open the account pages and your details sit there, including wallet history and sign-in activity. Fields such as your phone number or name spelling can be edited directly. For anything locked or unclear, raise it through the support route inside your account.
We do not sell them. Another party only sees a record where a service you picked needs it — a wallet step through Nagad, Upay or Bank Transfer, or a technical service that keeps the site loading. Those areas sit outside this policy and under their own terms.
Only to the point where the step happens inside your account. Once you move into the wallet or bank app to complete it, that provider's own privacy notice applies to what it stores. Your transaction entry here stays as it was recorded.
Account details are held while the account is open. Wallet and transaction entries stay for the period local law and accounting rules require. Support messages are kept long enough to resolve the question. Where nothing obliges us to keep a record, we clear it.
Send the request through the support option inside your signed-in account, or the footer contact link if you cannot sign in. State which record you mean. We remove what we no longer need, though wallet and legal records may be kept for the required period.