Reference

Privacy Policy For Your flexi138 Account

Our Privacy Policy explains how flexi138 handles your account details, payment records and device data from registration through lobby access.

Account dataWallet recordsDevice choicesPolicy requests
flexi138 Privacy Policy For Your flexi138 Account
CONTACT THE DESK

Privacy Help For Login And Wallet Questions

A clear contact path matters when a privacy question appears beside a login or wallet issue. Our support desk can help you identify which account detail is being used, what payment record is linked to a request, and which step is needed to correct your profile. Send the request from the contact route connected to your account where possible, so we can check ownership before discussing personal data.

Team online

Account detail request

Ask our support desk to confirm the account details held for your flexi138 access. We may ask you to verify the phone detail used during account setup before discussing a profile record or changing the contact route.

Wallet record question

If a DANA, OVO, GoPay or QRIS entry looks unfamiliar, send the payment reference and account contact detail through support. We use those points to locate the relevant record without exposing another account's transaction history.

Correction request

You can ask us to correct inaccurate name, phone or contact data through the account support route. Describe the change clearly, and we will check account ownership before applying an update to your stored profile.

DATA HANDLING

What We Do With Your Account Data

We keep this policy practical: your account record supports sign-in, phone verification and payment matching, while device details help us investigate unusual access.

Account collection

During account creation, we collect the contact and verification details needed to identify your account. Phone verification comes before account access, helping us avoid sending profile or payment details to the wrong person.

Payment matching

When you use DANA, OVO, GoPay or QRIS, we retain payment references needed to match a request with your account. Bank transfer and virtual account references may be handled in the same way for reconciliation.

Cookie choices

Session cookies can keep your login path and selected account state working between pages. On a phone or desktop browser, you can adjust cookie controls through the browser settings, though some account steps may then need to be repeated.

Device security

We may record device, browser and session signals when you sign in. These signals help us notice unusual account access and investigate a login concern without treating your device details as a public profile.

Record retention

We retain account, payment and support records only for operational, security or legal reasons that apply to the account relationship. Ask our support desk how a particular record is used or whether a request can be made.

Change requests

For a data correction, access request or deletion question, contact us through the account support route and include the account phone or email detail. We verify ownership first, then explain the available next step under local requirements.

Privacy Policy Questions About flexi138

These Privacy Policy answers focus on the account actions you are most likely to ask about before opening access in Indonesia. We explain what happens around phone verification, wallet records, cookies, device signals and requests for account data. If your situation is different, send the details through support without sharing a password or one-time code.

The flexi138 Privacy Policy covers account, phone verification, payment, device, cookie and support records connected with your use of the service. It also explains how to ask about stored data, request a correction and contact us about retention.

We use your phone detail to create and verify the account before access. It helps us connect sign-in activity with the correct account and confirm ownership when you ask about profile data or a DANA, OVO, GoPay or QRIS record.

Yes. The Privacy Policy covers references linked to QRIS, DANA, OVO and GoPay activity, as well as bank transfer and virtual account records. These references help us match a payment request, investigate a status question and protect account history.

We may collect browser, device and session signals connected with sign-in and page use. The purpose is to identify unusual access patterns, keep the account path working on phone or desktop, and help support investigate a security concern.

Send a request through the account support route using the phone or email detail attached to your account. Tell us whether you want access, a correction or a retention explanation. We verify ownership before discussing personal records.

You can ask us to correct inaccurate account data or raise a deletion question through support. Some payment, security or legal records may need to remain for a valid operational reason. We will explain the applicable step after ownership checks.

Yes. Account access and any related eligibility depend on local law. Our Privacy Policy describes how we handle data within the account relationship, while local rules may affect whether access is available and what request process applies.