Reference

Privacy Policy For Your logic99 Account

Our Privacy Policy explains what we collect when you open a logic99 account, sign in, use a mobile browser, or choose DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesPolicy requests
logic99 Privacy Policy For Your logic99 Account
CONTACT ROUTES

Ask About Your Privacy Policy

You can ask us about personal data without leaving your account journey. Start with the support contact route shown in the account help area, and include the email or phone detail linked…

Account access Use the account help contact route when you need to know which personal details are linked to your login. We may ask for an account identifier before disclosing records, so a request is not answered to the wrong person.
Wallet records For a payment-data question, include the transaction reference and rail, such as QRIS or bank transfer. We can check the matching record without asking for your DANA, OVO or GoPay wallet PIN.
Change request Send correction, access or deletion requests through the privacy contact path shown on the site. Describe the requested change clearly and use the account email or phone detail needed for identity checks.
HANDLING DETAILS

How logic99 Handles Personal Data

The policy works alongside the account steps you already see: create an account, complete phone verification, sign in, then use the lobby from your chosen device.

Account creation

When you open an account, we collect the details needed to create login access and communicate about that account. Phone verification is an account step before access, helping us connect a request to the correct person.

Payment references

A DANA, OVO, GoPay or QRIS transaction can produce a reference, status and time record. Bank transfer and virtual account records may also include the bank rail used, allowing us to reconcile the request.

Device signals

A mobile browser or desktop session can create technical details such as browser type, device settings and connection time. We use these signals to keep sessions working and spot access that does not match normal account activity.

Cookies

Cookies can retain session choices and help us see whether a page or policy link loads correctly. You can adjust cookie controls in your browser, but blocking required cookies may interrupt sign-in or make you repeat a step.

Security access

We restrict account data to people and service processes that need it for account support, security checks or transaction handling. Never place a password, verification code or wallet PIN in a privacy request.

Retention requests

We keep records only for the operational, security, accounting or dispute purpose that requires them, subject to applicable obligations. You can ask what remains, why it remains, and whether correction or removal is available.

Privacy Policy Questions For Indonesia

These Privacy Policy answers address the account and wallet questions we hear most often from Indonesian customers. They cover the practical path from phone verification to a mobile session, including what happens when you use QRIS or return to the site from a different device. If your request concerns a specific record, contact us with the account detail and transaction reference that lets us locate it safely.

It covers account details, phone verification, device and browser records, cookies, payment references, security checks, retention and privacy requests. It applies when you open an account, sign in from mobile or desktop, use the lobby, or contact us about DANA, OVO, GoPay, QRIS or bank activity.

Phone verification helps connect account access to the person completing the account step and supports checks when an access or data request arrives. We use the detail for account security and service handling, not as a reason to request your wallet PIN or password.

Yes. The Privacy Policy covers references created when you use QRIS, DANA, OVO or GoPay, including status, time and matching details. We may also retain bank transfer or virtual account references, while wallet PINs are not needed for transaction matching.

A phone, tablet or desktop session may provide browser type, device settings, connection time and technical session details. We use these records to maintain sign-in, diagnose a page issue and identify unusual access. The device path does not require you to disclose a wallet PIN.

Use the privacy contact route shown on the site and describe whether you want access, correction or another change. Include the account email or phone detail needed for identity checks. For payment records, add the transaction reference, but leave out passwords and verification codes.

Retention depends on why a record exists and whether an account, payment reconciliation, security check or dispute still needs it. We remove or reduce access to records when that purpose ends, subject to applicable obligations. You can ask us to explain the period for a specific record.

Yes. Access and eligibility depend on local law and the location associated with your session. Our Privacy Policy still explains data handling for an account or request, but it does not change local requirements. If you are unsure, contact support before submitting personal details.