Reference

idnscore Privacy Policy For Your Account

Our idnscore Privacy Policy explains which account, device and payment details we collect when you open an account or use the lobby.

Clear data purposesWallet record detailAccount access choicesPrivacy contact path
idnscore idnscore Privacy Policy For Your Account
CONTACT ROUTES

Get Privacy Help Near Your Account

A clear contact route helps you ask what we hold, why we use it or how to correct an account record.

Account data request Ask our account support chat for a copy of personal data linked to your account. Include your registered phone or email so we can verify the request before responding.
Wallet record check For DANA, OVO, GoPay or QRIS questions, send the receipt reference and approximate time. We use those details to locate a status record without requesting your wallet PIN.
Correction path If your phone, email or account name needs correction, contact support from the account area. We may ask for an account step to confirm that the request comes from you.
HANDLING PRACTICES

Six Ways We Handle Account Data

Privacy work covers more than a payment record. We separate login protection, cookie settings, account activity and support evidence so each purpose has a clear reason.

Account security

We use phone or email verification before account access and may record device signals, login time and session details to detect unusual access. Never send us your password, PIN or one-time code.

Cookies and devices

Cookies and similar device storage can remember session choices, help keep the account signed in and show the correct wallet status. You can manage browser permissions, though some account functions may then need another check.

Payment matching

A payment reference, amount and status can be retained to reconcile DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity with the correct account.

Limited access

Access to personal data is restricted to staff or service partners who need it for account support, security, payment matching or legal duties. We do not ask partners to use it for unrelated purposes.

Retention periods

We keep records for as long as needed for the stated purpose, account support, dispute handling or legal requirements. When a record is no longer needed, we remove or securely separate it.

Your requests

You can ask for access, correction, deletion or a purpose explanation through support. We verify the account connection first, then assess the request under applicable law and explain any limit.

Privacy Policy Answers For idnscore Accounts

These answers address the questions we receive most often about the idnscore Privacy Policy. They cover account records, cookies, payment references, device checks and the steps needed to contact us from Indonesia, where local law permits.

It covers account details, phone or email verification, device and cookie data, payment references, support messages and activity records needed to protect access or respond to your request.

We use a DANA or QRIS reference to match a cashier request with its status. We may also retain timing and amount details, but we do not need your wallet PIN.

Yes. It explains that cookies can maintain a session, remember account choices and help display wallet status. Browser controls can restrict them, although another account check may be required.

Contact our account support chat from the account area and provide your registered phone or email. We verify the account connection before sending a data copy or explaining the next step.

You can request a correction through support. Include the current account identifier and the change needed; we may ask for phone verification before updating the record.

We retain payment references while needed for reconciliation, support, disputes or legal duties. Once the purpose ends, we remove or securely separate the record under our retention process.

Yes. Data access, correction and deletion requests are assessed where local law permits. If a legal or security reason limits a request, we explain that reason through the support route.