Skip to content
sm8 App / Live
DATA & PRIVACY

sm8 Privacy Policy: How We Handle Your Account Data

This Privacy Policy explains exactly what data sm8 collects when you open an account, make a transaction through Touch 'n Go eWallet, DuitNow or FPX, or contact support — and how that data is stored, used and protected. Availability of services depends on local law and eligible regions in Malaysia.

  • Account data protection
  • Touch 'n Go eWallet & FPX records
  • Malaysia-region scope
  • Support contact rights
POLICY SCOPE DETAILS

What This Policy Covers on sm8

When you register an account, sm8 collects the information you enter directly — your email address, contact details and the payment method you select at the time, which may include Touch 'n Go eWallet, FPX or DuitNow. Each time a transaction is processed through one of these payment rails, a record of the amount, method and timestamp is held against your account. We do not store full card numbers or wallet PINs; those credentials remain with the respective payment provider. Beyond account registration, data is also gathered through your browsing session on the sm8 site — pages visited, device type and browser session identifiers are logged to keep the session active and to detect unusual access patterns. This session data is not shared with advertising networks for targeting purposes. All data held by sm8 is processed in accordance with applicable data-protection obligations that apply to the eligible regions where the service is available. If you access the platform from a region where local law restricts data processing in a particular way, those local requirements take precedence. The current state of what we hold about your account is accessible after you log in to your account dashboard. If anything appears incorrect, the correction process is outlined in the Rights section below.

  • Touch 'n Go eWallet transaction records

  • DuitNow transfer history

  • FPX payment logs

  • Account session identifiers

  • Device type and browser data

INSIDE VS OUTSIDE

Where This Policy Applies and What It Covers

Not every data point on your device falls under this policy. The table below clarifies what is inside the scope of this Privacy Policy, what sits outside it, and where the boundary lies between sm8's responsibilities and those of third-party services you may connect to through the platform.

  • Account Access Data

    Login email, session tokens and access timestamps are covered fully by this policy. sm8 holds these records and you can request a summary or correction through the support channel at any time.

  • Payment Transaction Records

    Records of transactions made via Touch 'n Go eWallet, DuitNow and FPX — including method used, date and amount — are within scope. Credential details such as wallet PINs or bank passwords never pass through sm8 systems.

  • Site Content and Game Logs

    Game session activity on the sm8 platform — rounds played, wagers placed, results recorded — is covered. This data supports account history and dispute resolution but is not sold or shared with third-party advertisers.

  • Third-Party Services

    Links or services operated by external providers — including payment gateways, game studios such as JDB, Spadegaming, Habanero and CQ9, or external analytics tools — follow their own data policies. sm8 does not control how those parties handle data on their own infrastructure.

YOUR DATA RIGHTS

Actions Available to You Under This Policy

Once your account is active, several practical steps are available to you regarding your personal data. The account dashboard — accessible after login — shows the profile details currently held, including the contact information and payment methods linked to your account. If any detail is incorrect, you can submit a correction request directly through the in-platform support chat or by emailing the support address listed on the Contact page. Beyond corrections, you may request a summary of what data sm8 holds on your account. Requests of this kind are handled through the same support channel. Where applicable local law gives you the right to request deletion of non-essential data, that request can also be submitted to the support team, who will confirm what can and cannot be removed given account and transaction-record obligations. Response timelines depend on the nature of the request and are communicated when the case is opened.

  • Review Your Records

    Log in to the account dashboard to see the profile details, linked payment methods and session history currently held. The dashboard reflects the current state of your data as it stands at the time of login.

  • Correct Account Details

    If a name, contact detail or payment method entry is wrong, raise a correction through the support chat. The team will verify the change request against your account before updating the record.

  • Request a Data Summary

    You can ask for a summary of the personal data held on your account by contacting support via email or live chat. The team will confirm the scope and format of the summary before sending.

  • Raise a Privacy Question

    For questions about how a specific data point is used or shared, contact the support team with the relevant detail. Where applicable local law applies, the response will reflect those requirements.

CONTACT PRIVACY TEAM

How to Reach sm8 on Privacy Matters

Privacy questions, correction requests and data summaries all go through the same support channels. Use the path that suits how quickly you need a response — live chat is the most direct route for straightforward corrections; email is better for detailed data-summary requests where a written record is helpful.

  • Live Chat

    Open the chat widget from any page after login. State that the query relates to a privacy or data request and the team will route it to the right person. Suitable for quick corrections and account-access questions.

  • Email Support

    Send your request to the support email address listed on the Contact page. Include your registered email and a clear description of the data matter. Email is the recommended path for data-summary requests and deletion queries.

  • Account Dashboard

    For self-service corrections to profile fields, the account dashboard is the fastest path. Log in, navigate to account settings and edit the relevant field. Changes that require identity verification will prompt an additional step.

HOW WE PROTECT DATA

Data Handling, Cookies and Retention at sm8

Data handling at sm8 is built around a few consistent practices: collect only what is needed for the account to function, retain it only for as long as necessary, and make the process of reviewing or correcting it accessible without unnecessary friction. The sections below cover the main areas — cookies, account security, retention periods and how to request a change.

  • Cookies and Session Tracking

    sm8 uses session cookies to keep you logged in and to monitor unusual access patterns. These are functional cookies, not advertising trackers. You can manage cookie preferences through your browser settings, though disabling session cookies will affect login continuity.

  • Account Security Practices

    Account access is protected by login credentials that only you hold. sm8 does not store plaintext passwords. If there is activity on your account that you do not recognise, report it through live chat immediately so the team can review the session log.

  • Data Retention

    Transaction records — including FPX, DuitNow and Touch 'n Go eWallet logs — are retained for the period required by applicable financial-record obligations. Profile data that is no longer needed for account operation can be flagged for review through the support team.

  • Requesting Policy Changes

    If the way sm8 processes a specific piece of data changes materially, the policy page is updated and the revision date at the top of this page is amended. It is worth checking back periodically. For any specific question about a change, contact the support team via email.

PRIVACY FAQ

Common Questions About the sm8 Privacy Policy

The questions below cover what players in Malaysia most commonly ask about how account data, payment records and privacy rights are handled on sm8.

What personal data does sm8 collect when I open an account?

sm8 collects the details you enter during registration — email address, contact information and the payment method you link, such as Touch 'n Go eWallet, DuitNow or FPX. Session and device data is also logged to keep the account secure and the session active.

Does sm8 share my data with third parties?

Transaction processing is handled by the payment provider you select — Touch 'n Go eWallet, DuitNow or FPX — and data passes to them only as needed to complete the transaction. Game session data may be held by studio partners such as JDB or Habanero, under their own policies. sm8 does not sell personal data to advertisers.

How do I find out what data sm8 holds about me?

Log in to the account dashboard to see the profile details and payment methods currently on file. For a fuller summary of what is held — including session and transaction records — submit a request through the email support channel listed on the Contact page.

Can I request that my data be corrected or deleted?

Yes. Corrections to profile fields can be made in account settings after login. For corrections that require verification, or for deletion requests, contact the support team by email or live chat. Deletion of transaction records may be subject to financial-record obligations under applicable local law.

How long does sm8 keep my account data after I stop using the platform?

Transaction records are kept for the period required by applicable financial-record rules. Profile data that is no longer operationally necessary can be flagged for review. For the current retention period applicable to your account, raise the question through email support.

Does this Privacy Policy apply differently depending on where in Malaysia I access sm8?

The policy applies to all accounts on the sm8 platform. Access to services depends on local law and eligible regions. Where a specific local data-protection requirement applies in the region from which you access the platform, that requirement takes precedence over the general policy where the two differ.