Reference

idolpin Privacy Policy For Your Account

idolpin Privacy Policy explains how we handle the account, wallet and device details connected with your access.

Account dataWallet recordsDevice accessCookie choices
idolpin idolpin Privacy Policy For Your Account
CONTACT PATHS

Where To Ask About Your Data

A clear contact route helps when you want to question a record, correct an account detail or understand a wallet reference.

Account contact Use the support contact path inside your account when a phone detail, sign-in record or verification entry appears wrong. We use the account identifier you provide to locate the relevant record without asking for your password.
Wallet question For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference, include the date and transaction reference shown to you. We can check the stored payment record while keeping your full wallet credentials out of the request.
Privacy request Ask through the same support route if you want access, correction or deletion assessed. We confirm the account connection first, then explain what can be changed, retained or removed where local law permits.
HANDLING DETAILS

How We Keep Policy Practice Clear

Our privacy practice follows the records needed for account access rather than collecting every detail available on your device.

Account records

We may hold your phone number, account identifier and verification status so we can connect you with the correct account. If you request a correction, we compare the proposed change with the account details already used for access.

Wallet references

Payment records identify a method such as DANA, OVO, GoPay, QRIS, bank transfer or virtual account without requiring us to store your wallet password. A reference can help us trace a status question or match an account action.

Device signals

Browser, device and sign-in time details can help us recognise an unusual access attempt. We use these signals for account protection and troubleshooting, not as a substitute for your account credentials.

Cookie controls

Cookies and similar session tools can keep an account path working and help us understand a return visit. You can manage available browser choices, although turning off essential session tools may affect sign-in or account continuity.

Retention checks

We keep records only for the period needed for account operation, security checks, dispute handling or legal duties. When a retention reason ends, the record is deleted, anonymised or otherwise restricted where local law permits.

Change requests

Send a request through the account support contact path and state whether you seek access, correction, deletion or a reason for retention. We may verify your account before acting so another person cannot change your data.

Privacy Policy Questions From Indonesia

These answers address the questions we expect you to ask before opening an account or checking a wallet record. They focus on the Privacy Policy, not on general lobby use: what we collect, why we retain it, how device access is handled and how you can reach us. If your question concerns a particular account or payment reference, use the support path connected with that account and mention whether the record relates to DANA, QRIS or another listed method.

The idolpin Privacy Policy covers account details, verification records, wallet references, device signals, cookies and support messages connected with your access. It also explains why we use those records, how long they may remain available and how you can ask for access or correction.

We may collect your phone number, account identifier, verification status, sign-in details and messages sent through support. Device type, browser version, IP address and access time may also be recorded when needed to protect the account or investigate a sign-in issue.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those references to match account actions and status questions, while your full wallet password or secret credential is not requested through support.

Use the support contact path shown in your account area and state which detail needs correction. Include your account identifier, but do not send your password. We verify the request against the account before changing a phone detail, verification entry or other stored record.

We may use device and sign-in signals to recognise unusual access and help resolve account issues. Cookies can preserve an active session or record a return visit. Browser controls may limit optional cookies, while essential session tools can remain needed for account access.

We retain records for the period needed to operate an account, protect access, resolve a payment question, handle a dispute or meet a legal duty. After that purpose ends, we delete, anonymise or restrict the record where local law permits.

You can submit a deletion request through the account support route. We first confirm your account connection, then assess which records can be removed and which must remain for security, payment tracing or legal duties. Access and eligibility depends on local law.