Slots / Mobile
399bdr collects only what we need to run your account, process a bKash deposit or an Upay transfer, and keep your sportsbook and casino sessions working on one login. Below we explain what we record, how long we hold it, and the steps you can take to review or correct it, based on your local law and eligible region.
This policy covers the data 399bdr holds once you open an account with us — your registration details, your login activity, and the transaction records tied to the payment route you choose. If you fund your account through a bKash deposit or send a transfer through Upay, we keep a record of that transaction so you (and we) can match it against your account wallet balance; we do not store your mobile banking PIN or app password, because that stays inside bKash or Upay's own system, not ours. What applies to you depends on your local law and the eligible region you are accessing 399bdr from — some data handling obligations differ by region, and we follow the rule set that applies where you are. We also hold basic device details (browser type, access timestamps) tied to your login, which helps us tell ordinary account activity apart from unusual activity on your account. This policy does not extend to third-party sites you reach through outbound links, and it does not cover the internal systems of bKash, Upay, or any bank you use to move funds before they reach your account wallet. If a term here conflicts with a specific regional rule that applies to you, the regional rule takes priority. We update this page when our data practices change.
Not every part of your 399bdr experience sits under the same privacy rule, so we break it down by activity. Account access — your login, password resets, and session history — falls fully inside this policy, and we treat it as data we are responsible for. Transactions through bKash or Upay sit partly inside: we record the transfer reference and amount against your account wallet, but the wallet provider's own app and its security steps are outside our reach. Site content — the slot and live tables, your Cricket PowerPlay or Blackjack Showdown session logs, your Crash Rush round history — is covered the same way as any other account activity. Third-party services, including the systems that process your bKash or Upay transfer before it lands in your wallet, are governed by their own privacy terms, not ours, even though we exchange the data needed to confirm your payment.
Your login details, password changes, two-factor steps if enabled, and session history sit fully inside this policy. We record and store this data as part of running your 399bdr account, and it is the first place we check if you report unusual access.
We hold the transaction reference, amount and timestamp for a bKash deposit or Upay transfer against your account wallet, but the wallet app itself — including your PIN and login steps there — follows its own provider's privacy terms, separate from ours.
Your session history across slots, live tables and sportsbook markets — including rounds in Cricket PowerPlay or Crash Rush — is treated as account activity covered by this policy, the same way your login record is, with no separate rule for game data.
Outbound links and the payment systems that sit behind a bKash deposit or Upay transfer operate under their own separate privacy terms. This policy covers what 399bdr does with the data once a transaction or click reaches us, not what happens on their end.
You have a few practical ways to check and manage what 399bdr holds on you. Start inside your signed-in account area, where your registered details and your bKash or Upay transaction history are listed against your account wallet. If something looks wrong — a changed phone number, an outdated email — you can correct it from the same account section rather than waiting on a reply. Questions about what we record for a specific deposit or transfer should go through our published support route, with your account reference ready so we can locate the right record quickly. What you can request can vary depending on your local law and the region you are accessing 399bdr from, so we handle each request against the rules that apply to you rather than a single fixed process.
Open your account area to see the registration details, login history and bKash or Upay transaction references we hold against your account wallet.
Update an outdated phone number, email or other registered detail directly from your account section rather than filing a separate request.
Use our published support route with your account reference ready if you want to ask what we hold for a specific transaction or login.
If you cannot see a record you expect, contact support through the route shown on the site rather than assuming it is missing.
If you have a question about this policy or about a specific record tied to your account, go through the support route published on 399bdr rather than a third-party channel. Have your account reference and, if relevant, the bKash or Upay transaction detail ready — this helps us locate the right record without back-and-forth. We do not list a fixed response time here because we have not published one, so treat your request as something we work through case by case rather than against a set clock. For anything involving a payment record, keep the transfer reference from your bKash or Upay app on hand, since that is what links the transaction to your account wallet on our side. Support routes are the same whether your question is about a login, a deposit, or how long we hold a particular record.
Reach out through the support channel listed on your signed-in account page when you have a question about data tied to your login, your device history, or your account wallet balance after a deposit through bKash or Upay, and keep your account reference ready.
For a question about a specific bKash deposit or Upay transfer, keep the transaction reference and the approximate time of the transfer ready, then raise it through the same published support route so we can match it against your account wallet.
If a section of this policy is unclear, ask through our published support route and reference the section heading by name, so we can point you to the exact clause rather than resending the full policy page every single time.
Keeping your account data organised matters more to us than talking about it, so here is what actually happens behind your login. We tie your bKash or Upay transaction records to your account wallet so a deposit or transfer can be matched against your balance without guesswork. Device and browser details collected at login help flag activity that does not look like your usual pattern. We keep records for as long as your account is active and for a period after, depending on the rule set that applies in your region under local law. Cookies on 399bdr support session continuity — keeping you logged in across the slot lobby, live tables and sportsbook — rather than building an advertising profile. If you want a change made to what we hold, the request route is the same published support channel described above, not a separate form.
bKash and Upay transfer references are matched against your account wallet so your balance reflects a deposit or withdrawal correctly on your end, without us needing to store the PIN or password used inside either wallet app, since that detail stays with the provider, not with us.
Cookies keep your session active while you move between slots, live tables and sportsbook markets without logging you out mid-session; they are not used to build an advertising profile, and clearing them simply signs you out of your account entirely.
Login timestamps and device details help us notice access that does not match your usual pattern — a new device or an unfamiliar browser, for instance — without us storing your wallet PIN, OTP or password anywhere on our side.
We hold account and transaction records for as long as your account is active, and for a period after that depends on the rule set that applies in your region. Change requests go through the published support route described above, not a separate form.
Here are the questions we hear most about how 399bdr handles data, straight from account holders rather than a generic FAQ template. These cover what gets recorded against a bKash deposit or Upay transfer, how long we keep login history, and where to go if you want a record corrected. We have kept answers tied to the account and payment routes we actually run, not abstract policy language. If your question is not listed here, use the support route named above and reference your account rather than starting a new thread elsewhere. Availability of specific data rights can shift depending on your local law and the eligible region you are accessing 399bdr from, so treat these answers as the general pattern rather than a fixed rule for every single account across Bangladesh regions.
We record the transaction reference, amount and timestamp for a bKash deposit so it can be matched against your account wallet. We do not store your bKash PIN or app password — that stays inside the bKash app, outside our systems entirely.
Yes — open your signed-in account area to review your registered details, login history and recorded bKash or Upay transactions. If something is missing or looks wrong, raise it through the published support route with your account reference, and we will follow up through that same channel.
We exchange only the information needed to confirm a transaction, such as a reference number, with the payment provider you choose. What bKash or Upay then does with that data is governed by their own terms, separate from this policy.
We hold account and transaction records for as long as your account stays active, and for a further period after that depends on the local law and region your account falls under. We have not published a fixed retention figure beyond that.
Yes — details like your phone number or email can usually be updated directly from your account section. For anything that section does not let you change, contact support with your account reference and a short note on what needs updating.
Use the support route published on 399bdr and reference your account along with the specific record or transaction you are asking about. We work through these case by case rather than against a published response time, and we aim to reply once we can confirm the record you mean.