Reference

Open prediksi taiwan Privacy Policy

prediksi taiwan Privacy Policy explains what we collect when you open an account, sign in from a phone, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice accessPolicy choices
prediksi taiwan Open prediksi taiwan Privacy Policy
HELP PATH

Switch to our privacy support path

Privacy questions should reach the team that can connect your request with the right account record. Use the support route shown beside account access and include the email or phone detail attached to your profile, without sending a wallet password or one-time code. We can help with a data request, a receipt reference, a sign-in concern or a correction request. If your account is open on mobile, keep the support page in the same browser path so we can match the request accurately.

Team online

Privacy request

Ask us to confirm the data connected with your account, explain how it is used, or correct a detail that no longer matches your current record. Include your account contact detail so we can verify the request before discussing personal data.

Wallet record

If a DANA, OVO, GoPay or QRIS receipt appears with the wrong account status, send the reference through our support path. We use the payment reference to locate the relevant record without asking you to disclose a wallet password.

Access concern

When a login or phone verification step stalls, tell us the device type, approximate sign-in time and account contact detail. We use those points to check access records and protect your account before making any change.

DATA PRACTICE

Browse how data stays controlled

We handle privacy through practical account steps rather than broad promises. A phone, desktop browser and wallet connection can create different records, so we separate sign-in activity, payment references and support correspondence…

Account collection

We collect the details needed to open and maintain your account, including contact data and the phone verification result before access. We avoid asking for wallet passwords, one-time codes or unrelated personal details during a privacy request.

Cookie controls

Cookies can keep a session active, remember a selected setting and help us identify an interrupted sign-in. You can manage browser cookie controls on your phone or desktop, although changing them may affect account access and saved preferences.

Payment matching

A DANA, OVO, GoPay or QRIS reference helps us match a wallet event with the correct account record. Bank transfer and virtual account references are handled for the same checking purpose, not as a request for your banking password.

Security checks

We compare account contact details, phone verification and sign-in records when access looks unusual. This can mean asking you to repeat an account step before we discuss data or change a profile detail.

Retention period

We retain account, payment and support records for as long as they are needed for account service, security review or legal duties. When a record is no longer needed, we remove it or separate it from direct account identification.

Your request

You can ask what personal data we hold, request a correction, question a use, or ask whether deletion is available. Send the request through our support route with your account contact detail so we can confirm identity safely.

Check Privacy Policy answers before access

These Privacy Policy answers focus on the account actions you are most likely to take from Indonesia. We explain what happens when you open an account, verify a phone, connect a wallet, use a mobile browser or contact support about a record. If your situation is not listed, use the privacy support path and include only the details needed to identify your account. Where local law permits, we will assess your request against the applicable access, correction and deletion rules.

It covers account details, phone verification, device and sign-in records, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains why we use those records for access, security, account support and legal duties.

Phone verification helps us connect an account request with the correct contact detail before access is provided. It also gives us a security check when sign-in activity changes. We do not need your wallet password or one-time wallet code for this account step.

The policy covers payment references, wallet status and related account records for DANA, OVO, GoPay and QRIS. It can also cover bank transfer and virtual account references used to check a receipt. We do not ask you to share banking passwords through support.

Yes. The same policy applies when you sign in through a mobile browser, switch to the lobby or check a wallet status from your phone. Device, session and cookie records may differ from desktop records, but your rights and request path remain the same.

Use our privacy support route and include the account email or phone detail linked to your profile, plus a short description of the correction. We verify that you control the account before changing data, and we will explain if a record must remain for security or legal duties.

You can ask whether deletion is available for a particular record. We assess the request under applicable rules because some account, payment or security records may need to remain for legal duties or an unresolved account matter. Where local law permits, we will remove eligible data.

Use the privacy support path beside account access and identify your account with the linked email or phone detail. For a DANA, OVO, GoPay or QRIS issue, add the payment reference rather than a password. This lets us route the concern without exposing extra data.