Mobile / Sports
558hh operates under a clear policy framework that sets out how your account, transactions, and personal data are handled. Access to this platform depends on your local law and the eligible regions we serve — read this page carefully before you proceed.
Our policy covers every registered account and every transaction processed through this platform, including those made via Upay and Bank Transfer. Where you choose to fund or withdraw using a local payment route, the same policy terms apply — there is no separate framework for different payment types. We do not distinguish between account tiers when it comes to your rights under this policy. Access to 558hh and the availability of any account feature depends on the laws of your local jurisdiction and the regions we are eligible to serve. If local law restricts your participation, those restrictions take effect regardless of how you access the platform — through a mobile browser, a saved link or any other route. We do not override or circumvent local legal obligations. Where policy terms are updated, we publish the revised version in this section and note the effective date. Continuing to use your account after a change is published is taken as acknowledgement of the updated terms. If you have questions about a specific clause, you can raise them through the policy contact route shown further down this page.
Transactions made via Upay fall within standard account policy. No separate legal terms apply to this payment route.
Bank Transfer activity is subject to the same policy scope as all other account transactions recorded in your wallet history.
Accessing your account on mobile does not change which policy terms apply. The same rules govern your session regardless of device.
Platform availability is determined by local law and eligible region status. We do not confirm eligibility on behalf of individual accounts.
Our legal policy covers four distinct areas of your account relationship with us: how you access your account, how transactions are recorded and managed, what content we host on this platform, and how third-party services connect to your experience. Each area is handled differently, and understanding those distinctions helps you raise the right kind of question through the right route. If something falls outside our published scope — for example, a wallet provider's own terms — you will need to contact that service directly.
Your login credentials, session behaviour and account status are all within our policy scope. Access eligibility depends on your local law and the eligible regions this platform serves.
Deposits and withdrawals processed through your account wallet — including Upay and Bank Transfer routes — are covered by our transaction policy. We record these in your account history.
Game content, promotional notices and policy pages published on this domain fall within our editorial scope. We are responsible for accuracy on pages we publish directly.
Payment providers, game studios and any external link operate under their own terms. Our policy does not extend to their platforms, data practices or service conditions.
You have several concrete actions available to you under this policy. First, you can review your account records — transaction history, session logs and any correspondence related to your account — by signing in and navigating to the account section. If any detail in your profile is incorrect, you can submit a correction request through the support route; we will acknowledge it and let you know what verification is needed before a change takes effect. Raising a question about how your data is handled is also a recognised action under this policy, not just a support enquiry. Submit it through the same route and mark it clearly as a policy question so it reaches the right team. If you need to make a formal request — for example, asking us to review a decision that affected your account access — that can also be submitted in writing through the contact path shown in the support section below. We aim to handle all policy correspondence within the timeframe published in our terms.
Sign in and open the account section to see your full transaction history, session activity and any notes attached to your account by our support team.
Submit a correction request through the support channel. We will confirm what identity or wallet verification is needed before updating any account detail.
Mark your message as a policy question when you contact support. This routes it to the team that handles data and legal correspondence rather than general account help.
If a decision affected your account access or wallet status, you can submit a written review request. We respond according to the timeframe in our published terms.
If this policy raises a question you cannot resolve by reading it, three contact routes are available. Use the one that fits the nature of your query — routine account questions and formal policy requests are handled through different queues, and labelling your message clearly helps us respond to the right one first.
Open the chat widget from any page while signed in. Suitable for account access questions, transaction status and general policy clarifications.
Send policy and data-related questions by email. Mark the subject line clearly — for example, 'Policy Question' or 'Account Review Request' — so it reaches the correct team.
Use the in-account message centre after signing in to submit documented requests, attach screenshots or follow up on a previous policy correspondence thread.
Our approach to this policy area is built around four practices you can verify through your account and through the published documentation on this domain. We do not make claims about security or data handling that go beyond what our published terms describe.
We retain account data for the period specified in our terms. After that period, data is handled according to the deletion or archiving process described in the privacy section of our published policy.
We use cookies to maintain your signed-in session and to record basic navigation. Cookie preferences can be reviewed and adjusted through the settings prompt shown when you first visit.
Your account is protected through the verification steps set up during registration. If you suspect unauthorised access, contact support immediately through live chat or email and we will guide you through the account review process.
When we update this policy, the revised version appears here with the effective date noted. You can also request a summary of recent changes through the email or in-account messaging route.
These questions come up regularly when account holders read through our policy. If yours is not covered here, send it through the support route and mark it as a policy question.
Yes. Every transaction recorded in your account wallet — including those processed via Upay or Bank Transfer — falls within the same policy scope. There is no separate set of terms for different payment routes.
Access depends on your local law and whether your region is eligible. We do not override local legal restrictions. If your jurisdiction limits or prohibits participation, those restrictions apply regardless of how you reach the platform.
Sign in and open the account section to view your transaction history and session records. For a broader data request — such as what we store beyond visible records — submit a written request through the email or in-account messaging route.
Contact support and mark your message as a correction request. We will confirm what verification is needed — for example, identity or wallet confirmation — before making any change to your account profile.
The revised version is published here with the effective date shown. Continuing to use your account after the updated policy is live is taken as acknowledgement of the changes. You can also request a summary of recent changes via email.
Yes. You can submit a written review request through the email support route or the in-account message centre. Clearly describe the decision you are questioning, and we will handle it according to the timeframe set out in our published terms.