Reference

Privacy Policy For Your piringtoto Account

piringtoto Privacy Policy explains what we collect when you create an account, sign in from a phone or desktop, use DANA or QRIS, and contact our support team.

Account clarityWallet data contextPolicy accessIndonesia use
piringtoto Privacy Policy For Your piringtoto Account
CONTACT PATH

Privacy Help Beside Account Support

A direct support route matters when a privacy request and an account question arrive together.

Data request Ask our support team what account details we hold, why they are used and…
Correction path If your contact detail or account record is incorrect, request a change through the…
Access concern When a new phone, desktop browser or unusual login affects your account, tell us…
DATA PRACTICE

Inside piringtoto Privacy Controls

We handle Privacy Policy requests as account matters rather than general lobby questions. That means we check the relevant record, explain its purpose and apply changes only after the required ownership check.

Account records

We connect your account identifier with phone verification, sign-in events and support requests so we can recognise the correct record. A request from an unverified contact may need an ownership check before we disclose or change anything tied to your account.

Wallet references

Payment records normally show a method, status, amount reference and matching account detail rather than your wallet password. DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us trace a status without asking you to reveal private wallet credentials.

Device signals

A phone or desktop browser can create session, browser and connection records used to detect unusual access. These signals help us respond when your account opens from a different device, while they do not give us access to unrelated files or contacts on that device.

Cookies

Cookies can keep a signed-in session working, remember a language or display preference and help us diagnose a page error. You can manage browser cookie settings, although removing necessary cookies may require another login or prevent part of the account path from loading.

Retention

We keep personal records for as long as needed for account operation, payment tracing, security checks, disputes and legal duties. When a record no longer serves one of those purposes, we remove it or use a form that no longer directly identifies your account.

Request handling

Send privacy requests through the account help panel and describe the action you need, such as access, correction or deletion. We reply with the next verification step and explain any part we cannot change because retention or account protection still applies.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account details you are most likely to ask about before opening or using piringtoto. We cover phone verification, cookies, local wallets, device records, deletion requests and access checks. If your situation is different, use the support path described above and identify the account without including a password or one-time code.

The piringtoto Privacy Policy covers account creation, phone verification, login activity, device signals, cookies, wallet references and support requests. It explains why we use those records, how long we retain them and how you can ask for access, correction or deletion where local law permits.

Phone verification helps us connect an account to the person requesting access and reduces mistaken or unauthorised changes. We record the verification result and related account event, not your private phone content. A verification check may also apply when you request a data change.

Yes. The Privacy Policy covers payment references linked to DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use method and status details to match a transaction with your account, while wallet passwords and unrelated banking credentials remain outside our account records.

Use the account help panel and request access to your personal data. Include your account identifier and explain the record you want, such as login events, device signals or support history. We first confirm ownership, then describe the available records and any lawful reason for withholding part.

You can request correction of an inaccurate contact or account record, and you can ask whether deletion is available. We may retain records needed for payment tracing, security, disputes or legal duties. Our reply explains what changes, removal or anonymisation can take place.

Cookies can maintain your session, remember a setting and help us diagnose technical errors on mobile or desktop. Browser controls let you remove or restrict them. Necessary cookies may still be required for login, and changing them can make you sign in again or affect page access.

Yes, access and eligibility depends on local law. We may use location or connection signals for regional checks, but those signals do not replace the law that applies to you. If you need clarification about a location-related account record, contact support through the account help panel.