Skip to content
panalovip Live / Casino
POLICY AT A GLANCE

panalovip Legal Terms for Philippines Account Holders

These legal terms set out how your account, your data and your activity on panalovip are governed — and what rights you hold as someone accessing the platform where local law permits. Read through each section so you know exactly where you stand before you transact.

  • Account Use Policy
  • Data Handling
  • Cookie Practice
  • User Rights
POLICY POSTURE

How panalovip Applies This Policy

Access to panalovip and the rights described in this policy depend on local law and are available only where local law permits. We do not assert a blanket licence claim covering all jurisdictions; eligibility is determined by the rules of your region. When you open an account and fund it through Maya or Bank Transfer, the transaction record created in that process falls within the scope of these terms. Your account wallet, your deposit history and your session data are all handled under this policy — not just the game activity. We collect only what is necessary to operate your account, process payments through the supported local rails, and provide account support when you raise a question. Nothing in these terms removes rights that applicable law gives you directly. Where a conflict exists between this policy and a mandatory local rule, the local rule takes priority. If you are unsure whether access is permitted in your area, check the eligibility conditions shown during the account registration flow before proceeding.

  • Maya

    Deposits and withdrawals processed via Maya generate transaction records held under this policy.

  • Bank Transfer

    Bank Transfer activity is logged to your account wallet and retained as set out in the data retention section.

  • GCash

    GCash deposit records are covered by the same data handling obligations as all other account transactions.

  • Account Wallet

    Your wallet balance, funding history and account-level data are all within the scope of these legal terms.

WHAT THIS COVERS

Scope of These Terms Across Your Account

Not every service you reach through your browser falls inside this policy. We cover what we operate directly — your account, your wallet and the content delivered from our platform. Third-party services linked from the platform carry their own terms, and we do not extend our policy obligations to cover them.

  • Account Access

    Login credentials, session behaviour, account settings and the authentication flow you complete to reach the lobby are all within scope. Any change to your access path — email, password or verification step — is governed here.

  • Transactions

    Every deposit and withdrawal you make through supported payment rails, including Maya and Bank Transfer, creates a record that falls under this policy. Transaction data is retained as described in the trust section below.

  • Site Content

    Game content delivered from our platform — including titles from CQ9, Pragmatic Play, Microgaming and PlayStar — is governed by these terms while you are in the lobby. Game mechanics and payout structures are set by each provider, not by this policy.

  • Third-Party Services

    Payment processors, wallet providers and external links are outside the scope of this policy once you leave our platform. GCash, Maya and Bank Transfer each operate under their own terms, which you should review separately.

YOUR ACCOUNT RIGHTS

Practical Steps You Can Take Under This Policy

You hold concrete rights over the data and records we hold in connection with your account. These are not theoretical — each one has a process you can start today. To review your transaction history, open your account dashboard after login; every deposit and withdrawal entry is listed there with its status and timestamp. If you notice an error in your account details — name spelling, contact number, linked payment method — you can raise a correction request directly through the support channel. We aim to process corrections within the timeframe shown in the support response you receive, which varies by request type. If you want to understand what data we hold about you, or if you believe we are holding something incorrectly, you can submit a data query using the contact paths in the support section. Account closure requests are handled the same way. We do not require a reason for a closure request, but we do require identity verification before acting on one.

  • Review Your Records

    Your full transaction history — including Maya deposits and Bank Transfer entries — is visible in the account dashboard. No separate request is needed to access your own records; they are there after you log in.

  • Correct Account Details

    If your registered name, contact number or linked payment method contains an error, raise a correction through support. Provide the detail as it should appear and we will verify before updating.

  • Raise a Data Query

    To ask what personal data we hold, or to flag a concern about how it is being used, contact us via the channels listed in the support section. We will confirm receipt and outline the next step in the response.

  • Request Account Closure

    You may close your account at any time by contacting support. Identity verification is required before closure is processed; any remaining wallet balance is handled according to the withdrawal process shown in your account.

POLICY CONTACT PATHS

Reach Us About Any Policy Question

If any part of this policy raises a question — about your data, your account records or the scope of your rights — use the contact paths below. Each channel is monitored; response times depend on the volume of queries at the time you write in.

  • Live Chat

    The live chat button is available on the platform when you are logged in. This is the fastest path for account-level questions, including transaction record queries and correction requests.

  • Email Support

    For formal policy requests — data queries, closure requests or written records of a concern — send an email using the address shown in your account settings page. We reply in writing so you have a record of the exchange.

  • Account Dashboard

    For self-service access to your own records, the account dashboard after login is the right place to start. Transaction history, account details and the current state of any open request are shown there.

HOW WE HANDLE DATA

Data Practice, Cookies and Account Security

We handle account data, payment records and session information with a clear retention purpose: to operate the account, process transactions through Maya, Bank Transfer and other supported rails, and respond to support requests. We do not hold data beyond what those purposes require.

  • Data Retention

    Account and transaction records are kept for the period required to operate your account and meet applicable obligations. When your account is closed, retention periods for each data type are determined by those obligations, not by preference. The specific periods are set out in the full privacy document.

  • Cookies

    We use cookies to maintain your session, remember account preferences and measure how the platform performs. You can review and adjust cookie settings through the preference panel shown at your first visit or via your browser settings at any time.

  • Account Security

    Access to your account requires the credentials you set at registration. We do not share login details, and we will never ask for your password through chat or email. If you suspect unauthorised access, contact support immediately and use the account lock option shown in your dashboard.

  • Policy Contact

    To request changes to personal data we hold, or to ask about any aspect of our data practice, use the email channel in the support section. We confirm receipt in writing and provide a reference number for your records.

POLICY QUESTIONS ANSWERED

Common Questions About These Legal Terms

These questions come up most often when account holders review this policy for the first time. Each answer points to the right place inside your account or the correct contact path so you can act without delay.

Does this policy apply to me if I am in the Philippines?

Access and the rights under this policy depend on local law and are available where local law permits. If you are in the Philippines and the registration flow confirms your region is eligible, these terms apply to your account and all activity linked to it.

Where can I see the data panalovip holds about my account?

Your transaction history, account details and session-level records are visible in the account dashboard after login. For a broader data access request — covering everything we hold — submit a query through the email support channel listed in the support section.

How do I correct a mistake in my registered account details?

Contact support through live chat or email and specify the field that needs correcting and the accurate version. We require identity verification before updating any account detail. The correction is confirmed in writing once it is complete.

Are my Maya and Bank Transfer transaction records covered by this policy?

Yes. Every deposit and withdrawal processed through Maya, Bank Transfer or any other supported rail creates a record that falls within this policy. Those records are visible in your account dashboard and are retained under the data retention rules described in these terms.

What happens to my data if I close my account?

When you close your account, we retain data only for the period required by applicable obligations. After that period, records are deleted or anonymised. The specific retention periods for each data type are set out in the full privacy document linked from your account settings.

Can I ask panalovip to delete personal data it holds about me?

You can raise a deletion request through the email support channel. We review each request against our retention obligations before acting. Where deletion is possible under applicable law, we confirm the outcome in writing. Where an obligation requires us to keep specific records, we explain that in our response.