Reference

koi234 Privacy Policy for Indonesia Accounts

Our Privacy Policy explains what we collect when you open a koi234 account, sign in from mobile or desktop, and use DANA, OVO, GoPay or QRIS.

Clear data purposesWallet-aware account recordsMobile and desktop access
koi234 koi234 Privacy Policy for Indonesia Accounts
HELP PATHS

Find Policy Help Beside Wallet Status

A clear contact route matters when your account record or wallet status looks unfamiliar. Start from the account help path and include the email or phone detail attached to your account, plus the relevant DANA, OVO, GoPay or QRIS reference. We use those details to locate the correct record without asking you to send unrelated account data.

Team online

Account data question

Ask through account help when you want to know which personal details are connected with your koi234 profile. Include your registered phone detail so we can match the request safely.

Wallet record query

For a DANA, OVO, GoPay or QRIS record, share the payment reference and approximate time through the cashier support path. We use those fields to check status without requesting your wallet password.

Correction request

If your phone, email or account detail needs correction, contact account support from the signed-in device where possible. We may ask for phone verification before changing information tied to access.

DATA PRACTICE

Browse How koi234 Handles Account Data

We separate practical account records from data that is not needed for a specific purpose. Login events, device signals and phone verification help us detect unusual access, while wallet references help us…

Collected account details

We may hold your registered phone detail, email, verification result and account identifiers. These fields help us recognise your account during sign-in and prevent a correction request from being applied to the wrong profile.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records can include a reference, status and time. We use this limited payment context to match account questions and resolve unclear cashier entries.

Device and security data

When you sign in on a phone or desktop browser, we may record device type, browser signals and security events. These details help us review unusual access without treating them as your account password.

Cookie choices

Cookies can keep a signed-in session connected to the right page and remember essential access settings. If you clear browser data, you may need to complete the account sign-in and phone verification path again.

Retention approach

We retain account, security and payment records for the period needed for the stated purpose, account protection or applicable legal duties. When a record is no longer needed, our handling follows deletion or anonymisation procedures.

Change or removal request

You can ask us to correct, access or remove eligible personal data through account support. We first confirm account ownership, explain any required retention, and then record the outcome against the relevant request.

Check Privacy Policy Answers Before Opening

These Privacy Policy answers cover the practical questions we hear before an account is opened: which details are collected, how payment references are used, what cookies do and how to request a change. If your situation is not listed, use the account support path with only the details needed to identify your request.

It covers account creation, phone verification, sign-in, cookies, device signals, security events, support requests and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

We use your registered phone detail to connect sign-in and verification with the correct account. It also helps us confirm ownership before changing access details or responding to an account data request.

Yes. The Privacy Policy covers device type, browser signals and security events from your mobile or desktop path. Clearing cookies may require you to sign in and complete phone verification again.

We may retain a payment reference, status and time for DANA or QRIS so we can match a cashier question to your account. We do not need your wallet password for that check.

You can contact account support to request access or correction of eligible data. We confirm account ownership first, then explain the records available and any retention reason that limits a change.

We keep account, security and payment records only for the stated purpose, account protection or applicable legal duties. After that need ends, our process follows deletion or anonymisation procedures where permitted.

Yes. Account access and eligibility depends on local law. Where local law permits, the policy describes how we handle your account data, cookies, security records and contact requests.