Casino / App
nwws24 keeps this page plain: it names the records your account needs, the trail your mobile session leaves, and the routes you can use to ask us to change or drop something. Access to any of it depends on your local law and eligible regions, so read the sections that match your situation.
Data rules follow the law where you are, not wherever a server happens to sit, so what we can collect and keep depends on your local law and eligible regions. nwws24 describes its own account system on this page and nothing more: what you hand over when you open an account, what the lobby records as you move between slots and live tables, and which of those records you can ask us to change. Availability of a wallet rail, a game category or a sign-in route can differ across regions, and where your local rules give you a stronger right than this page describes, those rules win. The practical picture for a Bangladesh account holder is narrow. A contact field, a wallet reference and the transfer lines you generate through bKash, Nagad or Upay are the records that matter day to day. We keep them because the account cannot work without them, since a wallet transfer has to be matched to an account and a sign-in from a new phone has to be recognisable. We do not ask for more than the flow in front of you requires, and every field is visible while you complete it. If a paragraph here reads differently from what your own account shows, treat the account screen as the current version and tell support which line is out of step.
Inside this policy sits the account you open with us and everything you reach after signing in: the email address you register, the wallet reference attached to it, the category pages you browse and the game screens you open. Live tables, slot rooms and the sportsbook list all sit inside that boundary because they run in the same signed-in session. So does the technical trail your phone leaves, from the cookie that remembers your last lobby tab to the session that keeps you signed in while you switch apps, plus the device marker that shows a sign-in came from hardware you have used before. Outside the boundary sit the pieces we hand to somebody else. Game content from JDB, Microgaming, Bigtime Gaming and Spadegaming appears in our lobby, but a link that takes you to a separate website follows that website's own rules. Your mobile wallet keeps its own record of a bKash, Nagad or Upay transfer, and that copy is not ours to edit. The four entries below draw the line.
Registering, signing in with an email address and the confirmation step that proves the inbox is yours all sit inside this policy. So does the device marker that flags a new phone and the session a mobile browser keeps alive while you move between the lobby and a live table.
Anything that touches your account wallet belongs here: a transfer you start through bKash, Nagad or Upay, the reference that matches it to your account, and the statement line you see afterwards. The wallet's own app keeps a separate record of the same transfer, and that copy stays under the wallet's rules, not ours.
Category browsing, a slot room, a live table and the sportsbook list are all served inside the signed-in session, so the trail they leave sits inside this policy too. Game content itself arrives from JDB, Microgaming, Bigtime Gaming and Spadegaming, and those studios run their own separate websites.
Tap a link that leaves our lobby, whether it goes to a studio site, a wallet help page or a payment provider's statement screen, and the page you land on answers to its own privacy rules. We cannot read or amend what you enter there. Treat that page as somebody else's.
You have four practical moves on this page, and none of them need a lawyer. You can look at what your account holds, ask us to fix something that is wrong, ask what a particular clause means for your situation, and ask us to stop using a record for a purpose you no longer want. Start from the signed-in account area so we can see exactly which record you mean, whether that is a wallet line, a sign-in entry or a profile field. Quote the date and the route you were on if you can, because a precise message saves a round of questions. Requests that touch your local law are handled against that law, and eligibility can differ by region, so we may need to confirm where you are signing in from. Where a request is something we cannot action ourselves, a wallet statement that only bKash, Nagad or Upay can amend for instance, we will point you to the right place instead of leaving you to guess.
Sign in and open your profile and wallet areas. That is where your contact fields sit, along with the transfer lines your bKash, Nagad or Upay payments produced. Note the date and the route you were on before you write to us, since a short precise message travels much further than a vague one.
If your name spelling, email address or mobile number is out of date, ask us to change it before your next wallet transfer rather than after. A stale contact field can leave a confirmation step stranded. Bring the exact field and the value you want, and we will say what the account area can change on the spot.
Not every sentence here will read the same way to everybody, and asking costs you nothing. Tell us which heading you are on and what you are trying to do, opening an account, moving a wallet balance or closing a profile, and we will answer for that situation instead of pointing back at the same paragraph.
If you would rather we did not keep a record for a particular purpose, say so plainly and name the purpose. Some records we cannot drop while your account stays open, because a wallet transfer has to remain matched to an account. Where local law gives you a stronger right, that law decides the answer.
Getting an answer about this policy should not feel like hunting. We publish one contact route on the support page, and it reaches the same team that already handles sign-in trouble and wallet questions, so you are not passed between desks. Tell them you are asking about the privacy policy, name the heading you are reading, and describe the record you have in mind: a transfer line, a profile field, a sign-in notice on a new phone. That is usually enough for a straight answer. Some questions answer themselves in the signed-in area, and it is quicker to look there first, because you can see which wallet lines are attached to your profile, which contact field we hold and which category you last opened on your phone. Quote what the screen shows if it differs from this page, since a mismatch between the two is worth knowing about and worth fixing. If your question depends on your local law, say where you are signing in from; region matters to the answer and we will not guess at it.
The support page carries the contact route we publish, and it is the right place to start for anything about this policy. Write from the email address on the account where you can, so the message can be matched to your profile without a second exchange. A screenshot helps more than a description.
Many questions answer themselves inside the signed-in area: which wallet lines are attached to your profile, which contact field we hold, which category you last browsed. Look there first, then quote what you see. If the screen and this page disagree, tell us which one, and we will correct the wording at our end.
A written request about your own records should name the record, the date and what you want done with it. Keep it to that. We will answer through the same route you used unless you ask for something else, and we will say plainly when part of the answer has to come from a wallet provider.
Records only stay useful if somebody owns them. Inside our account system, the fields you fill in sit with the same team that answers wallet questions, which is why a privacy request and a transfer query can often be handled in one conversation instead of two. Cookies do a narrow job: they hold your signed-in session on a phone, remember the last category you opened and let the lobby load without asking you to sign in on every tap. Clear them and the session ends. That is the trade, and it is yours to make. Retention is deliberately boring. While your account is open we keep the lines that let a transfer be matched to it, because an unmatched transfer is money nobody can trace. Close the profile and we keep only what local rules require, then let the rest go. We do not read account records out of curiosity, and we do not hand them to outside advertisers. If you want to know where a specific record sits, ask and we will name the team holding it.
The records we hold are the ones the flow in front of you asks for: a contact field, a wallet reference and the transfer lines your payments generate. We do not ask for more than the account needs in order to work, and you can see each field yourself while you fill it in.
Cookies keep you signed in on a phone, remember the last category you opened and let the lobby load without asking you to sign in again on every tab. You can clear them from your browser at any time. Expect to sign in again afterwards, and expect some preference screens to forget your last choice.
Account records stay while your account is open, because a wallet transfer has to remain matched to an account that can still be queried. After you close a profile we keep what local rules require us to keep and drop the rest. We will tell you which part applies to your request.
Privacy questions land with the same support team that handles account and wallet issues, so nobody has to route you between departments. Give them the record and the date, and say which page heading you are reading. If a question needs your local law to answer, they will say so rather than guess.
Below are the questions that reach our support team most often about this policy, answered the way we would answer them in a chat window: short, specific and tied to what you can see in your own account. Read the pair that matches your situation, then act on the route it names. If your case sits between two of these answers, the support page is the next step, and quoting the heading you were reading makes the reply quicker to get right. Nothing here overrides your local law, and availability of any wallet rail, category or sign-in route can differ by region.
A contact field you register with, the wallet reference attached to the account, the transfer lines your payments generate, and the technical trail a browser leaves when you sign in. You can see most of it yourself in the signed-in area. Anything beyond that is described under the matching heading on this page.
We keep the lines needed to match a transfer to your account, which is what lets a wallet payment land in the right place. The wallet app keeps its own separate record of the same transfer, and only the wallet can amend that copy. If the two ever disagree, bring both to support.
You can always ask, and the signed-in area already shows much of it. What we can hand over beyond that depends on your local law and eligible regions, so the answer is not identical for every account holder. Name the record you want and we will tell you what applies in your case.
While the account is open, records stay because transfers have to remain traceable. Close the profile and we keep only what local rules require, then drop the rest. Ask us at the point of closing and we will tell you which records fall on which side of that line.
Yes, for the signed-in session. A cookie is what keeps you recognised while you move from the lobby to a live table without retyping anything. Clear your browser data and the session ends, so you will sign in again. Blocking cookies entirely will stop parts of the lobby from loading properly.
Start on the support page and use the contact route published there. Say which heading on this page you are reading, which record you mean and what you want done. A short, dated message gets a clearer answer than a long one, and a screenshot of the screen you were on helps most of all.