Reference

gps189 Privacy Policy for Your Account

The gps189 Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, and use local payment routes such as DANA…

Account clarityWallet recordsDevice controlsRequest access
gps189 gps189 Privacy Policy for Your Account
CONTACT ROUTES

Privacy Help Beside Account Support

A clear contact route helps you resolve a privacy question without guessing which team to reach.

Account privacy Send an account help request when you want to know which contact detail, verification…
Wallet receipt For DANA, OVO, GoPay or QRIS questions, attach the receipt reference and state the…
Access request Ask us to access, correct or remove eligible account data through the same support…
DATA PRACTICES

How gps189 Handles Privacy Details

We separate the data needed to operate an account from details used to protect access and answer support requests.

Account data

We collect details you enter during account creation and sign-in, such as contact details and verification state. These records support account access and privacy replies. We do not ask for a wallet password to match a DANA, OVO, GoPay or QRIS receipt.

Cookies and devices

Cookies and device signals help keep a signed-in session working, remember selected settings and identify unusual access. A phone browser may create different session records from a desktop browser. You can manage browser cookies, although some account functions may then require another sign-in.

Account security

Before we disclose or change private account data, we may compare your request with the phone verification step and recent sign-in context. This reduces the chance that another person changes your contact details or receives a reply about your account.

Payment records

For a bank transfer or virtual account, we use the reference, amount status and account match needed to reconcile the entry. For DANA, OVO, GoPay and QRIS, we use the payment reference and status rather than your wallet password or unrelated wallet activity.

Retention choices

We remove or anonymise records when they are no longer needed for the purpose that brought them into our systems, subject to account security, dispute handling and legal retention needs. A removal request may therefore receive a partial result under local law.

Policy requests

Contact us through account help with the request type, your account contact and any relevant receipt reference. We may ask for phone verification, explain the decision and identify any legal reason for keeping a record. Access and correction depend on local law.

Privacy Policy Answers for Indonesia

These Privacy Policy answers cover the searches we hear most often before an account is opened or a wallet receipt is checked. We keep each answer tied to an account step, device path or payment record so you can decide what to send through support. The available action depends on local law and applies where local law permits.

The gps189 Privacy Policy covers contact details, phone verification state, sign-in records, device signals, support messages and transaction references needed for account operation and security. We use those details for the stated service purpose, account protection and eligible requests under local law.

We do not need your wallet password to match a payment. For DANA, OVO, GoPay or QRIS, we use a receipt or transaction reference and its status. If you contact support, send the reference only and leave your wallet password out of the message.

Use the account help channel and state that you want a Privacy Policy data request. Include your account contact and the record type, such as phone verification or a QRIS receipt. We may request a phone check before replying, and access depends on local law.

You can ask us to correct an eligible account detail through account support. We may compare the request with your phone verification step and recent sign-in context before making a change. If a record must be retained for security, disputes or law, we will explain that limit.

Cookies help maintain a signed-in session and remember selected settings, while device signals help us identify unusual access. Your mobile browser and desktop browser can create separate session records. You can manage cookies in the browser, but some account actions may require another sign-in.

We keep each record for the period needed for its stated purpose, account security, dispute handling or a legal requirement. A bank transfer, virtual account or wallet reference may therefore remain after a payment is matched. Removal requests are assessed where local law permits.

Send the concern through our account help route and describe whether it involves account data, a device session, cookies or a payment receipt. Include only the details needed to locate the record. We may verify your phone before discussing private account data or changing it.