Reference

Privacy Policy For Your keren138 Account

Your account details, wallet records and device choices stay connected to a clear Privacy Policy on keren138.

Account clarityWallet record careYour access choices
keren138 Privacy Policy For Your keren138 Account
ASK ABOUT RECORDS

Privacy Help Through Your Account

A clear contact path matters when you want to understand a Privacy Policy decision or check a record tied to your account. We ask you to sign in first when possible, because the account route lets us match your request to the right phone verification and wallet reference. If login stalls, use the available support route and include the email or phone detail connected to your access. We keep the request focused on privacy, not general lobby questions.

Team online

Account privacy route

Use the signed-in account support path to ask which personal details are linked to your profile, why a phone check appeared, or how to request a correction. We may ask you to confirm account ownership before discussing private records.

Wallet record check

For a DANA, OVO, GoPay or QRIS question, include the relevant receipt reference and date rather than sending a full wallet password or security code. This gives us enough context to locate the record without exposing unnecessary credentials.

Access issue contact

When a privacy request follows a blocked sign-in or unfamiliar device alert, tell us the device type and approximate time. We use those details to separate an access concern from a normal mobile session, including sessions from Denpasar.

DATA HANDLING

What We Do With Your Details

Privacy is handled through practical account steps rather than vague promises. We limit collection to details needed for access, wallet records, security checks and your contact request, then…

Account creation

When you open an account, we collect the contact details and phone verification result needed to establish access.

Device signals

A browser or phone may share signals such as device type, session time and sign-in pattern.

Cookies

Cookies can keep a session active, remember a language or help us understand whether a page loads correctly.

Wallet records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may be retained with the related account event.

Retention period

We keep personal details only while they serve the stated account, security, support or record-keeping purpose, unless a longer period…

Your requests

You can ask us to access, correct or delete eligible personal details, or question how a record was used.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account questions we hear around sign-in, local wallets, cookies and data requests. We keep the wording direct so you know what to prepare before contacting us. Where an answer involves account eligibility or access, it depends on local law and applies where local law permits.

The keren138 Privacy Policy covers details connected with account creation, phone verification, sign-in, device signals, support requests and wallet records. It also explains cookies, retention, security handling and your ability to request access, correction or deletion of eligible personal data.

We may collect contact details, phone verification results, login events, browser or device signals, support messages and transaction references. For DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity, we use the record needed to match a status or receipt question.

Sign in and use the account privacy route to ask for access to eligible personal details. Include the phone or email connected with your profile and describe the record you need. We may verify account ownership before releasing information tied to your account.

Yes. Send a correction request through the account support path and identify the detail that needs changing. We may ask for a phone verification step, especially when the request affects sign-in or wallet records, so another person cannot alter your profile.

The policy treats DANA and QRIS references as account-related transaction records. We use them to reconcile a receipt, answer a status question and investigate a mismatch. Send only the reference and date needed for the request; never include a wallet password or security code.

You can ask us to delete eligible personal details through the privacy contact path. Some account, security or transaction records may need to remain for a permitted record-keeping period. We will explain the reason if a specific record cannot be removed immediately.

Cookies may keep your session active, remember language settings or show whether a page works correctly. Browser controls let you manage them. If you disable cookies, access may require another sign-in, and some privacy-request steps may not work until the session is restored.