Reference

pintoto Privacy Policy for Your Account

The pintoto Privacy Policy explains how we collect, use and protect details connected with your account, device and payment activity in Indonesia.

Account dataWallet recordsCookie choicesAccess depends on local law
pintoto pintoto Privacy Policy for Your Account
CONTACT PATHS

Privacy Help Beside Your Account Steps

Questions about this Privacy Policy should reach us through the support route connected with your account, because an authenticated request lets us check the correct record without asking you to send sensitive details in an open message. Tell us whether your question concerns login data, cookies, a wallet receipt or a requested correction. If you are in Makassar or elsewhere in Indonesia, the same account support path applies, subject to local law. We may ask for account details and phone verification before discussing private records.

Team online

Account support

Use the signed-in support path for a privacy question about your account, phone verification or device access. We can link your request to the right account record and avoid exposing details through an unverified conversation.

Wallet status

For a privacy question connected with DANA, OVO, GoPay or QRIS, include the transaction reference shown in your account. We use that reference to locate the relevant status without requesting your wallet password or full secret credentials.

Data request

Ask support to review, correct or explain personal data held for your account. We may confirm your phone number and account step first, then tell you what can be changed or supplied where local law permits.

HANDLING DETAILS

What This Privacy Policy Covers

We separate practical account handling from general browsing activity so you can understand why each data type appears in our records.

Account records

When you open an account, we record details needed to create and maintain access, including your contact information and phone verification status. We use these records to authenticate you and to respond to an account-specific Privacy Policy request.

Device signals

A mobile browser or desktop session may send device and connection signals during login. We use them to remember a session where permitted and to examine unusual access. We do not treat a device signal as a replacement for your account verification.

Cookies

Cookies can retain sign-in preferences, security settings and page choices. You can manage browser cookie controls, although removing required cookies may affect access to account pages. Optional cookie use remains subject to the choices available in your browser or account path.

Security checks

We use account checks around login, phone verification and payment-status questions to reduce unauthorised disclosure. Support may ask you to confirm an account step, but we do not ask for your wallet password or private authentication code.

Retention

We keep personal records only for the period connected with account operation, security review, dispute handling or a legal requirement. A receipt reference for QRIS, DANA or bank transfer may remain after the account action so the transaction history can be reconciled.

Your requests

You can ask us to access, correct or clarify personal data through the account support path. Where local law permits, you may also ask about deletion or restriction; we will explain any record that must remain for security or legal reasons.

Privacy Policy Answers For pintoto

These Privacy Policy answers address the account and data questions we expect before registration. They cover phone verification, mobile browsing, cookies, local wallets, access requests and contact steps. If your situation is not listed, use the account support route and describe the specific record or account action involved. We will handle the request according to this policy and where local law permits.

The pintoto Privacy Policy covers account details, phone verification, device signals, cookies, support messages and payment references. It explains why we use each category, how we protect account access, how long records may remain and how you can ask us to correct or clarify your data.

Phone verification helps us confirm that an account request is connected with the correct person before access or support discussion. It can also help us investigate an unusual login. We use the verification status for account security and do not treat it as permission to request your wallet password.

Yes. The Privacy Policy covers payment references and wallet-status records created when you use DANA, OVO, GoPay or QRIS through the account path. We use those references to match a receipt or status question, not to collect your private wallet password.

On a mobile browser, cookies may remember a session, security preference or page setting. Our Privacy Policy treats required cookies as part of account access, while browser controls can manage optional choices. Removing required cookies may mean that you need to verify your account again.

You can contact account support and request access to, or correction of, personal data linked with your account. We may confirm your phone number or another account step first. Where local law permits, we will explain available deletion or restriction options and any reason a record must remain.

We keep records for the period needed to operate account access, examine security events, resolve disputes or meet a legal duty. A QRIS, wallet, bank transfer or virtual account reference may remain while reconciliation or a related request is open, then be handled under our retention process.

Use the signed-in account support path and state whether your question concerns login, cookies, device access, phone verification or a wallet reference. Giving the relevant account step helps us route the request. Access and any available action depend on local law, including for requests from Indonesia.