Reference

kompas138 Privacy Policy for Your Account

kompas138 Privacy Policy shows how we handle your account details, phone verification, device signals and wallet records when you use our services.

Clear data purposesWallet record controlsRequest access by contact

Browse Our Lobby Read FAQ

What Our Privacy Policy Covers

kompas138 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy explains what we collect when you open an account, sign in, verify your phone or check a wallet transaction. Account details can include your contact information, login activity, device type and security events needed to protect access. Payment records may show a selected

1
rail such as DANA, OVO, GoPay, QRIS, bank transfer or virtual account, but we use them to match status and maintain transaction records rather than to request unnecessary wallet content. We also describe cookies used for sign-in continuity, language settings and security checks. We retain records
2
for the period needed for account administration, dispute handling and applicable legal duties. Access to our services depends on local law, and this policy does not change that requirement. You can ask what data we hold, request a correction, or ask a question through the contact
3
path shown in your account area.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

How To Ask About Your Privacy

A direct contact path helps you resolve a data question without guessing which team to reach.

Account contact Use the contact route displayed after account access and identify your phone-verified account. We use those details to locate the correct record before discussing a Privacy Policy request.

Wallet question For DANA, OVO, GoPay or QRIS status records, include the transaction reference and selected rail. Do not send a wallet PIN, password or complete payment credential.

Access request Ask for a copy, correction or clarification through the same support path. We may check account ownership before releasing personal data or changing a stored detail.

DATA PRACTICES

How kompas138 Handles Personal Data

Privacy choices work best when each data practice has a clear purpose and a practical account step.

Account details

We use your submitted contact and account details to create access, complete phone verification and respond to account requests. We do not need your wallet PIN to identify a DANA, OVO, GoPay or QRIS status.

Device signals

A mobile browser or desktop session may provide device and sign-in signals used to detect unusual access. These signals help us check an account step without reading unrelated files on your device.

Cookies

Cookies can keep a session active, remember a language choice and support security checks. Clearing browser cookies may require you to sign in again and repeat phone verification before account access.

Wallet records

We retain transaction references, selected payment rail and status details for account servicing and dispute checks. A bank transfer or virtual account reference is handled as a transaction record, not as permission to access your bank account.

Account security

Phone verification, sign-in events and device checks help us protect your account. Keep your password private, sign out on shared devices and contact us if a login or wallet status does not match your activity.

Retention and changes

We keep data only as long as needed for account operations, transaction questions and applicable legal duties. You can request access or correction through support, and we will explain any limit on changing required records.

Privacy Policy Questions From Indonesia

These answers cover the questions we expect you to ask before opening or using an account. They focus on personal data, local wallet records, device access, cookies and the practical steps for contacting us. Access and eligibility always depends on local law.

The kompas138 Privacy Policy explains account, phone verification, device, cookie and transaction records, why we use them, how long we retain them and how you can request access or correction.

We may handle contact details, account activity, phone verification results, device signals and support messages. Payment records can include a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference.

Yes. The Privacy Policy covers the payment rail selected, transaction reference and status used to match an account record. We do not ask for your DANA or QRIS PIN to check that status.

Use the contact route shown inside your account, state that you want a data copy and provide the phone number linked to the account. We may verify ownership before sharing personal records.

You can request a correction through the account support path. Include the detail that needs changing and the corrected value; we may retain an original transaction record when legal or dispute duties require it.

Cookies can support sign-in continuity, language settings and security checks on a mobile browser. If you clear them, you may need to sign in again and complete phone verification.

Open the support contact route in your account and describe the Privacy Policy issue without sending passwords or wallet PINs. Include a transaction reference only when your question concerns payment status.

kompas138 Privacy Policy for Your Account

How To Ask About Your Privacy

How kompas138 Handles Personal Data

Account details

Device signals

Cookies

Wallet records

Account security

Retention and changes

Privacy Policy Questions From Indonesia

01 What does the kompas138 Privacy Policy explain?

02 What personal data does kompas138 collect?

03 Does the Privacy Policy cover DANA and QRIS records?

04 How can I request a copy of my account data?

05 Can I correct details held by kompas138?

06 Why does kompas138 use cookies on mobile?

07 Where can I ask a Privacy Policy question?

Related Pages