Reference

Read popototo Privacy Policy Before Opening Access

Our popototo Privacy Policy explains what account data we collect, why we use it, and how you can ask us to change or remove it.

Account dataWallet recordsCookie choicesContact route
popototo Read popototo Privacy Policy Before Opening Access
ACCOUNT HELP ROUTE

Contact Us About Your Account Data

A clear contact route helps when a Privacy Policy question involves your account rather than a general reading of the page. Send your request through the account support path and include the sign-in phone number, the data request you are making, and any relevant payment reference. We may ask for account details to confirm that the request comes from you. Keep DANA, OVO, GoPay, QRIS, bank transfer, or virtual account receipts available when your question concerns a wallet record. We will use the contact details supplied for handling that request.

Team online

Data request

Ask us to correct account details, explain a stored field, or provide a copy of data connected with your popototo account. Include your verified phone number so we can match the request without asking you to send a full payment credential.

Wallet record

For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account question, attach the payment reference and date. We use those details to locate the relevant status while avoiding a request for your wallet password or personal PIN.

Account support

If sign-in or phone verification blocks a privacy request, use the account support route and describe the step that stopped you. We may request identity details already linked to the account before discussing personal data or changing contact details.

DATA CONTROL LAYERS

Protect Your Data Across Mobile Wallet Steps

We handle Privacy Policy questions through practical account controls rather than broad promises. Phone verification helps connect an account request to the correct account, while device and session records can help us…

Account creation

When you open an account, we collect the details needed for the account path and phone verification. We use those details to provide sign-in access, connect privacy requests to you, and maintain an accurate account record where local law permits.

Payment matching

A wallet or bank reference helps us match a DANA, OVO, GoPay, QRIS, virtual account, or bank transfer event to the right account. We record status and reconciliation details, not your wallet PIN or banking password.

Device sessions

When you move from mobile login to the lobby, technical session data may record device type, browser details, and sign-in time. We use this limited context to maintain sessions and investigate access activity that does not match your account pattern.

Cookie choices

Cookies can keep a sign-in session active, remember a language or display choice, and support page operation. You can adjust browser cookie controls, but refusing necessary cookies may require another login or prevent parts of the account path from working.

Retention periods

We keep account, payment, support, and security records for the periods described in the Privacy Policy. Retention can continue after account closure when needed for legal duties, transaction reconciliation, dispute handling, or protection against account misuse.

Change requests

You can ask us to correct, access, or delete eligible personal data through the account support route. We first confirm the request belongs to you, then explain any data that must remain because a legal or payment record requirement applies.

Find Answers About Your Privacy Policy

These Privacy Policy answers address the account questions we expect before you submit a phone number or use a wallet route. Each answer points back to a practical step, such as checking a QRIS receipt, changing a cookie setting, or sending a verified request through account support. If your situation is not covered, contact us with the smallest useful set of account details. Access and eligibility remain subject to local law.

It covers account and phone verification data, sign-in and device signals, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer, and virtual account routes. It also explains use, retention, security handling, and requests to access or change eligible data.

Phone verification helps us connect account access and privacy requests to the correct person. It can also support account recovery and reduce mistaken changes to contact details. We use the phone number for these account purposes and handle it under the Privacy Policy where local law permits.

No. Payment processing can provide a transaction reference, status, time, amount, and reconciliation detail, but you should never send us a DANA, OVO, GoPay, or QRIS PIN. We may ask for a receipt reference when checking a payment record.

Use the account support route and state whether you want access, correction, or deletion of eligible data. Include your verified phone number and a clear description of the request. We may confirm account ownership before sharing data or changing a stored detail.

Cookies and similar tools may keep a mobile session active, remember a display choice, and support account pages. You can manage them in your browser settings. If you block necessary cookies, you may need to sign in again or lose part of the account path.

The retention period depends on the type of record and the purpose described in the Privacy Policy. Account, payment, support, and security records may remain after closure when needed for legal duties, reconciliation, disputes, or protection against misuse.

You can submit a deletion request through account support, and we will assess which data can be removed. Some payment, legal, or security records may need to remain for the period stated in the Privacy Policy. We will explain the result of the request.