App / Casino
This Privacy Policy explains what personal information sg22 2026 collects when you access our platform, how that information is used, and the choices available to you. Availability of our platform depends on local law and eligible regions in the Philippines.
When you open an account with us, we collect the details you provide during registration — your name, contact information and any verification documents required by the account process. We also record transaction activity tied to your account wallet, including deposits made through GCash, GrabPay or PESONet, so that your account history remains accurate and accessible to you at any time. Beyond registration data, we collect technical information such as device type, browser session identifiers and approximate region, which helps us present the platform correctly on your screen and route account support to the right team. This technical data is not sold or shared for advertising purposes. We keep your information for as long as your account remains active and for a reasonable period after closure, in line with applicable record-keeping obligations. You may request a copy of the information we hold, ask us to correct anything inaccurate, or raise a deletion request through our support channel. Each request is reviewed individually, and we will respond within a reasonable timeframe. Where local law in the Philippines requires specific handling of personal data, our practices follow those requirements to the extent they apply to our eligible regions.
GCash deposit records are stored in your account transaction history and are accessible after login.
GrabPay payment references appear in your wallet log; we do not store full payment credentials on our servers.
PESONet transfer confirmations are linked to your account record and retained for the duration your account stays active.
This policy covers the data we handle directly through sg22 2026. It does not extend to third-party services you reach by leaving our platform. The four areas below define what falls inside or outside this policy's scope.
Data collected when you log in, verify your identity or update account settings falls fully within this policy. We control how that information is stored and who can access it internally.
Deposit and withdrawal activity processed through your account wallet — including GCash, GrabPay and PESONet — is recorded under this policy. Payment processor networks operate under their own separate privacy terms.
Browsing behaviour on our platform, including which game categories you open and session duration, is collected to improve how the lobby is presented to you. This data stays within our systems.
Links to external sites, third-party payment apps or game studio content portals are outside this policy's scope. We recommend reviewing their individual privacy terms before sharing personal information with them.
You have real, actionable choices about the personal information we hold. Reviewing your stored data is straightforward — log into your account and open the account settings section to see the profile and contact details on file. If anything there is wrong, you can correct it directly through the same settings page, or raise a correction request through our support channel if the field is locked. Questions about how a specific piece of data is used can be sent to our support team at any time; we answer policy questions through the same contact routes as account help. If you decide to close your account, you can request deletion of personal data that is no longer required for record-keeping. Each of these actions is handled individually, and we will confirm receipt of any formal request.
Log in and go to account settings to see the personal information currently on file — name, contact details and linked wallet references.
Edit unlocked fields directly in settings. For fields that require verification — such as registered mobile number or identity documents — contact support to start the correction process.
Send your question through our support channel. Policy queries are handled by the same team as account help, so you do not need a separate contact path.
After account closure, you may formally request deletion of personal data that is no longer needed for legal or record-keeping obligations. We review each request and confirm the outcome in writing.
If you have a question about this Privacy Policy, need to submit a data request, or want clarification on how a specific piece of your information is handled, our support team is the right first stop. Use the contact routes below to reach us.
Open the chat widget from any page on sg22 2026. Describe your privacy query and the support team will connect you to the right handler.
Send detailed data requests or policy questions by email. Include your registered account name and the specific data point or policy section your question concerns.
The help section inside your account dashboard lists the current support routes and response process for privacy and data queries after login.
We apply access controls to limit who within our organisation can view your personal information. Account credentials are stored in hashed form; we do not hold plain-text passwords. Cookies and session identifiers are used to keep your account active during a session and to remember display preferences — you can manage cookie settings through your browser. Personal data is retained for as long as your account is active and for a defined period after closure to meet record-keeping obligations. After that period, data that is no longer needed is removed from active systems.
Personal information is stored on servers with access controls in place. Only staff with a defined need to perform account or compliance functions can access your records.
We use session cookies to keep you logged in and functional cookies to retain display preferences. No advertising tracking cookies from third parties are placed without disclosure.
Your account password is stored in hashed form. We recommend using a unique password and keeping your registered mobile number — used for account verification — up to date.
We keep your data while your account is open and for a reasonable period after closure. After obligations are met, personal data that is no longer required is removed from active records.
These are the questions we hear most often about how we handle personal data. If your question is not covered here, use the support contact routes listed above.
We collect the name, contact details and any identity documents you provide during registration. We also record device and session data to present the platform correctly. Payment references from GCash, GrabPay or PESONet are logged in your account wallet history.
Yes. Log in and open your account settings to view the profile information currently on file. For a full data record or a formal access request, contact our support team through live chat or email and we will respond within a reasonable timeframe.
Unlocked fields — such as display name and contact email — can be updated directly in account settings. For fields that require verification, like your registered mobile number or identity document, raise a correction request through our support channel and the team will walk you through the steps shown there.
We do not sell your personal data. Payment processor networks — including those handling GCash and GrabPay transactions — receive only the data needed to process your specific transaction and operate under their own separate privacy terms. No personal data is shared for advertising purposes.
We retain account and transaction records for a defined period after closure to meet applicable record-keeping obligations. Once that period ends and no legal hold applies, personal data that is no longer required is removed from active systems. You can request confirmation of the retention period through support.
Use the live chat on sg22 2026, or send an email to our support team with your registered account name and the nature of your request. Policy and data queries are handled by the same support team as account help — no separate contact path is needed.