App / Casino
Our privacy policy sets out what 888cadino stores when you open an account, move money through bKash, Nagad or Bank Transfer, or work your way through the lobby and your wallet. It is written in plain terms so you can see the rules before you agree to them, and access still depends on your local law and the regions we can serve.
This policy is the set of rules that governs how 888cadino handles the details you give us, and it applies wherever you reach our site — a mobile browser, a computer, or the account pages behind the login. Because we serve Bangladesh, some of it is written with local law in mind. Even so, any feature, wallet route or game still depends on your local law and the regions we can serve, and where we cannot offer something in your area that limit comes first. We keep the wording plain in the places that matter most. What we store, how long we keep it, who inside our operation can see it, and how you raise a question are each set out in their own part of the page. Opening an account means you accept these rules; it does not change the terms you agree to when you join, and it does not promise a fixed outcome for any single transaction. Payment context is a fair example. bKash, Nagad and Bank Transfer appear across 888cadino because those are the rails we work with, and each one leaves a record attached to your account wallet. This policy explains what we hold about that record and how you can ask us to correct anything we are allowed to change. It will not tell you that a deposit or withdrawal clears in a set number of minutes, because that depends on the route, the network and the verification steps shown on screen when you submit it. If a rule here conflicts with a mandatory requirement where you live, the local requirement wins. Use the contact route on this page if any clause is unclear.
Scope comes down to one question — is the data moving through our own pages, or through something we only link to? Your account access sits inside the policy: the login, the profile fields you save and the security settings you switch on. So do the transaction records attached to your wallet when you use bKash, Nagad or Bank Transfer, because those entries are created on our side. Site content is covered too — the lobby, the games you open and the pages you see while signed in to 888cadino. Anything a third party controls falls outside. Follow a link to a wallet app on your phone, or to a service that runs to its own rules, and that provider's policy applies to what happens there rather than this one. We do not decide what those services collect. If you are unsure which side a page belongs to, check whether you are still signed in before you enter anything personal.
Everything behind your login belongs to this policy. That means the email or phone number you sign in with, the profile details you save, and any security setting you switch on. Keep your password to yourself, and change it from the account page if you think someone else has seen it.
When you move money through bKash, Nagad or Bank Transfer, an entry appears against your account wallet. We keep that entry so you and our support staff can both see what happened. This policy explains which parts of the record we hold and how you can ask about them.
Lobby pages, the games you open and what you played while signed in all sit inside this policy — a slot round, a live table hand, or a cricket market you followed. We use that view to run the site and answer your questions.
Follow a link out to a wallet app, a studio page, or any service that sets its own rules, and you are outside this policy. That provider decides what it collects and how long it keeps it. Read their terms first.
Your data is yours to ask about, and this policy gives you a few practical ways to act on that. Open your account profile and you can see which fields we hold — the phone number you joined with, your email, and the wallet entries created when you moved money through bKash, Nagad or Bank Transfer. Anything editable you can change yourself from that page. Anything locked, you can ask us about, and we will tell you why the field is fixed and what we would need to update it. When a question is about how a record was used, write through the route published on this page, name the part of the policy you mean, and give the date the entry appeared. If you want a copy of what we keep about you, or you want us to close the account, say so plainly in your message. Some requests depend on local law and the regions we can serve, and certain records we must hold for a set time — we will tell you which applies to you.
Your account area shows the profile fields and wallet records tied to you. Open it whenever you want to see what is stored, and check the wallet entries created through bKash, Nagad or Bank Transfer. If something looks wrong or missing, tell us through the same page.
Phone numbers, email addresses and similar profile fields are usually yours to update from the account area. Where a field is locked, write through the contact route with the correct value, and we will explain why it was fixed.
If you want to know why a particular entry exists or who saw it, say so in a message. Name the part of the policy you mean and include the date the record appeared, so the answer you get back is grounded in the right entry.
You can request a copy of what we hold about you, or ask us to close the account. Put the request in writing through the contact route. Some of it depends on local law and the regions we serve, and a few records must be held for a set period, so we will tell you what we can do.
Questions about data are not the same as questions about a game, and the path that answers them fastest is the account area. A message sent from there arrives with your account reference attached, so our team opens the right profile instead of asking you to describe everything from scratch. If you cannot sign in, use the contact route published on this page and name the part of the policy you mean. Add the wallet route you used — bKash, Nagad or Bank Transfer — and the date the entry appeared, so the first reply is useful. We do not quote response times or opening hours on this page, because both depend on how many messages the team is working through. What we can say is that data requests go to the people who own this policy rather than a general queue. Keep a copy of whatever you send. If you are writing for someone else, say so in your first line.
Sign in, open the account area and send your question from there. Your account reference travels with it, which saves a round of messages and lets the team open the right profile. Add the wallet route and the date of the entry.
If you cannot sign in, the contact route on this page reaches the same team that owns the policy. Tell us which section your question is about. Never send passwords or codes in a message.
If you have already written to us and need to add something, reply on the same thread instead of starting a new message. Mention the wallet route — bKash, Nagad or Bank Transfer — and the date of the entry, so the person handling it sees the full picture in one place.
How we look after your details comes down to four habits: collect little, keep it locked, hold it only while we need it, and say so when the rules change. We store what an account needs to work — your sign-in details, wallet records for bKash, Nagad and Bank Transfer, and the history that shows what you opened. Cookies do a smaller job: they keep you signed in between pages and remember a few preferences, and your browser lets you clear or block them at any time. Account security is shared work. Choose a password you do not reuse elsewhere, sign out on a shared phone, and tell us the moment a login looks wrong. Records stay while the account is open and for the period local law requires after that. When this policy changes, a new version appears on this path with a fresh date at the head of the page, so you can always tell which wording you are reading.
We hold what an account needs to work: your sign-in details, the profile fields you save, and the wallet records created through bKash, Nagad or Bank Transfer. Play history stays with your account so you can check it. We do not collect fields we have no use for.
Cookies keep you signed in between pages and remember small preferences, like the lobby view you last used. They also show whether a page loads properly on a phone. Clear or block them in your browser if you prefer, though parts of the account area may behave differently.
Use a password you do not reuse elsewhere, and sign out when you finish on a shared phone. If a login looks wrong, change your password from the account area and message us. We will look at the account with you.
Records stay while your account is open, and for the period local law requires afterwards; wallet entries tied to bKash, Nagad or Bank Transfer usually sit in that second group. When this policy changes, a new version appears on this path with a fresh date at the head of the page.
These are the questions that land in our messages most often about this page, and the short answers we give. They cover what the policy reaches, what happens to wallet records from bKash, Nagad or Bank Transfer, how to ask for a copy of your data, and who to contact when a detail looks wrong. If your question is not here, the sections above carry more detail, and the contact route on this page reaches the team that owns the wording. We change these answers when a policy update makes an old reply out of date, so what you read here should still match the section it points to. Nothing on this page replaces the policy itself — where the two differ, the policy is the version that applies to your account.
It covers the details tied to your account — sign-in details, the profile fields you save, wallet records from bKash, Nagad or Bank Transfer, and the games you open while signed in. Links out to services we do not run sit outside it, and those services apply their own rules.
We keep the transaction record that appears against your account wallet when you move money, because you and our team both need to see what happened. The wallet app on your phone holds your payment credentials, not us. Message us if you want to know exactly what we store.
Send the request through the contact route on this page, signing in first if you can so your account reference travels with it. Tell us which records you want and we will explain what we can share under local law and the regions we serve.
Only the teams that need them to run your account: the people handling wallet records and the support staff who answer your messages. We do not pass your profile to studios or advertisers, and we do not publish anything about your play. If a request arrives from outside, we check it before we act.
Closing the account ends the everyday use of your profile, but some records stay for the period local law requires. Wallet entries tied to bKash, Nagad or Bank Transfer usually belong to that group. Tell us what you want removed and we will say what is possible.
Open your account profile and change what is editable there. If a field is locked, write through the contact route with the correct value and anything we ask for. We will explain why the field was fixed and what we can update.