Reference

Your privacy inside lgogoal account flows

Your lgogoal account keeps live-table activity, slot-room sessions such as Rocket Crash, wallet receipts from DANA, OVO, GoPay and QRIS, and privacy choices tied to one profile.

Account privacy controlsCookie choicesDANA record careQRIS trace checks
lgogoal Your privacy inside lgogoal account flows
CONTACT ROUTES

Three privacy contact paths

Privacy requests need a clear route, not a generic inbox. We separate policy questions from game or promo questions so the team can check the right account record faster. Use the same phone number or email that you used at registration, then tell us whether your request is about cookies, wallet records, login access, retention, or correction of account details. We answer in English for Indonesia and may ask one extra verification question before discussing private data.

Team online

Live chat

Live chat is open 09:00–02:00 WIB for privacy questions tied to account access, cookies or wallet records. Tell us your registered phone ending and we will verify before discussing any data.

WhatsApp desk

WhatsApp privacy help is available 10:00–22:00 WIB for correction requests and login-device questions. Send only your account ID and the issue type; never send wallet PINs or full card photos.

Account mail form

The mail form inside Profile > Help is for longer requests, including access copies where local law permits. We attach replies to your account thread so your privacy case stays traceable.

ACCOUNT CARE

Six controls behind your privacy choices

We treat privacy as part of the account flow you use every day. The same care that checks a QRIS receipt also shapes cookie settings, login alerts, and support access.

Data mapping

We separate registration fields, wallet receipts, game-session logs and support chat threads so each record has a clear purpose. A Rocket Crash session does not need the same details as a QRIS receipt.

Cookie settings

Cookies help keep you signed in and remember device choices. On Chrome for Android, go to Settings > Privacy and security > Cookies if you want to clear browser data before returning.

Account security

Password changes live under Profile > Security after login. We record the device, time and IP range for security events, then use those records to spot unusual access to your account.

Retention checks

We keep payment and account records only as long as operational needs and legal duties require. Older chat threads may be archived, while active wallet traces remain available for dispute checks.

Correction requests

If your name, phone number or email is wrong, use Profile > Account Details and send a correction request. We may ask for one matching receipt reference before changing wallet-linked details.

Partner access

Payment checks pass through DANA, OVO, GoPay and QRIS rails, so limited transaction data may be shared to confirm status. We do not share unrelated game choices with those payment rails.

Privacy questions before opening an account

Before you open an account, you should know how the Privacy Policy affects your phone number, wallet receipts, cookies, and support chats. These answers cover the requests we receive most often from Indonesia. If your case involves a lost login, a changed phone, or a disputed QRIS trace, contact us from the account route first so we can match the request to the correct profile.

We collect the details needed to create and protect your account, such as phone number, login email, password record, device data and IP range. Wallet receipts are stored separately when you use DANA, OVO, GoPay or QRIS.

Yes, you can ask through live chat or the account mail form. We confirm your identity first, then provide account data where local law permits and where the record can be safely matched to you.

We keep wallet records to confirm payment status, handle disputes and protect your account from mismatched receipts. A QRIS trace, for example, may show time, reference code and status without exposing unrelated game choices.

Go to Profile > Account Details after login and send the correction request from there. If the change affects wallet access, we may ask for a matching payment reference before updating the account record.

Our cookies focus on login state, session safety, device choices and page performance inside our service. You can clear them in your browser settings, but you may need to log in again afterward.

Only support staff assigned to account and privacy cases can read the thread. We log access to sensitive cases, and we avoid asking for wallet PINs, private banking passwords or unrelated personal documents.

Retention depends on the record type. Payment traces and security logs may stay longer than ordinary chat threads because they help resolve account disputes, wallet checks and access questions tied to your profile.