Reference

pitontoto Privacy Policy for Your Account

Our Privacy Policy explains what pitontoto collects when you open an account, use the mobile lobby, or check wallet status through DANA, OVO, GoPay and QRIS.

Clear data purposesWallet reference handlingAccount access choicesCookie controls
pitontoto pitontoto Privacy Policy for Your Account
POLICY HELP PATH

Get Help With Privacy Policy Requests

A clear support path matters when you want to ask about a Privacy Policy record or correct an account detail.

Account record request Ask us which account details we hold and why they are used. Include the email or phone detail linked to your account, but never send a password, security code or full wallet login during a Privacy Policy request.
Wallet status query For a DANA, OVO, GoPay or QRIS record, provide the visible reference, date and status shown in your account area. We can compare that reference with our records while keeping your wallet credentials outside the support exchange.
Correction route If your name, phone detail or account record needs correction, tell us what appears wrong and what should replace it. We may ask for an account verification step before changing details tied to access or payment history.
DATA HANDLING PRACTICE

What We Do With Your Account Details

We keep this Privacy Policy practical: each record has a reason connected to account access, payment matching, security or a request you make.

Account details

We use contact and verification details to create your account, confirm requested changes and connect support replies to the correct record. Providing accurate details helps us avoid sending a correction or access response to the wrong account.

Cookies

Cookies may keep your session active, remember selected settings and help us understand whether a login request comes from the same browser. You can manage browser cookie controls, although disabling them may interrupt account access or saved preferences.

Device signals

The mobile path may record device type, browser version, approximate session timing and security events. These signals help us compare a new login with prior account activity; they are not a request for access to your personal files.

Account security

We use verification steps and login records to protect account access. If a sign-in looks unusual, we may ask you to confirm account details before discussing payment references or changing contact information connected with the account.

Retention periods

We keep records for the period needed to complete the related account, payment, security or legal purpose. When a record is no longer needed for that purpose, our handling follows the retention process that applies to the record type.

Changes and contact

You can request an explanation, correction or eligible deletion through the account support route. Tell us the record involved and your requested change; we may verify ownership first so another person cannot alter your account details.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account questions you are most likely to have before opening an account or checking a wallet status. We keep the wording specific to pitontoto records, including device activity, cookies, payment references and account corrections. If a question concerns eligibility or location, access depends on local law.

It covers details connected with your account, verification, device sessions, cookies, support requests and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains purposes, retention, security handling and the routes available for eligible corrections.

We use contact details to create and verify your account, connect a support request to the right record and confirm requested changes. Accurate details reduce access confusion. We may ask for an account verification step before changing contact data tied to login or payment records.

Our ordinary payment matching process uses references, timestamps and status results rather than your DANA, OVO, GoPay or QRIS password. Do not send wallet passwords or security codes through support. We use the reference shown in your account area to investigate a status.

The mobile account path may record device type, browser version, session timing and security events connected with a login. We do not need access to your personal files for this purpose. These records help compare unfamiliar activity with the account verification step.

Cookies can keep your account session active, remember selected settings and support security checks. You can adjust cookie controls in your browser. If you block required cookies, the login path or saved preferences may not work as expected, while optional cookie handling follows your available settings.

Yes. Use the account support route and identify the record, explain what appears wrong and provide the corrected detail. We may verify account ownership before making a change. This protects your contact, access and payment records from an unauthorised request.

The retention period depends on why a record exists, such as account access, payment matching, security or a legal requirement. We keep it for the applicable operational period, then follow the relevant removal process. You can ask support which record category your request concerns.