This policy explains how babu555 collects, uses and protects the personal information you share when you open an account or use your wallet — including transactions through Nagad, Rocket or Upay. Access to this platform and the scope of this policy depend on your local law and eligible region.
Account data handled with care
Nagad, Rocket, Upay payment context covered
Your rights are clearly listed
Contact path available any time
POLICY SCOPE DETAILS
What Information babu555 Holds and How We Use It
When you create an account, we collect the details you enter directly: your name, contact information, login credentials and any payment references you add — such as a Nagad wallet number, Rocket mobile banking ID or Upay account identifier. We use this information to operate your account, process transactions and respond to support requests. We do not sell your personal data to third parties, and we do not share it beyond what is needed to deliver the services you have requested. Cookies and similar tracking tools are used on this site to keep your session active, remember your login state and measure how different parts of the lobby are used. You can control cookie preferences through your browser settings at any time, though disabling certain cookies may affect how your account session behaves. We retain your account data for as long as your account remains active and for a period after closure as required by applicable record-keeping obligations in eligible jurisdictions. If you have a question about a specific data field we hold — for example, a transaction reference tied to a Rocket or Nagad payment — you can raise it directly through the support contact listed in this policy. Use of this platform and application of this policy depend on your local law and the region from which you access the service.
Nagad
Nagad wallet identifiers are collected only when you add them to your account. They are used to match your deposit or withdrawal request and are not shared beyond the transaction process.
Rocket
If you link a Rocket mobile banking number to your account, that reference is stored against your wallet record. You can request to review or update this detail through account settings or via support.
Upay
Upay account details you provide are held in your payment profile. We apply the same data-handling standards to Upay references as to any other payment method in your account wallet.
INSIDE VS OUTSIDE POLICY
Where This Policy Applies and What It Does Not Cover
This policy covers data we collect and process directly through babu555 — on this site and through your registered account. It does not extend to third-party services that operate independently, even where links or integrations exist. Understanding the boundary helps you know which questions to raise with us and which to direct elsewhere.
Account Access
Any information you enter during registration, login or account verification falls inside this policy. This includes your email, contact number and any identity details provided at the account verification step.
Transactions
Payment references associated with Nagad, Rocket or Upay that you store in your account wallet are covered. The payment provider's own data practices are governed by their separate policies, not ours.
Site Content
Browsing data collected as you move through the lobby, game pages and account sections is within scope. We use this to maintain session continuity and understand which parts of the site you interact with.
Third-Party Services
If you follow a link away from babu555 to an external site or payment network, the data practices of that third party are outside our policy. We are not responsible for how those services handle your information.
YOUR ACCOUNT RIGHTS
Practical Steps You Can Take Under This Policy
You have a set of practical choices available to you regarding the personal information babu555 holds. These are not abstract entitlements — each one maps to a real action you can take through your account or by contacting support. If you want to review the data on your account, log in and navigate to your account settings page, where your stored contact details, linked payment references and session preferences are displayed. To correct information that is out of date or inaccurate — for example, an old contact number or a Nagad wallet reference that has changed — update it directly in account settings or raise a correction request with support. If you have a question about how a specific piece of data is being used, or want to understand what records we hold against your account, submit a query through the support contact route listed in this policy. We aim to respond to data queries in the order they are received.
Review Your Records
Log in and open account settings to see the contact details, payment references and preferences currently stored against your account.
Correct Account Details
Update an outdated contact number, email or linked wallet reference directly in account settings, or ask support to apply a correction on your behalf.
Raise a Data Question
If you are unsure why a specific data point is held or how it is used, contact support with your account reference. We will explain what we hold and why.
Request Support
For anything this policy does not clearly answer, the support team is the right contact. Use the email or live chat route listed in the support section below.
PRIVACY CONTACT PATHS
How to Reach Us About This Policy
If you have a specific question about your data or want to act on any of the rights described in this policy, these are the contact paths available to you. Have your account reference ready so we can locate your record quickly.
Email Support
Send a detailed message to our support email with your account reference and the specific data question or correction you need. We handle privacy queries through the same support team that manages account help.
Live Chat
Open live chat from within your logged-in account to raise a privacy question in real time. This route is useful for straightforward queries about what data is stored or how a payment reference is used.
Account Settings
Many data actions — reviewing stored details, updating contact information or adjusting cookie preferences — can be handled directly in account settings without contacting support at all.
DATA HANDLING STANDARDS
How We Handle Data, Cookies and Account Security
The way babu555 manages personal data is grounded in a few consistent practices. We apply access controls so that your information is only reachable by the systems and staff who need it to deliver the service. Cookie data is session-scoped where possible, and persistent cookies are limited to the functions that genuinely require them — like keeping your login state active across pages. Data retention follows the obligations set by applicable rules in eligible jurisdictions, not an open-ended storage policy.
Data Storage
Personal data is stored on systems with access controls in place. Your account record — including any linked Nagad, Rocket or Upay reference — is not accessible beyond what is needed to run your account and process your requests.
Cookies
We use cookies to keep your session active, remember your account state and understand how the lobby is used. You can adjust cookie settings in your browser at any time; doing so may change how some account features behave.
Retention Period
We keep your account data while the account is active and for a defined period after closure, in line with record-keeping requirements in eligible jurisdictions. Once that period ends, the data is removed from active systems.
Policy Changes
If this policy changes in a material way, we will update the version shown on this page. Continuing to use your account after a policy update means you have seen the revised terms. You can request clarification on any change through support.
POLICY QUESTIONS ANSWERED
Frequently Asked Questions About This Privacy Policy
These are the questions we hear most often from account holders about how their data is handled, what rights they have and how to act on them. If your question is not covered here, the support contact paths in this policy are the right place to ask.
What personal data does babu555 collect when I open an account?
We collect the details you enter at registration — name, contact information and login credentials. When you add a payment method like Nagad or Rocket, that wallet reference is also stored in your account record. We only collect what is needed to operate your account and process your transactions.
Is my Nagad or Rocket wallet number shared with anyone outside babu555?
Your payment references are used to match your transaction requests and are not sold or shared beyond what is needed to process the payment you initiate. The payment provider itself handles the transaction on their own platform under their own data terms.
How do I find out what data babu555 holds on my account?
Log in and open your account settings page — your stored contact details and linked payment references are visible there. For a fuller picture of what is held in our systems, submit a data query through the support email or live chat with your account reference included.
Can I correct or update information babu555 holds about me?
Yes. Contact details and linked payment references can be updated directly in account settings. If a correction needs to be applied to a field you cannot edit yourself, raise it with the support team and include your account reference so we can locate the right record.
How long does babu555 keep my account data after I close my account?
We retain your account record for a defined period after closure, in line with the record-keeping requirements that apply in eligible jurisdictions. The exact period depends on the applicable rules for your region. After that window, the data is removed from active systems.
Does this policy apply to me if I am in Bangladesh?
The policy covers all accounts created on this platform. Whether you can access the platform at all depends on your local law and eligible region. We recommend checking your local legal position before opening or using an account. Access is not available in all regions.