Reference

viutoto Privacy Policy for Your Account

viutoto Privacy Policy explains what we collect when you open an account, use the mobile lobby, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet detailsCookie choicesRequest access
viutoto viutoto Privacy Policy for Your Account
HELP WITH PRIVACY

Get Clear Answers About Your Data

A direct support route helps you resolve a privacy question without sending sensitive details into a public channel. Start from the account support link, describe the request in plain English, and include only the account reference needed to locate it. We can explain a payment record, login event, cookie choice or correction request while keeping your account credentials out of the conversation.

Team online

Account support path

Use the support link shown after login when you need to ask about account data, a device record or a Privacy Policy request. We may ask for an account reference before discussing details.

Payment privacy check

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, share the transaction reference rather than a wallet password. We use that reference to check status without requesting secret credentials.

Correction request

Tell us which account field or recorded detail needs changing through the support form. We compare the request with your verified account step before applying a correction or explaining why more proof is needed.

DATA CONTROL ROOM

What We Do With Your Privacy Choices

The Privacy Policy is designed around practical account events rather than vague promises. We record the choices needed to operate login, payment status and security checks, then keep access to those records…

Account details

We may use your phone number and verification result to create an account, confirm that an access request belongs to you and send account-related replies. We do not need your wallet password for these checks.

Device signals

A browser or phone can provide login time, session details and security signals. These records help us identify an unfamiliar access attempt, whether you enter through the mobile path or a desktop browser.

Cookie settings

Cookies and similar storage can remember a session, protect sign-in and retain a choice you make on the privacy page. You can manage browser storage through your device settings, though some account steps may then need repeating.

Payment references

A DANA, OVO, GoPay or QRIS reference may be retained to match a cashier status and answer a payment question. Bank transfer and virtual account records are handled for the same account-support purpose.

Retention checks

We keep records for as long as they support the stated account, security, payment or legal purpose. When a record no longer has that purpose, we assess it for deletion or removal from active systems.

Your requests

You can ask for access, correction, deletion or a processing explanation through account support. We verify the request, identify any affected record and tell you if local law requires us to retain part of it.

Privacy Policy Answers Before Access

These Privacy Policy questions cover the account and payment situations you are most likely to meet before opening an account or contacting support. Each answer describes the request path we use, the details that may be needed and the point at which local law affects access or retention.

It covers account details, phone verification, device and session signals, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We may use your phone number to create an account, complete the clear phone verification step before account access and connect a support request to the correct account without asking for a wallet password.

Yes. The Privacy Policy includes session details and security signals from your mobile browser or desktop browser. These records can help us identify an unfamiliar login and protect the account path.

We use payment references to match the account status and answer a receipt or cashier question. We do not need your DANA, OVO, GoPay or QRIS password to check a transaction reference.

Open the account support path and ask for data access, then include the account reference requested during verification. We identify the relevant records and explain any limits that depend on local law.

Yes. Send a correction or deletion request through support with the affected account field or record. We verify ownership, assess retention needs and explain which parts can be changed or removed.

Use the support form linked from your account and describe the concern without sharing login credentials. The same route can handle cookie questions, device records, payment references and access requests.