Live / Sports
This page sets out how zuwin8 collects, uses and protects the information tied to your account — from login activity to payment records linked to Touch 'n Go eWallet, DuitNow and Bank Transfer. Access and data handling depend on local law and the eligible region you access the platform from.
When you open an account with zuwin8, certain information is collected to keep your session active, process transactions and verify your identity where required. This includes your registered email address, device type, session timestamps and any payment method you connect — such as Touch 'n Go eWallet, DuitNow or a direct Bank Transfer. We do not sell your personal data to advertisers or unrelated third parties. Information shared with payment processors is limited to what those processors need to complete a transaction; nothing more passes across. Cookies are used to maintain your login state and to remember your account preferences between sessions — you can adjust cookie behaviour through your browser settings, though some account functions depend on session cookies to work correctly. We retain account records for as long as your account remains active, and for a period after closure as required by applicable regulations in the regions where this service operates. If you have questions about what data we hold or how it is used, the support contact paths below are the right place to start.
Not every part of your experience falls under this policy in the same way. The four areas below clarify what is directly covered, what sits outside our control and how each relates to your account.
All data collected when you log in, browse the lobby or adjust account settings falls directly under this policy. That includes login events, device identifiers and session activity recorded while you are signed in to zuwin8.
When you initiate a deposit or withdrawal via Touch 'n Go eWallet, DuitNow or Bank Transfer, we pass the minimum required details to the relevant payment processor. The processor's own privacy terms govern what happens on their side of the transaction.
Game content served through the lobby — including titles from studios such as PG Soft, JDB and Spadegaming — is delivered by those studios. Gameplay data recorded within a game session may be subject to the studio's own data terms in addition to ours.
Links or embedded tools that leave the zuwin8 domain are outside the scope of this policy. We do not control what those services collect. Check each external service's own policy before entering personal details on their pages.
Your account data is not static — you have practical routes to review, correct or question what we hold. After logging in, the account settings page shows the profile details tied to your registration. If anything there is out of date or incorrect, you can update it directly through the fields shown, or contact support if a field is locked. For a broader record of your activity — session history, transaction logs tied to DuitNow or Bank Transfer, or payment method associations — submit a request through our support channel and the relevant records will be compiled for you. We aim to respond to data requests in a reasonable period; the timeline depends on the complexity of the request. If your account needs to be closed and data removed beyond standard retention, that request also goes through support with your verified account details. Every request is handled with the same account-holder verification step to protect your records from unauthorised access.
Log in and open the account settings page to see the profile data currently held. Transaction records appear in your wallet history tab, covering deposits and withdrawals processed through your connected payment methods.
Editable fields — display name, contact email, preferred language — can be updated directly in account settings. For locked fields such as registered identity details, contact support with your account credentials to request a correction.
If you want to understand exactly what data we hold or why a particular piece of information was collected, send the question through live chat or email support. Cite your account ID so the team can pull the right records quickly.
Account closure requests, including data removal beyond standard retention periods, are handled through support. The process requires identity verification matching your registered account details before any action is taken.
For anything related to this policy — a data question, a correction request or a concern about how your account information is used — these are the direct routes to the team that handles it.
Open the chat widget from any page while logged in. State your account ID and the nature of your data query. The team will log it and follow up within the same session where possible.
For detailed requests — full data records, correction of locked fields, or account closure with data removal — email is the most reliable route. Include your registered email address and account ID in the message.
Many routine changes — profile details, contact email, cookie preferences — are handled directly in your account settings without needing to contact support. Log in and navigate to the settings tab to see what is editable.
Keeping your account information secure is not an afterthought — it is built into how the platform operates day to day. Here is a plain account of the four practices that matter most to your privacy.
Account records are kept for as long as your account is active. After closure, a retention period applies as required by the regulations that govern the regions where this service operates. Once that period ends, records are deleted from active systems.
Session cookies keep you logged in and preserve your account preferences between visits. You can adjust non-essential cookie settings through your browser. Disabling session cookies may affect account functions that rely on login state to work.
When a deposit or withdrawal is processed via Touch 'n Go eWallet, DuitNow or Bank Transfer, only the data the payment processor requires is shared. Card or wallet credentials are never stored on zuwin8 servers — they pass directly to the processor.
When this policy changes in a material way, the updated version is published on this page with a revised effective date. Continuing to use the account after a policy update means you have seen the new terms. If you have questions about a change, contact support.
These are the questions we hear most often about how zuwin8 handles account data, what rights you have and how to act on them.
We collect the details you enter at registration — typically your email address and contact information — along with device type and session activity recorded while you are logged in. Payment method associations, such as a linked Touch 'n Go eWallet or DuitNow account, are also recorded in your profile.
Wallet and banking credentials are not stored on our servers. When you initiate a transaction, the minimum details needed are passed directly to the payment processor. The processor handles authentication on their side, and only a transaction reference is stored in your zuwin8 wallet history.
Log in and open your account settings page — profile details and editable fields are visible there. Your transaction history, including deposits and withdrawals, appears in the wallet tab. For a compiled record beyond what the dashboard shows, contact support with your account ID.
Yes. Submit a closure and data removal request through live chat or email support. The team will verify your identity against the registered account details before processing anything. A standard retention period applies after closure as required by applicable regulations; data is removed from active systems once that period ends.
Game studios receive only the session data needed to run a game — typically a session token rather than personal profile information. Studios such as PG Soft, JDB and Spadegaming supply game content; they are not given access to your registered email, payment details or full account records.
An updated version is published on this page whenever a material change is made, with a revised effective date at the top of the policy. We do not always send individual notifications for minor updates, so checking this page periodically is the reliable way to stay current on how your data is handled.