Reference

isu189 Privacy Policy for Your Account

The isu189 Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet activity.

Clear data purposesWallet activity contextAccount access choicesIndonesia policy access
isu189 isu189 Privacy Policy for Your Account
POLICY HELP ROUTE

Get Privacy Policy Help Near Your Account

A clear contact path helps you ask about the Privacy Policy without repeating your account story. We can connect your question to the relevant sign-in, phone verification or payment record, while you remain in control of the details you choose to share. If you are in Yogyakarta or elsewhere in Indonesia, use the support route shown beside your account and include the wallet name, device path and approximate transaction time. We use those details to locate the right record, not to request your password.

Team online

Account data request

Ask us which personal details are connected with your isu189 account and why we use them. Include your account contact detail and phone verification status so we can confirm the request before discussing records.

Wallet record question

If DANA, OVO, GoPay or QRIS shows a status you do not recognise, send the payment reference and receipt through the account support path. We use the reference to check the matching record without asking for your wallet password.

Policy contact path

For a correction, deletion request or Privacy Policy question, use the contact option attached to your account. Tell us the exact change you want, and we will explain any identity check or retention reason before taking action.

DATA HANDLING DETAILS

How Privacy Choices Work at isu189

We treat Privacy Policy questions as account matters, so our process starts with the smallest useful set of details.

Account collection

We collect information you enter for account creation and phone verification, then connect it with sign-in and support events needed to operate your account. We do not need unrelated personal details to answer a Privacy Policy request.

Cookie controls

Browser cookies can keep your session and account path available between pages. Device settings let you restrict cookies, but turning them off may require repeated sign-ins or another phone check before your account can open.

Security checks

An unfamiliar device or sign-in pattern may trigger an extra account check. We use that signal to protect access, and support will not ask you to reveal your password, wallet PIN or one-time verification code.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can be used to match a cashier event with your account. We use the reference for status checking and keep it under the retention rules in this policy.

Retention timing

We keep account, device and payment records only while they serve account operation, security or legal needs. When a record no longer has a valid purpose, we remove it or change it so it no longer identifies you.

Change requests

You can ask us to correct account details, explain their use or request removal through the account contact route. We may verify the registered phone first, and we will state clearly if a security or legal record must remain.

Privacy Policy Questions About isu189

These Privacy Policy answers address the account and device questions you are most likely to have before opening access. We keep the wording practical: what we collect, how wallet records are matched, which choices you have and how to contact us. If your request concerns eligibility, access depends on local law and is available where local law permits.

The isu189 Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, support messages and payment references. It explains why we use each category, how we protect it and when we remove or retain it for security or legal needs.

Phone verification helps us confirm that an account request comes from the account holder before access or a data request is handled. It also helps protect the account when a new device signs in. We do not ask for your password or wallet PIN.

When you use DANA or QRIS, we may retain the payment reference, status and account link needed to match the transaction. That record helps us answer a receipt question or investigate a stalled status. We do not need your wallet password to perform that check.

Yes. Use the account contact path and state whether you want a copy, correction or explanation of your personal data. We may confirm the registered phone first, then identify the records covered and explain any security or legal reason for keeping specific details.

Cookies and device signals can keep your mobile sign-in active and help detect unusual access. You can restrict them through your browser settings, but the account may ask for another sign-in or phone check. The Privacy Policy explains these uses rather than treating cookies as unrelated tracking.

We keep data while it supports account operation, security, payment matching or a legal requirement. After that purpose ends, we remove the record or anonymise it. If you request deletion, we explain which details can be removed immediately and which must remain temporarily.

Use the support contact attached to your account and include the policy topic, registered contact detail and any relevant DANA, OVO, GoPay, QRIS or bank transfer reference. Eligibility depends on local law, and our account access is provided where local law permits.