Reference

Privacy Policy For Your pedri89 Account

Our Privacy Policy explains what we collect when you open a pedri89 account, sign in from a phone, or use DANA, OVO, GoPay and QRIS at the cashier.

Account clarityWallet data contextCookie choicesContact route
pedri89 Privacy Policy For Your pedri89 Account
ASK OUR TEAM

Where To Ask About Privacy Policy

A clear contact route matters when a payment record or account detail looks unfamiliar. Our support path is designed for privacy questions rather than general lobby requests: tell us which account step you reached, what device you used and whether the matter concerns DANA, OVO, GoPay, QRIS or a bank transfer. We may ask for a reference or verified account detail so we can respond without exposing information to the wrong person.

Team online

Account access

If your phone verification or login record needs checking, contact us through the account support route. Include the registered contact detail and device path, but never send a password or one-time code. We use the account step to locate the relevant privacy record.

Wallet status

For a DANA, OVO, GoPay or QRIS record, share the payment reference and status shown at the cashier. We can examine whether the entry is pending, matched or reversed without asking you to repeat a full wallet credential.

Privacy request

To ask for a copy, correction or removal of personal data, state the request clearly and identify the account contact used during registration. We may verify ownership before making a change, because privacy requests must not expose another person’s account.

DATA HANDLING

How pedri89 Handles Account Data

We separate the details needed to operate an account from the activity signals used to protect it. Registration, phone verification and payment references support account administration, while device and login events help…

Registration details

When you open an account, we use the contact details you provide to create the account record and complete phone verification. Keeping those details current helps us recognise your request when you ask to inspect, correct or remove personal data.

Payment records

A wallet or bank transaction can create a reference, amount, timestamp and status in our records. We use that information to match the cashier event to your account, investigate a receipt and separate your payment history from another account.

Cookies

Cookies can remember session settings and help us understand whether a sign-in request belongs to the same browser. You can adjust browser cookie controls, although disabling them may require another login when you return from a mobile or desktop session.

Device signals

We may record device type, browser details, approximate session timing and login events to detect unusual access. These signals help us protect the account when your phone moves from login to the lobby or when a new desktop session appears.

Account protection

We do not ask you to send a password or one-time verification code through a privacy request. If a request concerns sensitive account data, we first check account ownership and limit the response to the information connected with your verified account.

Retention and changes

We retain personal data only while it supports account operation, payment reconciliation, security checks or a required legal purpose. You can request access, correction or deletion; we will explain any restriction when a record must remain for a documented reason.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions you may have before opening an account or connecting an Indonesian wallet. We explain why we request phone verification, how payment references are handled and what to include when you ask us to change a record. If a question depends on your location, the answer uses our stated local-law wording.

It covers account registration, phone verification, login and device signals, cookies, payment references and support requests. It explains how we use those details to provide the requested account path, reconcile DANA, OVO, GoPay or QRIS activity, protect access and respond to privacy requests.

We use phone verification before account access to connect the sign-in request with the account contact you provided. This helps us reduce mistaken access and confirm ownership when you ask about a payment record, device event or change to your personal data.

Yes. The Privacy Policy includes payment references linked to DANA, OVO, GoPay and QRIS, along with bank transfer and virtual account records. We use the reference, status and timing to match a cashier event to your account without requesting your wallet password.

You can request access to personal data connected with your verified account through the privacy contact path. Tell us the registered contact detail and the category you want, such as account, cookie, device or payment data. We may verify ownership before sending a response.

Send a correction request through support and identify the account detail that is inaccurate. Include the relevant account step, such as registration or phone verification, so we can locate it. We will check ownership and update the record when the request can be confirmed.

We keep personal data while it is needed for account operation, payment reconciliation, security checks, support or a documented legal purpose. The period can vary by record type. When retention is no longer needed, we remove, anonymise or restrict the data where appropriate.

Yes. The policy applies when you sign in through a mobile browser, use cookies, move from login to the lobby or check a wallet status. Device and session signals may be recorded for access protection, while cookie settings remain available through your browser controls.