Live / Mobile
At 458h, we keep this policy straightforward — you should know exactly what data we collect when you open an account, how we use it, and what choices you have. Access to our platform depends on your local law and eligible regions.
When you register an account with 458h, we collect the information you provide during sign-up — your name, email address, contact details and the payment methods you connect to your wallet. If you use bKash, Upay or Bank Transfer to fund your account, the transaction reference and wallet identifier associated with that payment are logged against your account record. We do not store full payment credentials on our servers; the payment processor handles those directly. We collect browsing and session data — pages visited, device type, browser version and approximate region — to keep the account session stable and to detect unusual activity. This data is not sold to third parties. We may share limited information with payment processors, fraud prevention services and regulators where our obligations require it. Retention periods vary by data category: account identity records are held while your account is active and for a period after closure as required by applicable rules; session logs are held for a shorter period. All use of this platform is subject to your local law and the eligible regions we serve. If you are unsure whether access is permitted in your area, check local regulations before proceeding.
This policy applies specifically to data collected through the 458h website and account system. It covers account creation, login sessions, payment wallet actions and support interactions. It does not extend to third-party services you reach through links on our site, and it does not govern data held by external payment processors operating independently. Understanding the scope helps you know exactly who is responsible for which part of your data.
Data collected when you open, log into or update your 458h account falls under this policy. This includes your registration details, session tokens and any identity verification steps shown in your account settings.
When you initiate a bKash, Upay or Bank Transfer transaction, the reference number and amount are recorded in your account wallet history. The payment processor's own privacy terms govern how they handle your wallet credentials on their side.
Pages you visit on 458h, cookie preferences you set and game lobby interactions are logged as session data. You can adjust cookie settings through your browser; restricting certain cookies may affect how your account session behaves.
Links to external platforms, game studio pages or support tools outside the 458h domain are not covered by this policy. Check the privacy terms of those services independently before sharing any personal details with them.
You have concrete options available to you regarding the data we hold. Reviewing your account page shows the profile information currently on record — name, contact details and linked payment methods. If anything looks incorrect, you can update most fields directly from your account settings without contacting support. For records you cannot edit yourself, such as historical transaction logs or closed-account data, you can raise a formal data request through our support route and we will respond according to the applicable process. Where you believe data is being held longer than necessary or processed incorrectly, you can submit a written query; we will review the record and reply with an explanation or a correction. Withdrawing consent for non-essential data processing — such as marketing communications — is available through the notification settings in your account. These actions are available to you regardless of which payment method your wallet uses, whether bKash, Upay or Bank Transfer.
Open your account profile page to see the personal details we currently hold. The information shown there reflects what was submitted at registration and any updates you have made since.
Most contact and profile fields can be edited directly in account settings. For fields that are locked — such as identity verification data — use the support contact route to request a correction.
If you want to know why specific data is held, how long it will be retained or who it has been shared with, send a written request through our published support route and we will respond with the relevant details.
For any privacy matter that cannot be resolved through account settings alone, our support team is the correct contact point. Use the live chat or email route listed on the support page to open a case.
If you have a privacy question that the policy text does not answer, or if you need to raise a data request, these are the contact routes available through the 458h site. We do not publish estimated response times here because those can change; check the support page for the current status.
Open the live chat widget visible on the 458h site to raise a privacy or account data question in real time. This route is suitable for straightforward queries about what data your account holds.
For formal data requests — corrections, deletions or access inquiries — send a written message through the email address published on the contact page. Include your account reference so we can locate the correct record.
The help section within your signed-in account area contains self-service options for updating profile details and adjusting notification preferences without needing to contact the support team directly.
Here is how 458h approaches the practical side of data protection — what we do with the information we collect, how long we keep it, and who you contact if something needs to change. These are the operational realities behind the policy text.
Account identity data is retained while your account remains active and for a defined period after closure, as required by applicable rules. Session logs and browsing data are held for shorter periods. The exact retention schedule is available on request through our support route.
We use cookies to maintain your login session, remember preferences and measure how pages are used. You can manage cookie settings through your browser. Blocking functional cookies may cause your account session to behave differently or require you to log in again.
Account access is protected by the login credentials you set at registration. We do not ask for your password by email or chat. If you receive a message requesting your credentials, treat it as suspicious and contact support through the published route immediately.
When this policy changes, the updated version is published on this page with a revised date. Continuing to use your account after a policy update indicates your acknowledgement of the revised terms. Check this page if you want to confirm the current version.
These are the questions we see most often about how 458h handles account data, cookies and your rights. If yours is not here, use the live chat or email route to ask directly.
At registration, we collect your name, email address and contact details. When you add a payment method — bKash, Upay or Bank Transfer — a transaction reference is recorded in your wallet history. Session and device data is also logged to keep your account stable.
We share limited data with payment processors, fraud prevention services and regulators where our obligations require it. We do not sell your personal data. Third-party services linked from our site operate under their own privacy terms, which we do not control.
Open your account profile page when signed in — the details shown there reflect what we currently hold. For transaction records, check your wallet history. For data we hold that is not visible in the account area, send a request through the published email support route.
Yes. Most profile fields can be edited directly in account settings. For locked fields or historical records, submit a written request through our email support route. We will review the record and respond with either a correction or an explanation of why the data must be retained.
Account identity records are held for a defined period after closure as required by applicable rules. Session and browsing logs are retained for shorter periods. If you want the specific retention schedule for your data category, contact us through the published support route.
When you transact via bKash, Upay or Bank Transfer, the transaction reference and amount are logged in your 458h wallet history. The payment processor handles your wallet credentials on their side under their own privacy terms. We do not store full payment credentials on our servers.