Live / Sports
bdmudic99 sets out how we collect, store and use your account details when you open and use your account with us. We explain what we hold, how long we keep it, and where to ask us about it — worth a quick look before you link bKash, Nagad or Upay to your wallet.
This policy covers the account details, device details and transaction records we hold when you use bdmudic99 — from the mobile number and email you register with, to the payment rail you choose when you move funds through bKash, Nagad or Upay. We treat these details as part of running your account: confirming who you are, keeping your wallet balance accurate, and responding when you raise a question through support. What applies to you depends on where you're accessing us from and the law that governs that region — we don't make blanket legal claims that override local rules, and access itself depends on your local law and eligible regions. We keep records for as long as they're needed to run your account, resolve a support query, or meet a request you've raised with us; once that need passes, we don't have a reason to hold onto it. If you link a payment method like bKash, Nagad or Upay, we treat the transaction reference and timestamp as account data, not as something we share outside running your wallet. Cookies and basic device signals help your session stay signed in and your account page load the way you left it — nothing more elaborate than that. This page sets out our posture plainly: what we hold, why we hold it, and where you can ask about it, rather than a long list of clauses copied from somewhere else.
This policy sets boundaries so you know what's covered where, rather than lumping every data point into one bucket. Account access covers your login and session; payment transactions cover the record tied to a bKash, Nagad or Upay transfer; lobby content covers which game pages you've opened, like Roulette Spinners or Teen Patti LuckySpin; and third-party services covers data that lives with someone else entirely — your wallet provider or your device maker, not us. We draw this distinction because a question about a payment reference needs a different answer than a question about why your account page remembers a game category you opened last week. Where something sits outside our direct control, we say so plainly rather than claiming reach we don't have. What applies to you in practice still depends on your local law and the region you're accessing bdmudic99 from, since not every rule reads the same everywhere.
Covers the login details, device details and session details tied to signing into your bdmudic99 account — including how long a session stays active, what we log when you sign in from a new device, and how your account page recognises a returning session versus a fresh one.
Covers the record of a bKash, Nagad or Upay transfer linked to your wallet — the reference number and timestamp we keep on your account, not the private login credentials of your mobile wallet provider, which stay with that provider and outside what we hold.
Covers how we log which game pages or categories you open on bdmudic99, such as Live Cricket Scores or Roulette Spinners, so your account page can show where you left off and your recent lobby activity without needing you to search for it again.
Falls partly outside our direct control — your mobile wallet provider, browser and device manufacturer each handle their own data separately, and this policy only speaks for what bdmudic99 itself holds against your account, not what happens on their systems.
You have practical options for managing what we hold on your bdmudic99 account, and most of them start from the account page itself. If a detail is wrong — a mobile number, an email address, a name spelling — correcting it keeps your wallet and support records accurate, which matters most when a bKash, Nagad or Upay transfer needs to be matched to your account. You can also ask us directly what details we're holding against your account and why, and raise that through the published support route rather than guessing. We don't ask you to prove anything beyond what's needed to confirm you're the account holder. None of this changes depending on which payment method you use — the same check and correction steps apply whether your wallet is linked through bKash, Nagad or Upay.
Open your account page to check the details we hold against your profile — your registered mobile number, email, and the payment method you've linked, along with a short record of recent account activity you can look back on.
Update a wrong mobile number, email address or name spelling directly from your account settings, so your wallet and support history stay matched to the right profile and nothing gets delayed because a detail doesn't line up.
Use the published support route to ask what we hold on your account or why a particular record was kept, and we'll respond through that same channel rather than asking you to start over somewhere else.
Questions about this policy go through the same support routes we publish for account and payment queries — we haven't set up a separate privacy-only desk, because most privacy questions come up alongside an account or wallet question anyway, like why a bKash, Nagad or Upay reference shows up a certain way on your account. Open the support option from your account page first; it's the quickest way to reach someone who can see your account context without you repeating details already sitting in your profile. If the answer needs more than the help section covers, that same route carries it forward.
Reach us through the support option listed on your account page whenever you have a question about what we hold or how a particular record was created — it's the quickest route to a reply, since the conversation already carries your account context with it, instead of starting from zero.
Check the help section linked from the site footer for written answers before raising a direct question — it covers account basics, wallet linking and common questions about bKash, Nagad or Upay transfers without needing to wait on a reply.
Send a written question through the support channel if you want a specific record checked or corrected, and keep a note of when you sent it — that way, if you follow up, we can match the two conversations together quickly.
We built our account and payment handling around keeping your bdmudic99 profile consistent, rather than collecting more than running an account actually needs. Session cookies keep you signed in; account records tie your login to the payment method you've chosen, whether that's bKash, Nagad or Upay; and support notes exist mainly so a second conversation with us doesn't start from zero. Retention follows the same logic across the account — we hold what a live account, an open support thread or a recent transaction needs, and no longer than that purpose lasts. Verification steps on your account page stand between a visitor and your wallet details, every time, not only on the first sign-in. If you want something checked or changed, the same support route covers that request.
Keep your account signed in as you move across pages and remember basic display preferences, without tracking anything beyond what your current session needs to work properly — closing the browser or signing out of your account ends that session cleanly, with nothing carried into the next one.
Confirm it's really you accessing the account before showing wallet or payment details, using the verification steps already shown on your account page — the same check applies whether you've linked bKash, Nagad or Upay, and it runs every time, not just on first sign-in.
Tied to how long your account stays active or a support query stays open, rather than to a single fixed public schedule we publish elsewhere — once a record has no active purpose left, we don't keep holding it for its own sake.
Routed through the same support channel as any other account question, so a request to check or correct a record gets a direct response from someone who can see your account context, rather than a generic reply that starts the conversation from nothing.
These are the questions that come up most often when you're setting up a bKash, Nagad or Upay-linked wallet, checking a session, or wondering what happens to a record after you've asked a support question. If something you're looking for isn't covered here, the support route on your account page is the direct way to ask us without waiting for this page to be updated.
We treat your linked payment reference as account data used to match transactions to your wallet. We don't use it for anything beyond running your account and resolving a support query you've raised with us.
Yes — open your account page for the basics, and raise a direct question through the published support route if you want a fuller look at what's recorded against your profile.
Update it directly from your account settings. Keeping these details current matters most when a bKash, Nagad or Upay transfer needs to be matched correctly to your wallet.
Access and how this policy applies depend on your local law and eligible regions, so we don't state a single blanket rule — check the account and terms pages for what applies where you are.
We keep records for as long as your account stays active or a support thread remains open. Once that purpose passes, we don't have a reason to continue holding the detail.
Use the support option listed on your account page first — it carries your account context already, so you won't need to repeat details you've already given us.