Reference

Privacy Policy: What We Collect and Why

This page sets out the account data we hold on you, from the mobile number you register to the wallet reference attached to a bKash or Nagad transfer, plus how long each record stays with us.

What we collectCookie choicesWallet data handlingYour access rights

Explore the Lobby Read FAQ

Where This Policy Applies to You

22222bet Service availability depends on eligible regions and local law. Users should check local rules before opening an account.

By opening an account or simply browsing 22222bet, you accept the practices set out on this page; if you do not, the right move is to close the tab and leave the account unused. We control the data you hand over at sign-up and treat the

1
privacy rules of your own country as the starting point, not an afterthought. Availability, the wallets we can accept and the way records are handled all depend on your local law and eligible regions. If Nagad or Rocket payments are not open to you where you
2
live, we cannot process them, and we will not pretend otherwise. You may withdraw consent at any time by writing to our support desk, though transaction records may still be held for audit and fraud checks. Where we lean on a legal ground to keep data,
3
an agent will name that ground if you ask. Nothing here removes a right you already hold under the law where you live. If a local rule conflicts with a line on this page, the local rule wins and we adjust our handling. Being old enough
4
to gamble legally where you are is a condition of use, and we may ask for proof before access continues.

Service availability depends on eligible regions and local law. Users should check local rules before opening an account.

ACCOUNT DATA CONTROLS

Cookies, Retention and Login Codes

Security and privacy sit on the same shelf here. Every sign-in is tied to a one-time code sent to your registered mobile, so a leaked password on its own will not open your account wallet. Cookies do the quieter work: they hold your language choice, keep the session alive and show us which screens load slowly on mobile data. Wallet references and bet records stay for as long as the audit trail runs, and not a day past it.

Cookie categories

Essential cookies keep you signed in on mobile; analytics cookies show which screens stall on a weak connection. Clear them in your browser whenever you like, though sign-in will then ask for a fresh code.

Device-bound login

Your account is bound to one mobile number, and each new handset needs the one-time code before the wallet is visible. Change that number only through the verification step in profile settings.

Retention periods

Deposit and withdrawal records, including bKash and Rocket references, are kept while the audit trail is open. Once that period closes we delete or anonymise the record rather than storing it indefinitely.

Requesting a change

Ask for a copy, a correction or an erasure through chat or email. We check the request against your registered details first, then tell you what we can action and what has to stay for audit.

REQUEST CHANNELS

Getting Privacy Requests Answered

Data questions land on the same support desk that handles your wallet queries, so nobody forwards you between queues. Write from the mobile number or email registered on the account and say plainly what you need, whether that is a copy of your records, a correction or closure. We answer in English through the channel you used, and no agent will ever ask for your bKash PIN or a Nagad one-time code to confirm a request.

Privacy Questions You Send Us

These are the points players raise most often about this policy. If your situation is not covered, message the support desk from your registered number and we will answer it directly, including any local-law detail that changes how we handle your records.

Your name, mobile number, date of birth and the wallet reference from your bKash, Nagad or Rocket transfer. We also log device type, sign-in times and sportsbook activity during cricket matches to spot access from unfamiliar handsets.

No. The payment completes inside your own wallet app, so the PIN and the code never reach us. We receive only a confirmation reference, which we match against your account to credit the amount.

Yes. Message support from your registered number and ask for a data copy. After we verify the request, the file comes back through the same channel and covers profile details, wallet references and sign-in records.

Request closure in chat or by email. We settle any open wallet balance first, then remove your profile data. Transaction records stay until the audit period ends, because record-keeping rules require it.

Essential cookies are, since they keep you signed in on mobile. Analytics cookies are optional and clearing them in your browser settings will not lock you out, though you may be asked for a code again.

Write to the privacy contact through the support desk with the dates and what went wrong. We log the complaint, trace which agent or system touched the record and reply with what we found.

Reference

Privacy Policy

Service availability depends on eligible regions and local law. Users should check local rules before opening an account.

Access may be available only where local law permits.

InfoLegal InfoAbout Us Games22222bet Casino

Privacy Policy: What We Collect and Why

Cookies, Retention and Login Codes

Cookie categories

Device-bound login

Retention periods

Requesting a change

Getting Privacy Requests Answered

Privacy Questions You Send Us

01 What personal data do you collect when I open an account?

02 Do you ever see my bKash PIN or Nagad one-time code?

03 Can I ask for a copy of my account data?

04 How do I close my account and have details removed?

05 Are cookies required to use the lobby?

06 Who do I contact if I think my data was mishandled?

Privacy Policy

Related pages

Related pages