Reference

pisangtoto Privacy Policy for Your Account

pisangtoto Privacy Policy explains how we use account details, phone verification records, device signals and wallet references when you access our services in Indonesia.

Account dataWallet referencesCookie choicesAccess requests
pisangtoto pisangtoto Privacy Policy for Your Account
DIRECT HELP PATHS

Get Privacy Help Near Account Access

A privacy question should not leave you searching through unrelated pages. We keep the contact route close to account access so you can ask about a phone record, device entry, cookie choice or wallet reference in one message. Include the account contact detail you used and the specific request, while leaving out passwords and wallet credentials. Our support team can then confirm the next step.

Team online

Account privacy request

Use the support path connected to your account and state whether you want access, correction or deletion. We may ask for account details to confirm that the request comes from you.

Payment reference question

For DANA, OVO, GoPay or QRIS records, share the transaction reference and date rather than a wallet password. We use those details to locate the relevant payment entry.

Login or device concern

If an unfamiliar device entry appears, contact support through the account help path and mention the device type and sign-in time. We can explain the security record and next action.

DATA CONTROL DETAILS

Protect Account Data Across Devices

Privacy depends on small account decisions as much as on written rules. We separate identity details from payment references where practical, use security logs to investigate access, and explain how cookies support…

Collected account details

When you open an account, we use the contact details and phone verification status needed to recognise your account. We do not ask you to send a wallet password through support.

Device and sign-in records

A mobile browser or desktop session may create security records such as device type, browser events and sign-in time. These records help us examine access concerns without storing your device password.

Cookies on the account path

Cookies can support sign-in continuity, security checks and page preferences. You can adjust browser controls, but blocking some cookies may affect account access or require another verification step.

Payment references only

For DANA, QRIS, bank transfer and other listed rails, we use references such as amount, status and timing to match a request. Wallet credentials are not needed for that matching process.

Retention and removal

We keep personal records while they support account security, payment reconciliation, dispute handling or legal duties. When those needs end, we remove or anonymise the data under our retention process.

Requests and corrections

You can ask us to access, correct or delete eligible personal data through the account support path. We first confirm ownership, then explain any lawful reason a record must remain.

Privacy Policy Answers for Your Account

These Privacy Policy answers focus on the questions you may have before opening an account or contacting us from Indonesia. Each response points to a practical account step, device setting or payment reference so you know what to prepare. Where access or eligibility is discussed, it depends on local law and applies where local law permits.

It covers account details, phone verification, device and browser records, cookies, support messages, payment references and retention. It also explains how to request access, correction or deletion where local law permits.

No. Our Privacy Policy describes using payment references, status and timing to match DANA, OVO, GoPay or QRIS activity. Do not send wallet passwords or security codes through account support.

Device type, browser events and sign-in timing can help us identify unusual account access and investigate a login concern. These records support security checks and are handled under the Privacy Policy.

Send an access request through the account support path, identify the account contact detail and describe the records you need. We may verify ownership before responding, subject to local law.

Yes, you can request a correction through support and specify the inaccurate account field. We may ask for verification before changing it, while records required for security or legal duties may remain.

We retain payment references while needed for reconciliation, account security, disputes or legal duties. After those purposes end, we remove or anonymise eligible records according to the retention process.

Some account functions may not work as expected, and you may need another sign-in or verification step. The Privacy Policy explains cookie purposes; your browser controls determine which cookies remain active.