Reference

neo123 Privacy Policy for Your Account

Our Privacy Policy explains how neo123 handles the details connected with your account, device and wallet activity in Indonesia.

Account dataWallet recordsDevice accessPolicy requests
neo123 neo123 Privacy Policy for Your Account
CONTACT PATHS

Ask About Your Privacy Policy Rights

A clear contact path helps you question a record without sending sensitive details through an unrelated channel.

Account data request Use the account support path to ask what personal details are connected with your neo123 profile. We may verify your phone number or email first, then explain the available access, correction or deletion route under the Privacy Policy.
Wallet record question For a DANA, OVO, GoPay or QRIS record, send the payment reference through account support rather than sharing a password. We use the reference to locate the relevant entry and keep the response focused on your Privacy Policy request.
Receipt and status help If a bank transfer or virtual account receipt does not match your account history, ask for a status check through the same support route. We can explain which transaction data is held and what further identity check may apply.
HANDLING DETAILS

How neo123 Applies This Policy

The Privacy Policy is practical: it follows the account steps you take and the records created by those steps.

Account creation

When you open an account, we collect the details needed to create your profile and support phone verification before account access. The Privacy Policy explains the purpose of each required field and distinguishes it from optional contact details.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a payment to the correct account. We do not need your wallet password or one-time code to investigate a receipt or status question.

Cookies and sessions

Cookies can keep your sign-in session connected and remember selected settings on the device you use. You can manage browser cookie controls, although changing them may affect account access and require another sign-in.

Device security

We may record device, browser and security-event details when you sign in or confirm your phone. These signals help us identify unusual access, protect your account and explain why an additional verification step appeared.

Retention approach

We keep account, support and payment records only for the period needed for the stated purpose, security work or a legal duty. Retention can differ by record type, and the Privacy Policy provides the route for questions about a specific entry.

Correction requests

If your account detail is outdated, contact us through the account support path and identify the field you want changed. We may request confirmation before making an update, and the available action depends on local law.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the account and payment questions we expect you to ask before opening an account. They explain the practical route for checking data, changing details, understanding cookies and raising a payment record concern. If your situation is different, use the account support path and refer to the current wording on this page.

The neo123 Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, support messages and payment references. It explains why we use each category, how we protect access and how you can ask about correction, access or deletion where local law permits.

Yes. The Privacy Policy covers the DANA, OVO, GoPay and QRIS references needed to match a payment with your account and answer a receipt question. It can also cover bank transfer and virtual account records, while wallet passwords and one-time codes should not be shared.

Use the support route inside your account and ask for a data access request under the Privacy Policy. We may confirm your email or phone number before responding, because the request must be tied to the correct account. The available response depends on local law.

You can contact account support and name the detail that needs correction, such as a phone number or account email. We may ask for an identity check before changing it. Payment references may need a separate reconciliation step, and the action depends on local law.

Cookies can maintain a sign-in session and remember device settings, while security signals can help identify unusual access. You can adjust cookie controls in your browser, but blocking required cookies may send you back to login or interrupt account access.

We retain payment and support records for the period needed for account service, security checks or a legal duty. The period can differ between a QRIS receipt, a bank transfer reference and a support message. Ask through account support about a specific record.

Raise the request through the support path linked inside your account and label it as a Privacy Policy matter. Include only the details needed to identify the issue, such as a reference number, and never send a wallet password or one-time code.