Reference

kakap69 Privacy Policy for Your Account

Our Privacy Policy shows how kakap69 handles the details you provide when opening an account, signing in, checking wallet status or entering the lobby from Jakarta and other…

Account detailsWallet referencesDevice choicesCookie controls
kakap69 kakap69 Privacy Policy for Your Account
CONTACT ROUTES

Need Help With Your Privacy Policy?

A clear contact route matters when you want to ask about a phone record, device entry or wallet reference. Use our support channel from the account area and state the email or phone linked to your profile; include the relevant date and payment rail, such as QRIS or GoPay, without sending a password or wallet PIN. We use those details to locate the request safely.

Team online

Account privacy request

Ask us to confirm the account data linked to your phone verification step. We may request an account detail already on file before discussing records or making a change.

Wallet reference check

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account queries, share the transaction reference and date. Never include a wallet PIN, password or full secret credential.

Access support

If a sign-in or policy request stalls on mobile, contact support from the same account path where possible. We can explain the next verification step without asking for your private login code.

HANDLING PRACTICES

Inside kakap69 Data Handling

We keep this policy practical by separating what is needed for account operation from what helps us understand device access.

Account records

We use your phone number, account identifier and verification status to recognise your profile and handle sign-in checks. We do not need your wallet PIN to match a payment reference.

Device details

When you sign in from a phone or desktop, we may record device and connection details to spot unusual access. This helps us ask for an extra account check when needed.

Cookies

Cookies can keep a session active and remember selected settings. You can control cookies through your browser, although switching them off may require you to sign in again.

Payment references

DANA, OVO, GoPay, QRIS and bank rails can provide a reference or status result. We use that value for reconciliation, support and account records, not for storing your wallet secret.

Account security

We limit internal access to account data and use verification before discussing private records. Keep your password and phone codes private; support will not ask you to publish them.

Changes and retention

You can request access, correction or deletion through support. We explain any retention reason, such as an unresolved transaction or legal duty, before keeping a record longer.

Privacy Policy Answers Before Account Access

These answers focus on the questions you may have before opening an account or using the mobile sign-in path. If your situation is not covered, contact us with the smallest useful detail, such as your account identifier, request type and the date of a wallet reference.

It covers account details, phone verification, device and connection records, cookies, support messages, payment references and how long those records may be retained. It also explains requests for access, correction and deletion.

We use phone verification to connect sign-in activity with the correct account and reduce unauthorised access. The record can show whether verification was completed; support does not need your private code to discuss policy requests.

No. We use a payment reference or status result to match activity with your account. Do not send a DANA, OVO, GoPay or QRIS PIN to support, even during a payment query.

Contact our support route from your account area and ask for a data access request. Include the phone or email linked to the profile and a short description so we can verify the correct record.

Yes. Send a correction request through support and identify the field that needs updating. We may verify an existing account detail first, then explain whether the change affects phone verification or access.

We retain records for the stated account, security, support or legal purpose and remove them when that purpose ends where permitted. Some transaction records may remain while a status issue or legal duty continues.

Yes, the policy applies when you sign in through a mobile browser or desktop path. Cookies and device details may differ by browser, while access and eligibility remain where local law permits.