Sports / Live
4514y handles your information with care — this page explains exactly what data we collect when you use the platform, how it is stored, and the choices you have over it. Access to this platform and its features depends on your local law and eligible regions.
When you open an account, we collect the details you enter during registration — your name, contact information, and the credentials you set. When you make a deposit or withdrawal through Nagad or Rocket, we record the transaction reference and wallet identifier associated with that action. We do not store your full mobile wallet PIN or password at any point. As you navigate the platform on mobile, we collect device and session data — browser type, screen resolution, session timestamps — to keep your experience consistent across visits. This data helps us detect unusual activity on your account and respond appropriately. We also collect records of your account actions: login events, wallet top-ups via Nagad, Rocket or bKash, game session starts and any support requests you raise. These records are kept for the period required by our operational and compliance obligations. We do not sell your personal data to third parties. Where we share data with service partners, we do so only to the extent needed to operate the platform and process your transactions. You can ask to review what we hold about you at any time by contacting support through the channels listed on this page.
This policy covers data we collect and process directly through the 4514y platform. It does not extend to third-party services you may reach from our pages, including external payment processors or studio game environments. Understanding what falls inside and outside this policy helps you know who to contact when a data question arises.
Data you enter when logging in or managing your account — email, password hash, session tokens — falls fully within this policy. We control how it is stored and for how long.
Records of deposits and withdrawals made via Nagad, Rocket or bKash are covered here. We hold the transaction reference and timestamp; your wallet provider holds its own records under its own policy.
Session data generated while you browse the lobby or open a game is covered. However, game engines run by studio partners operate under their own data environments — we do not control data held inside those environments.
Links to external sites, payment provider portals or studio landing pages are outside the scope of this policy. Once you leave the 4514y domain, the destination site's own privacy terms apply.
You have several concrete actions available to you regarding the data we hold. The starting point for most requests is your account settings page, where you can review and correct the contact details and preferences recorded against your profile. If something looks wrong — an address, a linked mobile number, a notification setting — you can update it directly from that screen without contacting support. For anything that requires our involvement, the support routes listed on this page are the right path. We aim to acknowledge data queries raised through our published channels within a reasonable time, though we do not state a fixed response window here as it can vary. Requests to understand what data we hold, to correct inaccurate records, or to ask how your Nagad or Rocket transaction history is stored are all handled through the same support route. Where your request involves data held by a third-party partner, we will direct you to the appropriate contact at that partner.
Open your account settings to see the personal details currently on file. This includes your registered mobile number, email address and notification preferences — all editable from the same screen.
If any stored information is inaccurate, update it directly in your account settings. For fields that cannot be self-edited, raise a correction request through the support channel listed below.
Questions about what we store, why we store it, or how long we keep it can be sent to our support team. Describe the specific record or data type you are asking about so we can respond clearly.
If your query relates to a Nagad or Rocket transaction reference held in your account history, include the transaction date and wallet type when you contact support — it speeds up the lookup.
If you have a question about this policy, want to review what data we hold, or need to raise a correction, the routes below are the ones we actively monitor. Use the channel that works best for you — we keep these consistent so you are not chasing an answer across different touchpoints.
The live chat widget in your account dashboard connects you directly to the support team. Use it to ask about data records, account details or wallet transaction history stored against your profile.
Send your privacy or data query to the support email address published in your account help section. Include your registered mobile number and a brief description of your request so we can locate the right record.
The help centre inside your account lists common privacy questions and account-data actions. Check there first — many requests around notification settings, linked wallets or stored details can be resolved without waiting for a reply.
Understanding the mechanics behind how we keep your data secure is part of what we owe you as a platform. These four areas cover the practical reality of how your information moves through our systems.
We use session cookies to keep you logged in across pages and to remember your account preferences. You can manage cookie settings through your browser. Disabling certain cookies may affect how the mobile account page loads and keeps your session active.
Your login credentials are stored in hashed form — we do not hold your plain-text password. If you notice any unexpected login activity, use the account security section to change your password immediately and contact support via live chat.
We keep account and transaction records — including Nagad and Rocket deposit references — for the period our operational obligations require. When a record is no longer needed, it is removed from active storage according to our internal schedule.
When this policy is updated, we publish the revised version on this page. Continued use of your account after an update is posted constitutes acknowledgement of the revised terms. If a change materially affects how we handle your data, we will notify you through your account.
These are the questions that come up most often when members want to understand how their data is handled. Each answer points to the specific action or account path that applies.
We collect the details you enter at registration — name, email address, mobile number — along with the device and session data generated each time you log in. Wallet identifiers from Nagad, Rocket or bKash are recorded when you transact.
Yes. Start by opening your account settings page, where profile and contact details are visible. For a fuller record of transaction references or session history, send a request through live chat or the support email address listed in your account help section.
We share data only with service partners who need it to operate the platform — for example, payment processors handling your Nagad or Rocket transactions. We do not sell your personal data. Third-party partners handle their own data under their own policies.
Records are kept for the period our operational and compliance obligations require. The exact duration depends on the type of record — transaction references, login history and support conversations each follow their own retention schedule, which we review internally.
Many fields — contact number, email, notification settings — can be edited directly in account settings. If a field is not self-editable, raise a correction request through live chat or email support. Include which field needs updating and the correct value.
This policy applies to your account and the data we process when you use the platform. Access to the platform itself depends on your local law and eligible regions — if access is restricted in your area, this policy still governs any data already held.