Reference

pelangi123 Privacy Policy For Your Account

pelangi123 keeps this Privacy Policy practical: it explains the account details we collect, why we use them, how wallet checks work and how you can contact us.

Account dataWallet checksCookie choicesContact rights
pelangi123 pelangi123 Privacy Policy For Your Account
CONTACT PATHS

Privacy Policy Help Beside Your Account

A clear contact path helps when you need to ask about your data rather than a lobby feature.

Account contact Send a policy request through the account support path and include your registered phone number, request type and any relevant date so we can locate the correct record.
Wallet receipt For DANA, OVO, GoPay, QRIS or bank transfer questions, include the payment reference only. Do not send a wallet PIN, password or one-time security code.
Access concern If a sign-in or device check blocks your account, describe the message and device path. We may ask for account verification before discussing protected data.
HANDLING YOUR DATA

What We Do With Account And Cookie Data

We keep policy handling tied to a clear operational purpose: account access, payment reconciliation, security, support and legal duties.

Data collected

We may process your name, phone number, login events, device signals, support messages and payment references. We collect only the details needed for the account task, security check or legal record involved.

Cookie choices

Cookies and similar browser storage can remember session settings and help us understand account navigation. You can adjust browser controls, although disabling them may interrupt sign-in or policy preferences.

Account security

We use account verification, session controls and device checks to reduce unauthorised access. Keep your password private and never place a wallet PIN or one-time code in a support message.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us match a cashier event. We use the reference for reconciliation and do not need your wallet password to check status.

Retention

We retain account and transaction records for as long as needed for the stated service, security checks, dispute handling and legal duties. When a record is no longer needed, our process removes or de-identifies it.

Change requests

You can ask us to correct account data, explain its use, provide an applicable copy or address a deletion request. We may verify ownership first and may retain limited records where a legal duty applies.

Privacy Policy Answers For pelangi123

These Privacy Policy answers address the searches we hear most often before account access. They cover the data behind sign-in, wallet matching, mobile cookies, retention and contact requests, so you can decide what to share before opening an account where local law permits.

It covers account details, login activity, device signals, cookies, support messages and payment references used for pelangi123 account access, security, reconciliation, support and applicable legal duties.

No. We may record a DANA or QRIS transaction reference to match status, but you should never send a wallet password, PIN or one-time code through our account contact path.

Use the account support path, state whether you want correction, access, an explanation or deletion, and provide your registered phone number. We may verify ownership before handling the request.

Device and browser signals help us recognise a new sign-in, maintain a secure session and identify unusual access. On mobile, these checks can occur before protected account details are displayed.

Retention depends on the record and its purpose. We keep account, support and payment references while needed for service, security, dispute handling or legal duties, then remove or de-identify them.

You can adjust cookie controls in your browser. Some choices may affect sign-in, session continuity or saved policy preferences, so the account path may not behave the same after cookies are disabled.

Yes. Account access and eligibility depend on local law. Some data requests may also be limited where a legal, security or fraud-prevention duty requires us to keep or protect a record.