Live / Sports
wn555 keeps this policy straightforward so you know exactly what we collect, how we use it and what choices sit inside your account. Access to our platform and the rights described here depend on your local law and eligible regions.
When you open an account with us, we collect the details you enter directly — your name, contact address, login credentials and any payment identifiers linked to a transaction method such as bKash or Bank Transfer. We also collect technical signals your device sends when you load a page: browser type, session timestamps and approximate network region. We use this information to operate your account, process transactions through the payment rails you choose and respond to support requests you raise. We do not sell your personal details to third parties for their own marketing purposes. Where we share data with processors — for example, a payment gateway handling a bKash or Bank Transfer instruction — those processors are contractually limited to acting only on our instructions. We retain account records for as long as your account is active and for the period required by applicable regulations in the regions where we operate. You can find your account transaction history in the wallet section of your profile. Because access to wn555 depends on your local law and the eligible regions we serve, the specific regulatory framework governing data handling may vary. If you are unsure whether this policy applies fully in your jurisdiction, reach out through the support route listed at the bottom of this page before proceeding.
This policy governs data we collect and process directly through wn555. It draws a clear line between what falls inside our control and what sits with third-party services you may reach from our platform. Understanding the scope helps you know exactly who to contact when a question arises.
Covers all data you submit when creating or updating your account — login details, contact information and profile fields. We hold and process this data directly. You can review and request corrections through the account settings page.
Covers payment identifiers tied to methods like bKash and Bank Transfer when a transaction is initiated from your wallet. The payment processor handles the transfer itself under its own data terms; we store only the record of that instruction on our side.
Covers behavioural signals collected while you browse the lobby — pages opened, session length and device category. This data informs how we organise game categories and does not identify you to studios such as Microgaming, Joker, PlayStar or CQ9.
Does not cover external sites, payment gateways or service providers you reach from a link on our platform. Once you leave wn555, their own privacy terms govern. We cannot accept responsibility for data handling on those external destinations.
You have practical options under this policy that go beyond simply reading it. Start with your account settings page — that is where you can view the personal details we hold on file and submit a correction request if something is wrong. If a correction affects a payment identifier, such as a bKash mobile number or Bank Transfer account detail, include the relevant transaction reference so our team can locate the right record quickly. For questions that go beyond a straightforward correction — such as asking what data we hold, why we hold it or how long we will keep it — send a written request through the support contact route published on this page. We acknowledge every such request and route it to the appropriate internal team. Where access to your data depends on regulatory requirements in eligible regions, we will tell you clearly rather than leave the response open-ended. Nothing in this policy removes rights you hold under the laws of your jurisdiction.
Open the account settings page to see the personal data we currently hold. Your wallet history, contact details and login records are all visible there without needing to contact support first.
Submit a correction through account settings or by contacting support directly. Include your account identifier and the specific field to change so the update can be applied accurately and without delay.
Send a written enquiry through the published support route if you want to know exactly what we hold, why we process it or when we will delete it. We will respond with a clear, specific answer rather than a generic policy statement.
If your question cannot be resolved at the first contact level, ask for escalation. We route unresolved data queries to a dedicated internal team and follow up through the same channel you used to open the request.
Every data question or correction request has a direct route. Use the channel that suits your situation — email for formal written requests, live chat for faster account-level queries and the on-site help section for self-service steps. We route privacy-related messages to the team responsible for this policy, separate from general account support.
Send a written privacy request to our published support email address. Include your account identifier and the specific question so we can match it to the right record and respond clearly.
Open the live chat window from within your signed-in account to raise a privacy or data question in real time. Suitable for account-level queries where a quick back-and-forth helps.
The on-site help section contains self-service steps for reviewing account data, updating contact details and understanding what each data field is used for. Check there first for common questions.
Transparency about how we store and protect your data is part of how wn555 operates. Each area below covers a distinct part of the data lifecycle so you can see exactly what we do at each stage rather than relying on broad assurances.
We use cookies to maintain your login session, remember your language preference and understand how the lobby is navigated. You can adjust cookie permissions through your browser settings. Disabling non-essential cookies does not prevent you from accessing your account.
Login credentials are stored using one-way hashing so we cannot retrieve your password in plain text. We recommend keeping your password unique to this account. If you suspect unauthorised access, use the account settings page to change your credentials immediately.
We keep account data for as long as your account remains active and for the period required under applicable regulations in eligible regions. When an account is closed, we follow the deletion schedule set by the regulatory framework that applies to your region.
When this policy changes in a material way, we update the version date at the top of this page and, where required, notify you through your registered contact address. Check this page periodically if you want to stay current without waiting for a notification.
These questions cover what visitors ask most often about how their data is handled, what rights they have and how to act on those rights through their account.
We collect the details you enter at registration — name, contact address and login credentials — along with device and session signals your browser sends automatically. Payment identifiers like a bKash number are collected only when you add a payment method to your wallet.
We share data only with processors that handle specific functions, such as a payment gateway processing a bKash or Bank Transfer instruction. Those processors are bound by contract to act only on our instructions and may not use your data for their own purposes.
Open your account settings page — your contact details, payment identifiers and profile fields are all displayed there. To correct a field, edit it directly in settings or contact support with your account identifier and the specific change you need made.
We retain data for the period required by the regulations applicable to your eligible region. Once that retention period ends, we delete or anonymise the record. The exact timeline depends on your jurisdiction; ask support if you need the specific period for your region.
Access to wn555 and the rights described in this policy depend on your local law and whether you are in an eligible region. If you are uncertain whether this policy applies in full in your jurisdiction, contact us through the support route on this page before proceeding.
Send a written request through our published support email with your account identifier and a clear description of your query. We route formal data questions to a dedicated internal team and respond through the same channel, not with a generic acknowledgement.