Reference

ffbeta Privacy Policy for Your Account

Our ffbeta Privacy Policy shows how we handle the details connected with your account, including payment references from DANA, OVO, GoPay and QRIS.

Account dataWallet referencesCookie choicesAccess requests
ffbeta ffbeta Privacy Policy for Your Account
ACCOUNT HELP ROUTE

Where To Ask About Privacy Changes

A direct support path helps you ask what we hold, why we use it, or how to change an account detail.

Access request Ask us for the personal data connected with your ffbeta account. Include your registered contact detail and the account step that concerns you, such as phone verification or a login record, so we can check the right profile.
Wallet query For DANA, OVO, GoPay or QRIS records, send the transaction reference visible in your receipt or account history. We use that reference to trace a status without asking you to disclose a wallet password or private wallet credential.
Correction path If your name, phone detail or contact address is inaccurate, use the support route beside the cashier path and describe the requested change. We may ask for an account check before editing information that affects access or verification.
DATA HANDLING

What We Keep Secure And Why

Privacy controls work alongside the account steps you already recognise: phone verification before access, a mobile login session, and payment status checks.

Account details

We use your registration details to create and maintain your account, confirm requested changes and respond to support questions. Phone verification can connect an account action to the correct person before we disclose or edit account information.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create reference numbers, amounts and status markers in our records. These details help match a cashier event to your account without storing your wallet sign-in secret.

Cookies

Cookies and similar browser storage can remember session settings, keep login steps functioning and show the right account state on mobile. You can manage browser permissions, although turning off essential storage may interrupt access to account pages.

Device security

We may record device type, browser version, session time and network signals to spot unusual login behaviour. If an access check appears after you open Live Blackjack Turbo, follow the account prompt and contact support if the device is yours.

Retention periods

We retain records only for as long as needed for the purpose described here, account support, transaction matching, security checks or a legal obligation. When a record is no longer needed, we remove it or reduce it to a form that cannot identify you.

Your requests

You can ask which personal data we hold, request a correction, object to a use where applicable, or ask for deletion subject to local requirements. Send the request through the account support route and identify the specific record or purpose.

Privacy Policy Answers For ffbeta Accounts

These Privacy Policy answers focus on the searches we hear most often from Indonesian account holders. They cover registration data, wallet references, cookies, device checks, access requests and policy changes. If your question concerns a particular receipt, phone verification step or login event, use the support route beside your account and include that specific detail.

The ffbeta Privacy Policy covers data from registration, phone verification, login sessions, device signals, cookies, support requests and payment references. It explains how we use, protect, retain and handle requests about those records when you access the account area where local law permits.

No. When you use DANA or QRIS, we handle transaction references and status details needed to match the payment with your account. Your wallet password or private wallet credential should stay with the wallet provider and should never be sent through support.

OVO and GoPay can generate payment references, status markers and receipt details during an account transaction. We mention them so you can understand the records connected with your wallet activity, not because we need access to your wallet login or private wallet balance.

Use the support route shown beside your account and provide the contact detail registered to your profile. Tell us that your request concerns the Privacy Policy and specify whether you want access to account, device, cookie or payment-reference records.

Yes, you can request a correction when a name, phone detail or contact address is inaccurate. Send the request through account support, identify the field that needs changing, and complete any account check required before we edit access or verification records.

Cookies can keep your mobile session, account state and page preferences working as you move from login to the lobby. Your browser controls these files. Blocking essential cookies may prevent account pages from recognising your session or completing a verification step.

We keep the current Privacy Policy available through the policy access path and may use the contact detail linked to your account when a change needs direct attention. Check the policy page before using account or wallet functions, where local law permits.