Reference

Open goaloo25 Privacy Policy before access

goaloo25 Privacy Policy explains how we handle the account details, wallet records and device signals connected with your access to Live Baccarat Elite, Live In-Play Football and other…

Account data explainedWallet records coveredCookie choices availableAccess depends on local law
goaloo25 Open goaloo25 Privacy Policy before access
CONTACT ROUTES

Check your Privacy Policy questions

A clear contact path helps when a data request and an account question arrive together.

Data request path Ask us to access, correct or explain personal data through the support route on goaloo25. Include your account phone number and request type so we can identify the right record before responding.
Wallet record check If a DANA, OVO, GoPay or QRIS entry looks unfamiliar, send the payment reference and date through support. We compare the record with your account rather than requesting your wallet PIN or full sign-in details.
Account access help For a stalled login or phone-verification question, contact us through the account support path. We may ask for safe account details, but we will not ask you to disclose a password or one-time security code.
DATA PRACTICE

Browse our account data controls

We keep the Privacy Policy practical by linking each data category to an account action. Signing in, verifying your phone and checking a wallet status can create different records, so we describe…

Account details

We use your registration details and verified phone status to create and protect your account. Those details can also help us match a support request to the correct account without exposing another person’s records.

Cookie settings

Cookies and similar device signals help keep your session open and remember selected access settings. You can manage browser cookie controls, although switching them off may affect sign-in continuity or the way policy choices are saved.

Security checks

We examine sign-in patterns, device signals and phone verification events for account protection. If activity looks unusual, we may pause a step and ask you to confirm account details through the secure support route.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference lets us trace a cashier status. We use that reference for reconciliation and support, not as a substitute for your wallet PIN or banking password.

Retention period

We retain account, security and payment records only for the period needed for the stated purpose, account support and applicable legal duties. When a record is no longer needed, our handling follows the retention process described in this policy.

Change requests

You can ask us to correct account data or explain how a record was used through support. We may verify your identity with the phone linked to the account before making a change or sharing account-specific details.

Find Privacy Policy answers quickly

These Privacy Policy questions address the account steps you are most likely to take before opening access. We have kept the answers tied to actual records, including phone verification, wallet references, cookies and device use. If your question concerns eligibility or access from Indonesia, the applicable answer depends on local law.

It covers data created when you open an account, verify your phone, sign in, use a cashier route or contact support. It also explains cookies, device signals, payment references, security checks, retention, disclosures and the process for requesting access or correction.

We use the phone number linked to your account for account creation, phone verification and safer support checks. It helps us distinguish your request from another account. We do not need your password or one-time security code to locate a normal policy request.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. We use those references to match a status or support query, while your wallet PIN and banking password stay with your payment provider.

Send the request through our support route and state whether you want access, correction or an explanation of use. Include the phone number linked to your account and enough detail to locate the record. We may verify your identity before answering.

On a mobile browser, cookies and device signals can help preserve your sign-in path and selected settings. Browser controls let you manage cookies. If you block them, some access steps may need to be repeated, including returning to the account sign-in screen.

We keep account, security and payment records for the period needed for their stated purpose, support and applicable legal duties. The exact period can differ by record type. When retention ends, the record is handled under the deletion or restriction process in this policy.

You can contact us about how an access decision uses account data, but eligibility itself depends on local law. Where local law permits, we apply the account route described on this page. We can explain the relevant record without promising access where law does not allow it.