Reference

filla88 Privacy Policy For Your Account

Our Privacy Policy explains how filla88 handles the account details connected with DANA, OVO, GoPay and QRIS, from phone verification through wallet status checks.

Clear data purposesWallet record contextCookie choicesAccount contact route
filla88 filla88 Privacy Policy For Your Account
CONTACT ROUTES

Privacy Help Along Your Account Path

A clear contact path helps when a Privacy Policy question relates to a real account event.

Account help Use the account support path for questions about phone verification, sign-in records, device activity…
Cashier context When a Privacy Policy question concerns DANA, OVO, GoPay or QRIS, mention the displayed…
Document request Ask through support if you need clarification about stored data, cookie use, retention or…
DATA PRACTICES

Six Data Handling Commitments We Follow

Privacy becomes easier to assess when each handling step has a practical purpose.

Purpose before collection

We collect account and contact details for identifiable operating needs, such as creating your login path, completing phone verification and…

Wallet record separation

A DANA, OVO, GoPay or QRIS reference helps us match a payment status with your account.

Device event checks

We may record sign-in time, device type and related access signals to spot unusual account activity.

Cookie control

Cookies and similar browser storage can support sign-in continuity and page settings.

Retention by purpose

We keep records for as long as they serve account, security, payment-status or support needs, then assess whether continued retention…

Change and access requests

You can ask what personal data is linked with your account, request a correction or ask how a record is…

Privacy Policy Questions Indonesian Accounts Ask

These Privacy Policy answers focus on the searches we hear around account creation, mobile access and local wallet records. If your situation is not covered, send the question through account help with the smallest useful detail. We will use the account step, payment status or device context you provide to locate the relevant policy answer.

It covers data connected with account creation, phone verification, sign-in activity, device signals, cookies, payment-status records and support requests. It also explains retention, correction requests and how we handle questions about account data when access depends on local law.

Phone verification links account access to a contact detail and helps us respond to account-security questions. We may use the verification event to confirm ownership before changing personal details or discussing records connected with DANA, OVO, GoPay or QRIS.

Yes. The policy covers payment references and status details connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account checks. These records help us match a cashier event to the correct account and investigate a status question.

We may record practical access signals such as device type, sign-in time, browser storage and related security events. These details help us investigate an unusual login or a mobile account issue; they are handled for account and security purposes described in the Privacy Policy.

Use the account support path and state which detail needs correction, such as a contact field or account setting. We may ask for an account ownership check before changing it, so the request does not alter another person’s record.

Retention depends on the reason for keeping a record, including account operation, security checks, payment-status questions and support history. We assess whether continued storage is needed under applicable requirements rather than keeping every record without a purpose.

Yes. Send a request through account help asking for the personal data linked with your account and explain the account step involved. We may verify ownership first, then clarify the relevant records, purposes and any limits that depend on local law.