Live / Casino
899db sets out the terms that cover your account, the games lobby and how we handle your details on this platform. Access depends on your local law and eligible regions, so read this page alongside the account steps shown when you sign in.
This page sets out the policy terms that apply once you open an account with 899db and move between the mobile site and a desktop browser. Because online gaming access depends on local law and eligible regions, some sections of this policy may read differently depending on where you're signing in from — we keep the wording general rather than naming a specific jurisdiction we cannot verify for every visitor. When you add funds through bKash, Nagad, Rocket, Upay or Bank Transfer, the transaction record attached to your account falls under this same policy, alongside any wallet details you save for later sessions. We don't sell your account details to third parties, and any change to this policy is reflected on this page rather than through a separate notice elsewhere. If you switch between the 899db shortcut on your phone and a browser tab on desktop, the same account and the same policy terms travel with you — nothing resets when you change device. Where a game or payment provider shows its own terms inside the lobby, those sit alongside this page rather than replacing it. Check the account section in your profile for the specific permissions tied to your sign-in, and treat this page as the general framework behind those permissions.
Not every page on 899db falls under the same rule, so this section draws the line simply. Your account access — the sign-in flow, the session that carries over when you switch from your phone to a desktop browser — sits inside this policy. So does the transaction record tied to payment chips like bKash, Nagad, Rocket, Upay or Bank Transfer, even though we don't set out processing details here. Game descriptions and lobby listings count as site content and are covered too. What sits outside this page: the specific rules inside an individual game screen, and any separate terms a provider attaches to a feature it supplies. If you're ever unsure whether something falls under this page or a provider's own terms, the safest read is to check inside the feature itself first.
This policy covers how you sign in, how your session continues when you move from the 899db shortcut to a browser tab, and the permissions tied to your profile. It does not set out individual game rules — those sit inside the game screen itself, separate from this page.
Deposits and withdrawals you record through bKash, Nagad, Rocket, Upay or Bank Transfer fall under this policy for how we store and reference that activity on your account. We do not state processing times here — check your account history for the actual record of each transfer.
Game names, lobby descriptions and category listings on 899db are covered by this page as general site content. Where a provider such as Microgaming, PlayStar, Spadegaming, Pragmatic Play or CQ9 supplies a title, the game itself may carry its own in-game rules shown on screen.
Some features inside the lobby are supplied by outside studios or payment partners rather than built by us directly. Those providers may apply their own terms inside the feature itself; this page covers your relationship with 899db, not the provider's separate terms.
Your account carries a record of sign-ins, saved details and the payment chips you've used, and this policy gives you a way to act on that record rather than just read about it. You can open your profile to check what's stored against your account, update details that are no longer correct, such as a changed phone number, and send a question through our support route if something on your account looks off. We respond to the channel you use to reach us, not to a separate request form, so keep that in mind when you write in. None of this changes how a specific game works — it only covers the account layer sitting underneath the lobby you browse on your phone or desktop.
Open your profile to see the account details and payment chips linked to your sign-in. This is the quickest way to see what 899db holds against your account before you raise anything with support.
If a saved detail is wrong — a phone number, an email, or a payment chip you no longer use — update it from your profile screen rather than waiting for us to notice.
If a line in this page is unclear against your own account activity, use our published support route to ask. We handle it as a normal account query, not a formal filing.
Policy questions usually come from something small on your account — a chip row showing a payment method you don't remember adding, or a profile field you can't edit yourself. Rather than guess, bring that specific detail to our support route listed on 899db and let the team look at your account directly. We keep this policy general because access and account handling depends on your local law and the region you're signing in from, so a reply tied to your actual account is more useful than a blanket answer. If you reach out while switching between your phone and a browser tab, mention which device you were using when the issue came up — that detail helps our side locate the right account record without us promising a fixed response time.
The most direct path is the support option shown inside your signed-in account, where our team can view the same profile, saved details and payment chips you are looking at on your screen. Keep the conversation inside that same screen rather than switching to an unlisted channel.
If a clause on this page doesn't line up with something you actually see in your account — a payment chip, a saved detail, a login step — send that specific example through the same support route instead of a general comment.
Use support to confirm that a change you made on your profile, such as an updated phone number or a corrected detail, has actually saved against your account the way you expect, rather than assuming it went through.
We treat the details behind your account — your sign-in details, saved payment chips and session history — as part of what this policy covers, not as a separate matter handled elsewhere. Cookies and similar session tools are what let you move from a browser tab to the 899db shortcut on your phone without logging in twice; turning them off in your browser settings will affect that continuity. Account security sits with both sides: we apply the checks visible during sign-in, and you're responsible for keeping your own credentials to yourself. We hold account records for as long as your account stays open, and if you want a copy of what's attached to your profile, send that request through support rather than expecting an automatic export. Any update to how we describe this handling appears on this page first, which is why it's worth checking back if your account activity changes.
Session cookies keep your sign-in active when you move between the 899db shortcut and a browser tab on the same phone, so you don't re-enter your details every time you switch screens.
Sign-in checks run on our side each time you access your account; keeping your own password and device unlocked only to you is the part that sits with you.
We keep your account history, including saved payment chips like bKash, Nagad or Rocket, for as long as your account stays active rather than clearing it on a fixed schedule.
If you want to know what's recorded against your profile, raise that through support — we don't publish an automatic self-service export on this page.
A short set of answers covering the account, data and access questions we hear most often about this policy on 899db.
Access and account handling depends on your local law and the eligible regions set for this platform, so parts of this page may read differently depending on where you're signing in from. We keep the wording general rather than naming a specific region we can't confirm for every account.
Open your profile inside your signed-in account to see which payment chips, such as bKash, Nagad, Rocket, Upay or Bank Transfer, are attached to your record. This policy covers how that record is handled, not the processing details of each transfer.
Your account and this policy travel with you across devices — signing in on a browser tab after using the 899db shortcut on your phone doesn't reset your profile or your saved details, as long as you use the same account.
Yes — update it directly from your profile screen rather than waiting for support to notice. If the field isn't editable from your side, send the correction through our support route and reference the exact detail that needs changing.
Use the support route listed inside your signed-in account and describe the specific mismatch — a payment chip, a saved detail, a login step — so the reply can check your actual account rather than just repeat this page back to you.
We don't sell your account details to third parties. Where a game or payment provider shown inside the lobby applies its own terms to a feature it supplies, that sits alongside this page rather than replacing how we handle your core account record.