Casino / Slots
The zw55 privacy policy sets out, in plain terms, what we hold about your account and what you can ask us to change. It covers your profile details, the wallet records behind your transfers, and the device signals that keep a signed-in session going.
Our starting position is simple: we hold what an account needs to run, and we tell you what that covers. When you open an account, we keep the details you enter — your name, your contact route, your sign-in credentials and the device access records that let us recognise you moving between mobile and desktop. Payment references from bKash, Nagad, Rocket, Upay or a Bank Transfer sit in the same place, attached to your account wallet, so a question about a transfer can be answered later. Privacy rules are not identical everywhere, and that shapes the rest. Some of what we may store, how long we keep it and which choices you can exercise follows the law where you are and whether your region is eligible to be served… thing from different places can get different answers, and we would rather say that openly than pretend one rule fits everyone. We also keep this page short on purpose. Long legal walls bury the parts that matter, so we set out the practical facts: what we keep, why it exists, how to ask for a change, and who to contact. If a line here is unclear, use a published support route and we will explain it before you act on anything.
Scope questions usually come up around the edges — what we hold ourselves and what belongs to someone else. Anything you do while signed in sits inside this policy: the profile fields you fill, the wallet activity tied to your account, and the device signals we read to recognise a signed-in session on mobile and desktop. Two things sit outside that line. Payment providers such as bKash, Nagad, Rocket, Upay and your bank run their own privacy practices, so when you confirm a transfer inside their app, their rules cover that step rather than ours. Game content from studios including Bigtime Gaming, PG Soft, Habanero, PlayStar and JDB loads inside our lobby, and parts of that delivery may rest on services we do not operate. We draw the line so you know who to ask. If a question is about your account, your wallet record or how we handle data, bring it to us. If it concerns a balance inside a payment app or a line on a bank statement, the provider is the right place to raise it.
Everything behind your sign-in is covered here. That includes the name and contact details you enter at registration, the sign-in credentials you use, and the session records that show when a mobile or desktop device reached your account. If you want to change or correct any of it, the account page is where you start.
Deposits and withdrawals you make through bKash, Nagad, Rocket, Upay or a Bank Transfer leave a record attached to your account wallet. We hold the reference we need to match a transfer to your account and to answer a question about it later. The balance inside your payment app stays with that provider.
Titles from Bigtime Gaming, PG Soft, Habanero, PlayStar and JDB load inside the lobby, and the pages you open there are part of what we serve. We keep the content side simple: what you see in the lobby, the category pages you browse and the game screens you launch are handled under this policy.
Some steps happen on systems we do not run. Your wallet app, your bank and any service a game studio relies on to deliver a title sit outside this policy. When you are redirected away from our pages, read the privacy terms shown there, because that provider decides what it stores and for how long.
Behind the policy sits a short set of actions you can take yourself. Start in your account area, where your profile fields, sign-in details and wallet history are visible from one screen — useful when you want to confirm what we hold before you ask us to change anything. Nothing about that step is hidden or delayed. If something is wrong, correct it where the field allows an edit, and bring it to support when it does not. A misspelled name or an outdated contact route is worth fixing early, because those details are how we reach you about your account. Then there is the asking part. You can raise a question about how data is handled, request a copy of what sits on your account, or ask us to remove what we are not required to keep. Some of those choices are set by the law where you live and by the regions that are eligible to serve you. Support routes published on the site are the way in.
Your account area shows the profile fields you entered, the contact route we use and the wallet activity linked to your sign-in. Open it on mobile or desktop whenever you want to check what is stored. If a field looks wrong to you, that same screen is where the fix begins.
Where a field can be edited, we leave it editable so you can update a contact route or a spelling yourself. Where it cannot, message support with the correction and we will set it right. Keep your sign-in credentials current too, since that is the first line of your account access.
Ask us anything about how your details are handled and we will answer in plain terms. That covers what we keep, why a record exists and what happens to it after an account closes. Use a published support route and describe the account you are writing about.
You can request a copy of the account data we hold, and ask us to delete what we are not required to keep. How far that goes is set by the law in your area and by which regions are eligible to serve you, so we explain the parts that apply before acting.
Privacy questions deserve a route that actually reaches someone, so we keep the options visible rather than buried at the bottom of a long page. The contact page on this site is the entry point for anything about how we handle your data — a question about a stored record, a correction you cannot make yourself, or a request to remove details we are not required to keep. If you are already signed in, start from your account area. Opening a support request there means we can see which account you mean without you explaining it, which usually saves a round of messages. Include the specific field, transfer reference or page you are asking about, and what outcome you want. We do not publish separate hours or response promises, because those would be guesses. What we can tell you is that every policy request arriving through a published route gets read and answered, and if a request turns on local law or on which regions can be served, we will say so before you take another step.
The contact page published on this site is the main route for anything about your account data. Describe the record or field you are asking about and the outcome you want. If your request turns on local law or eligible regions, we will tell you which part applies before acting.
When you are logged in, raise the question from your account area. The request arrives with your account attached, so you do not need to explain which profile it relates to. Include the page, field or payment reference involved so the answer can be specific.
Many privacy actions start in the settings screen you already use. Changing a contact route, updating a password or closing an account are all done from there, and the same screen shows what a change affects. If a control is missing, ask support rather than working around it.
Four habits sit behind how we look after account data. Collection with a purpose comes first: we take the details an account needs, and we do not gather fields just because a form has room for them. The second is session care. Cookies and similar storage keep a signed-in session alive while you move between the lobby, a game screen and your wallet on the same phone. Clear them and you will be asked to sign in again — expected, not a fault. The third is retention. Records linked to your account stay while it is open, because wallet activity and transfer references are what we use to answer a question months later. When an account closes, we keep only what the framework covering your region requires and let the rest go. Fourth, the route back to us. Every change request runs through the support routes published on this site, where you can name the field, record or page you want altered. Because privacy rules vary by market, what we can action follows the law where you are. We will say so plainly.
We take the details an account needs to open and run: name, contact route, sign-in credentials, and the device signals that tell us a session is really yours. Wallet activity tied to bKash, Nagad, Rocket, Upay or a Bank Transfer is recorded so a question about a transfer can be answered later.
Cookies and similar storage keep you signed in as you move between the lobby, a game screen such as Crash Blitz and your wallet on one phone. Blocking them is your choice, but expect to sign in more often. They serve session handling here, not advertising tracking.
Records attached to your account remain while the account is open, because payment references and wallet history are what let us look into a transfer question long after it happened. When you close an account, we keep only what the framework applying to your region requires, then remove the rest.
Every correction, copy request or deletion runs through the support routes published on this site. Tell us the field, record or page involved and what you want changed. Because rules vary by market, what we can action depends on the law where you are.
These are the questions we field most often about how account data is handled at zw55, answered without the legal padding. If yours is not here, the support routes published on the site will get you a straight reply.
It covers what we hold about your account and how we handle it — the profile details you enter, the wallet records tied to your transfers, and the device signals behind a signed-in session. Payment apps and game studios run their own practices, so those sit outside this policy.
Yes. Your account area shows the profile fields, contact route and wallet activity linked to your sign-in, on mobile or desktop. Open it whenever you want to check what is stored. If something looks wrong, the same screen is usually where the correction starts.
We record the transfer reference and the movement needed to match a payment to your account, not your wallet password or your bank login. Those credentials stay inside bKash, Nagad, Rocket, Upay or your bank, where you enter them yourself.
Cookies and similar storage hold your session together while you switch between the lobby, a game screen and your wallet on one device. Clear them and the next step is a fresh sign-in, which is normal. They serve session handling here, not advertising tracking.
Use a published support route and name the field, record or page you want changed. Tell us what the outcome should look like. How far we can go follows the law where you are and the regions eligible to serve you, and we set that out before acting.
Not exactly. Privacy law varies between markets, so what we store, how long we keep it and which choices you can exercise differ by place. Availability and eligibility also follow local law and the regions that can be served, so check what applies where you are.