Reference

violin88 Privacy Policy And Wallet Data

Our violin88 Privacy Policy explains what we collect when you open an account, verify your phone, sign in from a mobile browser, or use DANA, OVO, GoPay and…

Clear data purposesWallet activity contextPhone verification stepsRequest changes directly
violin88 violin88 Privacy Policy And Wallet Data
HELP WITH REQUESTS

24/7 Support For Privacy Questions

A clear support route helps when you want to ask about your personal data, correct an account detail, or check why a wallet receipt is attached to a record.

Account data request Open support while signed in, identify the phone number on your account, and tell us whether you want a copy, correction, or explanation of stored personal data.
Receipt and status check For DANA, OVO, GoPay or QRIS questions, share the transaction reference and date rather than private wallet credentials; we use those details to trace the related record.
Access support path If mobile login stalls in Bandung or elsewhere in Indonesia, contact support from the available account route so we can separate a device issue from a data request.
DATA CONTROL

Mobile Login Data Under Your Control

Privacy choices should remain understandable when you move from a phone to a desktop. Our policy sets out how account records, cookies, device signals and security events support sign-in and payment checks…

Account records

We use your account details and phone verification status to recognise the correct account during login, support contact and wallet receipt matching. We do not ask for a wallet password.

Device signals

A mobile browser or desktop session may create security signals such as session details and sign-in time. These help us identify unusual access without changing your personal account fields.

Cookies

Cookies can keep a session working and help us understand basic account navigation. Your browser settings can control cookies, although changing them may affect the sign-in path.

Account security

Phone verification and sign-in checks help protect account access. If a security event affects your records, we use the account contact route to ask for the next confirmation.

Retention period

We keep personal data for the period needed for account support, security checks, payment reconciliation or legal duties. The relevant retention reason can be requested through our support path.

Change requests

You can ask us to correct inaccurate details, explain processing, or consider deletion where applicable. Send the request from your signed-in account and we will confirm the required account step.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions you may have before opening an account or contacting us about stored data. We keep the route practical: identify your account, name the record involved, and use the support path for a response. Requests and access remain subject to local law.

It covers account details, phone verification, device signals, cookies, sign-in history, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use the phone number linked to your account for verification, account matching and support checks. It helps us distinguish your request from another account when access or wallet status needs attention.

Yes. A QRIS receipt reference may be stored to match a payment question with the correct account. We need the reference and date, not your QRIS wallet password or unrelated wallet activity.

Sign in through the mobile or desktop account path, open support, and ask for a personal data copy. Include your linked phone number so we can verify the request before responding.

You can request a correction through support. State which account detail is inaccurate and provide the linked phone number; we may ask for an account confirmation before changing the record.

Retention depends on the reason for collection, including account support, security, payment reconciliation and legal duties. Ask support which retention reason applies to the record connected with your account.

Yes. Privacy requests, account access and eligibility depend on local law. Where local law permits, we assess your request through support and explain any account confirmation needed before action.