Reference

iblis4d Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between the lobby and titles such as Aviator or Lightning…

Account recordsWallet activityCookie choicesContact rights
iblis4d iblis4d Privacy Policy for Your Account
CONTACT PATHS

Privacy Help Near Your Account Route

A clear contact path matters when a privacy request and a wallet question arrive together.

Account request Send an access, correction or deletion request through the account support path. We may ask you to confirm the registered contact detail before discussing private account records.
Wallet record For DANA, OVO, GoPay or QRIS questions, include the transaction reference and date. We use that pairing to separate your payment record from another account.
Security concern If a login alert or device session looks unfamiliar, contact us through the account route and change your password from the security page before sharing further details.
DATA HANDLING

What We Do With Your Account Records

We keep this policy practical by linking each data use to an account action. A login can create device and session records, while a cashier request can create a payment status record…

Account security

We use registration details, login events and device signals to help identify unusual access. Your password is for your account only, and our support route does not need your DANA, OVO or GoPay password.

Cookie controls

Cookies can remember a session, preserve selected settings and help us understand page errors. You can manage browser cookie settings, although removing them may require a fresh login.

Payment records

A QRIS, bank transfer or virtual account action may leave a reference, amount status and time record. We use that record to match your request and investigate a missing status.

Mobile sessions

When you move from login to the lobby on a phone, we may record browser type, operating system and session time. This helps distinguish a normal Mobile Legends visit from an unfamiliar sign-in.

Retention approach

We retain account, security and payment records only for the period needed for the stated purpose, account support and applicable legal duties. Records no longer needed are removed or separated from active use.

Changing your details

Ask us to correct a contact detail or explain a stored record through the account support path. We may verify your identity before changing information linked to your account.

Privacy Policy Answers for Indonesian Accounts

These questions address the searches we hear most often about the iblis4d Privacy Policy. Each answer stays focused on account data, device records, payment references and the practical route for asking us to explain, correct or remove information where the applicable rules allow it.

It covers account details, verification records, login and device events, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use the registered phone or email to create your account, confirm an account request, send security messages and match a privacy request to the correct record.

Yes. A session may record lobby access or a title request, such as Aviator or Lightning Roulette, together with device and time details needed for security and account support.

We retain the reference, status, time and related account details needed to match a DANA or QRIS request. Wallet credentials remain with the relevant payment provider, not in our support messages.

You can ask through the account support path using your registered contact detail. We may verify identity first, then explain which records can be provided under applicable rules.

Send the requested correction through account support and identify the affected field, such as email or phone. We check the request against your account before making an update.

You can request removal through support. We assess the request against security, payment records and legal duties; access or eligibility depends on local law and the applicable retention requirement.