Reference

logamwin Privacy Policy, Made Clear

logamwin explains how we collect, use and protect the details connected with your account, device and wallet activity.

Account dataWallet recordsCookie choicesRequest access
logamwin logamwin Privacy Policy, Made Clear
CONTACT ROUTES

Privacy Help Beside Your Account

A clear contact path matters when a privacy question appears during sign-in or a wallet check. We ask you to use the support route shown inside your account and include the email or phone detail linked to your profile, without sending a password or full payment credential. Our team can identify the relevant account record, explain a receipt or device entry, and tell you what information is needed for a formal Privacy Policy request.

Team online

Account privacy request

Send your request through the account support route and state whether you need access, correction or deletion. We may ask you to confirm the phone number attached to your logamwin account before discussing personal records.

Wallet record question

For a DANA, OVO, GoPay or QRIS entry, include the transaction reference and approximate date. We use those details to locate the correct record without asking you to share a wallet PIN, password or complete card credential.

Sign-in data concern

If a device entry or phone verification event looks unfamiliar, contact us from the account support path and change your password first. We can check the related sign-in record and explain the next account-security step.

HANDLING DETAILS

How We Apply This Privacy Policy

We keep the Privacy Policy practical by linking each data purpose to an account action you can recognise.

Account details

We use your registration details and phone verification status to maintain account access and route privacy requests to the correct profile. Keep your phone number current so we can distinguish an authorised request from an unrelated message.

Device signals

Browser type, operating system and sign-in timing can appear in security records. On mobile, these details help us investigate a session that changes between login and the lobby, without reading private files stored on your device.

Cookie controls

Cookies can retain session preferences and show us which policy page was opened. You can adjust cookie settings in your browser, though blocking necessary cookies may require another sign-in before account pages load.

Payment references

We record references and statuses for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We do not need your wallet PIN to match a payment status with the account that initiated it.

Retention periods

Records stay available for the period needed for account operations, security checks, dispute handling or legal duties. When that purpose ends, we remove or anonymise the data where local law permits and our retention process allows.

Change requests

You can ask us to correct profile data or explain how a record was collected. Send the request through account support with your linked phone detail; we may verify identity before changing or releasing personal information.

Privacy Policy Questions From Indonesia

Below we answer the questions we expect to receive before you open an account or continue using the lobby. Each answer stays focused on personal data, account access, wallet records and the practical steps for contacting us. If your situation falls outside these examples, use the support path inside your account and quote the relevant Privacy Policy question.

It covers details you provide for account opening and phone verification, along with device, session, cookie and payment-reference records created while you use the service. It explains our purposes, retention approach, security steps and the way you can request access or correction.

Yes. The Privacy Policy includes transaction references and status details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps. We use these records to match a cashier event to your account, not to collect your wallet PIN.

Device type, browser details and sign-in timing help us identify unusual account access and investigate a session that changes from login to the lobby. These signals support account security; they do not give us access to private files on your phone or computer.

Use the support route inside your account and ask for a data-access request. Include the phone number linked to your profile and describe the records you need, such as verification or wallet status. We may confirm account control before releasing personal data.

You can request a correction or ask about deletion through account support. We first confirm which record you mean and whether retention is still needed for security, payment tracing or legal duties. Requests are handled where local law permits.

Necessary cookies help keep a session active and remember basic settings, while other cookies can help us understand policy-page use. Your browser controls can block or remove them. Blocking necessary cookies may lead to another login or limited account-page access.

Yes. Account access and eligibility depends on local law. Our Privacy Policy still explains how we handle data connected with an account, including phone verification, Baccarat or Starburst activity, and DANA, OVO, GoPay or QRIS references.