Reference

viabola Privacy Policy For Your Account

Our viabola Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and access the lobby from a phone or desktop.

Account dataWallet referencesDevice accessPolicy requests
viabola viabola Privacy Policy For Your Account
PRIVACY HELP PATH

Get Privacy Help With Account Access

A clear contact route helps when your account record or wallet reference needs attention. We keep privacy questions close to the account support path, so you can identify the relevant login step, receipt or device session without sending unrelated details. Use the available support route shown in your account area and tell us which Privacy Policy request you want handled.

Team online

Account access

If your phone verification or login record looks incorrect, contact us through the account support path and describe the affected step. We use that context to locate the right account record.

Wallet reference

For DANA, OVO, GoPay, QRIS or bank-transfer records, include the payment reference rather than your wallet password. This lets us check the stored cashier entry without requesting unnecessary credentials.

Privacy request

Ask for access, correction or deletion through the available support route. We may ask you to confirm account ownership before changing personal data or releasing a copy of the record.

DATA HANDLING PRACTICE

How We Handle Your Account Data

We describe the practical controls behind this Privacy Policy so you can decide what to share before opening an account.

Account details

We may collect the details needed to create and protect your account, including contact data, phone verification status and sign-in records. We use them to connect your access request with the correct profile.

Payment records

A DANA, OVO, GoPay, QRIS, virtual account or bank-transfer action can leave a reference, amount status and timestamp. We use those records to match cashier activity and investigate a specific account query.

Device sessions

When you move from a mobile browser to desktop, session and security data can help us detect unusual access. We do not need your private device files to keep that session check active.

Cookies

Cookies and similar browser storage can preserve sign-in state, language choice and security preferences. You can manage browser permissions, although changing them may affect account access or require another verification step.

Retention period

We keep account, security and transaction records only for the period needed for the stated purpose, account protection or a valid legal request. When a record is no longer needed, our handling follows deletion procedures.

Changes and contact

If your stored name, phone detail or account contact needs correction, send a request through the available support route. We confirm ownership first, then explain what can be changed under this Privacy Policy.

Privacy Policy Questions About viabola

These answers focus on the account, wallet and device questions you may search before opening access. If your situation is not covered, use the privacy contact route and include only the details needed to identify your request.

The viabola Privacy Policy covers account details, phone verification, device sessions, cookies, wallet references, payment status, security checks, retention and requests to access or correct your stored data.

Phone verification helps connect an account request with the correct person and reduces mistaken access. We record its status for account security, and you can ask support how that record is handled.

Yes. The Privacy Policy includes DANA and QRIS references, along with OVO, GoPay, virtual account and bank-transfer status when those routes are connected with your account.

We may store session, browser and security signals from the mobile or desktop path you use. These signals help identify unusual login activity without giving us access to private files on your device.

You can request a copy through the available account support route. We may confirm account ownership first, then provide the records that can be disclosed under applicable rules and this Privacy Policy.

Send a correction request through the privacy contact path and identify the account field that needs changing. We check ownership before updating contact, verification or wallet-linked details.

We retain records for account security, transaction matching, dispute checks or a valid legal request, then follow deletion procedures when the stated purpose and applicable retention requirement have ended.