Reference

Privacy Policy for Your posototo Account

posototo Privacy Policy explains what we collect when you create an account, verify your phone, open the lobby on mobile, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice choicesCookie controls
posototo Privacy Policy for Your posototo Account
CONTACT PATHS

Get Privacy Help Along Your Account Path

A clear contact route helps when a Privacy Policy question involves a phone check, wallet status or a device sign-in.

Account privacy request Ask us to access, correct or explain personal data connected with your account. We may request account details or phone verification before discussing records, so a private request is matched to the right person.
Wallet record check For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, share the reference and status shown in your account. We use that reference to separate payment history from unrelated account activity.
Login and device help If a phone check or mobile sign-in does not match your records, contact support through the account path and explain the device change. We can review the access event without asking you to reveal a password.
HANDLING YOUR DATA

What We Do With Your Account Data

Privacy work is part of the account flow, not a separate promise hidden from you. We separate sign-in details, wallet references, device signals and support correspondence so each record has a clear…

Account collection

When you create an account, we collect the details needed to establish access and complete phone verification. Login events and account settings help us recognise your session without treating your password as a support credential.

Wallet matching

DANA, OVO, GoPay and QRIS references help us connect a wallet status or receipt to the correct account. Bank transfer and virtual account records are used for reconciliation, not for collecting unrelated device content.

Device signals

We may record browser type, operating system, approximate access time and security events when you move from login to the mobile lobby. These signals help identify unusual access without reading files, contacts or messages on your device.

Cookie choices

Session cookies can keep your login path and selected settings working between pages. You can adjust cookie controls in your browser; limiting required cookies may mean that phone verification or account access must be repeated.

Retention approach

We keep account, payment-reference and support records only for the period needed for access, reconciliation, dispute handling and applicable legal duties. When a record no longer serves one of those purposes, we remove it or use a form that no longer identifies you.

Change requests

You can ask us to correct inaccurate account details, explain a data use, or request deletion where applicable. Send the request through the account support path; we verify ownership before changing records linked to phone or wallet activity.

Privacy Policy Questions Before Account Access

These Privacy Policy answers cover the practical points you may check before opening an account from Indonesia. We explain the account step, the device information involved, the wallet references connected with payment status and the route for requesting a copy or correction. If a question depends on your location, the answer remains subject to local law.

It covers data collected during account creation, phone verification, login, mobile browsing, wallet status checks and support requests. It also explains cookies, retention, security events, correction requests and deletion requests where applicable. Access and eligibility depends on local law.

Phone verification helps connect account access to the details you submitted and helps us respond safely to account requests. We may use the verification result when you ask about login history, a device change or records connected with DANA, OVO, GoPay or QRIS.

Yes. The Privacy Policy covers references and status details linked with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. We use those records to match receipts, resolve status questions and maintain an accurate account history.

We may record browser type, operating system, access time, session details and security signals related to the sign-in path. We do not need to read your photos, contacts or messages for this purpose. Restricting required cookies can make a session or phone check repeat.

Use the support path linked to your account and state whether you want access, correction, an explanation or deletion where applicable. Include your account identifier and relevant date. We verify ownership before disclosing or changing records connected with phone or wallet activity.

We retain account, payment-reference and support records for the period needed for access, reconciliation, dispute handling and applicable legal duties. Retention can differ by record type. When the purpose ends, we remove the record or de-identify it where appropriate.

Yes. Send your question through the account support route and identify the decision or record involved, such as a login check, cookie choice or wallet status. We may request phone verification so the response goes to the account holder and not another person.