Reference

arwantoto Privacy Policy: Your Data Path

arwantoto Privacy Policy gives you a clear path through the personal data used when you open an account, verify your phone, sign in on mobile, or check DANA…

DANA recordsPhone verificationCookie choices
arwantoto arwantoto Privacy Policy: Your Data Path
CONTACT ROUTES

Where To Ask About Personal Data

If a Privacy Policy question affects your account, we keep the route close to the sign-in and wallet-status steps. You can use the support contact shown inside your account, include the phone or payment reference involved, and ask for a plain explanation of the relevant data use. We answer policy requests through the same account path used to check a DANA or QRIS status.

Team online

Policy questions

For a Privacy Policy request, use the support contact displayed after sign-in. Tell us which section concerns you and whether you need access, correction, removal, or a reason for a particular data use.

Account access

If phone verification blocks your account, contact us from the sign-in path and include the affected phone number. We use that detail to locate the request without asking you to send a wallet password.

Payment records

For a DANA, OVO, GoPay or QRIS record question, share the payment reference shown in your account. We can direct the request to the status-check path while keeping unrelated account details out of the message.

DATA PRACTICE

Six Data Choices We Keep Clear

The Privacy Policy is designed around actions you can take, not broad wording. It describes the data created during account access, the cookies placed on your device, the checks used to protect…

Data handling

We connect account details, phone verification and sign-in events only to stated operational purposes. Payment references from DANA, OVO, GoPay and QRIS help us match a status without requesting your wallet password.

Cookies

Cookies can keep your account path working between sign-in and the lobby. The Privacy Policy explains their purpose, while your browser settings provide a separate way to remove or restrict them.

Account security

Phone verification helps us distinguish an account access request from an unfamiliar attempt. Never send a password or one-time code through support; our policy explains the safer contact path.

Retention

We retain account and payment records for the period needed for stated account, security and reconciliation purposes. The policy explains how retention applies when an account is closed or a request is made.

Your contact path

You can ask about your personal data through the support contact shown after sign-in. Include the relevant account step, such as phone verification or a QRIS status, so we can locate the right record.

Policy changes

If our data practices change, we update the Privacy Policy and identify the affected section. Check this page before opening an account or returning to the lobby from a mobile device.

Privacy Policy Questions For arwantoto

These answers address the Privacy Policy questions we expect before account opening or a data request. Each response points to a practical account step, payment record or contact route so you know what to prepare when asking us for help.

It covers personal data connected with account opening, phone verification, sign-in, cookies, support requests and payment references. It also explains retention, security measures, data requests and policy changes.

We may collect your phone number, account details, verification result, device and browser signals, sign-in events, support messages and payment references connected with DANA, OVO, GoPay or QRIS.

Phone verification is part of account access, so the policy explains how the result supports sign-in security. If access stalls, contact us through the account path rather than sending a code.

Yes. It explains how payment references and status checks may connect to your account. We use those records for reconciliation and support, not to request or store your wallet password.

Use the support contact shown inside your account and state whether you want access, correction, export or removal of eligible data. Include the relevant account step so we can locate the request.

Retention depends on the purpose for holding a record, such as account security, payment reconciliation or a support request. The Privacy Policy explains the applicable period and what happens after closure.

Access depends on local law. Read the current Privacy Policy before opening an account, and use the support contact shown in your account if you need clarification about an access-related data request.