Sports / Slots
558hk collects only the account and transaction data we need to run your wallet, process payments through Nagad, Upay and Bank Transfer, and keep your session secure. This policy tells you exactly what we hold, how long we keep it, and what you can do about it — access, correction and removal requests included.
When you open an account with us, we collect the details you enter during registration — your name, contact information and the payment identifiers linked to your wallet (such as your Nagad mobile number or the Bank Transfer account reference you provide). We also record transactional metadata: deposit timestamps, session identifiers and the device type used at login. We do not collect payment credentials beyond what is necessary to route a transaction; card numbers and mobile wallet PINs are never stored on our servers. Cookies and similar session tokens help us keep you logged in across a mobile browsing session without asking you to re-authenticate on every page. You can clear these through your browser settings at any time, though doing so will end your active session. We retain account records for as long as your account remains open and for a further period required by the applicable rules of your eligible region. If you close your account, we will remove identifiable fields from active systems within a reasonable period, keeping only the non-identifiable summary data that operational records require. Access to and availability of our service depends on your local law and the eligible regions we serve — nothing in this policy constitutes a legal claim of availability in any jurisdiction.
This policy covers every data point 558hk collects directly through your account, your browser session and the transactions you initiate on this site. It does not extend to third-party services you reach from a link on our pages, to game studios whose titles appear in the lobby, or to payment processors who operate under their own privacy frameworks. Understanding the boundary helps you know who to contact when a question arises.
Login credentials, session tokens and the account details you submit during registration fall fully within this policy. You can review, correct or query any of these fields by contacting our support team directly.
Deposit and withdrawal records linked to Nagad, Upay or Bank Transfer are stored in your wallet log and covered by this policy. The payment processor's own privacy terms apply to how they handle data on their side of the transaction.
Game titles, lobby pages and editorial content served by 558hk are covered by this policy for any usage data we collect. Game mechanics or RTP figures displayed by a studio provider are governed by that studio's own disclosures, not by us.
External links, studio platforms and payment-gateway pages you navigate to from 558hk are outside the scope of this policy. We encourage you to read the privacy terms of any third party before submitting personal data to them.
You have concrete actions available to you under this policy — not just abstract rights printed on a page. If you want to see what data we hold against your account, open a support request through the contact route shown in the section below and ask for a data summary. We will respond with the fields we have on file. If any detail is wrong — a misspelled name, an outdated contact number — you can ask us to correct it, and we will update the record once we have verified your identity through your account login. If you decide to close your account, you can request that we remove your identifiable data. We will action that request within the period required by the applicable rules of your eligible region, retaining only non-identifiable operational records. For any question about how your Nagad or Bank Transfer payment data is stored, our support team is the right first contact. Availability of these rights may depend on your local law and the eligible region you access the service from.
Submit a support request asking for a summary of the data fields we hold for your account. We will respond through the same contact channel you used to reach us.
If any stored detail is inaccurate, flag it to support with the correct information. We verify your identity via your active account login before making any change.
Questions about how a specific field — such as your Upay reference or Bank Transfer record — is stored or used can be directed to support. We will answer in plain language, not legal boilerplate.
Closing your account triggers a removal process for identifiable fields. Contact support to initiate this. The timeline follows the requirements of your eligible region's applicable rules.
For any privacy-related question — a data review request, a correction, or a query about how a specific payment record is stored — use the contact routes published on this site. We respond through the same channel you used to reach us, so keep the conversation open until your question is resolved.
The fastest route for account-specific questions. Open the chat widget from any page on the site while you are logged in and describe your privacy query.
For formal requests — data summaries, correction requests and removal notices — email support is the appropriate route. Use the address listed on our published contact page.
The Help Centre on this site covers common privacy questions including how to update your contact details and what happens to your data when you close an account.
Our data handling approach is built around the minimum necessary principle — we collect what we need to run your account and no more. Each area below covers a specific aspect of how your information is managed from the moment you register.
Session tokens keep you logged in during mobile browsing without repeated re-authentication. You can clear these through your browser settings at any time. Clearing cookies ends your active session but does not delete your account or transaction records.
Access to your stored data is restricted to the account processes that require it. Payment identifiers — including Nagad numbers and Bank Transfer references — are not shared with advertising networks or unrelated third parties.
We keep account and transaction records for as long as your account is active and for the further period required by the rules of your eligible region. After a verified closure request, identifiable fields are removed from active systems within a reasonable operational timeframe.
When we update this policy, we note the change on this page. Continuing to use the site after a posted update means you have seen the revised terms. If a change affects how your Upay or Bank Transfer data is handled, support can explain the difference.
These are the questions that come up most often when members read through our privacy policy. If your question is not answered here, reach out through live chat or email support.
We collect the name, contact details and payment identifiers you enter at registration — for example, the Nagad mobile number or Bank Transfer reference you link to your wallet. We also record session and device data to maintain a secure login. We do not store wallet PINs or full payment credentials.
Your Nagad mobile number and Upay identifier are stored as deposit-record references in your transaction log. They are used only to match a payment to your account and are not shared with third-party advertisers. The payment processor also holds its own record under its own privacy terms.
Yes. Submit a data-review request through live chat or email support. We will compile the fields stored against your account and share them with you through the same channel. Your identity is verified via your active account login before we send any data summary.
Contact support with the inaccurate field and the correct version. After we verify your identity through your login, we update the record. This covers contact details, registered name and the payment references linked to your wallet, such as a changed Bank Transfer account number.
Once your closure request is verified, we begin removing identifiable fields from active systems. The timeline follows the requirements of your eligible region's applicable rules. Non-identifiable operational summaries may be retained for the period those rules require. Contact support to start the process.
No. Pragmatic Play, PG Soft and the other studios whose titles appear in our lobby operate under their own privacy frameworks. Our policy covers data we collect directly through your account and session on this site. For studio-level data practices, refer to their published terms.