499deb Privacy Policy: How We Handle Your Information
499deb collects only the information needed to run your account, process transactions through bKash and Rocket, and keep your session secure. What we collect, why we collect it, and how you can act on it — that is what this policy covers. Access to our platform depends on your local law and eligible regions.
Account data handled with care
bKash and Rocket transaction records
Your right to review and correct
Contact route published below
POLICY POSTURE
What This Policy Covers and How We Apply It
We collect personal information in two main ways: information you give us directly when you open an account or verify your identity, and information generated automatically when you browse or play. Directly submitted information includes your name, contact details and the payment method you choose — whether that is bKash, Rocket or another supported rail. Automatically collected information covers device type, browser session data, pages visited and approximate location signals used to route you to the correct regional version of the site. We store this data on secured servers and do not sell or rent it to third parties for their own marketing. We share data only where required to process a transaction (for example, passing a bKash reference to confirm a deposit), to comply with a lawfully issued regulatory request, or to operate a service that you have explicitly used. Any third-party service that handles your data on our behalf is bound by a data-processing agreement that limits use to the task at hand. Retention periods vary by data type. Transaction records linked to bKash or Rocket are kept for as long as financial regulations in the applicable jurisdiction require. Session and browsing data is kept for a shorter operational period. You may request a summary of what we hold at any time through the contact route listed in the Support section of this page. Access to and use of our platform depends on your local law and eligible regions.
bKash transaction reference
Rocket deposit record
Account identity data
Session and device data
Regulatory retention period
POLICY BOUNDARIES
Where This Policy Applies and Where It Does Not
This policy applies to everything that happens inside your 499deb account and on the 499deb domain. Some areas it governs are clearly inside the scope of our direct control; others — such as the networks that carry your bKash or Rocket payment — are operated by third parties and fall under their own published terms. Understanding the boundary helps you know where to direct a question.
Account Access
Login sessions, saved preferences, wallet balance views and history records inside your 499deb account are fully within this policy. We control what is stored, how long it is kept and who can access it internally.
Payment Transactions
When you initiate a bKash or Rocket transfer, the transaction moves through that provider's network. We receive a confirmation reference but do not hold or process the underlying payment credentials ourselves. Their privacy terms govern that leg of the transfer.
Site Content and Cookies
Pages, game lobbies and promotional content served at 499deb are within scope. We use cookies and similar technologies to keep your session active and to understand which parts of the site you use. You can manage cookie preferences in your browser settings.
Third-Party Services
Links to external sites, game studios such as PG Soft or Spadegaming serving content inside our lobby, and any identity-verification partner each operate under their own privacy frameworks. We are not responsible for how those parties handle data on their own infrastructure.
ACTIONS YOU CAN TAKE
Your Practical Choices Under This Policy
You have specific, actionable choices about the information we hold on your account. You can ask us to show you what personal data we have recorded, and we will provide a readable summary through our support channel. If any detail is incorrect — your contact number, the email address linked to your bKash notifications, or any other account field — you can request a correction and we will update the record once we verify the change against the account. If you believe data is being held longer than necessary or for a purpose you did not agree to, you can raise that as a formal question and we will respond with the legal basis for the retention or remove the data where no such basis exists. Finally, if you want to close your account entirely, that request will result in the deletion of personal data we are not legally required to keep. Transaction records tied to financial obligations — bKash transfer logs, for example — are retained for the period required by applicable rules. All requests are handled through the support routes listed on this page.
Review Your Records
Submit a data-access request through our support channel and we will send a summary of the personal information stored against your account — contact details, transaction references and session history within the retention window.
Correct Account Details
If your registered email, phone number or payment-linked contact is wrong, open a support request with the correct detail and a confirmation of your identity. We update records after verification.
Question Data Retention
If you want to know why a specific data point is still held, ask us via the published support route. We will explain the legal or operational basis or delete the record if no valid basis applies.
Request Account Closure
A closure request triggers deletion of data we are not legally required to hold. bKash and Rocket transaction logs are retained for the period required by financial regulations; everything else is removed on confirmation.
CONTACT THIS POLICY
How to Reach Us About Privacy Questions
If you have a question about this policy, a request under it, or a concern about how your data has been handled, use the contact routes that are published on the 499deb website. We do not list unverified channels here. The routes below reflect what is visibly available on the site.
Live Support Chat
Open the chat widget available on the 499deb site to raise a privacy question directly. Give your registered account email so the agent can locate your records quickly.
Email Support
Send your privacy request or data-access query to the support email address published in the site's contact section. Include your account reference and the specific data or action you are requesting.
Account Help Centre
The Help Centre accessible from your signed-in account area contains policy-related articles and a form for submitting formal requests. This is the structured route for correction and deletion requests.
HOW WE PROTECT DATA
Data Handling, Cookies and Account Security
We apply access controls, encrypted connections and session-token management to protect the information in your account. Here is how each area works in practice.
Data Storage and Access
Personal data is stored on servers with restricted internal access. Only roles that require your data to process a request — such as verifying a bKash transaction reference — can reach it. We do not grant broad internal access to raw account records.
Cookies and Session Tracking
We use session cookies to keep you logged in and functional cookies to remember your lobby preferences. Analytics cookies help us understand page usage in aggregate. You can block non-essential cookies in your browser without losing account access.
Account Security Steps
Your account password is stored in hashed form — we cannot read it. Login activity is logged so you can spot unfamiliar sessions. If you notice access you did not authorise, contact support immediately through the published chat or email route.
Policy Updates and Notification
When this policy changes in a way that affects your rights or how we use your data, we post a notice on the site and update the revision date at the top of this page. Continued use of the account after the effective date constitutes acceptance.
COMMON POLICY QUESTIONS
Privacy Policy Questions We Hear Most Often
These are the questions we receive through support most often about how this policy works in practice. If your question is not here, use the contact routes in the Support section above.
What personal information does 499deb collect when I open an account?
We collect your name, email address, phone number and the payment method you register — for example, your bKash or Rocket mobile number. We also log your device type and browser session data automatically when you access the site.
Does 499deb share my data with anyone outside the platform?
We do not sell your data. We share it only where necessary: to confirm a bKash or Rocket transaction with the relevant payment provider, to comply with a lawfully issued regulatory request, or with contracted processors who handle specific tasks under strict data agreements.
How long does 499deb keep my account and transaction data?
Retention periods depend on data type. Transaction records — including bKash and Rocket deposit references — are held for as long as financial rules in the applicable jurisdiction require. Session and browsing data is kept for a shorter operational window. You can request specifics through our support channel.
Can I ask 499deb to delete my personal data?
Yes. Submit a deletion request through the published support route or the Help Centre form in your account. We delete data we are not legally required to keep. Transaction logs tied to bKash, Rocket or other financial records are retained for the period required by applicable rules.
How do I correct a wrong detail on my 499deb account?
Contact support via chat or email with the correct information and a confirmation of your identity. We update the record after we verify the change. If the detail affects your bKash or Rocket payment routing, mention that so we can flag it for payment-side review as well.
Does using 499deb on mobile change how my data is handled?
The same policy applies regardless of whether you access the site on a mobile browser or a desktop. Mobile sessions generate the same session and device data as desktop. We do not collect additional data — such as location coordinates or contacts — from a mobile device unless you explicitly grant that permission.