Reference

keren88 Privacy Policy For Your Account

Our Privacy Policy explains how keren88 handles the details you provide when opening an account, signing in, and checking wallet activity through DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesContact requests
keren88 keren88 Privacy Policy For Your Account
CONTACT PATHS

Three Ways To Ask About Privacy

A clear contact route helps you act on this Privacy Policy without guessing where to begin.

Account support area Open the support area after signing in to ask which account details we hold or to request a correction. We may ask for a verification step before discussing private records.
Wallet record question If a DANA, OVO, GoPay or QRIS status looks unfamiliar, send the transaction reference through the account support path. We use it to locate the relevant record without requesting your wallet PIN.
Privacy request For deletion, access or cookie questions, describe the specific request and phone number linked to your account. We will explain any identity check and the next available step under this Privacy Policy.
HANDLING DETAILS

How We Apply This Policy

We apply this Privacy Policy at the points where account data is most useful: creating access, confirming a phone number, protecting a session and checking a payment record.

Account opening

We collect the details needed to create your account and connect it with your chosen contact route. Phone verification helps us match an access request with the account record before private details are shown.

Session protection

Sign-in records can include device type, browser details, session identifiers and unusual access signals. We use these technical records to protect account access and investigate activity that does not match your normal sign-in pattern.

Mobile browsing

When you move from login to the mobile lobby, our pages may store session and cookie data needed for continuity. Your browser settings can control optional cookies, while required session cookies support account access.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us match a wallet event with your account. We do not ask for wallet PINs or unrelated private credentials through support.

Retention choices

We retain records only for the stated operational, security or legal purpose, then remove or separate them when that purpose ends where applicable. The timing can differ between account, support and payment records.

Change requests

You can request access, correction or deletion through the support path shown inside your account. We may verify your identity first, then explain what can be changed and any reason a record must remain.

Privacy Policy Questions For keren88

These Privacy Policy answers address the searches we expect before you open an account or connect a local wallet. They cover the data collected during sign-in, how payment references are used, what cookies do and how to contact us. If your situation is not listed, use the support route inside your account and describe the exact record or request.

The keren88 Privacy Policy covers account details, phone verification, sign-in records, cookies, device data, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps us connect an access request with the correct account and reduce mistaken or suspicious access. We may repeat that check before discussing private account details through the support path.

Yes. The Privacy Policy covers technical records from mobile and desktop browsing, including device type, browser details, session identifiers and cookie settings used while you sign in or move through account pages.

We use DANA and QRIS references to match a payment event with your account and check its status. We do not need your wallet PIN, and support should never ask you to send that private credential.

You can request access to relevant account data through the support area shown after sign-in. We may ask for phone verification or another identity check before releasing details connected with your account.

Send a clear correction or deletion request through the account support path, naming the record involved. We will explain the identity check, available action and any retention reason that applies under this Privacy Policy.

Account access and eligibility depend on local law. The same Privacy Policy applies to relevant account and technical records where local law permits, while a request may be limited by applicable retention requirements.