Reference

Open kkfb Privacy Policy Before Account Access

The kkfb Privacy Policy explains what we collect when you open an account, use the mobile lobby, or connect DANA, OVO, GoPay and QRIS.

Clear collection rulesWallet data boundariesAccount access choicesCookie controls
Explore Lobby Read FAQ
kkfb Open kkfb Privacy Policy Before Account Access
CONTACT PATHS

Switch To Support For Privacy Requests

A direct support path helps you handle a privacy question without sending sensitive details through an unrelated channel.

Account message Use the signed-in account message route when you need to ask about a phone…
Wallet status help If a DANA, OVO, GoPay or QRIS reference appears incorrectly, contact support from the…
Access question When you are unsure whether a request can be completed in Indonesia, ask through…
DATA PRACTICES

Browse kkfb Data Handling In Plain Terms

We keep the Privacy Policy practical by connecting each data use to an account action you can recognise.

Account details

We collect the account details you enter, such as your phone number and contact address, to create an account, send account messages and handle access checks. You can ask support which field is held and request a correction when a detail is outdated or entered incorrectly.

Device records

Your browser or phone can provide technical records such as session data, device type and sign-in timing. We use these records to keep a session working and identify unusual access around your account, including when you switch from mobile to desktop.

Cookies

Cookies can remember a session, language choice or security state so you do not repeat the same account step on every page. You can manage cookies in your browser, although turning them off may interrupt sign-in, wallet status display or policy-page access.

Payment references

We may receive a reference, amount status or timing record for DANA, OVO, GoPay, QRIS, virtual account and bank transfer activity. These records help reconcile an account action; they do not give us your wallet PIN or unrelated wallet history.

Account security

Keep your password, verification code and wallet PIN private. We use sign-in checks and account matching before discussing personal records, so a support message should contain only the reference needed for the request and never a secret credential.

Retention requests

We retain records for the period needed to operate the account, resolve a payment question, protect against misuse or meet a legal requirement where local law permits. Ask support what applies to your record and request correction, access or removal when that route is available.

Ask About The kkfb Privacy Policy

These Privacy Policy answers cover the questions you are most likely to have before opening an account or connecting a local wallet. We keep the wording tied to real account steps, device use and support checks, so you can decide what to share and where to ask for help. If your situation is different, contact us through the account support route and refer to the specific record or request.

It covers details you submit for an account, technical records from your phone or browser, cookie activity, support messages and payment references linked to DANA, OVO, GoPay, QRIS, virtual account or bank transfer actions. It also explains security use, retention and request routes where local law permits.

We use your phone number to create and match your account, complete a clear phone verification step before access and help support identify the correct record. If the number changes or is wrong, contact us through account support and request a correction without sending your password.

Yes, it covers payment references connected with your account, such as a QRIS status or a DANA, OVO or GoPay transaction reference. We use those details to reconcile an account action and investigate status questions, not to collect your wallet PIN or unrelated wallet activity.

When you sign in from a phone or desktop, technical records can include device type, browser details, session timing and security events. We use them to maintain the account session and identify unusual access. You can ask support which device record relates to a specific sign-in.

Send an account support message describing the field or record that needs correction, such as an outdated phone number or contact address. Include the account reference needed for matching, but do not include a password, verification code or wallet PIN. We will explain the next step.

You can ask support about removal of a specific record or account data. We first confirm the account and assess whether retention is still needed for security, payment reconciliation, disputes or legal duties where local law permits. The reply will explain what can be removed or anonymised.

The same policy applies to Indonesia access, including when you connect from Semarang or another city, but some access and request outcomes depend on local law. Tell support your account region and the Privacy Policy question so we can direct you to the applicable route.

Related Pages

kkfb Indonesia Lucky Fortune Cat Sportsbook About Us Dragon Tiger