Reference

flb999 Privacy Policy for Your Data

Our Privacy Policy explains how flb999 handles the account details, device signals and wallet records used when you open the lobby on mobile or desktop.

Account dataWallet recordsDevice choicesPolicy requests
flb999 flb999 Privacy Policy for Your Data
REQUEST HELP PATHS

Where to Ask About Privacy Policy

A clear contact path matters when you want to inspect or correct personal data. Open account help from the same login path you use for the lobby, then describe the Privacy Policy…

Account data request Use the account-help route to ask what personal details are connected with your profile. We may ask you to complete phone verification before discussing account-specific records.
Wallet record question For a DANA, OVO, GoPay or QRIS record, share the date and reference shown in your receipt. We use those details to locate the relevant privacy or status question.
Access concern If a login or device path exposes an unfamiliar session, contact us through account help and change your password from the verified account settings before sending further details.
HANDLING YOUR RECORDS

What We Do With Account Information

The Privacy Policy is designed around the records our account flow actually creates. We separate identity checks, wallet references and device activity so a request can be directed to the right record.

Account details

We handle details such as your phone contact, verification status and account activity to provide account access and respond to requests. We do not need a wallet password to locate your profile.

Device signals

Mobile and desktop sessions can create browser, device and login records. We use these signals to recognise a returning session and investigate an access event you do not recognise.

Cookies

Cookies and similar session tools help keep the account path working between login, lobby and account settings. Your browser controls may let you remove them, though some account steps may then need repeating.

Wallet references

A DANA, OVO, GoPay or QRIS transaction can leave a reference, amount and status record. We use the reference to reconcile the account event without requesting your private wallet password.

Account security

Phone verification can be required before we discuss account-specific data or make a requested change. This helps us avoid sending personal details to an unverified contact.

Retention and changes

We retain records for the period needed for account administration, security checks and applicable legal duties. Ask us to correct, explain or review a record through account help.

Privacy Policy Answers for flb999

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover account access, payment references, cookies, device records and requests for correction. If your question concerns a particular login or receipt, use the account-help path and include only the details needed to find that event.

It covers account details, phone verification, login and device records, cookies, wallet references and contact requests created through the flb999 website. A payment provider may apply separate privacy terms to its own processing.

We use phone verification to confirm account access and help protect account-specific conversations. It can also help us direct a Privacy Policy request to the correct profile rather than disclose data to an unverified contact.

Yes. It covers references and status records created when you use DANA, OVO, GoPay or QRIS through the account flow. It does not mean we need your private wallet password to check a receipt.

Open account help from your verified login and describe the correction clearly. Include the affected field or account step, complete any requested phone check, and avoid sending passwords or complete wallet credentials.

Our mobile website can use session cookies and similar tools to keep login, lobby and account settings connected. Browser controls may remove them, but you might need to repeat verification or sign in.

We keep records while they are needed for account administration, access security, payment reconciliation and applicable legal duties. You can ask through account help which type of record your request concerns.

Yes. Send a data-access request through the account-help route and identify your verified profile. We may confirm your phone details first, then explain the relevant account, device or wallet records.