Mobile / Live
4499bd keeps one privacy policy for the whole site, and this page sets it out in plain English. Read it before you open an account so you know which details we hold, why we hold them, and how to ask us for a change.
Our privacy policy is written with Bangladesh members in mind, but it does not override the law where you live. Access to 4499bd depends on your local law and eligible regions, and the same applies to how we handle personal data: where a rule in your jurisdiction requires something different from what this page says, that rule takes priority. The payment chips below — Rocket, Upay and Bank Transfer — mark the routes we show in your account, and this policy applies to the account and transaction records tied to them rather than the wallet app on your phone. Each provider keeps its own privacy terms, and we cannot speak for how those apps store your details. What we do control is what happens inside your 4499bd account: the profile fields you type, the device and browser signals recorded when you sign in, and the transaction references attached to each funding step. If you are unsure whether you sit in an eligible region, check your local rules and ask our support desk before you fund the wallet. Nothing here is legal advice, and nothing promises a specific outcome in a specific country. We update this policy when our handling changes, and the version published on this page is the one that applies to your account.
Scope questions usually start with payments, so begin there. This policy governs your account itself — the profile you create, the device and browser details the site records, and the transaction references attached to each funding step you complete. It does not govern the Rocket, Upay or Bank Transfer app on your phone. When you send money from a wallet, that handover sits between you and the provider, and their terms apply from the moment you leave our screens. Third-party game content is similar: the lobby runs under our policy, but an external page or plug-in loading inside a game may follow its own rules. Messages you send to our support route are in scope too, because we keep them to answer you. Anything you do away from the site — a public forum post, a chat in a messaging app — sits outside this policy.
Your email, chosen password, wallet reference and any contact number you add sit here. We keep them so you can sign in, so the lobby shows your own balance, and so our support desk can find your record when you write in. You can ask us to correct these fields at any time.
Every funding step you begin through Rocket, Upay or Bank Transfer creates a reference in your account history. We store that reference, the amount and the status shown to you, so you can compare your own records with ours. The provider separately keeps its own version of the same transfer.
Titles in the lobby and the pages you browse on the site fall under this policy, including the pages you open from your mobile browser. If a game loads content from somewhere else, that part may follow the other party's terms, and we note that where it applies.
Rocket, Upay and Bank Transfer run their own apps, their own sign-in and their own privacy terms. Once you leave our screens to authorise a transfer, their handling rules apply. We cannot change, read or delete anything held inside those apps, and we will tell you to ask the provider instead.
You have practical choices under this policy, and you do not need a reason to use them. Ask us what we hold and we will show you the account fields and transaction references linked to your profile. Spot a wrong phone number or an old email? Tell us and we will correct the record, though some fields tied to a completed transfer stay as they are because the ledger has to match. If a policy sentence puzzles you, send the wording and we will explain what it means for your account. Closing your account is also your call: request it through our support route, and we will tell you what stays on file for record-keeping and what goes, along with how long the remaining record is kept. If you want someone else to speak for you on a policy matter, tell us first and we will set out what we need from you before we act on that request.
Write to our support route and ask for the account fields and transaction references we hold for your profile. We will set out what is stored, where it came from and why we keep it. You can make this request whenever you want, and you do not need to give a reason.
If your email, phone number or wallet reference is out of date, tell us and we will update the field. Details attached to a completed transfer usually stay as they were, because the transaction record has to match the reference your provider holds on their side.
Send us the sentence that is unclear and tell us which part of the site you were using. A short question with your account email attached lets our desk find the right answer instead of sending you back to this page to read it again.
You can ask us to close the account when you stop using it. Tell us which fields you want removed as well, and we will explain what has to remain for record-keeping, how long that remainder is stored and what happens to your wallet link afterwards.
Questions about this policy reach a person, not a queue that goes nowhere. Write to the address published on our contact page, or open the help section inside your signed-in account, and include your account email so the desk can pull up your record straight away. Tell us which page you were reading and what you expected to see — a sentence from this policy helps more than a general complaint. If your question is about a transfer, add the reference your Rocket, Upay or Bank Transfer app shows for that payment, because that is what we can match against our own record. We answer policy questions in the order they arrive, and we do not promise a fixed reply time, so keep the thread in one place rather than sending the same question twice. If your query is about the wallet app itself rather than your account here, the provider's own support desk is the right place to start.
The address published on our contact page is the main route for policy questions. Send your account email, the wording you want explained and, where relevant, the payment reference from your wallet app. One clear message with the details attached is easier for our desk to answer than several short ones.
Sign in and open the help section to find the published routes for account and wallet questions. Keep your session open while you write, so you can check your own profile fields and copy the exact reference shown against a transfer without leaving the page.
If you already have a thread open with our desk, reply there instead of starting a new one. The earlier messages stay attached, which means you will not have to repeat your account details or the reference you already sent in.
Data handling is the part of a privacy policy people skip, so here is the short version. We collect what an account needs: a sign-in email, the details you add yourself, device and browser signals recorded when you sign in, and the transaction references from each funding step. Cookies hold your session open and remember small choices such as display preferences, and you can clear or block them in your browser settings, though a few screens may then behave differently. Account security sits with both of us — our side is the sign-in flow you see on the account page, and your side is keeping your password to yourself and locking your device. Records linked to a transfer are kept for as long as the law and our own accounting need them; ordinary profile details go when you ask us to close the account. If you want a change made, contact our support route and say plainly which field or record you mean.
A sign-in email, the contact details you add, device and browser signals recorded at sign-in, and the transaction references from the funding steps you complete. Each one exists to run the account, show your own history and answer you when you write in about a payment.
Cookies hold your session open and remember small choices such as display preferences on mobile. You can clear or block them in your browser, and the site will still load, though a few screens may ask you to sign in again or reset a preference you had saved earlier.
Your password is yours alone, so keep it off shared devices and out of chat messages. Our side is the sign-in flow published on the account page. If something about a sign-in looks unfamiliar to you, contact our desk and we will look at the record together.
Profile details stay while your account is open and go when you ask us to close it. Transaction references tied to Rocket, Upay or Bank Transfer payments are kept for the period the law and our accounting require, and our desk will tell you which record that applies to.
These are the policy questions our desk sees most often, answered the way we would answer them on a support thread. If yours is not here, the contact routes above are the quickest way to reach us.
It describes how we handle data for the 4499bd site, but access and eligibility depend on your local law and eligible regions. Where your jurisdiction sets a stricter rule than this page, that rule applies to your account and we follow it.
A sign-in email, any contact details you add, device and browser signals recorded when you sign in, and the transaction references from funding steps you complete. You can ask our desk for the full set tied to your profile whenever you want it.
Yes for most profile fields, such as email, phone number and saved preferences. Transaction references have to stay while accounting and legal rules require them, and we will tell you exactly which record is being kept and for how long once you ask us to close the account.
No. Those apps run their own privacy terms and hold their own copy of each transfer. This policy applies to the account and transaction records on our side. Once you leave our screens to authorise a payment, ask the provider about anything held there.
Send the change from the email address you signed up with, or open the help section inside your account and write from there. Our desk updates the field after confirming the request came from you, and the old detail stops being used for contact.
Use the address published on our contact page, or start a message from the help section in your signed-in account. Include your account email and the exact sentence you want explained, and keep the thread in one place so nothing is repeated.