Reference

Privacy Policy for Your kepo66 Account

kepo66 Privacy Policy explains how we handle the details connected with your account, mobile browser, wallet status and support requests in Indonesia.

Account clarityWallet dataCookie choicesAccess requests
kepo66 Privacy Policy for Your kepo66 Account
CONTACT ROUTES

Privacy Help Beside Your Account

A clear support route matters when a privacy request and an account issue arrive together. We ask you to use the contact path shown in your account help area and include the email or phone number linked to your profile, so we can locate the right record without asking for your password. If a wallet status stalls after a DANA or QRIS attempt, our support team can separate a payment reference question from a request about personal data.

Team online

Account help

Use the support route inside your account when you need a copy, correction or explanation about stored details. Include your registered phone number and request type, but never send your password or full wallet credentials through the contact form.

Wallet records

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, provide the payment reference and date. We use those details to find the relevant record while avoiding unnecessary collection of unrelated account material.

Access concerns

If login or phone verification blocks a privacy request, tell us which device path you used, such as mobile browser or desktop browser. We can route the access issue and the data request separately for a clearer reply.

DATA CONTROL

Six Ways We Handle Your Details

The policy is designed around actions you can understand: what we collect, why we use it, how we protect account access and when records leave our working systems.

Account records

We may store your registered phone number, account identifier, verification result and login history. These fields help us connect a privacy request to your profile and identify unusual access without requiring your password.

Wallet references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can be retained with status and timing. We use it to reconcile an account event, not to request your wallet password or unrelated credentials.

Device signals

Your mobile browser or desktop browser may send device type, language, session time and security events. These signals help keep a login connected and allow us to investigate a session that does not match your usual path.

Cookie choices

Cookies can keep a session active and remember settings such as language or consent status. You can adjust cookie controls in your browser, although changing them may require another login or affect parts of the account path.

Retention timing

We retain records only while they support account operations, payment reconciliation, security checks, dispute handling or legal duties. When a record no longer serves one of those purposes, our handling follows the applicable retention process.

Change requests

Ask us to correct account details, explain a data use or request deletion where applicable through the account support route. We may confirm ownership by phone or email before changing or releasing personal records.

Privacy Policy Answers For kepo66

These Privacy Policy answers focus on the searches we hear around account access, Indonesian wallets, cookies and personal records. We keep the process practical: use the account support route, identify the profile with its registered phone number or email, and describe the request in plain English. If your question concerns eligibility or access, that outcome depends on local law.

It covers account details, phone verification, login events, device signals, cookies, wallet references, support messages and retention. It also explains how we use records connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

We use the registered phone number to create and protect your account, complete an access check and connect a privacy request to the correct profile. We do not ask you to send a password when you contact us about your data.

Yes. The Privacy Policy covers device type, browser settings, session events and cookie choices from a mobile browser or desktop browser. These signals help keep login activity connected and help us investigate unusual access.

We may receive a payment reference, status and timing for DANA or QRIS activity, then connect that record with the relevant account request. We use these fields for reconciliation, support and security rather than asking for wallet passwords.

Yes. Send a correction request through the account support route and identify the profile with its registered phone number or email. We may confirm ownership before changing the record, and the request remains subject to applicable legal requirements.

Retention depends on why the record exists. Account, payment, security and support records may remain while needed for operations, dispute handling or legal duties. After that purpose ends, handling follows the applicable retention process described in our Privacy Policy.

Use the support contact path shown in your account help area and state that your request concerns the Privacy Policy. Include the registered contact detail and device path if login is blocked; access or eligibility depends on local law.