Slots / Sports
These legal terms govern how your account, transactions, and access to club php1 work — written clearly so you know exactly where you stand before you open or use your account. Access and eligibility depend on local law and are available only in eligible regions where permitted.
Club php1 operates under terms designed for the Philippine digital environment, where account activity, wallet transactions, and game access are all governed by a single consistent framework. When you create an account and use services including deposits through Maya or InstaPay, you agree to the scope described here. These terms apply to your account profile, transaction records, session history, and any communications we send to your registered contact details. We do not claim jurisdiction beyond what local law permits. If you access club php1 from a region where online gaming is restricted or requires specific regulatory authorisation, it is your responsibility to confirm eligibility before proceeding. We will not process accounts or transactions in unsupported regions. The terms set out here are the current version. We update them when our processes change, and the version shown on this page is the one in effect for your account today. Changes take effect when published, and continued account use after publication constitutes acceptance. If you disagree with an updated term, contact support before your next session so we can advise on your options. Your account dashboard reflects the version accepted at registration alongside any subsequent updates.
Deposits and transfers made via Maya fall under these terms. Transaction records are visible in your account wallet history.
InstaPay transfers are logged against your account and subject to the same transaction policy as all other supported payment rails.
GCash wallet activity linked to your account is covered by this policy, including records of deposits and any wallet verification steps.
Your account wallet balance and all movements within it are governed by these terms regardless of which local payment method you used.
Not everything connected to your experience at club php1 falls under this single policy document. Understanding what is covered — and what sits outside — helps you direct questions to the right place without delay. Account access, wallet transactions and site content are all within scope. Third-party services linked from the platform operate under their own separate conditions.
Registration, login, identity verification and account status are all covered by these terms. Any restriction or suspension of your account follows the process described here.
All deposits and withdrawals processed through supported methods including Maya, InstaPay and GCash fall within this policy. Records are held in your account history.
Game content from studios available on this platform — including titles in the live casino and slots lobby — is delivered under licence agreements that sit alongside but are separate from your account terms.
Payment processors, identity verification partners and any external service accessed through a link on this site operate under their own terms. We are not liable for those third-party conditions.
You have concrete steps available at any point to manage how your information is held and used. Log in to your account dashboard to review your registered details, transaction history and any communications linked to your profile. If any detail is incorrect — your email address, contact number or payment method on file — you can correct it through the account settings page without contacting support first. If you want to raise a question about how we handle your data or request a change that cannot be completed through self-service, our support channel is the correct path. Raise a ticket with your account username and the specific detail you are querying; the team will respond with the relevant record or an action confirmation. Account closure requests are also handled through support, and we will confirm completion by the contact method registered on your account.
Your full transaction and session history is visible after login. Navigate to account history to see dated records for all wallet activity.
Update your registered email, contact number or linked payment method from the account settings page. Some changes may require identity confirmation.
Submit a support ticket referencing this policy page. Include your account username so the team can pull the relevant records for your query.
Contact support directly to request closure. We will confirm the outcome to your registered contact detail once the process is complete.
If your question about these terms cannot be resolved through your account dashboard, the following contact paths connect you directly to the team that handles policy and account matters. Have your account username ready when you reach out — it lets us locate your records without back-and-forth delays.
Open the chat widget from any page while logged in to raise a policy question. The team will confirm which terms apply to your specific account situation.
Send your query to the support address listed on the contact page. Include your account username and the policy section your question refers to for the fastest response.
Many legal and account questions can be resolved without contacting support. Check your dashboard first — policy version, transaction records and account status are all shown there after login.
Club php1 applies consistent practices across data storage, cookie use, account security and retention — and this section tells you specifically what each of those means for your account.
We keep your account records for as long as your account is active and for a period afterward as required by applicable law. You can request a summary of what we hold by contacting support with your account username.
We use cookies to maintain your login session and to remember display preferences. Cookie settings can be adjusted through your browser. We do not use cookies to serve advertising from third parties.
Your account is protected by the login credentials you set at registration. We recommend a unique password not shared across other services. If you suspect unauthorised access, contact support immediately so we can flag the account.
To request amendment or deletion of personal data, contact support referencing this policy. We will confirm the action taken within a reasonable period to your registered contact detail.
These are the questions we hear most often about account rights, data handling and policy scope at club php1. If your question is not here, open a support ticket and reference the relevant section of this page.
These terms apply to anyone who creates or uses a club php1 account, including making deposits through Maya, GCash or InstaPay. Access is subject to local law — eligibility is confirmed when you complete registration in a supported region.
The current version is the one published on this page. Your account dashboard shows the date your account accepted the terms in effect at registration. If updates have been made since then, the current page version governs your account from the publication date forward.
Yes. Submit a request through the support channel with your account username. We will respond with the relevant records or confirm the request process. We do not charge a fee for standard data requests submitted through the correct channel.
We retain transaction and account records for a period required by applicable law after closure. Following that retention period, records are removed from active systems. Contact support if you want details on the specific retention timeline that applies to your account.
Yes. All transactions processed through supported payment methods — including GCash, Maya and InstaPay — are covered by this policy and recorded in your account history. The payment processor itself operates under its own separate terms, which we do not control.
Contact support immediately through live chat or email and include your account username. We will review the session record and advise on next steps. Changing your login credentials at the same time through account settings is the first recommended action.