Mobile / Sports
jeta99 keeps one written page for how account details, wallet records and cookie choices are handled, so you can read the rules before you deposit and again after. Nothing here overrides your local law; it explains how we work inside it.
Privacy on jeta99 starts with one rule: we collect what an account and a wallet need to work, and we tell you where each piece goes. Your registration details, sign-in email, device and browser type, and the payment records tied to bKash, Nagad, Rocket, Upay and Bank Transfer make up most of what we hold. Transaction references exist so a deposit or withdrawal can be matched to your account wallet when a question comes up, not so we can build a picture of how you spend your evenings. How far that record-keeping reaches depends on your local law and eligible regions, and rules differ between countries and between payment routes. Where local rules ask for extra checks, we follow the steps published in your account rather than adding new ones at the counter. Where a route is not open to you, it simply does not appear on your wallet page. We do not sell account records, and we do not hand your details to a studio or game provider so it can market to you directly. Some processing sits with partners who help us run the lobby and process payments, and they act on our instructions. A lawful request from an authority is handled under the same test: if local law requires it, we comply, and we tell you what we can within those limits. Treat this page as our posture, not a fixed promise that fits every country equally.
This policy follows your account, not your device. Open jeta99 on a phone browser or a desktop and the same rules apply to the email you sign in with, the wallet page you see and the references stored against your deposits and withdrawals. What changes is only what the browser shares with us — screen size, browser type, general region — which helps the lobby load correctly on a small screen. Some things sit outside these pages. A game from JDB, PG Soft, Bigtime Gaming or Pragmatic Play runs inside our lobby but may show its own notices. A payment app you open from your phone has its own terms. Any site we link to is not covered here. Cricket markets, table games and slot rooms all sit under one account record. If you are unsure whether a page falls inside it, the test is simple: does it ask you to sign in to your jeta99 account? If yes, this policy applies.
Your profile, wallet page and transaction history sit inside this policy. Once you sign in, the details you see there — email, masked references, deposit and withdrawal lines — are the same records we describe on this page. Ask us before assuming anything outside that view is held.
When you move money through bKash, Nagad, Rocket, Upay or Bank Transfer, we keep the reference and status that route returns to us. We do not see your wallet PIN, and we cannot read messages inside your payment app. That part stays between you and the provider.
Titles supplied by JDB, PG Soft, Bigtime Gaming and Pragmatic Play run inside our lobby, and a game screen may load small files of its own. Those files support the game, not advertising. Where a studio shows its own notice, it sits alongside this policy rather than replacing it.
A link out to a payment app, a store page or another service leaves this policy behind. Their handling of your details is theirs to explain. Read their terms before you share anything there, and treat any request for your password or wallet PIN as a warning sign.
You are not stuck with what we hold. Sign in and open the account area to see the email, phone number and payment references attached to your profile, then use the edit fields there when something has changed — a new number, a different wallet, a corrected name spelling. Those edits reach us as an update request rather than a silent overwrite, so keep the confirmation you see on screen. If you want a copy of your records, or you want something removed, ask us rather than guessing. Tell us the account email and the specific item, and we will explain what we can do and what local law asks us to keep. Some transaction records stay for a period set by financial rules, and we say so plainly instead of promising a deletion we cannot make. Closing your account is also your call, and the same area handles it. Closing ends new activity; it does not erase records we are required to hold.
Sign in and open your profile to see the email, phone number and wallet references on file. The wallet page shows the deposit and withdrawal lines we keep against your account, including the reference each route returned when the transfer was created.
If a phone number, name spelling or preferred wallet is wrong, change it in the account fields instead of opening a second profile. A duplicate account splits your history and makes a later question about a bKash, Nagad or Rocket transfer harder to answer.
Write to the published support route from your profile email and say which records you want. We reply with what we can share and flag anything local law asks us to keep. We never send wallet PINs or payment app credentials, because we do not hold them.
If you think a record is wrong, or was used in a way this page does not describe, say so in the same message. Include the rough date and the route — Upay, Bank Transfer, bKash — so the search is quick. We will explain what we found and what changed.
Questions about this policy go through the same support route as any account question, which keeps one thread for your account instead of three. Open the help or contact link shown in the site footer or inside your signed-in account, and write from the email address on the profile. That match is what lets us find your wallet records without asking for extra documents first. Say what you want in the opening message: a copy of a record, a correction, a deletion request, or an explanation of how a cookie is used. Add the rough date and the route involved — bKash, Nagad, Rocket, Upay or Bank Transfer — plus the reference your wallet page shows. A message with those three things usually gets a direct answer on the first reply instead of a round of questions. We do not publish a phone line for policy matters, and we will not ask for your password, wallet PIN or a screenshot of your payment app. Treat any message that does as unrelated to us.
Use the contact link in the site footer or the help entry inside your signed-in account. Write from the profile email address so we can match the request to your wallet records. Keep the same thread for follow-ups rather than opening a fresh one each time.
When a deposit or withdrawal line looks wrong, include the route name — bKash, Nagad, Rocket, Upay or Bank Transfer — plus the reference your wallet page shows. We check the record against what the route returned to us and tell you what matches.
For a copy, a correction or a deletion, name the item in the first line of your message. We reply with what we can share and say what local law asks us to hold. Access and eligibility depend on your local law and eligible regions.
Most of what keeps a session working is invisible. A sign-in cookie remembers that you already passed the login step, so the lobby does not ask again on every page. A small preference file keeps your chosen language and screen layout in place. These are practical files, and clearing them signs you out and resets your view, which is a normal thing to do on a shared phone. Account access rests on the email you registered with and the password you set. We do not hold your bKash, Nagad or Rocket PIN, and no support message will ask for it. If you see a sign-in you do not recognise, change the password and write to us with the date; that is far more useful than a screenshot of the wallet app. Retention is tied to purpose. Transaction lines stay as long as payment and accounting rules require, while preference cookies expire far sooner.
A sign-in cookie keeps you inside your account between pages, so the lobby and wallet do not ask for the password again on every tap. Clearing browser data ends that session and you sign in once more. Nothing about the tables you played sits in that file.
Your profile email and password are the two keys we check. We never hold a wallet PIN, and we never ask for one by message. If a sign-in looks unfamiliar, change the password first, then tell us the date and we will look at the session record.
Deposit and withdrawal lines stay for the period that payment and accounting rules set, because a later dispute may need them. Preference cookies expire much sooner. We do not keep a record past its purpose, and we will tell you which rule applies to a specific item.
One message to the published support route covers a correction, a copy or a deletion request. Include the account email and the item you mean. We answer with what we can do, and we say plainly when local law means a record has to stay.
These are the questions that reach our support route most often, answered in the same plain terms as the rest of this page. They cover what we keep, what you can change and what happens when you close an account. If your question is not here, the contact route in the site footer reaches the same team that handles wallet issues, so you do not need a separate address for privacy matters. One point applies throughout: access and eligibility depend on your local law and eligible regions, and a rule that fits one country may not fit another. Read the answers with your own market in mind, and check the terms attached to whichever payment route you use, since those terms are set by the provider rather than by us.
Your profile email, phone number, sign-in details, selected language and the payment references tied to your wallet. Transaction lines from bKash, Nagad, Rocket, Upay or Bank Transfer sit alongside those. We do not keep wallet PINs, and we cannot read messages inside your payment app.
Sign in and open your profile and wallet page. The deposit and withdrawal lines you see there are the same ones we work from when you ask a question, each with the reference the route returned. If something looks missing from that view, ask us and we will say what we hold.
Send one message through the published support route from your profile email. Name the item and the date, and say whether you want a correction, a copy or a deletion. We reply with what we can do and flag any record that local law requires us to keep.
No. Studios such as JDB, PG Soft, Bigtime Gaming and Pragmatic Play supply titles that run inside our lobby, and they do not receive your account email or wallet records to market to you. Partners who help us run the lobby and process payments act on our instructions.
Closing ends new activity on the profile and stops the sign-in session. Transaction lines stay for the period that payment and accounting rules set, because a later dispute may need them. Preference cookies expire on their own. Ask us which rule applies to a specific record.
It describes how we work, and how much of it reaches you depends on your local law and eligible regions. Where a country's rules ask for something different, those rules win. Ask us before you open an account if you are unsure whether your region is supported.