Mobile / Casino
Your account data belongs to you. At ligaglo, we set out exactly what information we collect when you use GoPay, LinkAja, or QRIS to fund your session, how long we keep it, and what controls you have over it — all accessible from your account dashboard without needing to contact support first.
This policy applies to all data ligaglo processes when you access the platform, create an account, navigate the lobby, or complete a transaction using a supported local payment method. We collect the information you actively provide — such as your registration details and wallet credentials for GoPay, LinkAja, or QRIS — and information generated by your use of the service, including session timestamps, page navigation paths, and transaction records tied to your account wallet. We do not sell your personal data to third parties. Data shared with payment processors is limited to what those processors require to complete your specific transaction; it is not retained by us beyond the period needed for reconciliation and dispute handling. Retention periods vary by data category: account identification data is held for as long as your account remains active; transaction records are retained in line with applicable Indonesian financial record-keeping norms. Where local law requires us to adjust or limit how we process certain categories of data, those requirements take precedence. Availability of specific features described in this policy depends on local law and eligible regions.
Transaction data processed via GoPay is shared only with GoPay's systems to complete the transfer. We retain a reference record in your account history for your own review.
LinkAja payment data follows the same limited-sharing approach. The amount and timestamp appear in your wallet history; raw payment credentials are never stored on our servers.
QRIS scan-and-pay events are logged as transaction entries in your account. No additional personal data beyond the transaction value and time is captured from the QRIS flow.
Not every interaction with ligaglo falls under identical data rules. The four areas below clarify what sits inside this policy, what sits at its edges, and where a third party's own policy takes over — so you know exactly which rights apply to which part of your experience.
Login events, session duration, device type, and account preference settings are all covered fully by this policy. You can review your login history directly inside the account security tab.
Deposits and withdrawal requests processed through GoPay, LinkAja, or QRIS are within scope. The data shared with those payment rails is governed jointly — our obligations are described here; the payment provider's obligations sit in their own policy.
Your interaction with game titles in the lobby — which categories you open, how long a session runs — is captured as aggregate usage data under this policy. It is used for service improvement and is not sold or profiled for advertising.
Links or embedded tools that take you outside the ligaglo platform are not covered here. Once you leave our environment, the relevant third party's privacy terms apply, and we have no control over how they handle your data.
This policy is not passive — it comes with actions you can take right now. Open your account dashboard after login to find your transaction history, session log, and the current state of your stored details. If any information looks incorrect, the account details page lets you submit a correction request directly; most fields can be updated through the form shown there without needing to raise a support ticket. For data questions that go beyond what the dashboard exposes — such as a formal request for a copy of all records we hold about you, or a question about how a specific data category is used — our support team handles these via the contact route described in the support section below. Requests are acknowledged in the order they arrive. Where local law in Indonesia grants additional rights over your personal data, those rights apply to the fullest extent the law provides, and we will process requests accordingly.
Your full transaction history and session log are visible in the account dashboard. No request needed — log in and open the history tab to see what we hold.
Use the account details page to update stored information. Fields that cannot be self-edited — such as registered identity documents — can be corrected by submitting a support request with the updated detail attached.
For questions about a specific data category, retention period, or how a record was generated, contact support via the route below. Reference your account ID so the team can locate the relevant record promptly.
A formal request for a copy of your data, or a request to close your account and delete non-legally-required records, can be submitted through the support channel. We will confirm receipt and outline the steps from there.
Three direct routes connect you to the team that handles data and privacy questions. Use the channel that fits your situation — in-app chat for quick account queries, email for formal data requests, and the help centre for written policy clarifications.
Open the support icon from your account dashboard to start a chat session. This is the fastest route for questions about a specific transaction record or account detail.
Send a written request to the support address shown on the Contact page. Include your account ID and a clear description of the data question or correction you need. Formal data requests should use this route.
The Help Centre contains written answers to common policy questions, including retention periods, how to read your transaction log, and what happens to your data if you close your account.
Four areas cover how ligaglo manages your data day to day — from the cookies that keep your session running to the security measures protecting your account wallet.
We use session cookies to keep you logged in across page loads and preference cookies to remember settings like language and payment method. You can manage cookie preferences from the settings menu in your account. Blocking session cookies will affect login continuity.
Access to your account data inside our systems is restricted to staff with a specific operational need. Stored credentials are handled using standard encryption practices. If we detect an unusual login pattern on your account, you will be prompted to verify your identity before the session continues.
Active account data is retained while your account is open. After an account closure request, non-legally-required data is removed on the schedule shown in the closure confirmation. Transaction records required under Indonesian financial regulations are retained for the period those regulations specify.
When this policy changes in a material way, we will notify you via the email address registered to your account before the change takes effect. The current version is always accessible from the footer of every page. Continued use of the platform after notification constitutes acceptance of the updated terms.
Real questions from account holders about how their data is handled, stored, and what they can do about it.
We collect the details you enter at registration — name, email address, and the information needed to verify your account. Once you start transacting, we also record payment references tied to GoPay, LinkAja, or QRIS transactions. The full list is available in your account data summary after login.
Your transaction history and session log are visible directly in the account dashboard. For a complete copy of all records we hold, submit a formal data request via email support with your account ID. We will confirm receipt and outline the next steps.
Active account transaction records are available in your dashboard for as long as your account is open. After closure, records required by Indonesian financial regulations are retained for the period those rules specify. Non-required data is removed on the schedule confirmed at closure.
Only the data those payment processors need to complete your specific transaction is shared with them. We do not share browsing history, session data, or account preferences. Each processor's own privacy policy governs what they do with the data on their side.
Open the account details page from your dashboard — most fields can be updated directly using the form shown there. For fields tied to identity verification, submit a correction request through email support with the updated document or detail attached.
After a closure request is confirmed, ligaglo removes non-legally-required data on the schedule shown in your closure confirmation message. Transaction records subject to Indonesian financial record-keeping rules stay for the required retention period, then are deleted.