Slots / Live
k558 is clear about what account data we collect, why we hold it, and how you can review or update it at any time. Access to this platform and its features depends on your local law and eligible regions — this policy explains what applies when you use our services.
When you create an account with us, we collect the details you submit — your name, contact information, and the credentials you choose. As you use the platform, we record activity logs tied to your account, including session timestamps and device identifiers your browser passes to our servers. Payment activity is recorded at the transaction level: when you move funds through Nagad, Rocket, or Bank Transfer, we retain a structured record of the amount, method reference, and outcome. We do not store raw payment credentials on our side; those pass through the payment channel directly. Cookies and similar tracking tools are active on the site. Some are essential for session management — without them, you cannot stay signed in. Others are analytics-only, helping us understand which parts of the platform are accessed most. You can manage non-essential cookies through your browser settings at any time. Data retention follows the minimum period needed for account and compliance purposes. We do not sell your personal information to third parties. Access to your records within our systems is restricted to the functions that require it. If your local law grants additional data rights, those apply alongside this policy where they are recognised in eligible regions.
Not every part of your experience falls under the same policy rules. Use this breakdown to understand exactly what is and is not within the scope of this document before you contact us with a data question.
Login credentials, session tokens and device identifiers collected when you sign in are covered here. We use these records to maintain your session and to verify account activity if a support question arises.
Payment references generated when you use Nagad, Rocket, or Bank Transfer are stored as part of your account history. These records are visible in your signed-in wallet area and are within this policy's scope.
Analytics data collected while you browse the lobby, including page views and feature interactions, is covered by this policy. You can limit non-essential cookies through your browser without losing access to core account functions.
External links, payment channel interfaces and any service you reach by leaving our domain operate under their own data terms. We do not control how those third parties handle your information once you leave our pages.
Your rights under this policy are practical, not just stated. You can review the personal details held on your account by opening the account settings page when signed in — the fields shown there reflect what we have on record. If something is incorrect, the same screen lets you submit a correction request directly. For records you cannot update through the interface — such as historical transaction logs for Nagad or Rocket payments — you can raise a specific data inquiry through our published support routes. We will confirm receipt and tell you what we can share or amend under our retention rules. If you want to understand more about how a specific piece of data is used, that question belongs with our support team, not in the account settings page. Eligibility to exercise any rights beyond those we publish here depends on your local law and the eligible region your account falls under.
Sign in and open the account settings page. The personal details, contact fields and linked wallet references held against your account are shown there for you to read and compare.
Use the editable fields in account settings to update contact information or other personal details. Fields that are locked — such as your registered identifier — require a support request to change.
If you have a specific question about how a record is used or retained, send it through our published support contact. Include your account reference so we can locate the relevant data without delay.
For any data matter that cannot be handled through account settings alone, our support team is the right route. Open a ticket through the contact method shown in the support section of this page.
If you have a question about this policy, a data correction to submit, or a concern about how your information is handled, use one of the contact routes below. We only list routes that are published and active on the site — we do not invent channels or promise response windows we cannot confirm.
Open the live chat widget from any page on the site while signed in. Use this for account-specific data questions where your session reference is already visible to the support agent.
Send your data inquiry to the email address listed on the site's contact page. Include your account reference and describe the specific record or policy question so we can respond accurately.
The help centre on the site contains published policy articles and account guides. Check there first — your question may already be answered without needing to open a support ticket.
Our approach to data handling is built around four principles: collect only what is needed, store it only as long as required, restrict internal access to the functions that use it, and give you a clear route to ask questions. These are the four areas we apply consistently.
We keep account and transaction records — including Nagad, Rocket and Bank Transfer logs — for the minimum period required for account and compliance purposes. Once that period passes, records are removed from active systems in line with our internal schedule.
Essential cookies keep your session active and your account signed in. Analytics cookies are separate and can be turned off through your browser settings without affecting your ability to access account features or complete a payment.
Access to your stored data inside our systems is limited to the processes that require it. We do not share or sell personal account data to outside parties. Your payment channel credentials are not stored on our side after a transaction is submitted.
When this policy changes in a material way, we publish a notice on the site and update the effective date at the top of this document. Continuing to use the platform after a posted change means you have had the opportunity to review the updated terms.
These are the questions we hear most often about how account data is collected, stored and managed. If your question is not here, use the live chat or email route listed in the support section above.
We collect the details you submit during registration — name, contact information and login credentials. Once your account is active, session data and device identifiers are recorded alongside any transaction references generated through Nagad, Rocket or Bank Transfer.
Yes. When signed in, your wallet area shows the transaction history tied to your account, including payment method references. For older records or records that are not visible in the interface, raise a request through our published support contact with your account reference.
Open account settings while signed in and use the editable fields to update your personal information. Fields that are locked for security reasons — such as your registered identifier — require you to contact support directly with the correction you need made.
It covers the transaction records we hold on our side — the reference, method and outcome logged in your account history. The payment channel itself operates under its own terms. We do not store raw payment credentials once a transaction has been submitted through the channel.
Access is restricted internally to the functions that require it — account management, payment record handling and support processes. We do not sell personal data or share it with third parties outside of what is required for the platform to operate and for compliance purposes.
We post a notice on the site and update the effective date on this document when a material change is made. You can return to this page at any time to read the current version. Using the platform after a posted update means you have had the opportunity to review any changes.