Live / Casino
899db explains how we handle the data behind your account, your login sessions and the device you use to reach the lobby. What applies to you depends on your local law and the region you're playing from, so read this alongside the account terms before you continue.
This policy sits alongside the account terms you accept when you open an 899db account, and it works the same way whether you reach us through a mobile browser or a saved home-screen shortcut. We collect the account details you give us at signup, the device and browser data tied to each login, and the records that come from using the lobby — switching between game categories, raising a support question, or completing a payment through Upay or Bank Transfer. None of this is sold on; it exists to keep your account continuous across sessions, so you can close the app on your phone and pick up the same account later on a desktop browser without starting over. What we're allowed to hold, for how long, and what you can ask us to change depends on your local law and the region you're accessing 899db from — this page describes our general approach rather than a fixed legal position for every market. Where a payment route like Upay or Bank Transfer is involved, the transaction record sits against your account the same way a login record does, and it's visible to you through your account history rather than shared outward. If something here reads differently from how your account actually behaves, the account settings page and our support route take priority over this summary.
This policy draws a line between what sits inside your 899db account and what sits outside it. Account access, payment records tied to Upay or Bank Transfer, the lobby itself and anything linked to a third-party service each get treated a little differently, and knowing where one ends and the next begins helps explain why a question about a login gets answered differently from a question about a payment status.
This covers the login details, device fingerprints and session data tied to opening your 899db account on a phone browser or desktop, including how we recognise a returning login so you don't have to rebuild your account each time you switch devices.
Transaction records from Upay or Bank Transfer sit inside this scope once they're linked to your account history, covering the entry and status of a payment rather than the card or bank credentials you used to set the method up.
Browsing a game category — slots, live casino tables, or a sportsbook market around cricket — sits inside scope as navigation data, while outcomes and mechanics of a specific title like Crash ShockWave stay with the game itself and aren't account data.
Links that take you away from 899db, such as a payment provider's own confirmation screen for Upay or Bank Transfer, fall outside this policy once you leave our pages, and the external service's own data terms apply from that point on.
Your account on 899db comes with a handful of practical options once you're signed in. You can check the personal details tied to your account, ask us to correct something that's out of date, and raise a question about how a particular record — a login, a device change, a payment through Upay or Bank Transfer — got stored. We don't ask you to file a formal request; most of this starts from the account page itself or a short message through our support route. Where local law in your region sets out a stronger right than what's described here, that stronger right applies, and we'll work from your account settings page and support thread rather than a generic form. The fastest path is usually the one visible inside your own account rather than a separate channel.
Open your account settings to see the core details we hold against your profile, including device and login history, without needing to raise a separate request first.
If something on your account is wrong — a detail from signup or a device no longer in use — tell us through the support route and we'll update what's incorrect.
Ask about a specific record, like why a payment through Upay or Bank Transfer shows a particular status, and we'll answer against that record rather than a general statement.
When a question needs more than a quick check, our support route is where it goes next, and we work from the account details you already have on file.
A question about your data shouldn't need a separate account; it starts from the same place your account already lives. The account page carries the paths below for anything tied to this policy, whether that's a login record, a device change, or a payment reference from Upay or Bank Transfer.
The account page carries a direct line to our support team for a question about your data, your login history or a payment linked through Upay or Bank Transfer. It's the route we point you to first for anything on this policy.
If you'd rather write things out, our support route accepts a written message so you can describe exactly which account record or device session you're asking about, and keep a copy of the exchange for your own reference.
Before reaching out, the account settings page is worth a look — a lot of what you'd ask support about, like a stored device or a Upay reference, is already visible there without waiting on a reply.
Device continuity and account security sit close together in how 899db treats your data. We keep enough session data to recognise a returning login across a phone and a desktop browser, we hold payment records from Upay or Bank Transfer against your account history rather than anywhere external, and we keep account records on file only as long as your account stays active or your local law requires. Any change to a stored detail starts from your account page or our support route rather than a separate process.
Login sessions are tied to the device and browser you use, so a sign-in from an unfamiliar browser is treated differently from your usual phone session. We don't publish the exact mechanics, but device continuity sits at the centre of how we recognise your account.
We use session data to keep you logged in between visits on the same browser, including a saved mobile session so reopening the site doesn't ask you to sign in again right away. Clearing your browser data resets that session.
Account and transaction records, including those tied to Upay or Bank Transfer, stay on file for as long as your account is active and for whatever period local law in your region requires afterward, rather than a fixed length we set ourselves.
If a detail on your account needs correcting or a record needs explaining, the request starts from your account page or our support route, not a separate form, and we'll confirm what we can update once we've checked the details.
A short set of answers for the questions we hear most about data on 899db — covering sharing, devices, payments and who to ask when something looks off.
We only pass account data to a payment route like Upay or Bank Transfer when you ask for a transaction, and to our own support team when you raise a question. We don't sell account records, and anything shared stays limited to what the request needs.
Your account record stays the same across devices, so logging in from a desktop browser after using the mobile site doesn't create a separate profile. The session data we hold just updates to reflect the device and browser you're using at that moment.
Yes — your account settings page shows the core details tied to your profile, and you can ask through our support route if something looks missing or outdated. What you're entitled to see can depend on your local law and region.
We keep the record of the transaction itself — status, amount reference and the account it's linked to — rather than storing your banking credentials. That record sits in your account history so you can check it without contacting support first.
It covers the navigation data from opening those game categories — which lobby section you visited and when — but not game mechanics or outcomes, which sit with the game itself rather than your account record.
Start with our support route from your account page; that's the fastest path for a question about a specific record. If local law in your region gives you a stronger right, we'll work from that when we answer.