Mobile / Sports
dn520 keeps a plain record of what we collect when you open an account, deposit through bKash, Nagad or Rocket, or browse slot rooms like Spinner Star and Crash SparkBurst. This page sets out what we store, why, and how long we keep it — availability of any feature depends on your local law and eligible region.
This policy applies to every account you open with dn520 and to the data that moves through it — your registration details, device and browser data, and the records tied to transactions you initiate through bKash, Nagad or Rocket. We do not treat payment confirmations as public data; they sit inside your account history and are visible only to you and to the support team handling a specific query. Because online access and payment processing in Bangladesh sit under local law, what we can store, for how long, and what we can share with a payment partner depends on the rules in force in your region at the time you use the account. We update this page when our data practices change, not on a fixed schedule, so the version you read on the account page is the one that applies to you. If you access dn520 from a shared device or a public connection, the browser you use may retain session data outside our control; clearing that data is a device-level action, not something we manage on your behalf. Where we show payment chips such as bKash, Nagad, Rocket or Upay in your account wallet, those labels tell you which transaction rail a record belongs to — they are not an endorsement of availability outside what local law and eligible regions permit. Read the account page itself for the live state of your data and payment history, since this page describes our general approach rather than a line-by-line account statement.
This policy covers what happens inside dn520 once you open an account — the details you enter at sign-up, the device data tied to your session, and the records created when you move money through bKash, Nagad or Rocket. It does not describe how a payment provider or a game studio such as Habanero or Pragmatic Play handles data on its own systems once a transaction or a game round leaves our platform; those providers carry their own data practices. Account access, in-session activity on titles like Blackjack TableChamp or Football Punter Hub, and the support messages you send us all sit inside scope. What a third-party wallet app does with your phone number, or what a browser extension stores locally, sits outside it. Read this section alongside the account page if you want to see exactly which record belongs where before raising a question with support.
Your registration details, login activity and the device you use to reach dn520 fall inside this policy. We record sign-in attempts and basic session data to keep your account wallet secure, and that record sits with your account rather than anywhere public.
Deposits and withdrawals you make through bKash, Nagad, Rocket or Upay generate a record tied to your account wallet, not to your public profile. We hold these records only to confirm a transaction and to answer a support query you raise about it.
Browsing a slot room like Spinner Star or Crash SparkBurst, or opening a live table such as Blackjack TableChamp, creates session data about the page you viewed — not a personal profile of your play. That data helps the lobby load correctly on your device.
A payment provider, a game studio such as Habanero or JDB, or a browser you use to reach dn520 each keep their own records once a transaction or a game round passes through their system; this policy covers our side only.
Checking your own record doesn't need a formal request every time. Your account page already shows your registration details, your linked bKash, Nagad or Rocket entries and a history of the transactions tied to your wallet — that's the fastest way to see what we hold. If something looks wrong, a mismatched name or an old phone number, you can correct it from the same account settings screen rather than waiting on a reply. For anything the account page doesn't show directly, such as a question about how long we keep a closed-account record, raise it through support with your account reference ready. We answer account-data questions in the order they reach us through the published routes below, and we may ask you to confirm identity details already on file before we change anything, since that step protects the wallet attached to your name.
Open your account page to see the registration details, device sessions and bKash, Nagad or Rocket entries we hold for you. This is the quickest check before you raise anything formally, since most account-data questions are answered by what's already visible there.
If your name, phone number or wallet entry needs an update, the account settings screen is where you make that change yourself. Keeping these fields accurate also keeps your bKash, Nagad or Rocket transactions matching your profile without a delay on your end.
Not every situation fits the account page — closed-account records or an old support thread, for example. Send the detail through the published support route with your account reference, and we treat it as a direct data question, not a general feedback message.
If your first message needs a reply tied specifically to data held on your account, say so when you contact support so the thread doesn't get filed as a general query. We confirm identity details already on file before changing anything on your record.
Questions about this policy move through the same support paths as any account question — we don't run a separate line just for data requests. Start from the support route listed on your account page; it's built to carry your account reference straight into the message so our team isn't asking you to repeat details you've already typed once. If you'd rather read before writing, the published help page linked from the account and footer area walks through common privacy and wallet questions, including what a bKash, Nagad or Rocket entry on your statement actually means. We don't publish a fixed response window for this page, since how long a reply takes depends on the type of record involved and whether we need to confirm identity details first. Keep your account reference and the rough date of the transaction or session you're asking about ready — that's the detail that moves a privacy question along fastest.
The support option inside your account carries your account reference automatically, so a privacy question starts with the right record already attached. Use it for anything about a wallet entry, a bKash, Nagad or Rocket transaction, or a session you don't recognise.
Before writing in, the help page linked from the footer area covers common privacy and account questions — what a payment chip label means, how a closed account is treated, and how to update a detail yourself without waiting on a reply.
When a request touches your personal record, we ask for identity details already on file before changing anything. This step applies whether you reach us through the account support route or the help page, and it protects the wallet tied to your name.
Keeping your record straight starts with where it sits, not with a promise we can't measure. Your registration details and transaction history tied to bKash, Nagad or Rocket stay inside the account system rather than on a page anyone outside your login can read. Cookies on dn520 mostly do ordinary work — keeping you signed in across a session, remembering that you were midway through a lobby page like Football Punter Hub, or carrying your language setting between visits. We don't use them to build a public profile of your activity. Account security on your side starts with the password and any verification step shown at login; we can't control what happens on a device you've lost or lent out, so treat your own login discipline as part of this policy, not separate from it. Retention follows the record type: a closed account doesn't disappear instantly, since some entries are kept long enough to answer a later support question about a transaction.
Your account details and transaction records tied to bKash, Nagad or Rocket are stored inside the account system behind your login, not published anywhere a visitor browsing the lobby could see. Only you and the support team handling a specific question can view them.
Cookies keep your session active while you move between a slot room like Spinner Star and a live table, and they remember basic preferences such as language. We don't use cookie data to build a profile we sell or share outside the account system.
Your password and any verification step at login are the first line of protection for the wallet attached to your account. If you access dn520 on a shared device, sign out before you leave — that step matters more than anything we do server-side.
A closed account or a finished transaction doesn't drop out of our system the moment you stop using it; some entries are kept long enough to answer a later support question. How long depends on the record type and the law in your region.
Here are the questions we hear most often about how dn520 handles account and payment data. If your question isn't answered here, the support route on your account page is still the fastest way to get a direct answer tied to your own record, not a general one pulled from this page.
We keep a record of the transaction itself — the amount type, the time and the wallet rail used — rather than your full payment credentials, which stay with the payment provider you used. Your account page shows the transaction record tied to your wallet.
Yes — most of it is already visible on your account page: registration details, device sessions and your transaction history. For anything that page doesn't show directly, raise it through the support route with your account reference so we can look it up for you.
Open the account settings screen and update the field yourself where that's available; it's quicker than waiting for a reply. If the field is locked for a security reason, use the support route and include your account reference so the change is matched to the right record.
Yes. What we can store, how long we keep it and what we can share depends on the local law and eligible regions tied to where you're accessing the account from, so the practical answer can differ by region even though the page stays the same.
A closed or inactive account isn't deleted the moment you stop logging in; some entries stay on file long enough to answer a later question about a past transaction. How long depends on the record type and the rules that apply to your region.
Start with the support route shown on your account page — it already carries your account reference so the team can match the question to your record. The help page linked from the footer area also covers common privacy questions before you write in.