Reference

unlockffbetacom Privacy Policy For Your Account

The unlockffbetacom Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between the lobby and your wallet.

Account dataWallet recordsCookie choicesSecurity checks
unlockffbetacom unlockffbetacom Privacy Policy For Your Account
PRIVACY HELP ROUTES

Get Help With A Privacy Request

A clear contact route matters when your account record needs correction or you want to understand a wallet reference.

Account contact Send a privacy request through the account support path and include your registered phone…
Payment records For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account query, share the…
Device concern If a phone or desktop session looks unfamiliar, contact support before changing several account…
RECORD HANDLING

Six Privacy Checks Behind Your Account

We keep the Privacy Policy practical by linking each principle to an account action you can recognise.

Collected details

We may handle your phone number, account identifiers, payment references, support messages, and technical session details. We collect these details when you create an account, verify access, use a wallet route, or ask us to resolve a record issue.

Cookie controls

Cookies and similar tools can remember a session, protect account access, and show which page request needs attention. Your browser provides controls for clearing or restricting them, while some account functions may need an active session.

Account security

Phone verification comes before account access, and device signals can help us identify an unusual session. Never send us a wallet PIN or password in a support message. We use the details needed to check ownership without requesting secret credentials.

Payment matching

When you use QRIS or a bank transfer, the payment reference lets us match a status with your account record. For DANA, OVO, and GoPay, we use the relevant reference and timestamp to investigate a missing receipt or pending entry.

Data retention

We keep records for the periods needed to run the service, protect accounts, resolve disputes, and meet applicable legal duties. The Privacy Policy explains the purpose behind retention, and support can clarify the category of record involved in your request.

Change requests

You can ask us to correct inaccurate account data or explain how a specific record is used. Include the account phone number, the field you want checked, and supporting context. We verify the request before changing or disclosing personal data.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the searches we hear most often before an account is opened. We focus on data collected during account access, wallet activity, cookies, device sessions, and contact requests. If your question concerns a specific record, mention the account step or payment reference so our support team can respond with context. Eligibility and access depends on local law.

It covers account details, phone verification, device and browser signals, cookies, support messages, and payment references. It also explains why we use those records, how long they may remain available, and how you can ask for access, correction, or clarification.

We use your phone number to create and identify the account and to complete the verification step before account access. It also helps support locate the correct record when you ask about a QRIS receipt, wallet status, or account correction.

Yes. The policy covers payment references, timestamps, and status details connected with DANA, OVO, GoPay, QRIS, bank transfer, and virtual account routes. We use these records to match a transaction and investigate a missing receipt without requesting your wallet password.

You can contact support and request a correction to inaccurate account data. Include your registered phone number, the field that appears wrong, and useful context. We verify account ownership first, then explain whether the record can be changed and when.

On mobile, cookies and related session tools can keep your account path active as you move from login to the lobby. Your browser settings can clear or restrict them. If a setting interrupts access to Aviator Mobile Play, support can explain the next account step.

Retention depends on the record type and the purpose involved, such as account operation, security checks, payment matching, dispute handling, or legal duties. The Privacy Policy describes these purposes, and support can address a question about a particular account or transaction record.

Use the account support path and provide your registered phone number, request type, and any relevant date or payment reference. Do not send a password or wallet PIN. We use the supplied context to verify the request and direct it to the appropriate privacy contact.