Reference

posototo Privacy Policy for Your Account

posototo Privacy Policy explains what we collect when you create an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Clear collection rulesWallet data contextAccount access choicesPrivacy contact path
posototo posototo Privacy Policy for Your Account
CONTACT ROUTES

Privacy Questions Near Your Account Path

A direct support route helps when you need to ask about a record, correct an account detail or understand a wallet reference.

Account access request Use the account support path to ask which personal details we hold, why a…
Wallet reference check For DANA, OVO, GoPay or QRIS questions, share the payment reference and date rather…
Correction request Tell our support desk which account field needs changing and why.
HANDLING DETAILS

Six Practical Privacy Controls We Use

Privacy work is tied to ordinary account actions rather than hidden steps. When you move from a phone login to the lobby, we record technical signals needed for access and security; when…

Account data

We use contact and verification details to create your account, confirm that the sign-in request matches you, and connect support replies to the correct account without exposing unrelated records.

Device signals

Your browser, device type, language setting and sign-in time can help us detect an unusual access attempt. These signals support account protection and are not a replacement for your password.

Cookie choices

Cookies can keep a session available while you move from login to the lobby and may remember basic preferences. You can manage cookie settings through your browser when that option is provided.

Payment references

For QRIS, bank transfer and virtual account activity, we handle transaction references and status details needed to reconcile an account. We do not need your wallet PIN or banking password.

Retention period

We keep account, support and transaction records for the period needed for security, service administration or legal duties. When that need ends, records are deleted, anonymised or restricted.

Change or deletion

Ask us to correct, access or remove relevant personal data through support. We check account control first, explain any legal reason for keeping a record, and respond where local law permits.

Privacy Policy Questions Before Account Access

These Privacy Policy answers address the practical searches you may make before creating an account from Indonesia. We focus on account records, device access, cookies, local wallets and requests sent through the support path. If a request concerns eligibility or regional access, it depends on local law and is handled where local law permits.

It covers account details, phone verification, device and sign-in records, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps connect an account to the person requesting access and helps us identify unusual sign-in attempts. We use the result for account security and support handling, subject to local law.

We handle the payment reference and status needed to match a DANA or QRIS transaction to your account. Do not send a wallet PIN, banking password or complete secret credential to support.

Yes, send an account data request through the support path and identify the email or phone linked to your account. We may verify control first, then respond where local law permits.

Describe the incorrect field through support and provide the account detail needed to locate it. We may request a verification step before changing the record, especially when wallet status is involved.

Retention depends on the purpose: account security, support handling, transaction reconciliation or legal duties. When a record is no longer needed, we delete, anonymise or restrict it under our process.

Yes, ask support which cookie or session issue you are seeing, or manage available settings in your mobile browser. Cookies may support login continuity between account access and the lobby.