Reference

pedro88 Privacy Policy For Your Account

Our pedro88 Privacy Policy shows how we use account, wallet and device data when you open your account, complete phone verification or use DANA and QRIS.

Account dataWallet recordsCookie choicesPhone verification
pedro88 pedro88 Privacy Policy For Your Account
CONTACT ROUTES

Three Ways To Ask About Privacy

A clear contact path helps you resolve a data concern without sharing more than necessary. Use the support route connected to your account when a phone verification record, wallet reference or cookie choice needs attention. We may ask for limited account details to locate the correct record, but we will not ask for your password, wallet PIN or full payment credentials.

Team online

Account access

Use support chat if your phone verification or sign-in record looks wrong. Send your registered contact detail and a short description; keep passwords and wallet PINs out of the message.

Wallet record

For a DANA, OVO, GoPay or QRIS receipt question, follow the cashier support path and provide the transaction reference. We use it to locate payment status without requesting your wallet password.

Data request

Ask us to access, correct or remove eligible account data through support. Include the request type and registered contact detail so we can confirm ownership before making a change.

CONTROL LAYER

Six Practical Privacy Safeguards

Privacy work is handled through ordinary account controls rather than vague promises. We separate sign-in activity from payment references, limit who can assist with account requests and use device session records to…

Data collected

We use account contact details, phone verification results, sign-in events, device session markers and payment references. These records support account access, receipt matching and security checks tied to your activity.

Cookie choices

Cookies can remember a mobile browser session and selected settings. You can adjust cookie controls in your browser, although disabling some cookies may require another sign-in before account data is displayed.

Account security

Before changing sensitive account data, we confirm the request against your registered contact details. Support will not request your password, wallet PIN or complete DANA, OVO, GoPay or QRIS credentials.

Retention period

We retain account and payment records only for as long as needed for account administration, receipt matching, security checks or a legal requirement. After that period, records are deleted or separated from direct identifiers.

Your request

You can ask for a copy, correction or deletion of eligible personal data. We may confirm your identity first, then explain any record that must remain for payment, security or legal reasons.

Contact ownership

Send privacy requests through the account support route rather than a payment wallet. We match the registered contact detail to the account before discussing records, including activity from a mobile device.

Privacy Policy Questions From Indonesia

These answers address the privacy searches we hear most often from Indonesian customers. They cover the data attached to an account, payment references from local rails, mobile sessions and the steps for asking us to change or remove eligible records.

It covers account details, phone verification, sign-in events, device session markers, cookie choices and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

No. We use payment status and reference data to match a transaction, but support does not ask for your wallet PIN, password or complete payment credentials during a privacy request.

Yes. Contact support through the registered account route and ask for a data copy. We confirm ownership using limited contact details before describing or releasing eligible records.

Send the correction request through support with your registered contact detail and the record that appears wrong. We may request a verification step before updating account or payment-related data.

A mobile browser can create session markers that keep your account connected during navigation and help identify unusual access. These markers are handled as part of account security and cookie controls.

We keep records for account administration, payment matching, security checks or legal needs. When a record is no longer needed, we delete it or remove direct links to your identity.

Access and eligibility depends on local law. Before opening an account or sending a privacy request, confirm that use is permitted in your location and follow the account checks shown to you.