Reference

Open logic89 Privacy Policy for Account Data

Your logic89 Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between the mobile lobby and Live Baccarat.

Account clarityWallet privacyCookie choicesLocal access
logic89 Open logic89 Privacy Policy for Account Data
PRIVACY HELP PATH

Contact us about your Privacy Policy

A clear contact route helps you ask about the Privacy Policy without repeating your account story.

Account requests Ask us to explain, correct or remove account data through the signed-in support path.
Wallet records For DANA, OVO, GoPay or QRIS receipt questions, send the reference and date shown…
Access concerns If a new device or sign-in check blocks your account, describe the device path…
DATA CONTROL DETAILS

Browse logic89 data handling controls

We keep our Privacy Policy practical: each data category has a reason connected to account access, wallet matching, security or support.

Account details

We use your submitted contact and verification details to create the account, confirm requests and respond to support. You can ask us to correct a detail when it no longer matches your current account record.

Device signals

Browser, device and session signals help us spot unusual sign-ins and protect the account path from login through the lobby. We do not need your wallet PIN to review a device access concern.

Cookie choices

Cookies and similar storage can keep a session active, remember selected settings and help us understand page errors. Your browser controls let you clear or restrict them, although some account steps may then need repeating.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can connect a wallet request to the correct account. We use the reference for status checks rather than requesting private wallet credentials.

Retention steps

We keep records for the period needed to operate an account, resolve a dispute, protect access or meet a legal request. After that need ends, records are removed or changed so they no longer identify you.

Change requests

To request access, correction or deletion, use the signed-in support path and state which record concerns you. We verify the account owner first and explain if a payment or legal record must remain.

Check Privacy Policy answers before opening

These Privacy Policy answers cover the searches we hear most often before an account is opened. They explain the practical route for account data, cookies, device access and Indonesian wallet records, while keeping eligibility wording tied to local requirements.

It covers account and verification details, device and session records, cookie use, payment references, support requests and retention. It also explains how to ask for access, correction or deletion where local law permits.

We use a DANA or QRIS reference to match a wallet request with your account, check its status and resolve receipt questions. We do not ask for your wallet PIN or full password.

Yes. The Privacy Policy covers OVO and GoPay references used with an account, including records needed to match a request, investigate a receipt and answer a wallet-status question.

You can ask through the signed-in support path, naming the account detail or time period you need. We verify ownership before sharing records and explain any data that must remain for legal or payment reasons.

Send a correction request from your account support area and identify the detail that is wrong. We compare it with your account record, complete an ownership check and update it when the request is valid.

We retain them only while needed for account operation, security checks, payment matching, disputes or legal duties. When the need ends, we remove or anonymise the records under our retention process.

Access depends on local law. Where local law permits, the policy applies to your account, device activity and wallet references; you should confirm that using the service is allowed in your location.