This page sets out what 09jbet records when you open an account, sign in and move money through your account wallet, and why that record is tied to you rather than to a single handset. You will see which details we ask for, how a session started on your phone stays recognisable on the browser of your computer, how long a record stays with us, and which route to use when you want something checked or changed — with the same answers applying only where local law and eligible regions allow.
Account details you can see
Cookie choices in your browser
Session records tied to your account
Support page for privacy requests
YOUR RECORD EXPLAINED
How We Handle Your Account Record
Your privacy on 09jbet starts with one rule: we ask for what an account genuinely needs and nothing that would sit unused. When you open an account we record the contact details you type, the wallet or bank route you attach for a transfer — bKash, Nagad, Rocket, Upay or Bank Transfer — and the amount and reference of each movement you make through that route. Sign-in records tell us which device and browser reached your account, which is how a session you began on your phone stays recognisable when you carry on with the browser on your computer. We keep those records because a question about a transfer, a disputed session or a sign-in you did not expect can only be answered with evidence rather than with a recollection. What we hold, how long we hold it and who may look at it depend on the law where you live and on whether your region is eligible for an account. That is why this page describes a posture instead of promising one fixed set of rules for every country. Where local requirements differ from what we describe here, those requirements apply to your account, and the notice in your account area tells you when that happens. We do not sell your details, and we do not hand your wallet numbers to anyone for their own marketing.
bKash
Nagad
Rocket
Upay
Bank Transfer
INSIDE THE BOUNDARY
What This Policy Covers and Leaves Out
This policy covers what happens inside your 09jbet account. Sign-in details, the device and browser records attached to a session, the transfer routes you add — bKash, Nagad, Rocket, Upay and Bank Transfer — plus the messages you send us through the support page all fall inside it. It also covers the small files our pages store on your phone or computer when you browse the lobby, and the record we keep of any change you make to your account details. Anything outside that boundary sits with someone else. A page you reach by following a link out of our lobby runs on another operator's rules, and a wallet app on your phone holds its own data under its own terms. We would rather mark that line clearly than blur it, because a privacy question is only answerable when you know who is holding the record.
Account access and sign-in
Your sign-in details, the recovery route on your account and the device and browser records created when you open a session are covered here. If you sign in on your phone and then on your computer, both records belong to you and both can be raised with support.
Wallet and transaction records
Every transfer you start through Nagad, Upay or Bank Transfer leaves a record on your account wallet: the route, the reference and the status shown at the time. That record is what we look at when you ask about a movement, so the policy covers it too.
Site content and cookies
What our pages store on your phone or computer — the small files that keep you signed in and remember layout choices — is inside this policy too. You can clear those files in your browser settings whenever you like; the account itself stays, but you may need to sign in again.
Third-party pages we link to
When you follow a link out of our lobby to a page we do not run — a game studio's own site, for example — the policy of that site applies from the moment you land there, not ours. We cannot see or change what such a page records about you.
ACTIONS FOR YOU
Steps You Can Take Yourself
What you can do about your own record is deliberately plain. Open your account area and you can see the contact details we hold and the transfer routes attached to your wallet; if a spelling is wrong or a number has changed, correct it there rather than living with it. When something looks off — a sign-in you do not recognise, a movement you did not start — the support page on this site is the route to use, and the more of the account reference you include, the quicker the check goes. You can also ask what we hold about you and ask for a copy of it; we answer from the same account record you can already see, so the reply and the screen should match. A request that touches a transfer entry may mean we keep the original for as long as local rules require, and we will tell you when that is the case.
Check what we hold
Sign in and the account area shows the contact details and wallet routes on your record. That is the same view our support team works from, so anything you see there is what a reply will refer to. Start there before you write in.
Correct your account details
A changed phone number or a mistyped email is yours to fix, and fixing it early keeps a session recovery from going to an address you no longer use. Edit it in the account area; the change is recorded against your account.
Ask what we hold
Send a request through the support page and we will confirm what can be shared, in what form, and whether local rules limit any part of it. Include your account reference so the answer comes back against the right record.
Raise a session concern
If a device or sign-in in your history is not one you recognise, say so through the support page with the date you saw it. We check the session record with you rather than closing the question with a general reply.
PRIVACY CONTACT ROUTE
Where to Send a Privacy Question
Privacy questions deserve a named route rather than a hunt. On 09jbet the support page is the published path for anything to do with your account record — a sign-in you want checked, a wallet entry you want explained, a detail you would like corrected, or a copy of what we hold. Use the form or channel listed there and include your account reference plus the date of the session or transfer you are asking about; a request carrying those two things is one we can act on straight away. We never ask for your password or a wallet PIN through any channel, so a message requesting one did not come from us. Keep the confirmation you receive as well — it is useful if the same question comes up again from another device. Where a request depends on the law in your country or on your region being eligible, the reply will say so plainly.
Support page on this site
The published route for a privacy question, a correction or a request about your record. Open it from the header on any page, describe the account detail you want checked, and keep the reply with your own records.
Your account area
Where you correct a phone number or email yourself, and where the wallet routes attached to your account are shown. Most privacy requests start here, because the detail in question is visible and editable before anyone needs to be contacted.
Account notices
When we change how this policy works, the notice appears in your account area as well as on this page. Read it when it appears; it tells you which part of the record the change touches and what you can do about it.
DATA CARE PRACTICE
Cookies, Security and Retention in Practice
Handling a record properly is quieter than talking about it. We keep your account details in one place, tie session records to that account rather than to a handset, and limit who inside the operation can open them. The small files our pages set do two jobs: they hold your sign-in and they remember how you left the lobby laid out, and you can clear them from your browser whenever you like. Retention follows the reason a record exists — a transfer entry stays for as long as accounting rules where you live require, while a browser record with no further use is not kept for its own sake. Nothing beyond what a transfer itself needs is shared with a payment provider. When you want something changed, the request goes through the support page and the change is recorded against your account, so the next person who looks sees the same version you do.
What we collect and why
Contact details, the transfer routes on your wallet, the movements through them and the device records behind each sign-in. Each of those exists to answer a question you might later ask about your own account, not to build a profile for someone else's use.
Cookies and your browser
Our pages set small files that keep you signed in and remember layout choices between visits. Clearing them in your browser signs you out and resets those choices; it does not close your account. If you share a phone, clear them before you hand it over.
Session security you can see
We tie a session to your account, so a sign-in from a device you do not recognise shows up in the same record you can ask us about. We never request your password or wallet PIN through a message, and any message that does is not from 09jbet.
Retention and removal requests
A transfer entry stays for as long as accounting rules where you live require it, because a query months later needs the original. Other records are dropped when their purpose ends. Ask through the support page if you want to know which applies to a specific entry.
COMMON PRIVACY QUESTIONS
Privacy Questions We Hear Most
Six questions come up more than any others when people ask about privacy on 09jbet, and they are answered below in the order they usually arrive. One theme runs through all of them: the record we hold is the record you can see. If your question is about a specific transfer, a sign-in you did not expect or a detail that needs correcting, the answer will point you to the account area or the support page rather than leaving you to guess. Read the pair that matches your case, then act from there. Anything not covered — a request for a copy of your record, a question about how long a wallet entry stays with us — belongs on the support page, where it can be answered against your own account instead of in general terms. Where local law or regional eligibility changes what we can do, we say so in the reply itself.
What does 09jbet record when I open an account?
We record the contact details you enter, the payment route you attach to your wallet, the movements made through it, and the device and browser that opened each session. That set is what lets us answer a question about your own account later. Nothing beyond that is collected for its own sake.
Can I see the details you hold about me?
Open your account area and the contact details and wallet routes we hold are shown there, in the same place you edit them. If you want a copy of the wider record, ask through the support page and we will confirm what can be shared and in what form, depending on local law.
Do you keep my Nagad or Upay wallet number?
Yes, for the transfers you make. The route, the reference and the status at the time are kept against your account so a question about a Nagad, Upay or Bank Transfer can be answered with evidence. We do not pass those numbers to anyone for their own marketing use.
Why does my session follow me from phone to computer?
Because session records sit against your account rather than one handset, a sign-in on your phone is recognisable when you continue on your computer. If a device in that history is one you do not know, raise it through the support page and we will check the entry with you.
How do I correct or remove something on my record?
Contact details you can correct yourself in the account area. For anything wider — a record you believe is wrong, or a request to remove what we no longer need — use the support page. Some entries tied to a transfer have to stay for as long as local rules require, and we say so when that applies.
Who do I contact with a privacy question?
The support page on this site is the published route, and it is where a privacy question should go rather than to a payment provider. Include your account reference and the detail you are asking about, and the reply will come from the team handling account records.