Slots / Casino
jowa99 keeps your account details under one written privacy policy, so you can see what we collect, why we hold it, and which route to use when you want something changed. Access to the service, and the choices this policy gives you, depend on your local law and eligible regions.
We keep one plain rule in front of every privacy decision: your account data belongs to you, and we hold it only to run the account you opened. That means we collect what the service needs — the email you sign in with, the mobile access details you add, and the wallet records that sit beside a local payment route such as bKash, Nagad or Rocket. We do not sell that data, and we do not hand it to a partner for their own marketing. What we may do with your data, and what you may ask us to do with it, follows two things: the law where you live and the rules of the regions we serve. Privacy rights differ across markets, so nothing on this page should be read as a promise of a right your local law does not give you. If you are outside an eligible region, some parts of the service will not open to you at all, and no page on this site changes that. Where the law gives you a choice, we show it inside your account instead of burying it in a document. Where the law puts a duty on us, we carry it and tell you what changed. One more thing worth saying: we revise this page when the way we handle data changes, and the version you see here is the one that applies to your account today.
Scope is where a privacy page earns its keep, so here is the line we draw. Signed-in activity on jowa99 falls inside this policy: the email you sign in with, the session that keeps you logged in, the wallet records built from a bKash deposit or a Nagad transfer, and the pages you open in the lobby. Support messages you send us land here too, because we need your account context to answer them properly. What sits outside is just as important. A payment app you open from your own phone screen, your mobile network, a browser extension and any site we link to run on their own privacy terms, and we have no say over how they store what you hand them. Game and sports content shown in the lobby is handled as part of your session, but a provider's own site is not. If a tool or partner is not named on this page, treat it as outside our handling until you ask us directly.
Your sign-in email, the method you use to sign in and the device details that come with it sit inside this policy. We use them to open your account on a phone or in a browser, to spot a login that looks wrong, and to keep your session alive.
A bKash deposit, a Nagad transfer or a Rocket payment leaves a record in your account wallet. We keep those records to show your balance, to settle a dispute and to meet bookkeeping duties. We do not publish them or pass the amounts outside the handlers who need them.
Opening a title such as Cricket Battle or Baccarat Green Table tells us which pages load for you and which device you used. That activity helps us fix a page that stalls and keep the lobby steady. It is not used to build a public profile of you.
A payment app, your mobile network or a browser extension sits outside our control. Once you leave our pages, that provider's own privacy terms apply, and we cannot answer for how they store your data. Ask them directly when their handling matters to you.
Rights only matter if you can reach them, so we put the useful actions in your own hands. Sign in, open your profile and you can see the email and mobile details attached to your account, along with the wallet records that follow each local payment you have made. If something there is out of date, correct it on the same screen rather than living with a wrong number. When a change is not something you can make yourself, our support route takes the request and passes it to the team that handles account data. You can also write to us with a plain question about this policy and get an answer about your own record, not a template. What you can demand, and how quickly we must act, follows the law where you live. We will tell you which requests we can act on and which ones your local rules do not cover.
Sign in and open your profile to read the email, mobile number and wallet entries attached to your account. Everything we hold for you starts there, so check a detail before you ask anyone else about it. If a field looks wrong, note it and move to the correction step.
Where a field can be edited, the profile screen saves the change and confirms it back to you. Mobile numbers and email addresses are the usual cases. If a field is locked, that means the change needs a support request, not that the record cannot be fixed.
Write a short question about what this policy means for your account, and our support route passes it to the team that owns the document. Mention the account reference so the answer is about your record rather than a general reply.
When you want a record corrected or removed, say which one and why. We will tell you what we can act on, what local rules require us to keep, and how long that hold lasts. You do not need a legal reason to ask the question.
Privacy questions deserve a named route, not a general inbox lost at the bottom of a footer. Use the support entry published inside your signed-in account; it carries your account reference, so the person answering can see what you are asking about without you pasting personal data into a message. If the question concerns a payment record — a bKash deposit, a Nagad transfer, a Rocket payment — mention the date and the amount shown in your wallet, and nothing more. Never send a password, a PIN or a full card number through any support channel. For a request about your data, tell us what you want changed and why; we may ask you to confirm the account first. When the question concerns this policy itself, say so plainly and we will route it to the team that owns the document. Response times depend on the queue and your region, so we will not promise a clock we cannot keep.
The support route published inside your signed-in account is the path to use. It carries your account reference, so the person answering can see the record you are asking about without you pasting personal data into a message box.
Say plainly that your question is about the privacy policy. That wording sends the message to the team that maintains this page, who can explain a clause in your own words instead of pointing you back to the same paragraph.
For a correction or a removal, include the account reference, the field you want changed and the reason. Keep passwords, PINs and full card numbers out of the message. If we need to confirm you hold the account first, we will say so before anything moves.
Handling data well is a set of small habits rather than one big promise. We collect the fields your account needs, keep the wallet records that explain a transaction, and leave the rest alone. Cookies do most of the quiet work: they hold your session so you are not asked to sign in on every page, and they remember small display choices on a mobile browser. You can clear them from your browser settings at any time; the trade-off is that you will sign in again. Security sits with both of us. We limit who inside the service can open an account record, and you keep your sign-in details to yourself and sign out on a shared phone. Retention follows purpose — a wallet record stays while it explains a balance or meets a bookkeeping duty, and then it goes. When you want something corrected or removed, the request goes through the support route and we tell you what we can do within your local rules.
We take the fields an account needs to work: sign-in email, mobile details, session records and wallet entries from a local payment. Each field has a job, and we do not collect extras to fill a profile. Ask us about a specific field and we will say what it is for.
Cookies hold your session so you are not signing in on every page, and they remember small display choices on a phone. Clearing them from your browser settings is always open to you. The trade-off is simple: you sign in again and some display choices reset.
Access to an account record is limited to the people who need it to answer you. Your side of the bargain matters more: keep sign-in details to yourself, sign out on a shared phone, and treat a message asking for your password as a fake, whoever it appears to come from.
A wallet record stays while it explains a balance or meets a bookkeeping duty, then it goes. Session records are shorter lived. When you want something corrected or removed, the request goes through support and we tell you what we can do and what local rules keep in place.
Most of what people ask us about this page comes down to four things: what we hold, who sees it, how long it stays and who to tell when something is wrong. The answers below are written for a signed-in account, because that is where every data action starts. If your case is not covered here, send it through the support entry in your account and mention the policy by name. Nothing in these answers overrides your local law, and nothing here widens access beyond eligible regions.
Your sign-in email, the mobile details you add, the session record that keeps you logged in, and the wallet entries created by a local payment. We do not keep a card number or a PIN. If you want to see what is attached to your profile, open your account page and read it there.
You can ask, and we will tell you what is possible. Some records, such as a wallet entry that explains a balance or meets a bookkeeping duty, have to stay for a set period. Others can go once the account is closed. Send the request through the support route in your account.
It covers the record we keep of it inside your account wallet — the date, the amount and the reference you see. It does not cover the payment app on your phone, which runs on that provider's own privacy terms. Ask them directly if you want to know how they store your details.
Open your profile after signing in. Where a field can be edited, the change saves there and we confirm it on the screen. Where it cannot, send the request through support with your account reference. We may ask you to confirm you hold the account before anything moves.
Only to the handlers who need them to run the service you asked for, and where the law requires it. We do not sell your data or hand it to a partner for their own marketing. The categories we work with are set out on this page, and you can ask us about your own record.
Use the support entry published in your signed-in account, which carries your account reference. Ask about this policy by name so it reaches the team that owns the document. Keep passwords, PINs and full card numbers out of any message you send us.