Reference

Read f7f7 Privacy Policy Before Account Access

Our Privacy Policy explains what we collect when you open an account, verify your phone, browse Blackjack or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests

Browse Our Lobby Read FAQ

Check Wallet Data In This Privacy Policy

f7f7 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy applies to data connected with your f7f7 account and the actions you take after access is permitted by local law. We may record account details needed for phone verification, sign-in protection and payment status checks. When you use DANA, OVO, GoPay or QRIS,

1
we use transaction references and status signals to match a wallet action with your account; we do not need your wallet password to perform that check. Bank transfer and virtual account records may include a reference, amount and processing status. Browsing activity around Blackjack, Gonzo's Quest,
2
Sportsbook or Rocket Crash can help us maintain session security and respond to account questions. We retain records only for the operational, legal or dispute-handling period that applies to the relevant record. Where local law permits, you may ask us to access, correct or clarify personal
3
data through the account support route. The policy may change when our data practices change, with the current wording presented on this page.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT PATHS

Contact Us About Privacy Policy Requests

A clear contact route helps you act on this Privacy Policy without searching through unrelated account pages. Start by opening your account support area and include the phone number or account identifier connected to the request. If your question concerns a DANA receipt, QRIS reference or an account access event, attach only the relevant record so we can locate it without asking for unnecessary wallet credentials.

Team online

Account support route

Open the support area after signing in and select the Privacy Policy request path. We use your account identifier to locate the correct record and keep the conversation attached to your account.

Wallet record help

For DANA, OVO, GoPay or QRIS questions, send the transaction reference and status shown on your receipt. Never send a wallet password, one-time code or complete payment credential.

Access correction

If a phone verification detail or account record is inaccurate, state the field you want checked. We may ask for an account step that confirms the request comes from you.

ACCOUNT SAFETY

Protect Your Account Data With Clear Steps

We handle Privacy Policy requests through account-linked checks rather than treating an unverified message as proof of identity.

Phone verification

Before account access, we use the phone verification step to connect the session with your account record.

Cookie controls

Cookies and similar session tools can keep your sign-in state, language choice and account route working.

Wallet matching

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we use references and status data to reconcile an…

Device sessions

A mobile browser and a desktop browser may create separate session records.

Record retention

We keep account, support and transaction records for the period needed for service operation, dispute handling or applicable legal duties.

Policy changes

When our data practices change, we update the Privacy Policy page so you can read the current wording before continuing…

Find Privacy Policy Answers Before Opening Access

These Privacy Policy answers cover the questions we expect before an account is opened or a wallet record is checked. If your situation is not listed, use the account support route and describe the exact account step, device path or payment reference involved.

It covers account details, phone verification, cookies, device sessions, support messages and payment status records linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification connects an access request with your account record and helps protect account data from an unknown contact. We may repeat the check when a device path or request needs confirmation.

Yes. The Privacy Policy covers references and status details used to match DANA or QRIS activity with your account. We do not need your wallet password or one-time code for that match.

Open the support area after signing in and select the Privacy Policy request path. Include your account identifier and specify whether you want account, cookie, device or payment-status records checked.

Yes, where local law permits. Send the account field you believe is inaccurate through the account support route. We may ask for phone verification or another account step before changing it.

We retain each record for the operational, dispute-handling or legal period that applies to it. Account support can explain the category and retention reason connected with a specific request.

Yes. The Privacy Policy applies to mobile and desktop sessions, including a mobile login followed by a desktop lobby visit. Cookies and device records may differ between those browser paths.

Read f7f7 Privacy Policy Before Account Access

Contact Us About Privacy Policy Requests

Account support route

Wallet record help

Access correction

Protect Your Account Data With Clear Steps

Phone verification

Cookie controls

Wallet matching

Device sessions

Record retention

Policy changes

Find Privacy Policy Answers Before Opening Access

01 What does the f7f7 Privacy Policy cover?

02 Why does f7f7 need my phone verification?

03 Does the Privacy Policy cover DANA and QRIS records?

04 How can I request a copy of my account data?

05 Can I ask f7f7 to correct personal data?

06 How long does f7f7 keep Privacy Policy records?

07 Does this policy apply when I use a mobile browser?

Related Pages