Reference

mawatoto Privacy Policy: Your Account Data Path

Our mawatoto Privacy Policy explains what we collect when you open an account, verify your phone, use DANA or QRIS, and move through the lobby.

Clear data purposesWallet record detailsAccount contact pathCookie choices
mawatoto mawatoto Privacy Policy: Your Account Data Path
CONTACT ROUTES

Get Policy Help Near Your Wallet

A clear contact path matters when your account record or wallet status needs attention. We connect policy questions to the account area, where you can identify the relevant sign-in, payment or verification event. Include the phone used for the account and the payment rail involved, such as OVO or GoPay, so we can locate the correct record without asking you to repeat the full story.

Team online

Account access

Use the account help route when a phone verification record, sign-in event or device detail looks unfamiliar. We use the account step and your submitted contact details to locate the request.

Wallet status

For DANA, QRIS, OVO or GoPay questions, tell us which rail appears in your account and the approximate transaction point. We check the related payment record against your policy request.

Data changes

Ask through the policy contact route when your account details need correction or removal. We may request an account verification step before changing personal data connected with access.

DATA PRACTICE

How We Handle Account Data

We separate account details from the activity needed to operate a secure sign-in and payment path.

Account collection

We collect the details needed for an account path, including your phone verification step and information you submit. We do not need unrelated profile details to explain how your account record is handled.

Payment matching

A DANA, OVO, GoPay or QRIS reference helps us connect a payment status with the correct account. Bank transfer and virtual account records may also remain linked while a status question is being checked.

Cookie use

Cookies can remember browser settings and help keep sign-in actions connected to the right session. Our Privacy Policy explains their purpose, while your browser provides controls for managing stored cookie data.

Account security

Phone verification before account access helps us distinguish your sign-in from an unfamiliar device event. Never send a password or wallet secret through a policy request; we only need enough detail to locate the record.

Retention periods

We keep personal and payment records only for the period needed for account operation, security, dispute handling or legal duties. The relevant period can differ by record type and the status of your account.

Change requests

You can ask who handles your data, what we hold, why it is used, or whether a correction is possible. We may confirm account ownership before responding or applying a requested change.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the account and payment questions you may have before opening an account or returning to the lobby. We keep the wording tied to practical steps, from phone verification to a QRIS record, so you know where to ask for help. Access depends on local law or where local law permits.

The Privacy Policy covers account details, phone verification, device activity, cookies, lobby activity and payment records connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

We use your phone number for the account path and verification before access. It helps connect your sign-in with the correct account and gives us a reference when you ask about account data.

Yes. The Privacy Policy explains how QRIS, DANA, OVO and GoPay references may be used to match payment status with your account and resolve a question about a transaction record.

Use the policy contact route in your account area and state whether you want a data copy, correction or deletion request. We may verify account ownership before handling the request.

Cookies can retain browser settings and connect sign-in actions to an active session. The Privacy Policy describes their purpose, while your browser controls how stored cookie data is managed.

Retention depends on the record, account status and any security, payment or legal need. We keep records for the period needed for those purposes, then handle them under the Privacy Policy.

Yes. Send a request through the policy contact route asking who handles a particular account or payment record. We may limit details where disclosure could affect security or a legal duty.