Reference

ipo138 Privacy Policy for Your Account Data

Our Privacy Policy explains what ipo138 collects when you create an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account dataWallet checksDevice accessCookie choices
ipo138 ipo138 Privacy Policy for Your Account Data
CONTACT ROUTES

Where to Ask About Privacy Policy

A clear contact route helps you resolve a data question without guessing which team to reach. We keep privacy requests close to the account and cashier paths, because a wallet receipt, phone check or device record may need matching before we can act. Use the support option shown in your ipo138 account area and include only the details needed to locate your request.

Team online

Account access

Ask us to check a phone verification record or sign-in issue through the account support path. We may request account identifiers before discussing private data.

Wallet status

For DANA, OVO, GoPay or QRIS data questions, mention the payment rail and receipt reference. We use those details to trace the relevant wallet event.

Policy request

Send a request to view, correct or remove eligible account data through support beside the cashier path. We confirm ownership before making a change.

HANDLING DETAILS

How ipo138 Handles Your Data

We separate practical data handling from broad promises: each record has a reason connected to account access, wallet reconciliation, security or site operation.

Registration records

We use the details you enter during account creation to set up access and match later phone verification. Check your account fields carefully before sending a correction request.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references can connect a receipt or status event to your account. We retain the minimum record needed for reconciliation.

Device signals

When you sign in on a mobile phone or desktop, technical signals can help us identify unusual access. These checks support account security and may prompt ownership confirmation.

Cookie settings

Cookies can preserve essential sign-in and session settings. Your browser controls may let you clear or restrict them, although some account steps may then need to load again.

Retention period

We keep account, security and payment records only for the period needed for their stated purpose, account administration or a legal requirement connected to where local law permits access.

Change requests

To correct, access or remove eligible data, contact us through the account support route with the relevant record. We verify ownership and explain any reason a record must remain.

Privacy Policy Questions for Indonesia

These answers address the searches we hear most often about the ipo138 Privacy Policy. They cover account creation, local wallets, device access, cookies and requests to change stored data, while eligibility remains dependent on local law.

It covers account details, phone verification, sign-in and device signals, cookie settings, payment references and support requests connected with your ipo138 account and access where local law permits.

We use phone verification before account access to confirm ownership and reduce mistaken or unusual sign-ins. If the record is wrong, ask us to check it through the account support path.

Yes. The Privacy Policy explains that DANA, OVO, GoPay and QRIS references may be used to match a wallet status or receipt with your account during payment reconciliation.

Device signals help us recognise unusual access from a mobile phone or desktop and protect the account session. They are handled for security purposes, not as a substitute for your account details.

You can ask through the account support route for access or correction of eligible records. We confirm your account ownership first, then explain what can be changed under local law.

We retain records for the period needed for account administration, security, payment reconciliation or a legal requirement. A retention question can be sent with the relevant account or receipt reference.

Use the support option beside your account and cashier path. Include the request type, such as cookie access, phone verification or QRIS receipt data, without sending unnecessary private details.