Reference

Open flexislot Privacy Policy clearly

The flexislot Privacy Policy shows what we collect when you create an account, complete phone verification, use a mobile browser, or check DANA and QRIS payment status.

Account dataCookie choicesWallet recordsPrivacy requests
flexislot Open flexislot Privacy Policy clearly
CONTACT ROUTES

Reach support about your privacy

A privacy request should be easy to connect to the correct account. We ask you to use the support route shown after login and include the phone number or account detail already attached to your profile. That lets us check identity before discussing records, correct a wallet reference, or explain why a request needs more time.

Team online

Account request

Use the signed-in support path for a copy, correction or deletion request. We first compare the request with your account details, so another person cannot simply ask for records linked to your phone verification.

Wallet record

If a DANA, OVO, GoPay or QRIS reference looks wrong, send the transaction reference through support. We can match the privacy request to the payment status without asking you to post wallet credentials in a public message.

Access concern

When login or phone verification affects your privacy request, tell us which device and browser you used. We use that context to separate an account-security issue from a normal request about stored data.

HANDLING PRACTICE

Browse how we handle your data

We keep our privacy process tied to real account actions rather than collecting extra details without a reason.

Account data

We use your account details to create access, confirm the phone verification step and respond to requests made from your profile. If a field is no longer needed for those purposes, we assess it for removal or separation from active account records.

Cookies

Cookies can keep a signed-in session working, remember selected settings and help us see whether a page loads correctly on your mobile browser. You can manage browser cookie controls, although disabling some cookies may affect the privacy settings or account path you see.

Payment records

A DANA, OVO, GoPay or QRIS payment entry may show its rail, reference, amount and status. Bank transfer and virtual account records are handled for matching and support, while we ask you not to send a wallet PIN or password in a request.

Account security

We use login events, phone checks and device details to identify unusual access and investigate a stalled session. If you change phone access or notice an unfamiliar login, contact support through the account route so we can verify the request before discussing stored data.

Retention timing

We retain records while they are needed for account operation, security checks, dispute handling or legal duties. When those needs end, we remove, anonymise or isolate the relevant record according to our internal retention process rather than keeping every detail indefinitely.

Change requests

You can ask us to access, correct or delete eligible personal data by using the support route attached to your account. Include the request type and phone detail; we may ask for an account check before making a change or explaining a lawful reason to retain a record.

Check answers before opening your account

These Privacy Policy answers focus on the practical questions you may have before using flexislot in Indonesia. They cover the account step, local wallet records, cookies, device access and requests to our support team. Where access or eligibility is discussed, it depends on local law, and the current policy wording on this page takes priority.

It covers account details, phone verification, login and device events, cookies, support requests and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains why we use those records and how you can request access or correction.

Phone verification helps us link a request or login to the correct account and reduce mistaken disclosure of personal data. We use it as an account-security step before discussing records, and access remains where local law permits.

Yes. The Privacy Policy covers the payment rail, reference, amount and status needed to match a DANA or QRIS transaction with your account. The same approach can apply to OVO, GoPay, bank transfer and virtual account records.

Cookies can keep your session active, remember privacy choices and help us identify page-loading problems on a mobile browser. You can adjust cookie controls in the browser, but some account or policy settings may not work as expected after cookies are blocked.

Yes. Send a correction request through the support route shown in your signed-in account and identify the field that needs changing. We may check your phone or account details first, then update the record when the request can be verified.

We keep account, security and payment records only for the period needed for account operation, dispute handling, security work or legal duties. After that need ends, we assess the record for removal, anonymisation or restricted storage under our retention process.

Contact our support team through the account support route and include the phone detail connected with your profile. For a DANA, OVO, GoPay or QRIS question, add the payment reference so we can identify the record without asking for your wallet password.