Reference

Open With A Clear Privacy Policy

Our Privacy Policy explains how velbet collects, uses and protects the details you provide when opening an account, signing in from a phone or checking DANA, OVO, GoPay…

Account dataWallet recordsCookie choicesContact requests

Explore Our Lobby Read FAQ

Explore Privacy Rules For DANA And QRIS

velbet Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy covers information we receive when you create an account, complete phone verification, sign in, contact support or use payment records connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We use those details to open and protect your account, match

1
payment status, investigate a receipt and respond to a privacy request. Device type, browser signals and login time may be recorded to detect unusual access and keep sessions connected to the right account. We do not describe any access or eligibility beyond the rule that it
2
depends on local law. You can ask us what data we hold, request a correction, ask about retention or question a processing purpose through the support route below. The policy applies to account activity on mobile and desktop browsers, including the path from phone verification to
3
the lobby.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

PRIVACY SUPPORT

Switch To Direct Policy Support

A privacy question should not get lost among payment messages, so we keep a direct route for requests about your account data. Tell us which account step raised the concern, such as phone verification, a QRIS receipt or a mobile login, and include only the details needed to locate the record. We use your existing account contact to confirm identity before discussing private data. If you are in Denpasar or elsewhere in Indonesia, access still depends on local law, and our support team can explain the policy path that applies.

Team online

Account request

Use the account support route when you want to see, correct or question personal data linked to your velbet account. Include your registered phone detail and the subject of the request, but do not send a wallet PIN or full payment credential.

Payment record

For a DANA, OVO, GoPay or QRIS privacy question, mention the payment rail and approximate transaction time. We can check the matching status record after confirming that you are the account holder, while keeping sensitive wallet details out of the message.

Security concern

If an unfamiliar device or login appears in your account history, contact support through the account path and describe the device type. We may ask for phone verification before discussing the event or making a change to your account details.

DATA HANDLING

Browse How velbet Handles Account Data

Privacy is managed through specific account steps rather than a vague promise. We separate contact details, login signals and payment references so support can investigate a status issue without asking for unnecessary…

Collection points

We collect details when you open an account, complete phone verification, sign in, use a wallet route or send a support request. The Privacy Policy explains why each collection point exists and how it relates to account access or payment status.

Cookie controls

Cookies and similar browser records can keep a session connected to your account and help us identify unusual device behaviour. You can ask support what cookie category relates to your concern and how a change may affect sign-in.

Account security

Phone verification is used before account access and before certain privacy discussions. We may compare login time, device type and account activity when checking a security concern, without asking you to reveal a wallet PIN or password.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records can show a reference, amount status and timing needed for reconciliation. We use those records to answer a payment question, not to request your private wallet sign-in details.

Retention checks

We keep account, security and payment records for the period needed for the stated purpose, operational checks or legal duties. Ask us which category concerns you and we can explain the applicable retention reason and request path.

Change requests

You can request a correction or ask what personal data is associated with your account through support. We verify the request against your account contact before changing records, so another person cannot redirect or expose your private details.

Check Privacy Policy Answers Before Opening

These Privacy Policy answers address the searches we hear most often before an account is opened. They explain what we collect, why payment references appear, how cookies relate to mobile access and how you can contact us about a correction or deletion request. If your situation is not listed, send the question through account support with the smallest useful set of details.

The Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. It also explains retention, security checks and how you can request access or correction.

We use phone verification to connect account access with the right contact and to reduce the chance of another person discussing private account data. A verification step may also be required before we answer a data request or change account details.

Yes. The Privacy Policy includes references needed to match DANA and QRIS activity with an account, such as payment status, timing and a transaction reference. We do not need your wallet PIN, wallet password or full private wallet credentials for that check.

When you sign in through a mobile browser, we may record device type, browser signals, login time and session events. These details help keep the session connected to your account and help us investigate unfamiliar access. The policy explains the related purpose and retention period.

You can contact account support to ask which personal data is associated with your account and request a copy where local law permits. We confirm your identity using the registered account contact before discussing records, and we may limit a request when a legal duty applies.

Send a correction request through the account support route and identify the field that needs attention, such as a phone detail or contact record. We may ask for phone verification before changing it, then explain whether the update affects account access or payment matching.

Contact us with a clear request about retention or deletion and name the record category, such as a support message, cookie record or QRIS reference. We assess the request under the Privacy Policy and local law, then explain what can be removed, retained or restricted.

Open With A Clear Privacy Policy

Switch To Direct Policy Support

Account request

Payment record

Security concern

Browse How velbet Handles Account Data

Collection points

Cookie controls

Account security

Payment references

Retention checks

Change requests

Check Privacy Policy Answers Before Opening

01 What does the velbet Privacy Policy cover?

02 Why does velbet need phone verification?

03 Does the Privacy Policy include DANA and QRIS data?

04 How does the policy handle mobile device data?

05 Can I ask for a copy of my velbet data?

06 How do I correct inaccurate account information?

07 How can I ask about retention or deletion?

Related Pages