zeetben7 keeps one privacy policy for the whole site, and it covers the account you open, the wallet records behind your deposits and withdrawals, and the device details our systems read when you sign in. This page sets out what we collect, why we keep it, and the choices you have once your account is live. Nothing here is written for a different market: if you play from Bangladesh, the sections below describe the routes you already use, from the login screen to the support form. Where you see a payment chip such as bKash, Nagad or Rocket, it simply shows which wallets appear in your own account area. Reading this page takes a few minutes, and it answers the questions our support route gets asked most, including how to check your records and how to ask us to correct something. If local law in your region restricts any part of this, that restriction applies to you.
Account data
Wallet records
Device sign-in
Support messages
HOW WE APPLY THIS
Policy Terms and Local Law
We treat this policy as the single record of how zeetben7 handles personal data, and we apply it the same way whether you sign in from a phone browser or a desktop screen. What changes is the law around you. Data protection rules differ from country to country, and access to the platform itself depends on your local law and eligible regions. Where a section here says we keep a record, we keep it only as long as the rules in your region allow or require. Read the paragraphs below as a description of our normal practice, not as a statement that every route is open to everyone. The chips in this section show the wallet names that appear in your own account area once your account is set up - bKash, Nagad, Rocket and Upay are the local rails we configure, and a bank transfer is listed where your bank supports it. Your choices under this policy do not change because of the wallet you pick, and picking a wallet never adds extra personal data to your profile. If you are unsure whether a data protection rule in your region applies to you, ask us through the published support route and we will point you to the part of this policy that covers it.
bKash
Nagad
Rocket
Upay
Bank transfer
COVERED OR NOT
Lobby Content and Wallet Steps
The policy you are reading applies to the account you hold with us and to the way you reach it. That means your login details, the profile fields you fill in, the wallet records tied to your deposits and withdrawals, and the device and browser signals our systems read each time you sign in. It also covers messages you send us through the published support route, because those messages become part of your account file. It does not cover what happens on a studio's own pages, in a wallet app, or on any site we simply link out to. If you open bKash, Nagad or Rocket to move money, that provider's own privacy terms apply to that step, not ours, and the same is true of a bank transfer you start from your bank's app. Our policy stops where their service begins, and the four blocks below show the split.
Account access
Your login details, the email attached to the account and the profile fields saved in your account area sit inside this policy. Signing in from a phone browser and later from a desktop belongs to the same account file, so we treat both sessions as one record rather than two separate visitors.
Wallet activity
Deposits you make through bKash, Nagad, Rocket or Upay, and the withdrawal records created afterwards, are held under this policy on our side. The wallet app keeps its own copy of that transfer, and its privacy terms govern the wallet half of the step you take there.
Lobby and game sessions
Slot, table and live dealer titles supplied by JDB, Spadegaming, CQ9, PlayStar and PG Soft load inside our lobby, and the session data around them falls under this policy. The same applies to anything you open in our cricket-led sportsbook from the same signed-in account.
Outside our scope
Anything you open after leaving our pages sits outside this policy - a studio page, a wallet app or a link we publish for convenience. Those services answer to their own privacy terms instead. If a route is not part of your account area or our published support, assume their rules apply, not ours.
WHAT YOU CAN DO
Handling Your Own Account Data
Your account area is where most of this work happens, and you do not need to ask us first. Open your profile to see the email and phone details on file, and change anything that has gone out of date; a corrected number matters more than you might think, because the wallet you use later has to match it. Transaction records sit alongside your wallet activity, so you can compare what you sent with what the account shows. If something looks wrong, raise it once and keep the reference number the form gives you. Requests that need a person - deleting a record we are not required to keep, or asking what we hold about you - go through the published support route. We may ask you to confirm your identity before we act, and where a rule in your region says we must keep a record for a set period, that rule wins over the request.
Checking your records
Open your account area to see the profile fields we hold, the wallet activity tied to your deposits and the reference numbers from past support messages. Comparing your own wallet statement with that page is the quickest way to spot a mismatch before it turns into a query.
Correcting your details
If your email, phone number or name has changed, update it in the profile fields yourself. A phone number that matches your bKash, Nagad, Rocket or Upay account keeps later wallet checks simple, and it saves a support round trip.
Asking what we hold
You can ask us to describe the personal data stored against your account. Send the request from the email attached to the account, through the support route published on the site, so the reply lands with the right file and not in a general queue.
Raising a concern
If you think we have handled your data badly, tell us first with your account email and roughly when it happened. We look at the record, reply on the same route, and explain what we can change and where a rule in your region stands in the way.
ASK US DIRECTLY
Asking zeetben7 About Your Data
Privacy questions reach us through the same support route as everything else, and you will find it linked from the site navigation once you are signed in. We do not run a separate privacy desk, so there is no second queue to learn. When you write in, include the email attached to your account plus the reference number if your question follows an earlier message; that lets us open the right file without asking you to repeat yourself. Tell us plainly what you want - a copy of what we hold, a correction, or an answer about how a rule applies to your region - and say which section of the policy you are reading, since the wording here differs from older copies of the page. We answer messages in the order they arrive. If a request needs identity confirmation, we ask for it inside the same thread rather than sending you somewhere else.
Published support route
The support form is the route we publish for privacy requests. You reach it from the site navigation, and it takes the email attached to your account plus a short description of what you need, which keeps the whole request in one thread.
Account area
Once you are signed in, the account area shows the records tied to your profile and wallet, including anything connected to a bKash, Nagad, Rocket or Upay step. Use it when your question is about a record you can already see on screen.
Policy questions
For anything about the policy itself - access, correction, deletion, or how a regional rule applies - say so in your first message and quote the section heading you are reading. The reply can then point at the exact paragraph instead of a general answer.
HOW DATA IS HELD
Cookies, Sessions and Retention
Day to day, most of what we hold about you is what keeps your session running. A cookie tells our lobby that you are still signed in; it does not decide what you can play. If you clear cookies on your phone, you will sign in again the next time, and your account records stay untouched. On security, we hold your login credentials and the device signals around each sign-in so that an unexpected session can be spotted and checked by a person. Retention follows the same practical rule: we keep account and wallet records while your account is open, and afterwards only for as long as a rule in your region requires. Some records - a deposit you made through bKash, Nagad, Rocket or Upay, for example - may have to stay longer than your profile does. When you want something changed, use the same support route described above, and the change is made against the file we actually hold.
Cookies and sessions
Cookies keep you signed in and remember basic display settings on your device. They are not used to change what your account can reach. Clearing them signs you out; your records, wallet activity and profile fields stay exactly as they were.
Account security
Your login details and the device signals around each sign-in are held so that an unfamiliar session can be checked. If you notice a sign-in you do not recognise, change your password in the account area and tell us on the published support route.
Retention windows
We keep profile and wallet records while your account is open. After closure, most of it goes, but transaction records tied to local payment rails may be kept longer where a rule in your region requires it. You can ask which applies to you.
Who to contact
Questions about cookies, sessions or retention go to the support route published on the site. Quote your account email and the section heading so the reply points at the right paragraph, and ask for any change in writing.
COMMON PRIVACY ASKS
Privacy Policy Questions Answered
The six questions below are the ones our support route receives most often about this policy, and they map to the sections above rather than replacing them. Start with the first if you want to know what we actually store, and jump to the last if you are ready to write to us. Two of them deal with records you can already see in your account area, so you may be able to settle those yourself. Where an answer mentions a rule in your region, treat that as the deciding factor: data protection law differs between countries, and access to the platform depends on your local law and eligible regions. If your question is not listed, use the published support route and quote the section heading you were reading. That way the reply points at the exact paragraph rather than repeating the page back to you. Write from the email attached to your account and keep our reply with its reference number, so a follow-up question does not start from scratch.
What personal data does zeetben7 hold about my account?
Your login email, the profile fields you filled in, wallet records from your deposits and withdrawals, and the device and browser signals around each sign-in. Support messages you send us become part of the same file, which is why keeping one thread per issue helps.
Can I see the records you keep about me?
Yes. Open your account area for profile fields, wallet activity and past support references; that covers most of what people ask for. For anything not shown there, send a request through the published support route and we will confirm your identity before replying.
How do I ask you to correct or delete something?
Use the support route published on the site, from the email attached to your account, and say plainly what should change. Corrections are usually quick. Deletion depends on the record: a transaction tied to bKash, Nagad, Rocket or Upay may have to be kept where a rule in your region requires it.
Does signing in from a new phone change what you hold?
No. A new device adds a fresh sign-in signal to the same account file, so you can pick up from the phone you last used without re-entering your profile details. If the device looks unfamiliar to our systems, we may ask you to confirm the session.
What happens to my data if I stop using the account?
We keep the profile and wallet records while the account is open. Once you close it, most of it is removed, though transaction records tied to local payment rails may be held longer where a rule in your region requires. Ask us which applies to your case.
Where do I send a privacy question?
The support route published on the site - the same one you use for account help. Include your account email, the heading of the section you are reading, and what you want us to do. That keeps the answer tied to your file instead of a general reply.
Casino / Sports