Mobile / App
bea444 collects and uses your account data only for the purposes described in this policy — nothing hidden, nothing beyond what your account activity requires. Access to this platform and its associated data practices depends on your local law and eligible regions.
When you open an account with bea444, we collect the information you provide directly — your registered name, contact details, and the wallet identifiers you link for transactions, such as your Nagad or Rocket account number. We also collect session data generated by your device during normal use: page visits, game launches, and connection type. This technical data helps us keep the platform running consistently across the mobile browsers that most accounts use day to day. We do not sell your personal information to third parties. Where we share data — for example, with payment processors handling your Nagad or Rocket transfers — we share only what that processor needs to complete the transaction. We retain account records for as long as your account remains active and for a further period required by applicable rules in your eligible region. If you close your account, we will confirm in writing what records we are required to keep and for how long. Any data practice on this page applies subject to the laws of your local jurisdiction. Where local rules differ from this policy, local law takes precedence.
Your Nagad account reference is stored only to process and reconcile transactions linked to your bea444 account wallet.
Rocket transfer records are retained for reconciliation and are not shared beyond what the payment processor requires to complete your transaction.
Where bKash is used, the same data-minimisation rule applies: only the reference needed to match the deposit to your account is stored.
Device session logs — browser type, connection and page events — are kept for platform stability and are not used for third-party advertising profiling.
This policy covers data collected through the bea444 website and its account system. It does not extend to third-party services you reach from our pages, and it does not cover data handled independently by payment networks. The table below clarifies what falls inside and outside this policy's scope so you know exactly which rules govern each part of your experience.
Covered. Any data you submit during account creation, login or password recovery is governed by this policy and handled solely by bea444's account system.
Partially covered. bea444 records the transaction reference and amount. The payment network — Nagad, Rocket or bKash — operates under its own privacy terms for data it holds on its side.
Covered. Game launch events, session duration and in-session behaviour recorded by bea444's platform are subject to this policy. Studio-side analytics are governed by studio terms.
Not covered. Links to external sites, affiliate pages or third-party support tools operate outside this policy. Check those services' own privacy documents before submitting any data to them.
You have concrete actions available to you under this policy — not just abstract rights written in legal language. First, you can review the personal information held on your account by opening the account settings page after signing in; the details shown there reflect what bea444 currently holds against your profile. Second, if any detail is incorrect — a misspelled name, an outdated contact number or a stale wallet reference — you can update it directly from the same settings page. For fields that are locked after verification, contact our support channel and we will walk you through the correction process. Third, if you want to understand how a specific piece of your data is being used, you can raise a data enquiry through the support route described in the section below. We aim to acknowledge every data enquiry and respond with a clear explanation. Fourth, if you decide to close your account, submit a closure request through support and we will confirm which records we are required to retain and for what period under applicable regional rules.
Sign in and open account settings to see the personal data currently held on your profile — name, contact and linked wallet references are all visible there.
Update editable fields directly in account settings. For locked fields post-verification, reach our support team to request a correction and we will guide you through it.
Submit a data enquiry through our support route if you want a specific explanation of how a record is used. We will respond with a direct, written answer.
Contact support to initiate closure. We will confirm in writing which records we retain after closure and the reason, based on your eligible region's applicable rules.
If this policy raises a question you cannot answer from the account settings page, the routes below are the ones published on this site. Use the channel that suits your device — most questions from Bangladesh accounts come through mobile, so the live chat path tends to be the quickest for account-level queries. Availability of each channel depends on the hours displayed on the site at the time you reach out.
Open the chat icon at the bottom of any page while signed in. State that your question relates to privacy or data, and the agent will route it to the right team.
Send your data or privacy question to the support email address listed in your account's help section. Include your registered contact detail so we can verify and respond.
The help centre, accessible from the footer of every page, contains published policy articles. Search 'privacy' or 'data' to find answers to common questions before contacting the team.
Data handling at bea444 is built around keeping account records accurate, accessible to you, and limited to what the platform actually needs. Cookies are used for session continuity — so that signing in on your phone and returning later does not require you to re-enter your credentials every time. You can manage cookie preferences through your browser settings; blocking functional cookies may affect how your account session behaves across page loads. Account security relies on the login credentials you set during registration. We do not store your wallet PIN or your Nagad, Rocket or bKash account password — those stay with the respective payment network. Retention periods are tied to account status and regional requirements; we do not hold data longer than those rules require.
We use functional cookies to keep your session active across pages. Preference and analytics cookies can be adjusted in your browser without affecting your ability to sign in.
Your bea444 login credentials are hashed and never stored in plain text. Wallet credentials — Nagad, Rocket, bKash — remain with those networks and are never accessible to us.
Active account data is retained while your account is open. After closure, we retain only what applicable regional rules require and confirm that scope to you in writing.
When this policy changes in a material way, we post a notice in the account area. Check the account dashboard after any update notice to see what changed and from what date.
These are the questions we receive most often about how bea444 handles account data, wallet records and your rights under this policy. If your question is not here, the support routes listed above are the right next step.
We collect the name, contact detail and wallet reference you provide during registration — for example, your Nagad or Rocket account number. We also log session data like browser type and page events to keep the platform stable. We do not collect more than what your account activity requires.
We share data only where necessary. Payment processors handling Nagad, Rocket or bKash transfers receive only the reference needed to match your transaction. We do not sell personal data. Any third-party sharing is limited to what the specific function requires and is not used for advertising.
Sign in and open account settings. The details shown there — name, contact, linked wallet references — reflect what we currently hold. If a field looks incorrect, you can update it directly or contact support for locked post-verification fields.
Editable fields can be updated directly in account settings after signing in. For fields that are locked following identity verification, raise a request through live chat or email support. Provide your registered contact detail so we can locate and verify your record before making changes.
Submit a closure request through support. We will confirm in writing which records we are required to retain and for how long, based on applicable rules in your eligible region. Data not required by those rules is deleted following the closure process.
No. bea444's policy covers the transaction reference and amount we record on our side. Data held by Nagad or Rocket on their network is governed by each network's own privacy terms. We recommend reviewing those separately if you have questions about their data handling.