Reference

lgo234 Privacy Policy For Your Account

Our Privacy Policy explains what we collect when you open an account, sign in from a phone, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice choicesPolicy requests

Explore Our Lobby Read FAQ

What Our Privacy Policy Covers

lgo234 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy covers details you provide during account creation, phone verification, sign-in, support conversations and wallet activity. It also covers technical records such as device type, browser signals, session time and pages opened around VIP Baccarat, Ganesha Gold or Sportsbook. Payment references from DANA, OVO,

1
GoPay, QRIS, bank transfer and virtual account can help us match a receipt to your account without treating wallet details as public. We use data for access checks, fraud detection, service operation, legal requests and policy administration. Access and eligibility depends on local law; where local
2
law permits, you can use the contact paths below to ask about your stored details, corrections or deletion.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Get Privacy Policy Help Near Payments

A clear contact route matters when a wallet receipt or account detail looks unfamiliar.

DATA CONTROL

How We Handle Privacy On lgo234

Privacy work is tied to practical account events rather than broad promises. We separate profile details from wallet references where our systems allow, limit staff access by support need, and retain records…

Collection at account opening

When you create an account, we collect the details needed for registration and phone verification. A correct phone path helps us connect later privacy requests with the right account instead of disclosing data to another person.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may leave reference, amount and status records. We use these records to reconcile an account event, not to request your wallet password.

Device and cookie records

A mobile browser may provide device type, browser version, session markers and cookie choices. These signals help detect unusual sign-ins and keep your account path working when you move from login to the lobby.

Account security controls

Phone verification, sign-in checks and internal access controls help protect private account details. We may pause a data response until account ownership is confirmed, especially when the request comes from a new device.

Retention and deletion

We keep personal and wallet records only as long as needed for account operation, security investigations, dispute handling or legal duties. A deletion request may be limited when a record must remain for one of these purposes.

Changes to your details

Ask support to correct an outdated phone number, email address or profile detail. We check the request against your account before making a change, then explain any step that still requires phone verification.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the account, device and payment questions we expect from Indonesian customers before they create an account. If your situation involves a specific DANA receipt, phone change or sign-in event, use the support route above and give only the reference needed to locate the record.

It covers account details, phone verification, device and cookie records, support messages, and wallet references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number for account creation, verification, sign-in protection and account-related requests. We may ask you to confirm it before discussing private records or changing profile details.

Yes. The policy covers technical signals such as device type, browser details, session markers and cookie choices. These records help maintain sign-in security and identify unusual access from another device.

We may store payment references, status and related account details so we can reconcile a wallet event, investigate a mismatch and respond to a support request without requesting your wallet password.

Yes. Contact support through the account help path and identify the profile detail that needs correction. We first verify account ownership, particularly when the request comes from a new phone.

Retention depends on the purpose of the record. We keep details for account operation, security, disputes or legal duties, then remove or restrict them when those purposes no longer require storage.

You can ask support about deletion of personal details. We assess the request under applicable rules; some records may need to remain for security checks, dispute handling or legal duties where local law permits.

lgo234 Privacy Policy For Your Account

Get Privacy Policy Help Near Payments

How We Handle Privacy On lgo234

Collection at account opening

Wallet references

Device and cookie records

Account security controls

Retention and deletion

Changes to your details

Privacy Policy Answers For Your Account

01 What does the lgo234 Privacy Policy cover?

02 Why does lgo234 collect my phone number?

03 Does the Privacy Policy cover my mobile device?

04 How are DANA and QRIS records used under this policy?

05 Can I ask lgo234 to correct my personal data?

06 How long does lgo234 keep my account data?

07 Can I request deletion under the Privacy Policy?

Related Pages