Sports / Slots
568h takes a straightforward approach to privacy — we collect only what we need to run your account, process transactions via Upay or Bank Transfer, and keep your session secure. Access and eligibility depend on your local law and eligible regions.
When you open an account with us, we collect information you provide directly — your contact details, login credentials and the payment method you choose, whether that is Upay, Bank Transfer, bKash or Nagad. We also record session data automatically: device type, browser version, IP address and pages visited. This helps us maintain account security and improve how the site loads on mobile. We do not sell your personal data to third parties. Data shared with payment processors is limited to what is needed to complete a transaction — the processor sees only what the transfer requires. Session logs are retained for a defined period, after which they are removed from active storage under our standard retention schedule. If you access our platform, the handling of your data is subject to the laws applicable in your jurisdiction. We do not make legal certainty claims about data residency or cross-border transfers beyond what local law requires. Where a local payment rail such as Rocket or Nagad is involved, the payment provider's own privacy terms also apply to that part of the transaction. You should read both this policy and your payment provider's terms before submitting sensitive information.
This policy covers how we handle data within our own platform — your account record, wallet activity, session behaviour and support correspondence. It does not extend to services operated independently of 568h. Understanding the boundary helps you know who to contact when a question arises.
Data you enter during login, registration and account updates falls fully within this policy. That includes contact details, password history and the session records tied to your account. We control this data directly and you can request a review at any time through our support route.
When you transact via Upay or Bank Transfer, we pass only the fields necessary to complete the transfer. The payment processor holds its own record under its own terms. Our policy covers the instruction we send; it does not govern what the processor stores on their side.
Game content delivered by studios such as Joker, Habanero or CQ9 may involve separate data flows within the game client. We do not control the data behaviour inside a third-party game engine; our policy applies to your account and session layer, not the game's internal telemetry.
Links or services outside 568h — including external payment wallets like bKash or Nagad apps — operate under their own privacy terms. Clicking away from our domain means our policy no longer applies. Check the relevant third-party policy before sharing data on those platforms.
You have a set of practical actions available regarding the data we hold on your account. First, you can request a summary of the personal information tied to your account — what we store, how long we keep it and the categories it falls into. Second, if any detail is incorrect — a contact number linked to your bKash account or a misspelled name — you can ask us to correct it, and we will update the record once we verify the change. Third, you can raise a question about how a specific piece of data is being used. Send the question through our support route with your account reference and we will respond with a factual answer. Finally, if you want to close your account and request deletion of personal data, you can do so by contacting support directly. Deletion is subject to any retention obligations that apply under local law — we will let you know if a portion of your record must be kept and for how long. None of these steps require you to submit sensitive payment credentials to us; use only the published contact routes listed on this page.
Request a summary of account data we hold by contacting support with your account reference. We will confirm the categories stored and the retention period that applies to each.
If a contact detail or wallet reference linked to your account is wrong, submit a correction request through the support route. We verify the change before updating the record.
Questions about how a specific data point is used — for example, how session logs relate to your account — can be sent to support. Include your account reference so we can give a specific, not generic, answer.
To close your account and request data removal, contact support directly. We process the request in line with applicable local law and confirm which records, if any, must be retained and for what period.
If you have a question about this privacy policy, a correction to request or a deletion to initiate, use one of the published routes below. We do not publish support hours we cannot confirm, and we do not promise response times we have not verified. Use the channel that suits your situation and include your account reference in every message.
Open the chat widget from any page while signed in. State that your query is privacy-related and include your account reference so the agent can locate your record without asking for payment credentials.
Send a written request to the support email address shown in your account settings. Email is the preferred route for data review or deletion requests, as it creates a written record of your submission and our response.
The help section inside your signed-in account lists current support options and policy documents. Check there first for the most current contact details, as routes may be updated periodically without a separate announcement.
We apply session-level security controls to protect account records. Cookies are used to maintain your login state, remember preference settings and monitor for unusual session activity. You can adjust cookie preferences through your browser settings; disabling certain cookies may affect how account pages load on mobile. Data retention periods vary by data type — transactional records are kept longer than session logs, and you can ask about the specific period for your account category via the support routes listed on this page.
We use cookies to keep your session active across pages and to detect abnormal login patterns. Functional cookies are required for the account area to work correctly. Analytics cookies, where used, record page-level behaviour only — not payment details or wallet credentials.
Account records are kept for as long as your account is active and for the period required by applicable local law after closure. Session logs have a shorter retention window. We do not keep payment credentials on our servers; those are handled by the payment processor.
Access to your account data is restricted to authenticated sessions. If you notice activity you did not initiate — a login from an unfamiliar device or a wallet action you did not authorise — report it through live chat immediately so we can flag the record.
When this policy is updated, we post the revised version at this address and note the effective date at the top of the document. Continued use of your account after a posted update means you have had the opportunity to review the changes.
These are the questions we hear most often about how this policy works in practice. If your question is not answered here, use the support contact route with your account reference.
We collect the contact details and credentials you enter during registration, plus session data such as device type, browser and IP address. Payment method references — for example that you use Upay or Bank Transfer — are recorded against your account, but we do not store full payment credentials on our servers.
We do not sell personal data. We share only what is necessary with payment processors like Upay or Bank Transfer to complete a transaction. Game content providers such as Joker or Habanero may process session data within their game clients under their own terms, which are separate from ours.
Send a data review request to our support team via live chat or the support email shown in your account settings. Include your account reference. We will confirm the categories of data stored and the applicable retention period for each category without asking you for payment credentials.
Yes. Contact support through the published routes on this page and state that you want your account closed and personal data removed. We will process the request in line with local law. Some records may need to be kept for a defined period after closure; we will tell you which ones and why.
Our policy covers the instruction we send to the payment processor. Once the transaction moves to the bKash or Nagad platform, their own privacy terms apply to that part of the process. We recommend reading your wallet provider's policy alongside ours before completing a deposit.
Yes. Access and eligibility depend on your local law and the eligible regions we serve. This policy describes how we handle data for accounts that are active under those conditions. If local regulations change your eligibility, the data handling obligations described here still apply to any records we already hold.