Reference

peatoto Privacy Policy for Your Account Data

peatoto Privacy Policy explains what we collect when you open an account, how we use login and wallet records, and how you can ask about your data.

Account dataWallet recordsCookie choicesContact route
peatoto peatoto Privacy Policy for Your Account Data
CONTACT PATH

Privacy Help Along Your Wallet Path

A clear contact route helps you raise a privacy question without explaining your whole account history again.

Account privacy request Use the account support route to ask what personal details we hold, why a field is needed, or how to request a correction. Include your registered phone details so we can identify the account safely.
Wallet record question If a DANA, OVO, GoPay or QRIS entry looks unfamiliar, share its visible reference and date through the support path. We use those details to locate the relevant record without asking you to resend a full history.
Access and privacy concern When login or phone verification affects a privacy request, tell us which step stopped you. We may ask for account checks before discussing personal data, helping keep the request tied to the correct account.
DATA PRACTICE

Account Data Controls Inside peatoto

We handle privacy as part of the account path, not as a separate message after a wallet issue. Our process connects account creation, phone verification, device behaviour, payment references and support requests…

What we collect

We may receive the account details you enter, phone verification results, login events, device information, support messages and payment references. We use each category for a stated account, security, service or request-handling purpose.

Cookie choices

Cookies and similar device storage can help retain session choices and understand whether a page loads correctly. Your browser settings provide a way to limit them, although some account steps may then require another sign-in.

Account security

Phone verification and account checks help us avoid discussing private records with the wrong person. If a login looks unusual or a request changes account details, we may ask for an additional ownership check.

Retention approach

We keep account, transaction and support records for as long as they serve the stated service, security, dispute or legal need. When a record is no longer needed, our handling follows the applicable retention process.

Request a change

You can ask us to access, correct or otherwise address personal data through the account support route. Describe the requested change clearly; where local law permits, we will explain the available response and any identity step.

Who to contact

For a Privacy Policy question, contact us through the support path connected to your account rather than sending sensitive wallet details in an open message. We can then match your request to the correct account record.

Privacy Policy Questions Before Account Access

These Privacy Policy answers focus on the questions we expect you to ask before opening an account or checking a wallet record. They cover data collection, cookies, account access, payment references and requests for changes. If your situation is unusual, use the account support path so we can assess the details under the applicable local rules.

The peatoto Privacy Policy covers account details, phone verification, login and device records, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS or bank transfers.

We may collect details you enter during account creation, verification results, login events, device signals, support content and wallet references. We use them for account access, security, service handling and privacy requests.

DANA and QRIS references help us connect a payment status to your account and investigate a receipt question. We do not treat the payment name alone as permission to use unrelated personal data.

Yes. Send a clear correction request through the account support route, identify the affected field and complete any ownership check we request. Where local law permits, we will explain the available next step.

We retain account, transaction and support records while they serve a stated service, security, dispute or legal need. The applicable retention process determines when records can be removed or otherwise handled.

Cookies can preserve session choices and help us understand page loading on your phone. Limiting them in your browser may require another login or affect parts of the account path.

Use the support path linked with your account and state whether you want access, correction or another privacy response. Avoid sending unnecessary wallet details; we may verify ownership before replying.